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    

 

 

Overview on XML Schema Vocabulary Design and Introduction to Model-driven XML Vocabulary (MXV)

On this page

Topic

1. What is a XML Vocabulary?
2. What is semantic data interoperability?

3. What is MXV (Model-driven XML Vocabulary)?

4. Why W3C XML Schema & Vocabulary Design?

5. Who can benefit from MXV?
6. MXV Implementations

1. What is a XML Vocabulary?

A XML Vocabulary is a collection of pre-defined XML tag names and meanings for a distinct business scope or industry.

 

XML is sometimes referred to as one of the most revolutionising standards in the IT industry. However, XML is is only a format, which does not reveal the meaning of its data payload. When two parties exchange information in an XML format, humans or computers can easily 'read' the files. Correctly deducing the true meaning though is not so simple. While humans are able to interpret and enquire, computers are not capable of asking about meaning. Accurate and efficient data interpretation and processing requires an agreed and precise XML vocabulary.


2. What is semantic data  interoperability?

Beyond the ability of two or more computer systems to exchange information, semantic interoperability is the ability to automatically interpret the information exchanged meaningfully and accurately in order to produce useful results as defined by the end users of both systems. To achieve semantic interoperability, both sides must refer to a common information exchange reference model [such as a XML vocabulary]. The content of the information exchange requests are unambiguously defined: what is sent is the same as what is understood.

 

Excerpt from Wikipedia (http://en.wikipedia.org/wiki/Interoperability#Semantic_interoperability)


3. What is a Model-driven XML Vocabulary (MXV)?

  • MXV is a practical and proven XML Vocabulary design solution consisting of concepts, open standards, processes and tools
  • MXV enables semantic data interoperability through a XML Vocabulary
  • MXV lets you define your master vocabulary in form of a UML enterprise data model
  • MXV transforms your master UML vocabulary into your XML Vocabulary
  • The XML Vocabulary is implemented as a XML library in form of W3C XML libary schemas
  • MXV lets you compose your XML document schemas by cherry-picking simple and nested components from the XML Vocabulary
  • MXV lets you define new nested components by cherry-picking simple components from the XML Vocabulary
  • MXV generates the XML Schema files (.xsd) and eliminates the need for hand-coding them
  • MXV ensures your XML document schemas are always in line with your master vocabulary
  • MXV ensures your XML document schemas comply with a range of globally used naming and XML design standards
  • MXV enables W3C XML Schema design governance
  • MXV ensures your XML document schemas are consistent across projects and over time
  • MXV encourages backward-compatible evolution of your XML document schemas through standardised schema versioning
  • MXV supports multiple parallel minor versions of the same XML document schema in a production environment
  • MXV supports backward and forward compatibilty of XML instances based on different minor schema versions (loose coupling the schema versions)
  • MXV is suitable for data exchanges both between internal and external systems, i.e. business-to-business (B2B) and enterprise application integration (EAI)

 

 

 

 


 

4. Why W3C XML Schema & Vocabulary Design?

Capabilities of computer systems have significantly advanced in recent years. And so has the number of computer systems in use. And this poses a new challenge: 

Many organisations have long recognised the value of information: Linking distributed information enables organisations to function with a new openness. For example, a government communicating with its citizens, or a business combining information for making well-informed decisions.

 

Sharing data, and thus making systems interoperable, is progressively becoming more important for a wide range of organisations, including governments. But access to distributed systems is often restricted to a select few. As a result, point-to-point data exchanges have become common. Organisations are increasingly struggling to sustain the ever-growing number of such non-standardised data exchanges fraught with misunderstandings, processing errors and data quality issues.

 

Many organisations are acutely aware of the consequences they are suffering from inadequate interoperability and the drawbacks of point-to-point data exchanges.

 

Many XML implementations are plagued by the lack of both a XML vocabulary and an enforced W3C XML design standard. The W3C XML Schema language itself is often unfairly blamed for this situation, when in fact the problem is caused by the inconsistent ways XML is applied across projects and time.

 

But there is a proven solution to this: Using MXV, an enterprise data model can now also be implemented as W3C XML Schema, comparable to implementing a data model as a relational database. The resulting XML vocabulary enables semantic interoperability, where sender and receiver of a message share a common understanding of the meaning of data items. The XML vocabulary itself complies with a number of commonly used open standards, thus further improving interoperability.

 


5. Who can benefit from MXV?

MXV is a proven design solution for organisations which:

  • want semantic data interoperability, and
  • use XML data exchanges either internally (EAI) or externally (B2B / G2G), and
  • cannot find a suitable off-the-shelf XML vocabulary that meets their data exchange requirements, and
  • want to centrally manage their XML data exchanges, and
  • want to standardise XML data exchanges across projects and over time, and
  • need to create their own XML vocabulary, and
  • want to standardise the XML tag names, and
  • want to standardise the XML schema design style, and
  • want to automatically enforce XML schema design governance, and
  • want to replace hand-coded XML schemas with generated ones, and
  • want to evolve the XML vocabulary through controlled schema versioning, and
  • want to organically grow the re-usable, nested XML constructs, and
  • want support for multiple parallel minor schema versions in production (optional), and
  • want support for highly validated XML values using XML Value Validation (optional)

Read on if this sounds like what your organisation needs. Otherwise, MXV is probably not suited for your organisation.

 


6. MXV Implementations

In 2006, the New Zealand Ministry of Education (MoE) adopted MXV. For the real life business background of Student Record Transfer (SRT), one of MoE's MXV based interoperability solutions, see http://vimeo.com/19733408.

 


7. MXV deployment options

MXV can be deployed in a number of ways, ranging from:

  • in-house deployment, to
  • outsourced deployment, and
  • various arrangements in between.

 

With the in-house MXV option, your organisation is responsible for the deployment of MXV, including:

  • maintaining the UML Master Vocabulary
  • generating the XML Vocabulary library schemas
  • specifying data exchange requirements
  • composing and generating document schemas
  • applying of change management process
  • using and licensing of tools

Data Management Solutions will provide the intial MXV setup and configuration, ongoing ad-hoc support, and also training if desired.

 

With the outsourced MXV option, Data Management Solutions is responsible for all of the above. I do not recommend outsourcing the UML Master Vocabulary though, because it is a business asset too valuable to lose control over. Perhaps it can be safely outsourced if it is small, simple and not business critical.

 

With the 'in between MXV arrangement', your organisation and Data Management Solutions agree on a split of responsibilities. One prudent split could be that your organisation is responsible for maintaining the UML Master Vocabulary as well as specifying data exchange and validation requirements, while Data Management Solutions is responsible for delivering the resulting artefacts.

 

If you wish to discuss any of these MXV deployment options, please contact me.

 


Read more ...

See my résumé for more details, or feel free to contact me.

 


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