- From: Steven Pemberton <steven.pemberton@cwi.nl>
- Date: Wed, 16 Apr 2008 15:21:24 +0200
- To: "Shane McCarron" <shane@aptest.com>, "Tim Berners-Lee" <timbl@w3.org>
- Cc: "W3C RDFa task force" <public-rdf-in-xhtml-tf@w3.org>, "XHTML WG" <public-xhtml2@w3.org>
Yes, I have long meditated on the idea of suggesting the possibility of using <link rel="<http://www.example.com/index>" href="..." /> but I don't think it means that the [] should or needs to be removed. In fact, you need both for consistency: dc:creator and <http://purl.org/dc/elements/1.1/creator> in CURIE contexts, and [dc:creator] and http://purl.org/dc/elements/1.1/creator in URI contexts. Steven On Mon, 14 Apr 2008 20:37:04 +0200, Shane McCarron <shane@aptest.com> wrote: > > I don't hate this. However, I am copying the XHTML 2 Working Group > because they are the keepers of the CURIE spec. It would eliminate the > "SafeCURIE" production altogether, and instead change the URIorCURIE > production to be one where URIs are delimited. Mark? > > Tim Berners-Lee wrote: >> >> This is a comment I made earlier in a TAG context but thought I would >> repeat here. >> It seems silly to distinguish curies from URIs in a way which makes the >> short form longer. >> Why not make the short curie the default, and allow a longer syntax for >> the case in which someone wants to put a full URI? >> >> Thus not >> >> <a zref="[book:ch1]"> >> <a zref="http://books.example.com/20078-3-789/book#ch1"> >> >> but >> >> <a zref="book:ch1"> >> <a zref="<http://books.example.com/20078-3-789/book#ch1>"> >> or >> <a zref="[http://books.example.com/20078-3-789/book#ch1]"> >> >> This not only minimizes the number of characters in abbreviated case >> rather than the longhand case, it also uses a convention common >> elsewhere in N3 and SPARQL. Clearly a superior solution, better for >> the documents and better for learning. >> >> Tim >> >
Received on Wednesday, 16 April 2008 13:22:02 UTC