eCatalogue meeting

Date: 28/07/2022
Participants: Cecile Guasch, Veit Jahns, Natalie Muric, Giovanni Paolo Sellitto
Model editor: Eugeniu Costetchi
Note editor: Andreea Pasăre

Discussion

  • Should each module keep his own module? For example:

    • ePO (core) 3.0.0

    • eCatalogue 1.0.0

  • Or include the modules in the ePO core release? For example:

    • ePO (core) 3.0.0 - July publication

      • eCatalogue

    • ePO (core) 3.1.0 - December publication

      • eCatalogue

      • eOrdering

  • And if we do a major release on ePO core the version should be ePO (core) 4.0.0.

  • Predicate epo:attestedByLabel:

    • Predicate “epo:attestedByLabel” might need to be changed since a Label does not always need to be attested by a Certificate.

    • A certificate is between two parties and the label exists for a third party.

    • To get a label you can have different certificates for obtaining it.

    • Proposing to change the definition of the predicate as well since it is not clear what it means.

    • The Item Certificate may not relate to a label. (GH 359)

    • Labels do not always exist. Not all certificates have a label.

    • Changing cardinality from 1 to 0..1

    • But if we do not have a label it is useless to have a certificate.

    • If this relation is instantiated it must have a label.

    • For other use cases on the certification label, github issues should be opened. === Missing definitions

  • Add missing definitions for the following attributes:

    • epo-cat:hasAttributeType _“The property defined in a classification scheme. _

Additional Information:
For example, the following two properties are defined in the ECLASS classification of goods and services: (0173-1#02-AAA026#007) drilling diameter: drilling diameter, (0173-1#02-AAA030#007) flange diameter: flange diameter .

WG approval 28/07/2022”

  • epo-cat:hasClassificationScheme _“The classification scheme where a property is defined. _

Additional Information:
For example, the following two properties are defined in the ECLASS classification of goods and services: (0173-1#02-AAA026#007) drilling diameter: drilling diameter, (0173-1#02-AAA030#007) flange diameter: flange diameter .

WG approval 28/07/2022 ”

  • epo-cat:hasLiteralValue “Simple value of the property, which is defined in a classification scheme.

Additional Information:
_For example, the (0173-1#02-AAV139#001) coating 1 of an optical material has value of "silver". _

_This simple literal value is for the cases when the property value does not have units, in which case the qualifiedValue shall be used. _

WG approval 28/07/2022”

  • epo:attestedByLabel “Relation indicating to which label the certification is about.

WG approval 28/07/2022”

  • More predicate definitions to be added after release.

Discuss GH 138

  • This will be handled in the next iteration of eCatalogue modelling, after the ePO 3.0.0 release.

  • Might take efforts of half a year of biweekly meetings. Possibly doable by December.

Discuss GH 359

  • Is to be included in the next release.

  • For this release we have implemented GH 343.

Development page - ePO 3.0.0

  • Similar organisation to 2.0.1

  • One Glossary per each module

  • Option 1:

    • Conceptual Model

      • ePO core

      • eCatalogue

    • Glossary

      • ePO core

      • eCatalogue

  • Option 2:

    • ePO core:

      • Conceptual Model

      • Glossary

    • eCatalogue

      • Conceptual Model

      • Glossary

  • Note that it is impossible to use eCatalogue without ePO core.

  • Take into consideration how we can make sure that we do not duplicate relations in all glossaries.

  • Might need to include ePO core glossary in all the other modules glossaries.

  • Maybe we can do a single glossary.

  • Include the documentation for the OWL files. === Decisions

  • Renaming the meeting series from eCatalogue to eOrdering.

  • Versioning ePO releases as presented in the Discussion section:

    • Include the modules in the ePO core release? For example:

      • ePO (core) 3.0.0 - July publication

        • eCatalogue

      • ePO (core) 3.1.0 - December publication

        • eCatalogue

        • eOrdering

    • For major release on ePO core:

      • ePO (core) 4.0.0

  • Find a way to show the cardinality of attributes when it is 1.

dn8pPniFQlQAAAABJRU5ErkJggg==
  • Try exporting more modules (root nodes) from EA as one single xml file for the RDF representation toolchain.

  • Submitted new GH issue 360 for more requirements on the glossary.

  • Submitted new GH issue 104 for generating the documentation in a similar style to LODE/W3C/SEMIC.

  • Development page should be structured as follows:

    • Conceptual Model

      • ePO core

      • eCatalogue

    • Glossary

      • ePO core

      • eCatalogue

  • The Notice concept should be outside of the ePO core. Investigate how to do this for a future release. (GH issue 361 for december release)