We are pleased to announce the release of version 3.6, bringing significant enhancements and refinements to the data model. This release contains important updates in line with ongoing CEN Technical Specification revisions, incorporating feedback and improving the functionality and quality of several namespaces.
Key Changes from Version 3.5
Platform Independent Model
The TrafficRegulation and ControlledZone namespaces have been significantly revised in line with the current revision process for CEN TS 16157-11. The changes address issues of functionality and quality that had been raised in a CEN TC review, and the 3.6 model matches the updated version submitted for formal vote through CEN. These namespaces are now considered stable in version 3.
Model elements in the CommonExtension and LocationExtension namespaces that were created for use in the TrafficRegulation or ControlledZone namespaces and were therefore in “Draft” packages until the latter pair of namespaces achieved stability have been moved from “Draft” into “Final” packages within their respective namespaces. That change has no effect on schemas. Some CommonExtension elements for describing kinds of vehicles have had minor improvements arising from the CEN TC review of TS 16157-11. All these extension elements are now considered stable in version 3.
The TrafficManagementPlan namespace has one bugfix allowing activation conditions for a Strategy or Measure to be composite. The model matches the version of CEN TS 16157-8 submitted for 2nd formal vote through CEN. A new extension namespace SituationExtension has been added, containing a simple extension of the enumeration RoadOrCarriagewayOrLaneManagementTypeEnum to identify length and width restrictions.
Minor Backwards-Compatible Changes
- There are very minor editorial changes to definitions in the FaultAndStatus namespace to align with changes made by CEN editors when preparing CEN TS 16157-13 for publication.
- Typo fix in a Situation enumeration definition.
Model Files
As planned, 3.6 is the first release where the old EAP format of Enterprise Architect is not supported and only the current QEA format is provided. This change only affects users of assembled model files.
JSON Schema Mapping
The JSON schema mapping has had further detailed changes to fix small issues after its significant change for release 3.5 to support current code generation tools.
- The version of the JSON schema specification used has been upgraded to “2020-12”.
- Some generated property names have a namespace prefix for disambiguation.
- Generated schema elements for super-classes contain description metadata advising that only one of the subclass properties shall be populated.
- An abstract class no longer results in a redundant schema element of the same name.
The mapping is currently being standardised in CEN TS 16157-15 and its stability should be confirmed after CEN TC review.