XML.orgXML.org
FOCUS AREAS |XML-DEV |XML.org DAILY NEWSLINK |REGISTRY |RESOURCES |ABOUT
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]
Re: [xml-dev] How to design XML to have broad utility and yet alsoenable efficient application processing?

 If XML is being used for document interchange then your XML design is predicated by the document formatting and content you wish to capture in your document.  However, you seem to be aiming this at the data interchange world? If so, the question is the question you seem to be circling around is; should XML data interchange formats directly reflect the data models they are transporting?  Given that this is data and not, therefore, an end product intended for humans I'd vote that the XML design should come after the data models are optimized for their various business purposes.  The XML will then hopefully be as efficient of serialization of those models as possible. Note that, in my opinion, good data models are also not optimized for, or specific to, any one program.  As I've noted before, _good_ data models span enterprises, least of all individual programs...

As to your last question, I certainly don't think applications should transform XML into forms that make it inefficient to process (duh)!



Peter Hunsberger


On Tue, Nov 19, 2013 at 4:41 AM, Costello, Roger L. <costello@mitre.org> wrote:
Hi Folks,

Liam Quin wrote:

        XML frees your information from being
        optimized for, and specific to, any one
        program.

An obvious question arises:

        What is the right way to design XML?

I believe the answer is:

        Design XML so that it reflects (models)
        the real world.

But real-world designs (models) may not be well-suited to efficient application processing. A second question arises:

        How do we design XML to have broad
        utility while still enabling efficient
        application processing?

I believe the answer is:

        Each application should transform the
        XML into a form that enables the
        application to process it efficiently.

Do you agree with this?

Is there anything else you would add?

/Roger



_______________________________________________________________________

XML-DEV is a publicly archived, unmoderated list hosted by OASIS
to support XML implementation and development. To minimize
spam in the archives, you must subscribe before posting.

[Un]Subscribe/change address: http://www.oasis-open.org/mlmanage/
Or unsubscribe: xml-dev-unsubscribe@lists.xml.org
subscribe: xml-dev-subscribe@lists.xml.org
List archive: http://lists.xml.org/archives/xml-dev/
List Guidelines: http://www.oasis-open.org/maillists/guidelines.php



[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