OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index]
How to do XML design, per Jackson Structured Design

Roger quotes"

"Design the data to model the end user's real world. "

Which one?

The challenge is having multiple end users with different real worlds and not enough time or will to reach a consensus, so you design the data to meet each point of view and glue that together with transforms to a high level intermediate form that you put somewhere as a communication hub. Jackson was designing in the days before Integration of Very Large Distributed Systems (say multiple polities, multiple authorities, no single payment source).

No free lunch.

However, it pays big time to design data first so you will at least know about these problems rather than designing an object-framework that tries to ignore them. The question is, does anyone care?

Clay Shirky blogged on the ACA problems and lays them at the feet of the unwillingingness of technical teams to explain technical problems to elite managers who no longer wish to listen to them because then they would have to tell their evermore elite paymasters that they aren't going to get the system on time to avoid a vote on the pay. See Christa McAuliffe: if the social network takes over the business and thus the design, you are done.

Or even dead.


[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index]

News | XML in Industry | Calendar | XML Registry
Marketplace | Resources | MyXML.org | Sponsors | Privacy Statement

Copyright 1993-2007 XML.org. This site is hosted by OASIS