PROPOSAL to close ISSUE-34: meta-name triple generation

If there are no objections to this proposal in 7 days, we will close
ISSUE-34: meta-name triple generation.

http://www.w3.org/2010/02/rdfa/track/issues/34

This issue raises the question of whether or not RDFa Core's processing
rules should recognize the META element's @name attribute when
generating triples.

There are a number of arguments against doing this at present:

1. One can already place @property on the META element in order to
   generate triples.
2. Adding processing of @name would further complicate the RDFa
   processing rules, which are already very complicated from the
   standpoint of someone new to RDFa.
3. Adding processing of the @name attribute doesn't seem to be
   something that has heavy demand (as opposed to things like
   "deprecating" xmlns: and adding RDFa Profiles).
4. Facebook's OGP uses @property, not @name - when this issue
   was first raised, there was concern that they would use @name
   instead of @property. This is no longer a concern since they
   use @property.
5. There is nothing preventing RDFa Processors from processing
   @name in addition to all of the other RDFa Core attributes.
   Why not wait to see if this is a widely implemented feature
   before placing it into the specification?

There is really only one argument (that I can see) in favor of adding
support for @name:

1. Providing an HTML-native mechanism for generating triples
   from HTML document metadata.

I propose that we do not add support for @name in RDFa Core and close
ISSUE-34.

Please comment in 7 days from this post if you object to this proposal.
If there are no objections within 7 days, ISSUE-34 will be closed

-- manu

-- 
Manu Sporny (skype: msporny, twitter: manusporny)
President/CEO - Digital Bazaar, Inc.
blog: WebID - Universal Login for the Web
http://blog.digitalbazaar.com/2010/08/07/webid/2/

Received on Sunday, 5 September 2010 14:26:50 UTC