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] what's missing in XML? What's coming?

Liam,

Happy new year!
 
We've got XQuery and people doing XRX-basd Web sites, but no generalized
standard app framework, no way to pass HTTP/form params back to XQuery
or XSLT, no standard http-back-end libraries.

There are some efforts there, but not a lot of standardization yet. Most XQuery frameworks do incorporate some way of retrieving request headers and parameters and body content as well as setting response content types and headers, and the exquery http libs are getting some uptake for server side http, and the work that both Florent Georges and James Fuller is worth noting here, but these are outside of the W3C envelope.

It's actually debatable about the degree of standardization that is necessary here. In most cases these are tied to back-end XML databases - eXist, MarkLogic, EMC's xdb, as part of more extensive libraries, and the degree to which any of these organizations would be willing to change their API to conform to the W3C standards is likely minimal, unless there are obvious benefits to doing so. Sausalito and the 28ms folk are probably closest in that regard, but even there you see existing libraries.

As to XRX app frameworks in general, this is also a mixed bag. XForms has seen some uptake, and Alain's XSLTForms and Orbeon's implementation are both reaching a respectable level of maturity, but adoption there is still agonizingly slow, to the extent that even the XForms WG is exploring how JSON based integration could work given the existing frameworks.


Kurt Cagle
Invited Expert, XForms Working Group, W3C
Managing Editor, XMLToday.org
kurt.cagle@gmail.com
443-837-8725




On Sun, Jan 1, 2012 at 1:27 AM, John Cowan <cowan@mercury.ccil.org> wrote:
Liam R E Quin scripsit:

> We've got XLink for explicit links, but no link discovery mechanism --
> no equivalent to HyTime architectural forms.

Well, the idea was that everyone would use the xlink: namespace to
write down their links.  Few have, unfortunately.

> What did I forget? What should be on our radar that isn't?

/me waves his 10-page MicroXML spec in the air (which includes an
explicit JSON story).

http://home.ccil.org/~cowan/MicroXML.html

--
Babies are born as a result of the              John Cowan
mating between men and women, and most          http://www.ccil.org/~cowan
men and women enjoy mating.                     cowan@ccil.org
   --Isaac Asimov in Earth: Our Crowded Spaceship

_______________________________________________________________________

XML-DEV is a publicly archived, unmoderated list hosted by OASIS
to support XML implementation and development. To minimize
spam in the archives, you must subscribe before posting.

[Un]Subscribe/change address: http://www.oasis-open.org/mlmanage/
Or unsubscribe: xml-dev-unsubscribe@lists.xml.org
subscribe: xml-dev-subscribe@lists.xml.org
List archive: http://lists.xml.org/archives/xml-dev/
List Guidelines: http://www.oasis-open.org/maillists/guidelines.php




[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