Version 1.0

Release date

2023-12-20

This is the first release containing profiles and transactions to be part of the OpenPeppol Logistics Domain. The content is developed in the Logistics Incubation project with BEAst and Offshore Norge as main contributors.

New BIS documents

  • Advanced Despatch Advice Only 1.2

  • Advanced Despatch Advice with Receipt Advice 1.0

  • Weight Statement 1.2

  • Transport Execution Plan with Request 1.0

  • Transport Execution Plan Only 1.0

  • Waybill 1.0

  • Transportation Status with Request 1.0

  • Transportation Status Only 1.0

New transactions

  • Advanced Despatch Advice 1.2 (T120)

  • Weight Statement 1.2 (T122)

  • Transport Execution Plan Request 1.0 (T123)

  • Transport Execution Plan 1.0 (T124)

  • Waybill 1.0 (T125)

  • Transportation Status Request 1.0 (T126)

  • Transportation Status 1.0 (T127)

  • Receipt Advice 1.0 (T128)

Validation artefacts for each BIS

Rules

For each BIS there are three sets of rules:

Common rules

These are rules that apply to all transaction and address issues such as, there may not be empty elements or that a date must be structure following the YYYY-MM-DD ISO format.

Each common rule has an identifier. As example "PEPPOL-COMMON-R001"

Basic rules

These are rules that are automatically generated based on the syntax datamodel. These include rules on:

  • Cardinality of elements and classes.

  • Allowed fixed values for elements and attributes.

  • Allowed codes in code lists.

Each basic rule has an identifier that include the transaction id and a sequential number starting with a B. As example "PEPPOL-T120-B00101"

Business rules

There are business rules that can not be automatically generated from the data model. These are mainly rules that concern relations between elements, such as:

  • Conditional values (IF-THEN)

  • Calculations of elements.

  • Minimum and maximum values.

  • Dependencies between elements.

Each business rule has an identifier that include the transaction id and a sequential number starting with a R. As example "PEPPOL-T120-R001"

Downloads

These contain two type.

  • Schematron files that can be used for validating a transactions.

    • Schematron files for all transactions are provided in a single zip file.

  • Example files that can be used in tests and as reference in implementations.

    • Example files for all transaction are also provided in a single zip file.

Codes

The documentation includes a listing of all code lists used in one or more transactions. The code lists are fully populated with information on where they are used, what their code values are and their definitions.

When a BIS specification defines how a code is used that definition overrules the general definition in the code list.