Niclas Scheiber
Niclas Scheiber
Hello, thanks for both of your input! @gxclark: I am looking forward to hearing about your models, but a major rework of the TransportMovement and/or the way Activities are modelled...
> Hello @NiclasScheiber : yes, I understand the situation, if it is implemented, then there are less opportunities to change it. This is normal as a system matures. Also, if...
Hi @gxclark, this is indeed some imprecision in wording. Generally speaking, we consider cargo:Loading to be the LogisticsAction describing „attaching“ OR detaching“ a number of PhysicalLogisticsObjects to a TransportMovement. The...
This is correct, yes!
The issue and the proposed solutions are reasonable. I support handling the issue as suggested by @ddoeppner, using the existing vocabulary of the api ontology - https://onerecord.iata.org/ns/api#hasRevision - https://onerecord.iata.org/ns/api#hasLatestRevision I...
Unsure about filtering **LogisticsEvents** being defined in API specs and handled server-side. Filters are set based on business requirements by the client. So they should compute the filter query on...
Adding another thought: Changing the filter parameter from `string` to `IRI` would also work, as it is highly encouraged to link pre-existing code lists instead of instancing CodeListElements in LogisticsEvents....