The script can be specified in the src attribute of the SCRIPT element or embedded inline in some cases (e.g. when the inline content does not contain the text "</script"). The content of the SCRIPT element would contain the metadata directly as XML text. Chris
-----Original Message----- From: Julian Reschke [mailto:[EMAIL PROTECTED] Sent: Friday, August 22, 2008 9:45 PM To: Ian Hickson Cc: Bonner, Matt; Ben Adida; Dan Brickley; Kristof Zelechovski; Tab Atkins Jr.; Henri Sivonen; [email protected] Subject: Re: [whatwg] Creative Commons Rights Expression Language 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_inv ent_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? BR, Julian
