You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In order to facilitate fixed @id for CodeListElements to make them queryable inside LogisticsEvents, I propose to make CodeListElement inherit from LogisticsObject. This allows to host codes as re-usable objects while following the new recommended URI structures.
I think is a good suggestion, we need @id to be able to search with event-code. On the contrary, logistics objects have some properties that we do not need in the codelistelement. Maybe we can instantiate them as logistics objects but we can avoid having all properties. Something to discuss in details
In order to facilitate fixed @id for CodeListElements to make them queryable inside LogisticsEvents, I propose to make CodeListElement inherit from LogisticsObject. This allows to host codes as re-usable objects while following the new recommended URI structures.
Structure:
@id: {{baseURL}}/{{codeListName}}#{{code}}
Example:
https://data_holder.org/logistics-objects/handlingCodes#ABC
The text was updated successfully, but these errors were encountered: