The DATEX II organisation is pleased to announce the 2016 DATEX II User Forum on 13th and 14th September in Dublin.

An introduction about what to find where in the DATEX II information model and the basic DATEX II Information Model design.

DATEX II profiles and extensions, by Jörg Freudenstein.

prEN 16157-1 contains a specification for a property namespaceUri in section 6.2.1 which does not exist in the UML profile. Remove this specification.

An explicit requirement is missing in prEN 16157-1 that ensures unique namespace names. Since the namespaces are actually derived from the D2namespace package name, the rules has to require all names of D2Namespace packages in a model to be unique. Since a PSM property exists that controls the use of namespcae prefixes in generated XSD code, unique values hae to be required for these properties as well.

In Italian DATEX Profile we manage the temporary alternating one-way for vehicles using Networkmanagement class RoadOrCarriagewayOrLaneManagement with roadOrCarriagewayOrLaneManagementTypeassigned to  IntermittentShortTermClosures.

besides the definition seems more tuned to specify closures then alternating one-way traffic.
No mention of "alternate one-way" road management can be found in the model

Annex A.3 of prEn 16157-1 as submitted to CCMC for publication describes rules how UML qualifiers are mapped to XSD. The tool implements these rules and the mapping is consistent with the handling of qualiifers in earlier DATEX II versions. Qualifiers are actually used throughout the Level A model, as is the basis for EN 16157-2, 3 and 7 and will be the basis for further parts of the standard.
Nevertheless, there is no rule mentioning the use of UML qualifiers in the main section of the document.

Proposal:

Add the following section to clause 7.2: