Cart
|
[XML-DEV Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message] Re: XML Schema as a data modeling tool
 Bill, thank you very much for your thoughts and for pointing to UBL and HL7. It is this kind of pointing which I had hoped for, and I will try to get an idea of the approaches taken.
Kind regards, Hans Von: William Velasquez <wvelasquez@visiontecnologica.com> An: Hans-Juergen Rennau <hrennau@y...>; "xml-dev@l..." <xml-dev@l...> Gesendet: 0:44 Dienstag, 1.Oktober 2013 Betreff: RE: XML Schema as a data modeling tool Hi Hans,
Using XML Schema for data modeling is an excellent idea for these reasons:
-
You don’t have to normalize.
-
Trees are more like the real world structures than rows and columns.
-
It’s an standard representation, universally accepted
-
You can find many tools to represent it visually and generate nice documentation on HTML and other presentation formats.
-
Could be used as the basis for Model Driven Development in combination with XRX. Just imagine generating XForms automatically from Schemas
and using an XML database to store the data as XML Instances. Many people is saving lot of work using this approach (including me).
-
And finally, it’s XML! You can manipulate it using the XML ecosystem of tools and technologies.
Off course, there are some disadvantages:
-
XML Schema is not so good representing relationships, but is flexible to allow you to design a mechanism for representing them
-
Some concepts are complex to represent, like inheritance, but you can find some helpful XML Schema patterns on the web.
-
One of the most useful features, assertions, is new on XML Schema 1.1 and the vast majority of tools only support XSD 1.0.
In infer from you question that your need is related to business systems and XML Schema fits very well on these, even best than ER model. The best
examples you could find are ecommerce standards, like UBL and HL7. Those are based on XML Schemas for modeling both messages and entities, and solved the problem of representing relations dividing the models in two layers core concepts and messages:
All the ‘static’ entities on the core concepts layer are represented as XML elements, with ID attributes, and in the messages layer, these ID’s
are used as references, but is allowed to include a full copy of the core concept elements in the message, not only the ID (to avoid normalization).
Maybe UBL is not very successful, but it’s due to the human resistance to standardization, but is an excellent example of a data model made with
XSD.
Hope you find these ideas useful,
-
Bill
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] |
PURCHASE STYLUS STUDIO ONLINE TODAY!Purchasing Stylus Studio from our online shop is Easy, Secure and Value Priced! 
Download The World's Best XML IDE!Accelerate XML development with our award-winning XML IDE - Download a free trial today! Subscribe in XML format
|
|||||||||
