Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Matching Strategies semantic IDs etc. #471

Open
BirgitBoss opened this issue Oct 7, 2024 · 2 comments
Open

Matching Strategies semantic IDs etc. #471

BirgitBoss opened this issue Oct 7, 2024 · 2 comments
Labels
accepted accepted in principle to be fixed documentation Improvements or additions to documentation

Comments

@BirgitBoss
Copy link
Collaborator

Is your feature request related to a problem? Please describe.
There are different ways to express IRDI or an IRDI as an URI.
E.g. in ECLASS

· https://api.eclass-cdp.com/0173-1-02-AAC895-008
o ECLASS offers a webservice where the information can be retrieved
· 0173-1#02-AAC895#008
o Direct IRDI that can be used in context of an existing ECLASS dictionary

In IEC CDD

0112/2///61360_4#AAA000#001

Describe the solution you'd like

https://api.eclass-cdp.com/0173-1-02-AAC895-008
matches 0173-1#02-AAC895#008
matches 0173/1///02#AAC895#008
@BirgitBoss BirgitBoss added documentation Improvements or additions to documentation requires workstream approval strategic decision proposal needs to be prepared in TF spec team labels Oct 7, 2024
@BirgitBoss
Copy link
Collaborator Author

2024-10-30 TF AAS Metamodel
Decision Proposal:
add new group Consider different syntax

With intelligent matching, different syntax of the same identifier is considered. For example ECLASS allows to ways of referencing: via IRDI or via URL. Another example is the different delimiters used in ECLASS and IEC CDD within an IRDI.

Example:
https://api.eclass-cdp.com/0173-1-02-AAC895-008
matches 0173-1#02-AAC895#008
matches 0173/1///02#AAC895#008

@BirgitBoss BirgitBoss added ready for approval TF proposes how to resolve the issue. Needs final approval my Workstream and removed requires workstream approval strategic decision proposal needs to be prepared in TF spec team labels Oct 30, 2024
@BirgitBoss BirgitBoss mentioned this issue Oct 30, 2024
Closed
BirgitBoss added a commit that referenced this issue Oct 31, 2024
@BirgitBoss
closes #471 different syntax intelligent matching
ac3579d
@BirgitBoss BirgitBoss added accepted accepted in principle to be fixed and removed ready for approval TF proposes how to resolve the issue. Needs final approval my Workstream labels Nov 14, 2024
@BirgitBoss
Copy link
Collaborator Author

2024-11-14 Workstream AAS
Decision Proposal accepted: #471 (comment)

@seicke seicke mentioned this issue Nov 15, 2024
Merged
@BirgitBoss BirgitBoss mentioned this issue Nov 18, 2024
Open
BirgitBoss added a commit that referenced this issue Dec 13, 2024
@BirgitBoss @s-heppner
fix or improve explanation for References and Semantics (#482)
e098147 
* fix formatting

* #480 add example with referredSemanticId

* extension of #480: added invalid examples for all constraints for References

* closes #471 different syntax intelligent matching

* closes #473 Matching semanticId
value-match and exact match

* closes #479 supplementalSemanticId and isCaseOf

* see #479 now isCaseOf included in strategy

* add note that implementations may differ

Co-authored-by: s-heppner <[email protected]>

* grammar

* fix typo

Co-authored-by: s-heppner <[email protected]>

* exact match for semanticIc
+ formatting

---------

Co-authored-by: s-heppner <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
accepted accepted in principle to be fixed documentation Improvements or additions to documentation
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@BirgitBoss