1c1 < Status of This document --- > Status of this document 5,7c5,18 < current W3C publications and the most recently formally published < revision of this technical report can be found in the W3C technical < reports index at http://www.w3.org/TR/. --- > current W3C publications and the latest revision of this technical > report can be found in the W3C technical reports index at > http://www.w3.org/TR/. > > This is a Working Draft of the "HTML+RDFa: A mechanism for embedding > RDF in HTML" specification for review by W3C members and other > interested parties. > > This Working Draft includes the following changes: > > * Updating HTML5 coercion to Infoset rules (normative) > * Clarifying how to extract RDFa attributes via Infoset > (informative) > * Clarifying how to extract RDFa attributes via DOM2 (informative) 10,19c21,23 < to public-html-comments@w3.org (subscribe, archives) or < whatwg@whatwg.org (subscribe, archives), or submit them using our < public bug database. All feedback is welcome. < < The working groups maintains a list of all bug reports that the editor < has not yet tried to address and a list of issues for which the chairs < have not yet declared a decision. The editor also maintains a list of < all e-mails that he has not yet tried to address. These bugs, issues, < and e-mails apply to multiple HTML-related specifications, not just < this one. --- > to public-rdf-in-xhtml-tf@w3.org (subscribe, archives) or to > public-html-comments@w3.org (subscribe, archives), or submit them using > the W3C's public bug database. 24,26c28,34 < ways. Vendors interested in implementing this specification before it < eventually reaches the Candidate Recommendation stage should join the < aforementioned mailing lists and take part in the discussions. --- > ways. Vendors interested in implementing this specification should note > the status, and are encouraged to join the RDFa Working Group. > > Publication as a Working Draft does not imply endorsement by the W3C > Membership. This is a draft document and may be updated, replaced or > obsoleted by other documents at any time. It is inappropriate to cite > this document as other than work in progress. 37,70c45,51 < is always available on the W3C CVS server and in the WHATWG Subversion < repository. The latest editor's working copy (which may contain < unfinished text in the process of being prepared) contains the latest < draft text of this specification (amongst others). For more details, < please see the WHATWG FAQ. < < There are various ways to follow the change history for the HTML < specifications: < < E-mail notifications of changes < HTML-Diffs mailing list (diff-marked HTML versions for each < change): http://lists.w3.org/Archives/Public/public-html-diffs/latest < Commit-Watchers mailing list (complete source diffs): < http://lists.whatwg.org/listinfo.cgi/commit-watchers-whatwg.org < Real-time notifications of changes: < Generated diff-marked HTML versions for each change: < http://twitter.com/HTML5 < All (non-editorial) changes to the spec source: < http://twitter.com/WHATWG < Browsable version-control record of all changes: < CVSWeb interface with side-by-side diffs: < http://dev.w3.org/cvsweb/html5/ < Annotated summary with unified diffs: < http://html5.org/tools/web-apps-tracker < Raw Subversion interface: svn checkout < http://svn.whatwg.org/webapps/ < < The W3C HTML Working Group is the W3C working group responsible for < this specification's progress along the W3C Recommendation track. This < specification is the 4 March 2010 First Public Working Draft. < < The contents of this specification are also part of a specification < published by the WHATWG, which is available under a license that < permits reuse of the specification text. --- > is always available on the W3C CVS server. The latest editor's working > copy (which may contain unfinished text in the process of being > prepared) is also available. > > This specification has been jointly developed by the RDFa Task Force > and the HTML Working Group and is currently being published by the HTML > Working Group to further discussions there.