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] "Introducing MicroXML, Part 1: Explore the basicprinciples of ...


David,

>I would hope so otherwise MicroXML will have to stay its own island like JSON.  In which case why even bother making it look like XML?

Exactly.  Simplify XML, via a profile.  "Full, fat XML" is still necessary, and useful.  Simplified XML could work where XML itself might not be a good fit.  What goes in the profile?  The minimum possible.  It should be backwards compatible, though, so XQuery and XSLT can work with it.

>I admit I have not kept up with the MicroXML "specs" to know if even <foo:bar/> is valid MicroXML ... let alone to consider
how it would be converted to XDM.

I think that just eliminating <foo:bar/> in favour of <bar/> would work.


>But this latest series of discussions has me interested.

Me too.

Peter


[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