[XML-DEV Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message] Re: XML Schema as a data modeling tool
You are certainly right that XSD is a problematic resource, when it comes to its consumption. But an XSD implies an unambiguous tree structure, and it is a concise representation of that tree structure what should be dropped on your manger's desk. And I can tell you from experience that managers like - and start to demand - concise tree representations, because they have rarely seen so expressive and intuitive representations of complex information.
I suppose we are thinking of different scales - yours may be larger than mine, and perhaps we are both "right" in the context we tacitly assume. I think primarily of self-contained entities (like a shopping cart, or a protein), and you think perhaps system views composed of many independent entities. It pleases me to think that our views might be complementary, rather than contradictory. Hans-Juergen Von: Peter Hunsberger <peter.hunsberger@gmail.com> An: Hans-Juergen Rennau <hrennau@y...> CC: Michael Kay <mike@s...>; "xml-dev@l..." <xml-dev@l...> Gesendet: 17:00 Montag, 30.September 2013 Betreff: Re: XML Schema as a data modeling tool On Mon, Sep 30, 2013 at 6:48 AM, Hans-Juergen Rennau <hrennau@yahoo.de> wrote: 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! 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
|