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] James Clark: XML versus the Web

 XML v JSON

 Does it have to be either/or, in our imagination?

 What about building JSON into XML by replacing XML's attribute syntax?

 So that every XML 1.0 and every JSON document were allowed, but also:


 <?xml version="2.0"?>

 <glossary><title>example glossary</title>

   <GlossEntry
     	ID="SGML"
 	"Sort As": "SGML",
 	"Gloss Term": "Standard Generalized Markup Language",
 	"Version"=2,
 	"Acronym": "SGML",
 	"Abbrev": "ISO 8879:1986"
 	"Gloss See Also": ["GML", "XML"]
   >A meta-markup language, used to create markup languages such as 
 DocBook.</GlossEntry>

 </glossary>


 This would solve the following problems that XML has:

 1) fatty fat fat bloato burpy blubberware XML schemas just to get 
 simple typing
 2) no structured attributes
 3) attribute names cannot have spaces (or entity refs)

 and have a standard translation into JSON, so that

 Cheers
 Rick


[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