Roger, an example semantic data model is found here, for 91 different
document types in the UBL 2.3 OASIS standard (UBL 2.1 is standardized
as ISO/IEC 19845:2015):
https://docs.oasis-open.org/ubl/os-UBL-2.3/mod/summary/reports/All-UBL-2.3-Documents.html
The model is expressed using UN/CEFACT CCTS 2.01 modeling concepts:
https://docs.oasis-open.org/ubl/os-UBL-2.3/UBL-2.3.html#A-THE-UBL-2.3-DATA-MODEL
OASIS has naming and design rules (NDR) that are followed in the
conversion of a CCTS data model into both XSD and JSON-Schema
expressions of document constraints:
https://docs.oasis-open.org/ubl/Business-Document-NDR/v1.1/Business-Document-NDR-v1.1.html
(that draft was finalized four days ago and the final version has not
been published yet, but no changes from above)
The XSD expressions resulting from using these NDRs are found here:
http://docs.oasis-open.org/ubl/os-UBL-2.3/xsd/
The JSON-schema expressions resulting from using these NDRs are found here:
https://docs.oasis-open.org/ubl/UBL-2.3-JSON/v1.0/UBL-2.3-JSON-v1.0.html
(finalized after the BDNDR is published, but no changes from above)
Our semantic model is maintained in two Google spreadsheets for all
committee members to work on:
Common library:
https://docs.google.com/spreadsheets/d/1XjhMEKJLpKfn1Z6bjNVT5myoYvsvD2yQQsnRja1QGq0/edit#gid=1482665391
91 document types:
https://docs.google.com/spreadsheets/d/1vsjDwzxmXbeJU11mu8wPQIDIP3I0g2GlQP9ObjhKCJ0/edit#gid=1761200356
Every time a committee member pushes any changes of any UBL document
to github, the back-end Actions pull the spreadsheet into a
transformation to an XML serialization, which, in turn, is converted
to XSD and JSON-Schema. The committee members need know nothing about
XML nor JSON, only CCTS. Every time they push a change, they get a
complete set of 91 document schemas in two syntaxes to then
experiment with on their branch.
https://github.com/oasis-tcs/ubl
By focusing solely on CCTS, the business experts on the UBL committee
can focus solely on the semantic model ... the runtime artefacts are
automatically generated.
Please let me know if you have any questions.
. . . . . . ken
At 2021-11-12 12:46 +0000, Roger L Costello wrote:
>Stephen Green wrote:
>
> >Is it maybe time to focus on standardizing mappings
> > and transformations from XML to JSON?
>
>Michael Kay responded:
>
> > Unfortunately, converting a good XML design to a
> > good JSON design can only be done with knowledge
> > of the semantic data model: mechanical transformations
> > (in either direction) done without knowledge of the
> > data model always produce a mess.
>
>Michael, what is a "semantic data model"? Would you give an example
>of a semantic data model for XML and an example of a semantic data
>model for JSON, please? How are their semantic data models used to
>transform XML to JSON and vice versa?
>
>/Roger
>
>
>
>_______________________________________________________________________
>
>XML-DEV is a publicly archived, unmoderated list hosted by OASIS
>to support XML implementation and development. To minimize
>spam in the archives, you must subscribe before posting.
>
>[Un]Subscribe/change address: http://www.oasis-open.org/mlmanage/
>Or unsubscribe:
>subscribe:
>List archive: http://lists.xml.org/archives/xml-dev/
>List Guidelines: http://www.oasis-open.org/maillists/guidelines.php
--
Contact info, blog, articles, etc. http://www.CraneSoftwrights.com/x/ |
Check our site for free XML, XSLT, XSL-FO and UBL developer resources |
Streaming hands-on XSLT/XPath 2 training class @US$125 (5 hours free) |
Essays (UBL, XML, etc.) http://www.linkedin.com/today/author/gkholman |
