Below are descriptions of XML elements follows an example description of an XML element from the NeTEx export of ARGE ÖVV based Austrian NeTEx Profileb ased on the EPIP template (prCEN TS 16614-PI Profile FV (E) -2019 - Final Draft-v3.pdf).
Any peculiarities are dealt with in the "Description" field.
(1) The general description of the respective XML element
(2) Represents the exact description of the elements within the individual XML element
The deviations or peculiarities of the Austrian National Profile implementation are described. (See element ResponsibilityRoleAssignment)
(3) Shows an extract from the national profile of ARGE ÖVV Mobilitätsverbünde Österreich OG for the field described in each case
Every Description will follow the same scheme
(1) Codespace
A CODESPACE is similar to the XML concept of aNamespace that gives a context within which the names of elements and attributes in an XML schema shall unique, (using the generic W3C domain mechanism), thus permitting the combining of elements from different schemas in the same aggregated model. In a similar way, NeTEx uses Codespaces to ensure that the identifiers of instances of elements in an XML document are unique, even if they come from many different systems and are placed in the same document – see examples below. This allows data elements from different countries, different regions, and different organisations to be combined without clashes.
(2) Codespace – XML Element
Classification | Name | Type | Cardinality | Description |
::> | ::> | Entity | ::> | CODESPACE inherits from ENTITY. |
«PK» | id | CodespaceIdType | 1:1 | Identifier of CODESPACE. Unique within documents. |
«AK» | Xmlns | xsd:NMTOKEN | 1:1 | CODESPACE prefix, unique within a given XML document e.g. 'napt' |
XmlnsUrl | xsd:anyURI | 0:1 | CODESPACE path. Globally unique. For example, http://naptan.org.uk/naptan or http:/vdv.de/vdv/haltstelle/ | |
Description | xsd:string | 0:1 | Description of CODESPACE. |
(3) Example from the Austrian NeTEx Profile:
...