Re: Decentralized poetry markup (language)

Dr. Olaf Hoffmann, Tue, 19 Jan 2010 20:41:55 +0100:
> Leif Halvard Silli:
>> It strikes me that this is an example of a language which we could have
>> developed within HTML5, if  Toby's Decentralized Extensibility proposal
>> had been implemented in HTML5.
>> 
>> http://www.w3.org/mid/1263511821.18556.5.camel@ophelia2.g5n.co.uk

   ———
>> OTOH, we have - as you have noted - XHTML, which allows you to use
>> validly use specific elements. And, we can serve XHTML as text/HTML.
>> So, with HTML5 we get two kinds of text/HTML: "real" text/HTML and
>> XHTML text/HTML. The latter gives us much more freedom than HTML5.

> What you can currently do is to use XHTML+RDFa  [ snip ]
> Or alternatively SVG tiny 1.2  [ snip ]
> And referencing a vocabulary like LML or simply refer to the
> few poetry elements from DAISY as a minimal solution for 
> many/most applications. 

/Currently/ we cannot do anything with HTML5, as it is not an official 
standard yet. But, there is a third, option inside the HTML5 draft - 
namely to /extend/ HTML5 with an applicable specification, the way that 
Jonas described here:

http://www.w3.org/mid/63df84f1001191243o23f4087ar892df42ef1836136@mail.gmail.com


Developing a vocabulary within XHTML in general sounds like a good 
starting point for anyone who wants to enrich the HTML family of 
language. And since HTML5 will include both ARIA, @role and (via 
applicable specification[s]) meta data, we can be quite assured that 
UAs will be able to make sense of such documents, also when served as 
text/HTML.

But to spread this vocabulary to the entire HTML family, the next step 
could then be to try to make the vocabulary available also in "native 
text/HTML", by submitting it a independent draft to this WG - as Jonas 
described. 
-- 
leif halvard silli

Received on Wednesday, 20 January 2010 00:59:24 UTC