-
Notifications
You must be signed in to change notification settings - Fork 53
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
DM: Refactor core code list ontology URIs to adhere to linked data best practices #268
Labels
Comments
I am fine with the renaming but we need to have full approval |
nscheiber-champ
added a commit
to nscheiber-champ/ONE-Record
that referenced
this issue
Nov 26, 2024
- Added new code-lists ontology (IATA-Cargo#268) - Deprecated coreCodeLists ontology (IATA-Cargo#268) - Added new code list DensityGroupCodes (IATA-Cargo#248) - Added property densityGroupCode to BookingShipment (IATA-Cargo#230)
nscheiber-champ
added a commit
to nscheiber-champ/ONE-Record
that referenced
this issue
Nov 27, 2024
- Mirrored DGR and Security Status Codes to the Special Handling Codes namespace for simplification as part of code list review (IATA-Cargo#268) - Fixed remaining EquivalentTo statements
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
With the new recommended URI structure for code lists to enable querying ( #256 ), the fragments after the # of the URIs in the core code lists are too long.
Structure:
@id: {{baseURL}}/{{codeListName}}#{{code}}
UNCEFACT (Example):
@id: https://vocabulary.uncefact.org/UnitMeasureCode#10
CoreCodeLists (Unpractical):
https://onerecord.iata.org/ns/coreCodeLists#RadioactiveMaterialClassification_SPECIAL_FORM
To mitigate, and to not put current implementations in trouble, I suggest to deprecate the whole coreCodeLists ontology and re-publish existing and publish all new code lists in a new Ontology, e.g. https://onerecord.iata.org/ns/code-lists
Code-Lists (New):
https://onerecord.iata.org/ns/code-lists/RadioactiveMaterialClassification#SPECIAL_FORM
The text was updated successfully, but these errors were encountered: