The transport ontology defines the transport order that is used for ordering a specific transport service. The transport order specifies the user requirements for transporting a cargo from one place to another. The order consists of a request (TransportRequest class) from the transport user to the transport service provider, and a plan (TransportPlan class) from the transport service provider to the user, which contains the data required by the transport service provider to plan and schedule the transport. This includes elements like locations for loading and unloading, required delivery times, etc. The transport user should also provide specific conditions and requirements for the transport, relating to agreements (e.g. legal conditions) and the cargo itself (e.g. hazardous materials). One transport order can contain multiple consignments. This allows the customer to specify the transport from A to B and Cto D in one integrated transport order.

Prefix

logitrans

Links

Homepage Repository

Pattern for Local Unique Identifiers

Missing LUI pattern

Example Local Unique Identifier

CodeIssuingAgency_GLN   Resolve

Example CURIE

logitrans:CodeIssuingAgency_GLN

Contact

Laura Daniele   0000-0002-9267-7160   danielelm

Identifier Space Owner

Netherlands Organisation for Applied Scientific Research

Contributors

submitter Charles Tapley Hoyt   0000-0003-4423-4370   cthoyt

A provider turns a local unique identifiers from a resource into a URI. Many providers are also resolvable as URLs (i.e., they can be used in a web browser).

The local unique identifier CodeIssuingAgency_GLN is used to demonstrate the providers available for Logistics Transport Ontology. Some providers may use a different example, which is displayed in the table below. A guide for curating additional providers can be found here.