liusemweb / ceon Goto Github PK

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.

Models the Circular Value Network (CVN) itself. Everything connects to the CVN module.
The CVN requires, e.g., a distinction between: plans vs. the execution of plans or "CSV" blueprint vs CVN configuration.

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.

Additionally,

I would clarify in the repository not only the technical documentation, but also documentation on the method:

• Link to the ontology design method
• Link to the alignment between the devised ontology and the use case requirements that lead to specific classes/attributes/constraints. This also gives a hint at the completeness of the ontology with respect to the requirements.

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.

We need to add documentation to the entities (classes, properties etc) in the resource module. Each should have a textual description.

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?)

Currently, we only publish ontologies represented in Turtle syntax. We should add support for all the common RDF syntaxes.

Provide a specialisation of the actors module

Capabilities of actors are needed for modelling the CVN, hence this needs to be added.

Create a module that integrates the whole network, for the convenience of the user.

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.

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.

Shouldn't the Constituent be the superclass of both these classes, in their respective modules?

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

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.

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

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?

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.

The module needs documentation of all classes and properties.

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.

There are some wrong and outdated namespaces in some of the ontology files:

acctor.ttl

• http://w3id.org/CEON/ontology-network/cvn/CVN
• http://w3id.org/CEON/ontology-network/cvn/Collaboration
• http://w3id.org/CEON/ontology/actor//[...] (double slash)

actorODP.ttl

• http://w3id.org/CEON/ontology-network/cvn/Collaboration
• http://w3id.org/CEON/ontology-network/process/Process
• http://w3id.org/CEON/ontology-network/resource/Resource
• http://w3id.org/CEON/ontology/actorODP//[...] (double slash)

process.ttl

• http://w3id.org/CEON/ontology-network/Process#
• http://w3id.org/CEON/ontology-network/Core#[...]

Hi all, I reviewed the repository (state at commit: fd1e850) and have some (small) remarks.

Setup

I'm missing an instruction to run/serve/host the generated documentation.
Suggestion:

python -m “http.server” -d ./docs 
# navigate to http://localhost:8000/

ActorODP

Participation

• Typo “har participating actor”, see https://github.com/LiUSemWeb/CEON/blob/develop/ontology/modules/actorODP/0.1/actorODP.ttl#L87

Role

• Typo “specfic”, see https://github.com/LiUSemWeb/CEON/blob/develop/ontology/modules/actorODP/0.1/actorODP.ttl#L213

ResourceODP

This is a small & concise module. LGTM.

ProcessODP

I couldn't find ProcessODP on the index page.

Actor

• 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

Material

Concise & comprehensible module. LGTM.

Product

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?

Process

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.

Move them to the actor module.

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?