Niclas Scheiber

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).

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...

Another possibility would be to declare in the ontology that both IATA codes and the ones provided by UNCEFACT are valid, but for an Air Waybill, the ones from IATA...

Thanks for the feedback, I suggest to discuss this in the next DMWG call as a proposal. While modelling as multiple TMs is possible today, my rationale for this simplification...

@gxclark: Thanks for this very good input! Let me clarify: “TransportLegs“ is a nested object to transmit specific flights inside the booking process - so just a structural object (exactly...

Regarding GLEC, I agree that it is possible to derive TCEs from an ONE Record TransportMovement in principle. But it will get messy if goods are dropped off at various...

This is currently not possible, since a TransportMeans can only be connected to just one TransportMovement at a time. We would have to lift that restriction then?

But isn't that overlapping modelling approach opening a back door for poor data quality? And compromising on the Single Source of Truth? Lifting this restriction would make the creation for...

Thanks for the input! Given the scenario of a truck from HAM to BRU, dropping off freight at GHA_BRU1 and GHA_BRU2. How would you model this currently? Just to be...

Hello, great idea. The main modelling language OWL, formalized as ontology. But for the visualization, we could do better. Mind opening an issue for this? @gxclark: Alignment with GLEC is...