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]
XML JSON Mutant

Since its nearly Friday, how about an XML JSON Mutant!

In XML a couple of data oriented values might look like:

    <Name>Value</Name>
    <Name2>Value2</Name2>

In JSON they might look like:

    Name:Value,
    Name2:Value2,

In Mutant they might look like:

    <Name:Value>
    <Name2:Value2>

XML with attributes like:

    <Name attr1="v1" attr2="v2">Value</Name>

Would in Mutant be like:

    <Name attr1="v1" attr2="v2" :Value>

(i.e. attributes are placed between the name and the colon)

And XML markup like:

    <Name attr1="v1" attr2="v2">This is <b>Markedup</b> Text</Name>

Would be represented in Mutant like:

    <Name attr1="v1" attr2="v2":This is <b:Markedup> Text>

Or another example might be:

    <Name attr1="v1" :Read <a href="http://...":this> article>

You could even make arrays more efficient by saying that if a pair starts 
with <: (i.e. does not have a name field) it takes the name of the previous 
pair, like:

    <Name:Value1><:Value2><:Value3>

The benefit is that everybody gets to recognise something of their favoured 
technology in the resultant solution, and everybody feels equally 
compromised!

Pete Cordell
Codalogic Ltd
Interface XML to C++ the easy way using C++ XML
data binding to convert XSD schemas to C++ classes.
Visit http://codalogic.com/lmx/ or http://www.xml2cpp.com
for more info





[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