ISSUE-1 compare and contrast Vocabularies and Profiles proposals

Ivan has already compared/contrasted the vocabulary proposal[1] and
profiles proposal[2] in a previous thread[3]. I'll try and highlight the
differences using less words and in a way that may help those that
aren't heavily involved in this area to grasp the core differences
between the current proposals. The hope is that this list will drive
discussion on ISSUE-1 and ISSUE-11:

Vocabulary Proposal[1]:

* Use @vocab attribute to extend reserved keywords
* @vocab document marked up in RDFa
* @vocab document uses "rdfa:" vocabulary to express reserved keywords
* Last reserved word definition wins
* There is no default RDFa vocabulary
* Does not support recursive inclusion of other @vocabs
* Does not depend on @profile being re-instated in HTML5
* Does not address ISSUE-11
* Requires CORS support for Javascript implementations

Profiles Proposal[2]:

* Use @profile attribute to extend reserved words AND declare prefixes
* @profile document marked up in RDFa or JSON
* @profile document uses "xmlns:" to express reserved words/prefixes
* Last reserved word/prefix definition wins
* There is no default RDFa profile
* Supports recursive inclusion of other @profiles
* Depends on @profile being re-instated in HTML5
* Does not address ISSUE-11
* Requires CORS support for profiles that are not specified in JSON

Items that are in neither proposal that we should consider supporting:

* There should be a default RDFa vocabulary/profile
* The default RDFa vocabulary/profile should only be used when there is
  no active @vocab/@profile.
* Default profile would address ISSUE-11

Is this a complete list of each proposal's key points as well as the
more recent concerns with ISSUE-11 that have been raised?

-- manu

[1]http://rdfa.digitalbazaar.com/specs/rdfa-vocab-20100111.html
[2]http://webbackplane.com/mark-birbeck/blog/2010/02/vocabularies-token-bundles-profiles-rdfa
[3]http://lists.w3.org/Archives/Public/public-rdfa-wg/2010Feb/0090.html

-- 
Manu Sporny (skype: msporny, twitter: manusporny)
President/CEO - Digital Bazaar, Inc.
blog: PaySwarming Goes Open Source
http://blog.digitalbazaar.com/2010/02/01/bitmunk-payswarming/

Received on Thursday, 4 March 2010 04:22:52 UTC