Moving HTML+RDFa draft issues to HTML WG bug tracker

As promised to Paul Cotton on last Thursday's telecon, here is the link
to the RDFa Task Force Issue Tracker:

This is actually the Semantic Web Deployment issue tracker, which
contains a product called "RDFa". I believe that Paul and Maciej would
prefer that all of the current HTML+RDFa issues noted on the RDFa wiki:

are entered as bugs in the HTML WG bug tracker:

before being escalated to ISSUES in the HTML WG or RDFa ISSUE tracker.
Ben had asked what we wanted the bug reporting process to be for
entering and escalating bugs while working with the HTML WG. Here's the
current plan:

1. All HTML+RDFa WD spec bugs should be entered in the HTML WG tracker.
   I'll try to close them out as quickly as I can.
2. If I close a bug and the submitter feels that the bug was not
   addressed, and it is clear that I won't address the submitter's
   concerns, the submitter should raise the item as an ISSUE on the HTML
   WG or RDFa TF ISSUE tracker (URLs listed above).
3. Once an ISSUE is raised on the HTML WG or RDFa TF tracker, the
   respective group should formally address the issue and create
   a resolution.
4. Once there is a resolution to an ISSUE, the HTML+RDFa specification
   will be updated to reflect that resolution.

To ensure that we don't drop any of these bugs or issues on the floor,
I'm volunteering to keep an eye on the bugs and issues as they make
their way through both the HTML WG and RDFa TF systems.

-- manu

Manu Sporny (skype: msporny, twitter: manusporny)
President/CEO - Digital Bazaar, Inc.
blog: The Pirate Bay and Building an Equitable Culture

Received on Saturday, 26 September 2009 14:35:30 UTC