W3C home > Mailing lists > Public > public-rdfa-wg@w3.org > January 2011

Closing RDFa API issues

From: Manu Sporny <msporny@digitalbazaar.com>
Date: Sat, 01 Jan 2011 19:45:40 -0500
Message-ID: <4D1FCAB4.50408@digitalbazaar.com>
To: RDFa WG <public-rdfa-wg@w3.org>
There are a number of issues that have been resolved as a by-product of
the RDF/RDFa API document split and re-work. There will be a number of
proposals following this e-mail that will attempt to close each of these
obsolete/resolved issues:

ISSUE-3: HTML5 Infoset coercion
Updating HTML5 coercion to Infoset rules

ISSUE-29: DOM origin generalization
RDFa API .origin property needs to be more carefully specified

ISSUE-33: RDFa API WebIDL issues
Fix all WebIDL related issues regarding RDFa API

ISSUE-43: DataParser hasFeature() method
Determine if DataParser interface needs a hasFeature("hcard") or
hasFeature("hrecipe") mechanism

ISSUE-44: Processing remote documents
Add a mechanism to the RDFa API to parse remote documents and place them
into a DataStore.

ISSUE-53: DataParser interfaces
DataParser Interface and Arguments Upgrades

ISSUE-54: DataSerializer Interface
Missing DataSerializer Interface

ISSUE-56: DataContext and setBase()
DataContext needs base for relative URI resolution

ISSUE-59: DataQuery is limited
DataQuery support for other query languages

ISSUE-61: Add vocabulary helper
Does the RDFa API need a vocabulary helper?

We'll follow the standard practice that has been established over the
past several months - giving a 7 to 14 day window to object to resolving
the issue before closing the issue in the tracker.

-- manu

Manu Sporny (skype: msporny, twitter: manusporny)
President/CEO - Digital Bazaar, Inc.
blog: Linked Data in JSON
Received on Sunday, 2 January 2011 00:46:10 UTC

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