Hi all: I am back on deck as of next week and well.


Costello, Roger L. said:

> Hypothesis - How to Design XML Documents
>
> I am supremely compelled by the argument that the future is much too
> uncertain to bother attempting to anticipate or design for.  Thus I put
> this down as the first part of this hypothesis:
>
>     Part 1: Design your XML documents so that they are well-suited for
> processing by your applications *today*.
>
> In other words, how your data is going to be processed tells you how to
> design your XML.
>
> A large percentage (majority?) of applications today operate on the
> data only after it is placed into a (relational) database.  A smaller
> percentage (minority?) of applications operate directly on the data in
> an XML document.  So, as an 80-20 rule I make the second part of this
> hypothesis:
>
>     Part 2: Design your XML to be flat, with direct mappings from XML
> to (relational) database tables.
>
> I am also supremely compelled by the argument to keep the markup (tags)
> to a minimum.  So here's the third part of this hypothesis:
>
>     Part 3: Eliminate nonessential markup (tags).  Only use tags that
> are actually used by your applications *today*.
>
> To recap - when designing XML:
>                          - be practical;
>                          - be simple;
>                          - don't use unnecessary tags;
>                          - design your XML to work well with your
> applications *today*;
>                          - most likely, "flatter is better".
>
> Comments?  /Roger