This specification is intended for readers with relevant prior knowledge (refer to dependence on other specifications). Addressed here, firstly, are decision-makers who want to estimate the effort required to implement this specification and, secondly, developers who implement such an interface. General explanations regarding Veloconnect therefore do not need to be repeated here; they can be found at the website.
Readers desiring quick reference can have a look at the examples and refer to details wherever necessary.
A section at the end of this document (changes / new features) provides an overview of the changes compared to the previous version 1.1; version jump from 1.1 to 1.3 explains why version 1.3 is the successor to version 1.1 and not version 1.2.
...
This document is structured as follows: After a dependence on other specifications has first been explained, a general overview of the model underlying the specification is provided. The following two sections explain the constituents of the XML schema used to transmit data. Generic rules for parties communicating via a Veloconnect interface, as well as specific requirements of ordering procedures, can be found in operations and transaction: order. Newly added to version 1.3 is a section on the exchange of documents. A section on catalogue data describes searching in the catalogue and complete download of the assortment data. Explained subsequently is the planned test mechanism, as well as rules ensuring upward and downward compatibility in future versions of the specification. A few examples are provided at the end.
The UBL specification whose copyright is held by the OASIS consortium forms the basis for this specification whose copyright is held by Verbund Service und Fahrrad e. V. (VSF). The detailed licensing terms can be found in the section on copyright notices.
Error reports and suggestions are welcome at the address spezifikation@veloconnect.de.
...