from February 2010 by subject

@profile everywhere proposal

Access rights for participants page

ACTION-11 Proposed Short Names

Error in RDFa generated by

Finalizing the RDFa WG transition

for those who will need write access to our site (ie, future editors)

HTML+RDFa is in-scope for HTML WG Charter

HTML+RDFa is now a REC-track deliverable for HTML WG (was Re: HTML+RDFa is in-scope for HTML WG Charter)



ISSUE-1 (RDFa Vocabularies): Explore providing a mechanism for extending reserved words while processing the current document [RDFa 1.1 Core]

ISSUE-10 (@lang and @xml:lang Processing): Determine the processing order for @lang and @xml:lang [RDFa 1.1 Core]

ISSUE-11 (Default prefix declarations): Determine if there is a subset of popular prefix declarations that should be enabled in all RDFa Processors [RDFa 1.1 Core]

ISSUE-12 (Benji's wishlist): Analyze Benji's wishlist and determine if there are suggestions that will improve RDFa [RDFa 1.1 Core]

ISSUE-13 (empty @typeof creates bnode): Determine if an empty @typeof attribute should create a bnode [RDFa 1.1 Core]

ISSUE-14 (alternate prefix declaration mechanism): Determine if another attribute should be created to declare prefix mappings [RDFa 1.1 Core]

ISSUE-15 (@version attribute in HTML5): RDFa may not have access to the @version attribute in HTML5 [RDFa 1.1 in HTML5]

ISSUE-16 (RDF Collections): Determine if there is a good way of supporting RDF Collections [RDFa 1.1 Core]

ISSUE-17: Coordinate with PFWG on @role and how @role integrates with RDFa

ISSUE-2 (CURIEs as complete URIs): Extend RDFa to allow URIs where only CURIEs were once allowed [RDFa 1.1 Core]

ISSUE-3 (HTML5 Infoset coercion): Updating HTML5 coercion to Infoset rules [RDFa 1.1 in HTML5]

ISSUE-4 (Normative XML namespaces document): Determine the proper XML namespaces document to refer to in the RDFa specification [RDFa 1.1 Core]

ISSUE-5 (@datatype and rdf:XMLLiteral): Clarify the case where the rdf: prefix is bound to another namespace and used in @datatype [RDFa 1.1 Core]

ISSUE-6 (Invalid values in @datatype): Do invalid values in @datatype cause plain literals to be generated?

ISSUE-7 (RDFa Examples in Test Suite): Integrate RDFa Syntax and Primer examples into RDFa Test Suite [RDFa 1.1 Core]

ISSUE-8 (Parsing CURIE lists): Whitespace characters that act as CURIE list delimiters should be specified [RDFa 1.1 Core]

ISSUE-9 (Subject declaration best practices): Provide guidance when specifying subjects via @about, @id, pages and concepts in pages [RDFa Usage Cookbook]

list-expansion in RDFa

meeting minutes

NEW - RDFa telecon times poll

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

New HTTP Link Header and Site Meta Specs

Practicalities for the Working Group...

precedence of xml:lang and lang?

RDF::RDFa::Parser 1.00 released today

RDFa DOM API: Adding RDF triples to the DOM

RDFa in OpenDocument [Re: Introduction]

RDFa Telecon time has been scheduled

RDFa telecon times

RDFa Test Harness permanently moved to Test Suite

RDFa WG telecon minutes for 2010-02-25

RDFa WG Work Plan

Reverted HTML+RDFa Heartbeat Draft (2010-02-18)

Telecon Agenda - 18th February 2010, 1500 UTC

Telecon Agenda - 25th February 2010, 1500 UTC

test version of rdfa distiller set up

vocabularies, token bundles, profiles (on ACTION-4)

Last message date: Saturday, 27 February 2010 18:19:42 UTC