[Home] [By Thread] [By Date] [Recent Entries]
On Mon, Sep 30, 2013 at 6:48 AM, Hans-Juergen Rennau <hrennau@y...> 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] |

Cart



