[Task] Besides "see" introduce "sourceOfDefinition" conformant to IEC61360

[BirgitBoss]

Is your task related to a problem? Please describe. There is a "see" attribute with type anyURI for referencing other dictionaires or ontologies. Sometimes, however, it is useful to add just text, e.g. something like "conformant to STEP 1.2" etc.

Describe the solution you'd like add new attrtibute sourceOfDefinition parallel to the see attribute

Describe alternatives you've considered

Additional context source of definition is a standardized field in IEC61360 that is also used as one of the data specification templates in the Asset Administration Shell

[atextor]

What would be the benefit of a separate attribute over including this information in the bamm:description? I.e., for what exactly can this attribute be used if it is only another plain text field?

[atextor]

SDS WG discussion 2022-07-28: ECLASS makes use of this attribute, but not very often. Clarify the origin of semantic of element. Usage in documentation generated for an Aspect Model. bamm:see is already available to refer to elements in other standards (as long as they can be referenced to as URI); having both bamm:see and bamm:sourceOfDefinition might lead to confusion. Is "sourceOfDefinition" a "strong" relation, i.e., there can be only 0 or 1, but not multiple relations (like with see)? Possible (workaround) solution: Don't add sourceOfDefinition attribute, but add a section in the specification that explains how to deal with IEC61360, e.g., use bamm:see when possible and add information in bamm:description otherwise. This solution could be preferrable so that this attribute is not the start with many following that would have to be added.

Bi-directional mapping between Aspect Model and external formalisms can always be done via bamm:see (importing to Aspect Model: add see, exporting from Aspect Model: ignore attribute if not present)

---

Decision: WG agrees: a specification section is appropriate. It has low to medium priority.