IATA-Cargo
Bad IRIs
Hi IATA,
There seems to be a bug on how your LD term definitions are hosted.
Example:
https://onerecord.iata.org/Carrier#airlineCode
is clearly the correct IRI, but doesn't resolve.
The links on https://onerecord.iata.org/cargo points to
https://onerecord.iata.org/cargo#Carrier#airlineCode
This resolves, but is misaligned with the stated IRI. The double-fragments (#) also very much looks like a mistake.
Hi IATA, any updates on this? This bug is causing confusion, the IRI not resolving to its documentation.
Also, ultimately you'll have users choosing differently (some https://onerecord.iata.org/cargo/Carrier#airlineCode others https://onerecord.iata.org/cargo#Carrier#airlineCode), which is certainly the opposite of what an authoritative vocab is all about.
When you dereference https://onerecord.iata.org/Carrier#airlineCode, the client asks the server for https://onerecord.iata.org/Carrier, which apparently doesn't exist; in whatever it gets back, the client looks for id=airlineCode or id=https://onerecord.iata.org/Carrier#airlineCode.
When you dereference https://onerecord.iata.org#Carrier#airlineCode, the client asks the server for https://onerecord.iata.org, which does exist; in whatever it gets back, the client looks for id=Carrier#airlineCode or id=airlineCode or id=https://onerecord.iata.org#Carrier#airlineCode.
The IRIs have all been adapted in the latest release of data model 3.0.0: https://onerecord.iata.org/cargo
No more double fragments, and should be resolvable (as html).
I see the model has been updated, but there's still something weird on the hosting.
The links on the page point to e.g. https://onerecord.iata.org/cargo#Booking#carrier, which also resolves
However, https://onerecord.iata.org/cargo/Booking#carrier does not resolve to anything.
Excuse the confusion, we changed the whole namespace:
https://onerecord.iata.org/ns/cargo
Note the /ns/
Also no more domain names in the properties. This should resolve more or less correctly, although Widoco still causes some issues.
The namespace has been moved to https://onerecord.iata.org/ns/cargo. I am going to close this issue but in case something is not working feel free to open a new one.
Best, Davide
Confirming https://onerecord.iata.org/ns/cargo#Carrier resolving nicely. Well done!