Turning data into business advantage

 Home  Services  Downloads / Links  Résumé  Company Profile  Contact  Search
   Data Modelling      
   Data Architecture From UML to XML    
   Data Analysis MXV loose coupling    
   Database Design & Implementation MXV demo / case study    
   XML Schema & Vocabulary Design MXV trial download    
   XML Value Validation MXV Tool Suite V3.2    
   Model Change Management MXV Tool Suite V2.3    
   AllFusion ERwin & PowerDesigner Tool Suites Methodology documents    
   Hands-on consulting MXV NDR 2.1    
    Latest MXV news    


MXV history



    Copyrights and IPs    



What is new in MXV NDR 2.1

On this page


1. MXV NDR 2.1 Overview

2. Decoupling from XSD enumerated code lists referenced by the UN/CEFACT UDT Unqualified Data Type Schema Module XSD

1. MXV NDR 2.1 Overview

MXV, the first version of this UML model-driven XML Schema Vocabulary Design solution, was originally based on UBL NDR 2.0, OASIS' first approved XML Schema Naming and Design Rules standard.


In 2010, OASIS has published OASIS UBL 2.1 (*) work in progress. Its outputs are well documented on the OASIS website.


In parallel, Data Management Solutions has upgraded MXV to stay aligned with OASIS UBL NDR 2.1. (*)

Since October 2010, the latest MXV Productivity Tools are applying the MXV methodology v2.1, which emulates OASIS UBL NDR 2.1 (*).


OASIS UBL NDR 2.1 (*) delivers two major improvements:


2. Decoupling from XSD enumerated code lists referenced by the UN/CEFACT UDT Unqualified Data Type Schema Module XSD

NDR 2.0:

The problem: With NDR 2.0, the schema designer cannot modify the UN/CEFACT inbuilt code value lists for Country, Currency, Unit of Measure and MIME type.

This may lead to major processing issues when one of above code value list changes over time.


OASIS states: "The W3C Schema 1.0 expression of code list value constraints in the UN/CEFACT UDT Unqualified Data Type Schema Module XSD based on CCTS 2.01 and used in UBL 2.0 has been proven not to support the objective in UBL 2.1 of validating instances of UBL 2.0 and UBL 2.1. See the case study of different currency codes for Turkey at the dates of the releases of UBL 2.0 and UBL 2.1 in the two threads starting at http://lists.oasis-open.org/archives/ubl/200904/msg00015.html and http://lists.oasis-open.org/archives/ubl-dev/200905/msg00002.html."


NDR 2.1: 

UBL NDR 2.1 (*) eliminates the described restriction, and provides full flexibility on all code lists. For details, see the OASIS STGT strategy document at http://www.oasis-open.org/committees/document.php?document_id=35864

MXV NDR 2.1 provides the same code list flexibility as UBL by adopting the same data type schema modules as UBL 2.1


NDR 2.1 benefit:

  • Complete control over all code list changes, including the NDR 2.0 inbuilt UN/CEFACT code lists Country, Currency, Unit of Measure and MIME type, without the need for issuing new schema versions.

3. A much simpler XML Library Schema Module structure

NDR 2.0:

The following diagram depicts the Library Schema Module import structure of UBL NDR 2.0 and MXV NDR 2.0:


NDR 2.0


NDR 2.1:

The same high level of componentisation and re-use can be achieved in MXV NDR 2.1 by using the new UBL NDR 2.1 (*) library schema module structure, which by the way is backward-compatible with any NDR 2.0 instance document:


NDR 2.1


NDR 2.1 benefits:

  • The total number of XML Library Module schemas is reduced from 9 to 6

  • The total number of nested schema imports is reduced from 15 to 8

  • The simpler XML Schema import structure reduces complexity for developers

  • Less schemas and namespaces result in simpler messaging server and XML catalogue configuration

  • The size of the XML Library schemas is reduced by approx. 0.6 MB

  • Smaller operational footprint leads to better performance

  • The QDT Library Module Schema has become virtually maintenance-free

  • Only two of the Library Schema Modules require the administrator's maintenance: CBC and CAC Library Schema Modules

  • Simpler and faster schema maintenance for the administrator has reduced the release turn-around time

  • Simpler schemas and import structures reduces the risk of errors

  • Cost savings in design, implementation and operation of XML Schemas

  • Transparent upgrade from an instance document perspective, i.e. a 2.0 instance document will validate against a 2.1 document schema (provided this contains no business-driven backward-incompatible changes)

UBL NDR 2.1 (*) delivered many benefits, yet apart from the one-off migration to NDR 2.1 no real disadvantages.



Please help us with your feedback:

In order to continuously improve MXV, we would be delighted to receive your feedback.

Please provide your feedback here. Thank you!


(*) UBL NDR 2.1: Please note that as of November 2012 the UBL NDR 2.1 document has not been published yet. At this stage, MXV emulates UBL NDR 2.1. A detailed comparison of UBL NDR 2.1 rules against MXV will be made available once the UBL NDR 2.1 document has been finalised.


Data Management Solutions will continue to monitor and align MXV to future OASIS UBL NDR versions.

For further information, feel free to contact me.

Back to XML Schema & Vocabulary Design


        © Copyright 2011 Data Management Solutions, Wellington, New Zealand                   Last Update: 2012 November 28