W3C home > Mailing lists > Public > public-html@w3.org > September 2009

Re: Implementor feedback on new elements in HTML5

From: Anne van Kesteren <annevk@opera.com>
Date: Tue, 01 Sep 2009 13:48:02 +0200
To: "Henri Sivonen" <hsivonen@iki.fi>, "Robin Berjon" <robin@berjon.com>
Cc: "HTML WG" <public-html@w3.org>
Message-ID: <op.uzktqcax64w2qv@annevk-t60>
On Tue, 01 Sep 2009 13:33:29 +0200, Henri Sivonen <hsivonen@iki.fi> wrote:
> On Sep 1, 2009, at 14:19, Robin Berjon wrote:
>> Could adding an itemvaluetype attribute help (we can pick a better name  
>> later)? itemvaluetype = textContent | childNodes | ... defaulting to  
>> the former?
>
> How would you map the latter to JSON?

Having information loss seems like the easiest solution. It's not that  
relevant that it works in JSON.

I imagine it would mostly be useful to specialized spiders that can then  
generate alternate views of the data. E.g. merge #html-wg, #whatwg, and  
#webapps. Or give back chatlogs from various channels for a specific  
timeframe, etc. Basically enough added data to IRC chatlogs around the Web  
so that you can create mashups.

Basically for this to work #values needs a change one way or another.  
itemvaluetype could work, but it is very ugly :-)


-- 
Anne van Kesteren
http://annevankesteren.nl/
Received on Tuesday, 1 September 2009 11:48:54 UTC

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