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] Never mind the browser, let's do MicroXML

I think the problem here is questioning what we mean by well-formed. Well-formed HTML5 may be ill-formed XML - that's what seems to be emerging from discussions with the HTML5 side. HTML5 allows for ambiguities in interpretation that are correctable when you have a clearly defined schema, but that would cause a great deal of problems when applied to semantically neutral content, unless there was a fairly major change to the behavior of most XML schema validators. This may not be a problem when building a web page. It would be a MAJOR problem when building the messaging architecture of a health management system.

Kurt Cagle
XML Architect
Lockheed / US National Archives ERA Project

On Fri, Dec 17, 2010 at 2:54 PM, Rob Koberg <rob@koberg.com> wrote:

On Fri, Dec 17, 2010 at 10:55 AM, Uche Ogbuji <uche@ogbuji.net> wrote:
On Fri, Dec 17, 2010 at 5:50 AM, Michael Kay <mike@saxonica.com> wrote:
On 16/12/2010 16:18, Uche Ogbuji wrote:
So nobody who matters for MicroXML should need some spiffy business case.

I would go even further. If you can write a business case for doing it, then you are not being courageous enough. If this is going to succeed, there needs to be a high risk that it will fail.


Perhaps a simplified XML is simply well-formed HTML5. Instead of redesigning namespaces, duplicate/use the success of CSS (and you get inheritance) to build the namespaces which can live along different dimensions. Advocate skinning/styling at the CSS level and behavior at the JS layer. Show the benefits of the separation of concerns. Maybe it would be best to teach the basic semantics of HTML5 using the id, class and rel attributes to their fullest, with best practices. When people can understand one language and not be able to do what they need, they will get frustrated and want to expand/change it. Itch/scratch and eventually you will end up with XML (OK, maybe not using URLs for namespace IDs). 
(Wouldn't a CSS-like schema language be cool? In other words, for XML to gain adoption, don't always use XML.)


[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