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

RDFa API Super-session

From: Manu Sporny <msporny@digitalbazaar.com>
Date: Tue, 30 Nov 2010 11:08:07 -0500
Message-ID: <4CF52167.5020008@digitalbazaar.com>
To: RDFa WG <public-rdfa-wg@w3.org>
On 11/30/2010 12:20 AM, Manu Sporny wrote:
> 1) RDFa API Super-session
>    * Should we try to meet for 2 hours, and get through
>      as much of the RDFa API as possible?

Hi folks,

Nathan and I have had a few chats off-line to discuss the progress of
the RDFa API document. Both of us feel that we're not cranking through
issues fast enough and that we need to make a full sweep through the
RDFa API document in order to get a new Editors Draft out.

Nathan's also getting pressure from some of the RDF folks to produce a
solid RDF API (which just so happens to be embedded in the RDFa API).
The problem is that some of the issues that we've resolved over the past
few weeks have made parts of the document just plain wrong. There are
also some really neat approaches that Nathan has taken in his new JS3[1]
library that could really benefit the RDFa API.

We could raise issues for each of these and proceed in that manner, but
I'm afraid that if we do that, it could be weeks or months added to our
timeline. So, perhaps the better way forward is to present what Nathan,
myself, and whoever else wants to join, feel is the ideal path forward
and see if the rest of this community agrees.

We'd present a revised RDFa API document (which will carry much of the
old work forward, but reformulate it in a way that gels with the
direction we're headed, based on the way that we've been resolving
issues thus far).

There is an upcoming agenda item to discuss this approach, but I thought
I'd throw this out there to get feedback before Thursday. If there is no
strong objection, a group of us would have a break-out design session
over this weekend and would have a solid RDFa API proposal document by
next week.

We think that this will accomplish what would normally take us roughly 2
months to get through. Folks would still have the opportunity to object
or raise issues on the new document if the group decides that it would
like to go in that direction.

-- manu


Manu Sporny (skype: msporny, twitter: manusporny)
President/CEO - Digital Bazaar, Inc.
blog: Linked Data in JSON
Received on Tuesday, 30 November 2010 16:08:38 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 17:05:22 UTC