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

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

From: Sam Ruby <rubys@intertwingly.net>
Date: Mon, 17 May 2010 17:01:48 -0400
Message-ID: <4BF1AEBC.4040300@intertwingly.net>
To: tantek@cs.stanford.edu
CC: Boris Zbarsky <bzbarsky@MIT.EDU>, public-html-request@w3.org, Henri Sivonen <hsivonen@iki.fi>, public-html@w3.org
On 05/17/2010 03:46 PM, Tantek Celik wrote:
> 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.

For what it is worth, this is similar to how I use Venus: in my case the 
data is stored as Atom, and processed using xslt.

You can use a variety of templating languages with Venus, but none as 
powerful or as fast as XSLT.  It's not for everybody (the two downsides 
are it has a bit of a learning curve, and has a tendency to use a 
self-closing element syntax on non-void elements), but neither are 
insurmountable issues for me.

For those interested, my template can be found here:


The talisman is something I explicitly need to insert in the XSLT 
template, but isn't something I object to, and at the present time is 
required (in combination with using the proper mime type) to get my 
inline SVG images to be processed.

The much harder thing to accomplish is the doctype, where "much harder" 
means a single line of code.

> Tantek

- Sam Ruby

> -----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 21:02:27 UTC

This archive was generated by hypermail 2.3.1 : Thursday, 29 October 2015 10:16:02 UTC