- From: Ben Adida <ben@mit.edu>
- Date: Mon, 12 Dec 2005 11:38:34 -0500
- To: public-rdf-in-xhtml task force <public-rdf-in-xhtml-tf@w3.org>
This email begins the discussion for Issue #12 from our issues list [1]. Issue #12 is found at: http://www.w3.org/2001/sw/BestPractices/HTML/2005-current- issues#curies-in-predicates Briefly, the issue is about the datatype of the rel,rev, and property attributes. Clearly, the href attribute must be CURIE/URI, since URIs are required for backwards compatibility. For symmetry, it seems we have agreed that about should also be CURIE/URI (though this is certainly up for debate if people disagree.) The question is: should rel,rev, property also be CURIE/URI, or should they be CURIE only. The general arguments are: 1) CURIE/URI: consistency with other attributes: ==== This document is licensed under a <a rel="[cc:license]" href="[cclicenses:by-nc-sa/2.5/]">CC license</a>. ==== or ==== This document is licensed under a <a rel="[cc:license]" href="http:// creativecommons.org/licenses/by-nc/2.5/">CC license</a>. ==== or ==== This document is licensed under a <a rel="http://web.resource.org/cc/ license" href="http://creativecommons.org/licenses/by-nc/2.5/">CC license</a>. ==== or ==== This document is licensed under a <a rel="http://web.resource.org/cc/ license" href="[cclicenses:by-nc-sa/2.5/]">CC license</a>. ==== 2) CURIE only: removes the need to use special syntax like [cc:license] for distinguishing CURIEs and URIs. This is particularly useful for some level of backwards compatibility with HTML-built-in values for rel, specifically rel=next, rel=prev, etc... ==== This document is licensed under a <a rel="cc:license" href="http:// creativecommons.org/licenses/by-nc/2.5/">CC license</a>. ==== or ==== This document is licensed under a <a rel="cc:license" href="[cclicenses:by-nc-sa/2.5/]">CC license</a>. ==== Thoughts? -Ben
Received on Monday, 12 December 2005 16:38:46 UTC