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

New HTML+RDFa Heartbeat Draft (2010-02-16)

From: Manu Sporny <msporny@digitalbazaar.com>
Date: Tue, 16 Feb 2010 09:20:43 -0500
Message-ID: <4B7AA9BB.9000405@digitalbazaar.com>
To: Public RDFa WG <public-rdfa-wg@w3.org>
I forgot to cc this mailing list about the new HTML+RDFa draft that was
posted last night...

There is a new HTML+RDFa draft available that includes all of the bugs
logged against the "HTML+RDFa" project in W3C Bugzilla as of right now.
This draft attempts to resolve the publication issues raised with the
latest heartbeat requirement, namely:

* Larry's concerns over the Status of this Document section.
   * The concerns are now highlighted as bugs in the "Status" marker
     for the SotD section.
* Julian and Larry's concern that SotD sections be kept consistent
  between documents.
   * The HTML+RDFa SotD section's language has been reverted to the
     previous version, which should be in-line with the HTML5 spec,
     as well as the Microdata spec.
* Numerous participants concern that bug/issue reporting is done in
  a manner that is as unbiased as possible.
   * For HTML+RDFa, the status markers are generated directly from
     W3C's Bugzilla list.

Many thanks to Maciej for reviewing the HTML+RDFa spec a few days ago
and entering the (20+) bugs into Bugzilla... it made annotating the RDFa
bugs and getting this done much faster.

Reading the new spec

The new draft is available here:


Diff-marked version is here:


Remaining issues

The XML that is kicked out from W3C Bugzilla for bug #7670 is malformed,
causing the script to fail to include that one particular bug. The bug
states that "the use of prefixes are too complicated for the web". I
don't think that this should stop WD heartbeat publication for HTML+RDFa.

How it works

This is how the new in-spec bug status reporting works:

1. A spec reviewer files a bug against the HTML+RDFa specification.
2. The spec editor reviews the bug and accepts it, adding a comment like
   the following to the bug:
      RDFA-SPEC-SECTIONS [conformance-requirements parsing-model]
3. When the HTML+RDFa spec is generated, the entire bug list is
   downloaded from the W3C bug tracker and parsed for
   "RDFA-SPEC-SECTION" comments. If spec sections are found that should
   be annotated with the bug status, markers are created at the
   beginning of each section.

The script I hacked together tonight that does the specification bug
status markers is available here:


The script is run as the last item in the specification generation
toolchain. The specbugs script would need very minor modifications to
run against all of the specs that are currently being published via the

-- manu

Manu Sporny (skype: msporny, twitter: manusporny)
President/CEO - Digital Bazaar, Inc.
blog: PaySwarming Goes Open Source
Received on Tuesday, 16 February 2010 14:21:12 UTC

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