Tasks/Actions for the next version of CEON

[huanyu-li]

0. Structure (dependencies) of CEON

dependency diagram(dashed arrows are reusing concepts by stating URIs, solid arrows are direct imports)

1. Overall issues to keep in mind when updating the ontology

• Naming convention for classes and properties #201
• Provide better descriptions for abstract concepts #205

2. General tasks

• ontology requirements for the 3rd iteration (to updated if needed, based on D2.3)
• Check compliance of ontology with ISO standard #236
• alignment between CEON and ISO 59004:2024 at vocabulary level #278
• alignment work between CEON and top-level ontologies (e.g., EMMO) and other surveyed ontologies #277
• PCDS, it could be similar as we introduced the quantity module in CEON.
• Draft some examples from existing Value Ascription Ontology and Value Proposition Ontology, them discuss with WP4.

3. Identified modelling issues (both before and after 2nd evaluation)

3.1. resourceODP (v0.3 created after 2nd evaluation)

• Clarify Composition vs ResourceParticipation #154, we can remove Composition concept since it is captured by ResourceParticipation

3.2. actorODP and actor (v0.3 created after 2nd evaluation)

• Collaboration in actorODP has cvn prefix. #301
• Refactor ODPs e.g., actorODP and resourceODP #151
• clarify the relation between actorODP:Role and prov:Role #170, I added an Infrastructure concept in actorODP v0.3 to cover some collaboration participation may beed hardware/software or energy infrastructures. In this case we need to include that entities playing roles (like prov).
• Detailed modelling of roles #190
• There is no Manufacturing resource relation #242 in actor module
• ProcessParticipation in actor 0.2 has ActorCVNRole as participantRole. It should be ActorProcessRole instead of ActorCVNRole.
• neededResourceRelation does not have a range definition. It should be ResourceRelation?
• capabilityExtent is not clear.

3.3. processODP and process (processODP 0.3 and process 0.3 were created after 2nd evaluation)

• processODP has actorODP:participationIn object property which is not in use. (It is removed.)
• The domain of hasInput and hasOutput is Transformation. In general it could be Process.
• Process and ProcessExecution need clarification.
• initialSituation and resultingSituation have different domains (i.e., Transformation and Process). Both are changed to ProcessExecution now.
• occursAtTime and occursAtLocation have different domains (i.e., Process and ProcessExecution). Both are changed to ProcessExecution now.
• Situation pattern usage in processODP #302
• Potentially remove transformation from ProcessODP #309
• Cathalyst to Catalyst
• Reuse the new defined Energy concept in Energy module.
• process module defines three sub-concepts of Resource i.e., Catalyst, CO2Emission and Energy where the intention is they can be inputs or outputs of some transformations. The question is whether they should be captured in the resourceODP module or a new resource module. This modelling looks OK if we consider some resources are specifically associated with processes.
• The object property resultingProduct has Resource as range. It could be specified as Product. Change the name to resultingResource.

3.4. product (v0.3 created before 2nd evaluation)

• add some concrete examples illustrating the use of the product module #212
• Product, item and batch naming #235
• Resource vs Product #237
• The model of Product (or ProductModel) and ProductObject is not completely clear. double check when looking ISO standards about product related terms.

3.5. value and cvn modules

• property ex:hasReusePotential in the Construction demo #245, we need to see if this needs to be captured in value or cvn module
• cvn module report from evaluation #179, this is the evaluation result from 1st evaluation including OOPS!, FOOPS! and SPARQL verification

3.6. location module

• Include location of resources and actors #98, a location module v0.1 was added, but we may need more concepts and/or relationships for it

3.7. quantity module

• Double property for hasDismantlingCost, both in CEON quantity and construction ontology #244

3.8. Data sheet module

• Data sheet module use case evaluation report #191

3.9. construction

• add reification classes to construction use-case module #172
• add example to construction use-case module #174
• A number of data properties of which domains are Product and/or ProductObject could be moved to product module. For instance, hasProductDescription, hasProductionDate.
• Contaminant concept and isContaminated data property could be generalised and thus moved to product module or ...
• ProductQuality also seems to be a general concept that can be moved to product module, then in specific demo ontology, one can create sub concepts such as ConstructionProductQuality .
• TreatmentPolicy and PolicyOnTreatment are overlapped.

3.10. electronics

• batchNumber data property can be moved to resourceODP.
• Some data properties of processes can be moved to process module. For instance, dateOfProduction, dateOfInstallation, instructionOfMaintenance, instructionOfRepair, instructionOfUseAndAssembly.
• Some data properties of location can be moved to a general location module.
• Detailed compliance can be moved to product module. For instance REACHCompliance (also modelled in Textile).

3.11. textile

• Check textile module with respect to examples and new versions of other modules #160
• Minor fixes to textile ontology #164
• Print is a sub-concept of Constituent. PrintStuff is a sub-concept of Matter.
• The hasProperty object property has DataSheet as domain and Statement as range. It also has sub-properties but have specific ranges which do not seem to be statements. For instance, hasWaterProperty has WaterProperty as range.

4. CE CQ verification

• CE CQ verification report from the 2nd evaluation #273

5. Construction, Textiles, Electronics CQ verification

• Textile CQ verification report from the 2nd evaluation #276
• Minor fixes to textile ontology #164, seems solved, but may be not merged to develop/main branches
• Construction CQ verification report from the 2nd evaluation #274
• Electronics CQ verification report from the 2nd evaluation #275

6. Issues from OOPS! and FOOPS! evaluation

• resourceODP module report from the 2nd evaluation #259
• processODP module report from the 2nd evaluation #260
• actorODP module report from the 2nd evaluation #261
• process module report from the 2nd evaluation #262
• actor module report from the 2nd evaluation #263
• material module report from the 2nd evaluation #264
• product module report from the 2nd evaluation #265
• cvn module report from the 2nd evaluation  #266
• value module report from the 2nd evaluation #267
• bot module report from the 2nd evaluation #268
• datasheet module report from the 2nd evaluation #269
• provenance module report from the 2nd evaluation #270
• quantity module report from the 2nd evaluation #271
• qudt module report from the 2nd evaluation #272

7. Other Issues to address later

• Summarised technical points to do in the next release #279
• Integration modules #56, a module integrates the whole network
• add ontology/module category #231