On Fri, 22 Aug 2008, Julian Reschke wrote: > Ian Hickson wrote: > > On Fri, 22 Aug 2008, Julian Reschke wrote: > > > Ian Hickson wrote: > > > > On Fri, 22 Aug 2008, Bonner, Matt wrote: > > > > > Well, for example, HTML5 provides the data-* attributes. Could ccREL > > > > > use > > > > > those instead? To flip what you have said, perhaps reading/skimming > > > > > the > > > > > "extensions" sections HTML5 spec would help the ccREL advocates > > > > > understand > > > > > how best to fit ccREL into HTML5. > > > > The HTML5 spec admittedly doesn't make that very easy, but there's an > > > > entry > > > > in the FAQ that covers the main extension points: > > > > > > > > > > > > http://wiki.whatwg.org/wiki/FAQ#HTML5_should_support_a_way_for_anyone_to_invent_new_elements.21 > > > > > > > > For example, RDF n3 could be included directly (and unambiguously) using > > > > the > > > > <script type="..."> extension mechanism. > > > "The script element allows authors to include dynamic script and script > > > data > > > in their documents." -- <http://www.w3.org/html/wg/html5/#script> > > > > Right, this would be script data. > > How is this script data? Where's the script?
Hm, you're right, the terminology here isn't great. I've updated HTML5 to unambiguously allow this. -- Ian Hickson U+1047E )\._.,--....,'``. fL http://ln.hixie.ch/ U+263A /, _.. \ _\ ;`._ ,. Things that are impossible just take longer. `._.-(,_..'--(,_..'`-.;.'
