- From: Danny Ayers <danny.ayers@gmail.com>
- Date: Thu, 19 Jul 2007 11:03:42 +0200
- To: "Mark Baker" <distobj@acm.org>
- Cc: "Harry Halpin" <hhalpin@ibiblio.org>, www-archive@w3.org
A couple more suggestions for the parlour game :-) Did I miss this one already? : <link rel="http://blah.w3.org/2007/profile" href="http://www.w3.org/2003/g/data-view" /> (it might help to tweak the rel slot to be (cdata | uri) ) though perhaps this would be neater: <link href="http://blah.w3.org/2007/profile" /> <link rel="profile" href="http://www.w3.org/2003/g/data-view" /> As in GRDDL, where http://www.w3.org/2003/g/data-view plays a bootstrap role, so could the profile term. Here the <link> association between a document and http://blah.w3.org/2007/profile could be interpreted as "any <link> elements in this doc with rel="profile" should be interpreted as identifying Meta Data profiles". One teensy step more indirection. After all, the relevant use defined for @profile is: [[ As a link. User agents may dereference the URI and perform some activity based on the actual definitions within the profile (e.g., authorize the usage of the profile within the current HTML document). This specification does not define formats for profiles. ]] http://www.w3.org/TR/html401/struct/links.html#h-12.3 So why not use <link> "As a link."? Wouldn't this be consistent with HTML spec: "User agents may dereference the URI and perform some activity based on the definitions within the linked document"? Incidentally, in the discussions I've seen whenever <link> has been mentioned it's been along with @rel. Although there's the historical precedent in profiles where the statement is (loosely) <this_doc> hasProfile <that_doc>, there's also @rev available for the reverse relationship. It may be that something like <that_doc> appliesTo <this_doc> might work out neater. Cheers, Danny. -- http://dannyayers.com
Received on Thursday, 19 July 2007 09:03:46 UTC