liusemweb / ceon Goto Github PK
View Code? Open in Web Editor NEWAn Ontology Network for the Circular Economy Domain
Home Page: http://w3id.org/CEON
License: MIT License
An Ontology Network for the Circular Economy Domain
Home Page: http://w3id.org/CEON
License: MIT License
Can we add more annotation properties to be picked up when generating a module's documentation? For instance I would like to also store the CQs solved by the module in an annotation of the module itself.
Refactor actor ODP v. 0.2 before publishing the next version.
Additionally,
I would clarify in the repository not only the technical documentation, but also documentation on the method:
The module needs documentation of all classes and properties.
There seems to be overlap, or one can be drived from the other? Clarify and potentially refactor.
We need to refactor the current process module into a ProcessODP, covering the general notions of processes, transformation, phases and steps, order, plan and execution. Then add the current process module (with the taxonomy) as the extension of that.
To cover the fact that information is about something, and other relations related to information.
We need to add documentation to the entities (classes, properties etc) in the resource module. Each should have a textual description.
Capabilities of actors are needed for modelling the CVN, hence this needs to be added.
Provide a specialisation of the actors module
Add resource participation pattern to actor ODP (v 0.2)
The documentation is currently based on VocPub, but following the recent changes this may no longer be correct. If this is no longer the case, this should also be reflected on the documentation.
Is there a way to see also imported concepts and relations in a VOWL visualisation? Some of the visualisations are not very clear, due to many things missing (since they are imported things) - any good ideas for improving the visualisations?
Add a quantity module that should provide common classes, properties, and instances for capturing observational data. This is provided primarily through an extension to the qudt ontology. Use-case specific classes, properties, and instances should be defined elsewhere. Final name of the module to be decided.
Is it possible to show the instances of a class as a list (similar to how subclasses are shown now) in the documentation? Some of our concepts contains a set of instances, that constitute a list of known categories, e.g. the set of typical roles involved in a CVN or in relation to a resource in the actor module. It would be nice if these could be visible in the documentation page.
Hi all, I reviewed the repository (state at commit: fd1e850) and have some (small) remarks.
I'm missing an instruction to run/serve/host the generated documentation.
Suggestion:
python -m “http.server” -d ./docs
# navigate to http://localhost:8000/
Participation
Role
This is a small & concise module. LGTM.
I couldn't find ProcessODP on the index page.
In general, there’s no description about the classes, which makes it harder to review.
The specialized Actor module contains more specializations of the Resource class than the Actor classes – perhaps this should be refactored to a specialized Resource module?
Typo "updator". Replace with updater? https://github.com/LiUSemWeb/CEON/blob/develop/ontology/modules/actor/0.1/actor.ttl#L460
Concise & comprehensible module. LGTM.
Although the description of Product states that it is a thing that grows naturally or is produced by some kind or Process, there is no link to a Process (or subclass thereof).
Perhaps this will be taken care of in the additional overarching module that will be introduced?
A concise module.
Although the subclasses of Processes are self-explaining, it would be nice to add a description describing which Actors and Products can be involved with them.
When using the subset of qudt ontology, we should make sure the ontology versions are made explicit, so that we know that the definitions used are in synch with the published versions. This probably means that the current qudt.ttl
file needs to be split into multiple parts.
Currently, we only publish ontologies represented in Turtle syntax. We should add support for all the common RDF syntaxes.
There was initially a resource module, but it has now been replaced by the resource ODP, and that is directly used by the material and product modules (should be the case, we should check). However, the old resource module is still there on the CEON frontpage etc. Should be removed.
There are some wrong and outdated namespaces in some of the ontology files:
acctor.ttl
actorODP.ttl
process.ttl
WE should include the location of things, by referring to WGS84 (W3C standard vocab) and GeoSPARQL standard. This should be included through at least one property in both the actor module (or ODP?) and the resources module (or ODP?)
both ODPs have process concepts with different URIs.
Ontologies under development should be published (but not indexed or documentation generated) on the CEON pages, i.e., the develop
branch ontologies should simply be copied over into docs/
in the main
branch every time something is pushed to develop
.
Create a "stub" for the value module that the CVN module can refer to. we will not model details at this point, but the "empty" module should be there.
Move them to the actor module.
We need comments/definitions in natural language of each entity (class, property etc) of these modules. And were possible we could already add "non-logical" alignments, by referring to for instance EMMO concepts using seeAlso
The textile ontology is missing a few documentation properties. E.g.:
<..>
dcterms:creator "Eva Blomqvist" ;
dcterms:contributor "Robin Keskisärkkä" ,
"Huanyu Li" ,
"Mikael Lindecrantz" ;
dcterms:created "2024-01-18"^^xsd:string ;
dcterms:description "Textile Use-Case Ontology" ;
dcterms:license "https://creativecommons.org/licenses/by/4.0/"^^xsd:string ;
dcterms:title "Circular Economy Ontology Network (CEON) - Textile Ontology"^^xsd:string ;
vann:preferredNamespacePrefix "textile"^^xsd:string ;
vann:preferredNamespaceUri "http://w3id.org/CEON/ontology/textile/"^^xsd:string ;
rdfs:seeAlso <https://github.com/LiUSemWeb/CEON> ;
owl:versionInfo "0.1" .
The base should probably updated to the ontology prefix:
@base <http://www.semanticweb.org/evabl45/ontologies/2023/8/untitled-ontology-98/> .
Finally, pylode
has problems properly splitting URI:s where last part of the name is not a proper qualified name (https://www.w3.org/TR/rdf-syntax-grammar/#section-Serialising), i.e., where it starts with a numer. For example, http://w3id.org/CEON/ontology/textile/75to95Perc
could perhaps be renamed as http://w3id.org/CEON/ontology/textile/_75to95Perc
or similar?
The current structure of config.yml
is not very suitable for managing multiple ontology versions, since there is both a lot of redundancy and it's difficult to get a good overview. A better alternative would be to use a nested structure where only the version numbers are updated. E.g.:
ontologies:
actor:
source: "ontology/modules/actor/"
target: "ontology/actor/"
versions:
- 0.1
- 0.2
actorODP:
source: "ontology/modules/actorODP"
target: "ontology/actorODP/"
versions:
- 0.1
- 0.2
Does this work as expected? If I enter the URI of an ontology I was expecting to get to the documentation page, but I end up in the github repository page instead.
Create a module that integrates the whole network, for the convenience of the user.
Shouldn't the Constituent be the superclass of both these classes, in their respective modules?
Sometimes the pages have a long thing with "...(CEON)" before the module name, and sometimes only the module name. Unclear to me why this is the case, should be uniform.
Is it possible to do something with the front page of the network, i.e. w3id.org/CEON to have more information there, and not only the generated index of the modules?
A declarative, efficient, and flexible JavaScript library for building user interfaces.
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
An Open Source Machine Learning Framework for Everyone
The Web framework for perfectionists with deadlines.
A PHP framework for web artisans
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
Some thing interesting about web. New door for the world.
A server is a program made to process requests and deliver data to clients.
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
Some thing interesting about visualization, use data art
Some thing interesting about game, make everyone happy.
We are working to build community through open source technology. NB: members must have two-factor auth.
Open source projects and samples from Microsoft.
Google ❤️ Open Source for everyone.
Alibaba Open Source for everyone
Data-Driven Documents codes.
China tencent open source team.