W3C home > Mailing lists > Public > public-html@w3.org > May 2010

use cases for polyglot/biglot documents (was Re: ISSUE-4 - versioning/DOCTYPEs)

From: Tantek Celik <tantek@cs.stanford.edu>
Date: Mon, 17 May 2010 19:46:24 +0000
Message-ID: <620561291-1274125611-cardhu_decombobulator_blackberry.rim.net-1015497579-@bda088.bisx.prod.on.blackberry>
To: "Boris Zbarsky" <bzbarsky@MIT.EDU>,public-html-request@w3.org,"Henri Sivonen" <hsivonen@iki.fi>
Cc: public-html@w3.org
Boris has described exactly the real world use case of what I do with my blog/tweets at my site:

http://tantek.com/


All the data is stored in bi-glot HTML5+hAtom and processed server-side using PHP/CASSIS XML APIs/tools which also generate biglot HTML5+hAtom and serve it as text/html. No databases. No POX.

And FWIW I also have no need for any xmlns talisman.

Tantek

-----Original Message-----
From: Boris Zbarsky <bzbarsky@MIT.EDU>
Date: Mon, 17 May 2010 09:18:15 
To: Henri Sivonen<hsivonen@iki.fi>
Cc: <public-html@w3.org>
Subject: Re: ISSUE-4 - versioning/DOCTYPEs

On 5/17/10 4:57 AM, Henri Sivonen wrote:
> I'm aware of three use cases for polyglot documents:
...

4)  Serving content as text/html but using an XML toolchain on
     the server side to generate and process the content.

seems like an obvious use case...  Not sure how common this is in 
practice, though.  Note that using XSLT to generate HTML from XML is not 
an example of this use case; this use case involves actually storing the 
XHTML source and processing it as such.

-Boris

Received on Monday, 17 May 2010 19:47:40 UTC

This archive was generated by hypermail 2.3.1 : Monday, 29 September 2014 09:39:17 UTC