[XML-DEV Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message]

Re: XML Schema as a data modeling tool

  • From: Peter Hunsberger <peter.hunsberger@gmail.com>
  • To: Hans-Juergen Rennau <hrennau@yahoo.de>
  • Date: Mon, 30 Sep 2013 10:00:15 -0500

Re:  XML Schema as a data modeling tool

On Mon, Sep 30, 2013 at 6:48 AM, Hans-Juergen Rennau <hrennau@yahoo.de> wrote:
Thank you, Michael. You wrote "It [XSD] is a hierarchic model, whereas the real world is a network." I would say, it is as much a network as it is hierarchic. Think of economic structures (e.g. a shop inventory), of administrative structures (a registration procedure), of biological structures (a cell). At any rate the structures I have been dealing with were usually hierarchic, unwieldy and confusing if not dealt with as such, and often straightforward to handle, otherwise. I could show you an ER diagram representing over 100 relational tables storing shopping cart data, and also a single tree representation which can be read like a newspaper. A concise tree representation can be read like a text, conveying a sense of the whole. An ER diagram with many boxes and very many lines is very hard to read. Doubtless you are right in warning about the problems how to model relationships which do not correspond to containment. But I wonder - would you really suggest giving up the benefits of hierarchical modelling, and what is the alternative? You know the German saying, "Not to see the wood because of all those trees", which I suggest to invert, not to see the trees, because they are part of a wood.

You can make the same argument with conventional ER diagrams: decompose them into groups and you get simplification that people can understand.  The problem isn't the ER diagrams, it's the presentation of them.  XML Schema is, IMO, probably worse for that than a conventional ER diagram.  A logical schema diagram with boxes with names on them and arrows pointing between the boxes is something I can drop on a managers desk.  A XSD document, not so much so. 

However, in the end, trees, networks, what have you are all part of the larger problem called graph traversal.  There are many, many, ways to deal with graph complexity and extracting relevant levels of detail from a graph.  These days, if I was to look for a general approach for storing my model metadata and manipulating it, I would use a graph database.  I see that being useful to generate XSD or an ER diagram and there are visualization tools that let you partition and examine portions of the graph on the fly...


[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!

Buy Stylus Studio Now

Download The World's Best XML IDE!

Accelerate XML development with our award-winning XML IDE - Download a free trial today!

Don't miss another message! Subscribe to this list today.
Email
First Name
Last Name
Company
Subscribe in XML format
RSS 2.0
Atom 0.3
 

Stylus Studio has published XML-DEV in RSS and ATOM formats, enabling users to easily subcribe to the list from their preferred news reader application.


Stylus Studio Sponsored Links are added links designed to provide related and additional information to the visitors of this website. they were not included by the author in the initial post. To view the content without the Sponsor Links please click here.

Site Map | Privacy Policy | Terms of Use | Trademarks
Free Stylus Studio XML Training:
W3C Member
Stylus Studio® and DataDirect XQuery ™are products from DataDirect Technologies, is a registered trademark of Progress Software Corporation, in the U.S. and other countries. © 2004-2013 All Rights Reserved.