W3C home > Mailing lists > Public > www-tag@w3.org > March 2009

Re: @rel syntax in RDFa (relevant to ISSUE-60 discussion), was: Using XMLNS in link/@rel

From: Leif Halvard Silli <lhs@malform.no>
Date: Sun, 01 Mar 2009 19:32:16 +0100
Message-ID: <49AAD4B0.8010608@malform.no>
To: Mark Nottingham <mnot@mnot.net>
CC: Ben Adida <ben@adida.net>, Manu Sporny <msporny@digitalbazaar.com>, "www-tag@w3.org WG" <www-tag@w3.org>, HTMLWG WG <public-html@w3.org>, RDFa mailing list <public-rdf-in-xhtml-tf@w3.org>, public-xhtml2@w3.org
Mark Nottingham 2009-03-01 01.27:
> On 01/03/2009, at 10:33 AM, Ben Adida wrote:

> At this point, I think the most helpful thing that could be done for 
> HTML4 (and I'm really only talking about it, at the moment) is to come 
> up with some helpful, global (i.e., not RDFa-specific) conventions for 
> reuse.
> 
> E.g., a profile URI whose semantics is "all link relations in this 
> document that have a colon in them are (syntactic) URIs." That would be 
> less ambiguous than what the Link appendix proposes now, and also opt-in.


HTML 4 says that one might use profiles as

  "A globally unique name. User agents may be able to recognize
   the name (without actually retrieving the profile) and perform
   some activity based on known conventions for that profile."

The CURIE syntax working draft says:

  "Therefore the syntax for carrying a CURIE when there is any
   possibility of ambiguity is to enclose the CURIE in square
   brackets,"

Instead of speculating how it eventually could be made to happen,
what if one could just do this:

  <HEAD profile="[wiki]">
  <link rel="[wiki]" href="http://en.wikipedia.org/wiki/" >

?
-- 
leif halvard silli
Received on Sunday, 1 March 2009 18:58:24 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Thursday, 26 April 2012 12:48:13 GMT