Saturday, 27 February 2010
- HTML+RDFa is now a REC-track deliverable for HTML WG (was Re: HTML+RDFa is in-scope for HTML WG Charter)
- Re: ACTION-11 Proposed Short Names
- Re: ACTION-11 Proposed Short Names
- Re: ACTION-11 Proposed Short Names
Friday, 26 February 2010
- ACTION-11 Proposed Short Names
- Re: Error in RDFa generated by validator.w3.org
- Re: precedence of xml:lang and lang?
- Re: precedence of xml:lang and lang?
- Re: precedence of xml:lang and lang?
- vocabularies, token bundles, profiles (on ACTION-4)
- precedence of xml:lang and lang?
- Re: HTML+RDFa is in-scope for HTML WG Charter
Thursday, 25 February 2010
- Re: Error in RDFa generated by validator.w3.org
- Re: @profile everywhere proposal
- Error in RDFa generated by validator.w3.org
- Re: HTML+RDFa is in-scope for HTML WG Charter
- HTML+RDFa is in-scope for HTML WG Charter
- RDFa WG telecon minutes for 2010-02-25
- ISSUE-17: Coordinate with PFWG on @role and how @role integrates with RDFa
Wednesday, 24 February 2010
- Re: RDFa DOM API: Adding RDF triples to the DOM
- Re: New HTTP Link Header and Site Meta Specs
- New HTTP Link Header and Site Meta Specs
Tuesday, 23 February 2010
- Telecon Agenda - 25th February 2010, 1500 UTC
- RDFa DOM API: Adding RDF triples to the DOM
- RDFa WG Work Plan
- RDFa in OpenDocument [Re: Introduction]
- Telecon Agenda - 18th February 2010, 1500 UTC
- Introduction
- Re: @profile everywhere proposal
- Re: @profile everywhere proposal
- Re: @profile everywhere proposal
- Re: @profile everywhere proposal
- Re: @profile everywhere proposal
- Re: @profile everywhere proposal
- Re: @profile everywhere proposal
Monday, 22 February 2010
Sunday, 21 February 2010
Saturday, 20 February 2010
Friday, 19 February 2010
- @profile everywhere proposal
- Re: list-expansion in RDFa
- test version of rdfa distiller set up
- Re: RDF::RDFa::Parser 1.00 released today
- meeting minutes
Thursday, 18 February 2010
- RDF::RDFa::Parser 1.00 released today
- Re: for those who will need write access to our site (ie, future editors)
- Re: for those who will need write access to our site (ie, future editors)
- Re: Access rights for participants page
- Re: Access rights for participants page
- Access rights for participants page
- for those who will need write access to our site (ie, future editors)
- Re: RDFa Telecon time has been scheduled
- Re: Introductions
- Re: Reverted HTML+RDFa Heartbeat Draft (2010-02-18)
- Re: Reverted HTML+RDFa Heartbeat Draft (2010-02-18)
- Re: New HTML+RDFa Heartbeat Draft (2010-02-16)
- Re: Reverted HTML+RDFa Heartbeat Draft (2010-02-18)
- Reverted HTML+RDFa Heartbeat Draft (2010-02-18)
- Re: New HTML+RDFa Heartbeat Draft (2010-02-16)
- Re: New HTML+RDFa Heartbeat Draft (2010-02-16)
Wednesday, 17 February 2010
Tuesday, 16 February 2010
- Re: Introductions
- Re: Introductions
- Re: Introductions
- Re: RDFa Telecon time has been scheduled
- RDFa Telecon time has been scheduled
- Introductions
- New HTML+RDFa Heartbeat Draft (2010-02-16)
Monday, 15 February 2010
- Practicalities for the Working Group...
- Re: Finalizing the RDFa WG transition
- Re: Finalizing the RDFa WG transition
- Re: Finalizing the RDFa WG transition
- Re: Finalizing the RDFa WG transition
- Finalizing the RDFa WG transition
Monday, 8 February 2010
Sunday, 7 February 2010
- NEW - RDFa telecon times poll
- Re: RDFa telecon times
- ISSUE-16 (RDF Collections): Determine if there is a good way of supporting RDF Collections [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-14 (alternate prefix declaration mechanism): Determine if another attribute should be created to declare prefix mappings [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-12 (Benji's wishlist): Analyze Benji's wishlist and determine if there are suggestions that will improve RDFa [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-10 (@lang and @xml:lang Processing): Determine the processing order for @lang and @xml:lang [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]
- ISSUE-8 (Parsing CURIE lists): Whitespace characters that act as CURIE list delimiters should be specified [RDFa 1.1 Core]
- ISSUE-7 (RDFa Examples in Test Suite): Integrate RDFa Syntax and Primer examples into RDFa Test Suite [RDFa 1.1 Core]
- ISSUE-6 (Invalid values in @datatype): Do invalid values in @datatype cause plain literals to be generated?
- 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-4 (Normative XML namespaces document): Determine the proper XML namespaces document to refer to in the RDFa specification [RDFa 1.1 Core]
- ISSUE-3 (HTML5 Infoset coercion): Updating HTML5 coercion to Infoset rules [RDFa 1.1 in HTML5]
- ISSUE-2 (CURIEs as complete URIs): Extend RDFa to allow URIs where only CURIEs were once allowed [RDFa 1.1 Core]
- ISSUE-1 (RDFa Vocabularies): Explore providing a mechanism for extending reserved words while processing the current document [RDFa 1.1 Core]