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.

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

Identifier and Identifier System discussion on UNTP Github #50

Open
jgmikael opened this issue Oct 2, 2024 · 0 comments
Open

Identifier and Identifier System discussion on UNTP Github #50

jgmikael opened this issue Oct 2, 2024 · 0 comments

Comments

@jgmikael
Copy link

jgmikael commented Oct 2, 2024

Would be interesting to hear your opinion on this:
uncefact/spec-untp#137

The conclusion of the discussion is:

"I think the outcome of all this is

  • Identifier and IdentifierScheme should be different node objects - this is now the case.
  • Implementers should not assume that multiple identifiers listed for a given product/facility/organisation are semantically identical. AlsoKnownAs is not the same as owl:sameAs."

It's been really hard to try to defend the adms:identifier approach in a number of data modeling contexts. People simply want to state that an "Entity has an ID" - and if there are several IDs then the Entity has properties like "thisID" and "thatID" and "anotherID" etc. Sic!

Now I'm getting even more confused since this discussion seems to separate the Identifier-class into a Identifier -class and Identifier System -class.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant