W3C home > Mailing lists > Public > public-rdfa-wg@w3.org > March 2010

ISSUE-1: Status of RDFa Profiles

From: Manu Sporny <msporny@digitalbazaar.com>
Date: Thu, 11 Mar 2010 12:01:59 -0500
Message-ID: <4B992207.9020501@digitalbazaar.com>
To: RDFa WG <public-rdfa-wg@w3.org>
During the call, Ivan made the point that it would be good to have the
RDFa Profiles mechanism in the First Published Working Draft of RDFa 1.1
Core that is due in just three weeks. I think most would agree with that

We seem to be narrowing in on the set of features that we want to
support. Most of these items were discussed on the call today.

Here are the things that we may have consensus on:

* Moving forward, we should call this proposal "RDFa Profiles" and drop
  the "RDFa Vocabularies" moniker.
* RDFa profiles are specified in an external document (profile document)
* We should use the @profile attribute to specify the profile document
* The @profile attribute can be placed on any element and is scoped
  to the element on which it is defined and its children
* The profile document is marked up in RDFa, using a vocabulary
  designed to modify the behavior of the RDFa Processor
* The profile document can specify both tokens and prefixes
* One does not use xmlns: to declare prefixes and tokens because those
  definitions may leak into the author's document.

Here are the things that we still have to discuss:

* What happens when you can't dereference the profile document?
  (Toby's proposal)
* Are we limiting next/prev/index/license/etc to @rel/@rev or allowing
  them everywhere?
* What is the mental model are tokens/prefixes two different concepts
  in RDFa or are they the same thing?
* Are there backwards compatibility issues with the proposed path
* There seems to be strong opposition for using JSON to express the
  profile documents.
* The default profile document can be specified in the RDFa Core spec.
  This document will outline what prefixes and tokens are pre-defined.

I will break the larger topics topics into different e-mails so that we
can have most of the discussions in parallel. The goal is to have a
fairly good RDFa Profiles proposal by next week and integrate that into
the RDFa Core specification the week after that.

-- manu

Manu Sporny (skype: msporny, twitter: manusporny)
President/CEO - Digital Bazaar, Inc.
blog: PaySwarming Goes Open Source
Received on Thursday, 11 March 2010 17:02:28 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:19:46 UTC