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] nextml


>> I still think there's more mileage in exploring new APIs, especially for
>> Web browsers, and maybe event-based transformations like some of the
>> work done at JustSystems, than in changing the underlying syntax, today.
> Seconded. Trying to re-invent XML is a much larger effort, and I've yet
> to here a compelling business case for it. On the other hand, there's
> very compelling business cases being able to use XML directly in the
> browser, whether via APIs or via some other method.
>

The problem is that an API is always going to be complex if the data you 
are processing doesn't match the type system of the language used to 
process it (I hate the term "impedance mismatch" but that's what we're 
talking about). To make programming easy, you either have to design a 
data format that matches the programming language (JSON-JS), or you have 
to design a programming language that matches the data (XML-XSLT).

Michael Kay
Saxonica


[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