- From: Manu Sporny <msporny@digitalbazaar.com>
- Date: Sun, 30 Jan 2011 12:16:47 -0500
- To: RDFA Working Group <public-rdfa-wg@w3.org>
On 01/30/2011 11:34 AM, Nathan wrote: > I didn't realise @rev was "entirely obsolete, and must not be used by > authors" in html5 ? HTML+RDFa re-introduces @rev - which is allowed since the RDFa spec layers on top of the HTML spec and can thus make modifications to the language. This is allowed per this text in the HTML5 spec: """ When vendor-neutral extensions to this specification are needed, either this specification can be updated accordingly, or an extension specification can be written that overrides the requirements in this specification. When someone applying this specification to their activities decides that they will recognize the requirements of such an extension specification, it becomes an applicable specification for the purposes of conformance requirements in this specification. """ Only supporting @rel would require every vocabulary out there to specify two uni-directional properties - for example: Instead of just: ex:owns without @rev, you would need: ex:owns ex:belongsTo Having two vocab terms instead of one makes reasoning more complicated. We also need @rev there for backwards-compat reasons. > issue? Not an issue unless someone can think of a technical reason that supporting @rev would cause in HTML. If someone would want to remove @rev - we would create a backwards-compat issue and that would generate far more objections than keeping it in there. Unless there are any objections, I'm not going to raise an issue for this. -- manu -- Manu Sporny (skype: msporny, twitter: manusporny) President/CEO - Digital Bazaar, Inc. blog: Linked Data in JSON http://digitalbazaar.com/2010/10/30/json-ld/
Received on Sunday, 30 January 2011 17:17:16 UTC