- From: Sam Ruby <rubys@intertwingly.net>
- Date: Sun, 01 Mar 2009 12:29:06 -0500
- To: Karl Dubost <karl+w3c@la-grange.net>
- CC: Henri Sivonen <hsivonen@iki.fi>, Ben Adida <ben@adida.net>, Julian Reschke <julian.reschke@gmx.de>, Mark Nottingham <mnot@mnot.net>, HTMLWG WG <public-html@w3.org>, RDFa mailing list <public-rdf-in-xhtml-tf@w3.org>, public-xhtml2@w3.org, "www-tag@w3.org WG" <www-tag@w3.org>
Karl Dubost wrote: > > Le 1 mars 2009 à 09:54, Henri Sivonen a écrit : >> Now, to put an actual technical proposal in here: >> >> I suggest changing RDFa to use full IRIs instead of CURIEs. Then, >> suggest making it a conformance requirement for rel in both text/html >> and application/xhtml+xml that a rel token MUST NOT contain a colon or >> MUST be an absolute IRI and MUST NOT start with the string >> "http://www.iana.org/assignments/relation/". Authors SHOULD NOT mint >> relation IRIs that differ only in case. > > After discussing with henri this [morning (EST) on IRC][1], a possible > solution for solving the issue without creating too much hurdles for > authors and spec would be to use urn. > > urn:dc:title > > is a URI and as henri mentioned, "one could register a URI scheme for dc". If a URI scheme for dc were registered, HTML5 could treat 'xmlns:dc' attributes as talismans, and treat as conformance errors cases where such attributes have a value that differs from 'http://purl.org/dc/elements/1.1/'. - Sam Ruby
Received on Sunday, 1 March 2009 17:40:20 UTC