BirgitBoss
commented
3 weeks ago 2024-10-30 TF AAS Metamodel
Decision Proposal
- use same terms for reference and semanticId matching: either Equivalence or Exact Matching. Proopsal: use exact match
- reformulate exact matching for semanticId with
• With exact matching,the references of the two semantic IDs need to exact match as described in Clause "Matching Strategy for References". Example: ExternalRef0173-1#02-BAA120#008 is not an exact match to ModelRef0173-1#02-BAA120#008 but only a value match
Additionally introduce value match for semanticId with Example ExternalRef0173-1#02-BAA120#008 is a value match to ModelRef0173-1#02-BAA120#008
Correct
Examples for non-matching external references[[5](https://admin-shell-io.github.io/aas-specs-antora/IDTA-01001/v3.1/general.html#_footnotedef_5)]:
(GlobalReference)0173-1#01-ADS698#010, (GlobalReference)0173-1#01-ADS700#010
matches
(GlobalReference)0173-1#01-ADS698#010, (FragmentReference)0173-1#01-ADS700#010to
Examples for non-matching external references[[5](https://admin-shell-io.github.io/aas-specs-antora/IDTA-01001/v3.1/general.html#_footnotedef_5)]:
(GlobalReference)0173-1#01-ADS698#010, (GlobalReference)0173-1#01-ADS700#010
is no exact match to
(GlobalReference)0173-1#01-ADS698#010, (FragmentReference)0173-1#01-ADS700#010
Is your feature request related to a problem? Please describe. There are different matching strategies described for semantic IDs. What is not clear from the example is whether the key.type should be considered or not in exact matching etc. (see chapter on reference matching: these two matching strategies need to be combined).