[Home] [By Thread] [By Date] [Recent Entries]
See this insightful article from Sean McGrath: http://www.propylon.com/news/ctoarticles/Zen_and_the_Art_of_Motorcycle_Manuals_20020822.html Too much stuff is always too much stuff. len From: Jeff Lowery [mailto:jlowery@s...] Well, I guess in the media age you have to reduce everything to sound bites. All right, let's try a different approach. For those of you who are responsible for designing the code to populate large, industry-wide data interchange XML documents (and I know who you are), are you doing this via: 1. object hierarchies (that are document-type specific) 2. A DOM (or other generic data model) 3. A transform (from proprietary serialized format to XML interchange format) 4. Web interactive (HTML or other interactive forms originating from XML interchange format instances) 5. other I hope that's clear enough. You can respond to me privately and I'll summarize all the results I get. Assuming I get any. ----------------------------------------------------------------- The xml-dev list is sponsored by XML.org <http://www.xml.org>, an initiative of OASIS <http://www.oasis-open.org> The list archives are at http://lists.xml.org/archives/xml-dev/ To subscribe or unsubscribe from this list use the subscription manager: <http://lists.xml.org/ob/adm.pl>
|

Cart



