closes #376

closes #396
semantic identifier for semanticId, valueId, isCaseOf
no recommendation any longer to use external references

documentation/IDTA-01001/modules/ROOT/pages/changelog.adoc

@@ -75,7 +75,7 @@ Major Changes:
 Minor Changes:
 
 * explanation of ValueOnly-Normal round-trip issues (https://github.com/admin-shell-io/aas-specs/issues/364[#364])
-* improve explanation for recommendation to use external references for semanticId (https://github.com/admin-shell-io/aas-specs/issues/376[#376]) and related attributes like valueId and isCaseOf (https://github.com/admin-shell-io/aas-specs/issues/396[#396])
+* remove recommendation to use external reference for semanticId (https://github.com/admin-shell-io/aas-specs/issues/376[#376]) and related attributes like valueId and isCaseOf (https://github.com/admin-shell-io/aas-specs/issues/396[#396])
 * update information on OPC UA mapping (https://github.com/admin-shell-io/aas-specs/issues/373[#373])
 * update information on AutomationML mapping (https://github.com/admin-shell-io/aas-specs/issues/397[#397])
 * update bibliography (newer versions, link update, removal of entries not referenced)

documentation/IDTA-01001/modules/ROOT/pages/spec-metamodel/common.adoc

@@ -327,14 +327,6 @@ a|
 Identifier of the semantic definition of the element called semantic ID or also main semantic ID of the element
 
 
-====
-Note: it is recommended to use an external reference, (e.g. referencing a globally resolvable semantic definition).
-This is even recommended in the case a xref:spec-metamodel/concept-description.adoc#ConceptDescription[ConceptDescription] exists.
-Otherwise, lookup of the corresponding concept description may fail.
-
-In future releases a constraint may be added that makes it mandatory to use external references.
-
-====
 
 
 |xref:spec-metamodel/referencing.adoc#Reference[Reference] |0..1
@@ -344,14 +336,7 @@ a|
 Identifier of a supplemental semantic definition of the element called supplemental semantic ID of the element
 
 
-====
-Note: it is recommended to use an external reference, (e.g. referencing a globally resolvable semantic definition).
-This is even recommended in the case a xref:spec-metamodel/concept-description.adoc#ConceptDescription[ConceptDescription] exists.
-Otherwise, lookup of the corresponding concept description may fail.
-
-In future releases a constraint may be added that makes it mandatory to use external references.
 
-====
 
 
 |xref:spec-metamodel/referencing.adoc#Reference[Reference] |0..*
@@ -513,9 +498,7 @@ a|
 Reference to the global unique ID of a coded value
 
 
-====
-Note: it is recommended to use an external reference.
-====
+
 
 
 |xref:spec-metamodel/referencing.adoc#Reference[Reference] |0..1

documentation/IDTA-01001/modules/ROOT/pages/spec-metamodel/concept-description.adoc

@@ -38,11 +38,6 @@ a|
 Reference to an external definition the concept is compatible to or was derived from
 
 
-====
-Note 1: it is recommended to use an external reference, i.e. _Reference/type = ExternalReference_, compare to xref:spec-metamodel/common.adoc#HasSemantics[HasSemantics/semanticId]
-====
-
-
 
 ====
 Note 2: compare with is-case-of relationship in ISO 13584-32 (xref:bibliography.adoc#bib26[[26\]]) & IEC EN 61360 (xref:bibliography.adoc#bib25[[25\]])

documentation/IDTA-01001/modules/ROOT/pages/spec-metamodel/submodel-elements.adoc

@@ -545,10 +545,6 @@ a|
 Reference to the global unique ID of a coded value.
 
 
-====
-Note: it is recommended to use an external reference, compare to xref:spec-metamodel/common.adoc#HasSemantics[HasSemantics/semanticId]
-====
-
 
 |xref:spec-metamodel/referencing.adoc#Reference[Reference] |0..1
 |===