DATEX-II-EU / DatexII

Main repository for issues and bugs for the DATEXII standard
0 stars 0 forks source link

Include a JSON mapping in 16157-1 (Bugzilla Bug 396) #396

Open datexii opened 2 years ago

datexii commented 2 years ago

This issue was created automatically with bugzilla2github.py

Bugzilla Bug 396

Date: 2022-02-15T17:34:03+01:00 From: @iancornwellmottmac To: @JosefKaltwasser

Last updated: 2022-02-28T11:01:25+01:00

datexii commented 2 years ago

Comment 1655

Date: 2022-02-15 17:34:03 +0100 From: @iancornwellmottmac

EN 16157-1, the DATEX II modelling methodology, includes an XML Schema mapping. The DATEX II TMG defined a JSON Schema mapping and used this to make JSON Schemas for both D2Light and the full DATEX II UML model namespaces. This issue requests that the JSON schema mapping is promoted in status to be equivalent to the XML schema mapping, presumably by inclusion in a future revision of EN 16157-1 as another annex.

(The individual content standard parts 2-12+ might then also naturally include JSON schemas when they are revised, if there is a demand for that.)

Our draft DATEX II JSON schema mapping was published in CEN TS 17466 from WG17 but only as a snapshot in an informative annex.

It is acknowledged that the current JSON mapping is based on a technology [JSON schema] that cannot be regarded as mature given its version number is still 0.X. So part of discussing this issue is looking at the progress and roadmap of JSON specification technologies and deciding whether or not the request to include the JSON Schema mapping in 16157-1 is appropriate for the next revision of that standard. Another option is to separate all PSM mappings from Part 1 and put them in their own parts, so they can change independently.

datexii commented 2 years ago

Comment 1665

Date: 2022-02-28 11:01:25 +0100 From: @JosefKaltwasser

The proposal is to rephrase the clause about Conformance to clarify that the normative annex on XML/XSD is normative if you want to use this serialisation platform, but other platforms are possible may be specified in other standards. Then we could make the JSON platform a TS ( due to the 0.x status of JSON Schema).