Updated RDFa API spec

Hi folks,

I wasn't able to get in touch with Nathan today, but still went through
the entire RDFa API spec and updated it based on what I believe to be
the current direction.

http://www.w3.org/2010/02/rdfa/sources/rdfa-api/

The language was double-checked and tightened up in areas that needed
it, technical corrections were also made throughout the document.
Overall, the size of the RDFa API spec is shrinking but the overall
functionality remains high (which is really great - exactly what we
wanted to happen). Around 80% of the document is non-normative
explanation, with the interface definition (roughly 5 printed pages)
being the only normative requirement.

I also updated the concept diagram to reflect what is probably going to
happen with the RDF API:

http://www.w3.org/2010/02/rdfa/sources/rdfa-api/#concept-diagram

Merging the Projection interface with the Property Group interface went
really well - we only have Projections now and many of the interfaces
now either return Projections or DOM Elements:

http://www.w3.org/2010/02/rdfa/sources/rdfa-api/#projections

We still may decide to move the Projection and DocumentData interfaces
into the RDF API and make those the only requirements that the RDFa API
has on the RDF API. I tried to design the linkages such that we could
take the RDFa API to REC independently of the RDF API. We may or may not
end up doing it this way in the coming months. I'll need to discuss more
with Nathan, Benjamin, Mark and Ivan before making those changes.

The RDFa API document could be published as a Working Draft at this
point, but we'll probably wait a bit to make sure that Nathan and I are
synched up on the RDF API before trying to push two new WDs out.

-- manu

-- 
Manu Sporny (skype: msporny, twitter: manusporny)
President/CEO - Digital Bazaar, Inc.
blog: Payment Standards and Competition
http://digitalbazaar.com/2011/02/28/payment-standards/

Received on Saturday, 19 March 2011 20:50:16 UTC