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] JSON query processing


--> Chris Says
In reality it doesn't make that much difference since even if you do agree
on an interchange format it will never match the schema of both parties
exactly and therefore both sides will be doing some kind of conversion into
and out of the interchange format for their own systems. The only real
benefit that a defined interchange format would have is where you can define
it to be more suitable for whatever transport arrangements are in scope
(more compact, or fully encrypted, or easier to pass through some
particularly difficult gateway).
---------

There's another HUGE advantage to picking a single interchange format (and
schema).
That's validation .. or if you want to talk "Stake Holders" its "CYA".
If you have a single validatable interchange format then receiving parties
can validate all data they get and if it fails the agree-on contract they
can say without ambiguity "Not Our Fault" ... 

Other comments of yours, however, I agree completely .  Especially the
'smartass' part ...
Beware the sorry soul who sticks their neck out too far and suggests
something reasonable.
It tends to get ones head cut off.

-David





[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