Visits: 123

Reduce, Reuse and Recycle is the key concept of SDGs

Avoid Not-invented-here syndrome (NIH). NIH can be defined by a tendency for people and organizations to avoid things that they didn’t create themselves.
This syndrome is similar to the “let’s reinvent the wheel” syndrome. 
[SOURCE: https://www.bmc.com/blogs/not-invented-here-syndrome/ ]

Business Process

Now that we have extended the TC name to audit data services, we should support not only data modeling but also business processes, business rules, and these validation.

Extensibility

Organizations in each jurisdiction have regulations and / or internal control rules for each jurisdiction. We SHALL supports extensibility to meet these requirements.

Comparability

There are many things in common other than the expansion due to the jurisdiction differences. We SHALL support comparability based on common points.

Localization

As an international standard, we SHALL support localized labeling and description in the natural language of the jurisdiction.

CCTS

1. The Core Components technical specification itself. http://unece.org/trade/uncefact/ccts
2. The multi-layers Core Components library itself , with
a. the reusable, generic, domain-independent core components, and
b. the domain specific business information entities, etc.
3. The Naming and Design Rules, which turn the UML modeled data into schemas
4. The relevant schema from the CCL using the NDR.
I think the current draft contains only number 4 above. We need number 1 and 4 documented to support ADCS business requirements.

Links

Followings are The Naming and Design Rules by UN/ECE and OASIS published a document on JSON mapping.
— UN/ECE —
XML Naming and Design Rules For CCTS 2.01
Version 2.1 27 May 2014
https://unece.org/DAM/cefact/xml/XML-Naming-And-Design-Rules-V2_1.pdf

— OASIS UBL —
OASIS Business Document Naming and Design Rules Version 1.0
http://docs.oasis-open.org/ubl/Business-Document-NDR/v1.0/Business-Document-NDR-v1.0.html

UBL Naming and Design Rules Version 3.0
http://docs.oasis-open.org/ubl/UBL-NDR/v3.0/UBL-NDR-v3.0.html

Currently OASIS published following documents for public review. There is a document on JSON mapping.
OASIS Business Document Naming and Design Rules Version 1.1
http://docs.oasis-open.org/ubl/Business-Document-NDR/v1.1/Business-Document-NDR-v1.1.html

UBL 2.1 JSON Alternative Representation Version 1.0
http://docs.oasis-open.org/ubl/UBL-2.1-JSON/v1.0/UBL-2.1-JSON-v1.0.html

ISO 20022

ISO 20022 consists of the following parts, under the general title Financial services — Universal financial industry message scheme:
— Part 1: Metamodel
— Part 2: UML profile
— Part 3: Modelling
— Part 4: XML Schema generation
— Part 5: Reverse engineering
— Part 6: Message transport characteristics
— Part 7: Registration
— Part 8: ASN.1 generation
They didn’t use CCTS, but they documented the modeling framework on their own. All international standards are documented based on the modeling framework. I don’t think it’s possible to develop the ADCS modeling framework ourselves within a limited time frame. The best solution is to extend CCTS and its naming and design rules to support ADCS’s business requirements.