Telecon Agenda - March 3rd 2011, 1400 UTC
ISSUE-86 (prefixes and terms): Determine if prefixes and terms can be collapsed into one concept in the RDFa API [RDF API]
ISSUE-85 (projections and property groups): Determine whether both Projections and PropertyGroups are necessary [RDFa 1.1 API]
A mnemonic for learning RDFa : APRIL
RDFa WG telecon minutes for 2011-02-24
terms and prefixes are the same in rdflib
ISSUE-81: Specification Structure, Part 3.
ISSUE-80: Specification Structure, Part 2.
ISSUE-79: Specification Structure, Part 1.
'registering' other formats?
HTML WG ISSUE-120 - Counter Arguments
Telecon Agenda - February 24th 2011, 1400 UTC
Please get your AC rep to vote
Last Call Response to ISSUE-73: RDFa Profile management
- Re: Last Call Response to ISSUE-73: RDFa Profile management
RDFa Default Profile Management/Vocabularies/Authoring
- Re: RDFa Default Profile Management/Vocabularies/Authoring
- Re: RDFa Default Profile Management/Vocabularies/Authoring
- Comments on the profile management (Re: RDFa Default Profile Management/Vocabularies/Authoring)
Re: ISSUE-67 triage
ISSUE-70: Formal Response
ISSUE-70: PROPOSED response to Jeni
Default profile files installed
RDFa WG telecon minutes for 2011-02-17
FYI: renewed RDFa Charter
Telecon Agenda - February 17th 2011, 1400 UTC
Last Call comment (ISSUE-77) : default blank node generation in the header
GRDDL and XHTML+RDFa 1.1
RDFa WG telecon minutes for 2011-02-14
ISSUE-65: Michael Hausenblas' editorial comments (was Re: LC comments on RDFa Core 1.1)
RDFa Super Session II: The Last Calling
prefixes for the default rdfa profile (related to ACTION-62 )
Profile URI-s
RDFa WG telecon minutes for 2011-02-10
Proposal about xmlns
PROPOSAL to address RDFa Profiles - ISSUE-73 and ISSUE-78
- Re: PROPOSAL to address RDFa Profiles - ISSUE-73 and ISSUE-78
- Re: PROPOSAL to address RDFa Profiles - ISSUE-73 and ISSUE-78
Editorial changes to clarify usage of URIs / Absolute URIs and @profile
- Re: Editorial changes to clarify usage of URIs / Absolute URIs and @profile
- Re: Editorial changes to clarify usage of URIs / Absolute URIs and @profile
- Re: Editorial changes to clarify usage of URIs / Absolute URIs and @profile
- Re: Editorial changes to clarify usage of URIs / Absolute URIs and @profile
- Re: Editorial changes to clarify usage of URIs / Absolute URIs and @profile
- Re: Editorial changes to clarify usage of URIs / Absolute URIs and @profile
- Re: Editorial changes to clarify usage of URIs / Absolute URIs and @profile
- Re: Editorial changes to clarify usage of URIs / Absolute URIs and @profile
Telecon Agenda - February 10th 2011, 1400 UTC
ISSUE-84 (Cool URIs and HTTPRange-14): The W3C TAG has asked us to mention that the use of fragment identifiers can be problematic [LC Comment - RDFa Core 1.1]
- Re: ISSUE-84 (Cool URIs and HTTPRange-14): The W3C TAG has asked us to mention that the use of fragment identifiers can be problematic [LC Comment - RDFa Core 1.1]
- Re: ISSUE-84 (Cool URIs and HTTPRange-14): The W3C TAG has asked us to mention that the use of fragment identifiers can be problematic [LC Comment - RDFa Core 1.1]
- Re: ISSUE-84 (Cool URIs and HTTPRange-14): The W3C TAG has asked us to mention that the use of fragment identifiers can be problematic [LC Comment - RDFa Core 1.1]
- Re: ISSUE-84 (Cool URIs and HTTPRange-14): The W3C TAG has asked us to mention that the use of fragment identifiers can be problematic [LC Comment - RDFa Core 1.1]
- Re: ISSUE-84 (Cool URIs and HTTPRange-14): The W3C TAG has asked us to mention that the use of fragment identifiers can be problematic [LC Comment - RDFa Core 1.1]
- Re: ISSUE-84 (Cool URIs and HTTPRange-14): The W3C TAG has asked us to mention that the use of fragment identifiers can be problematic [LC Comment - RDFa Core 1.1]
- Re: ISSUE-84 (Cool URIs and HTTPRange-14): The W3C TAG has asked us to mention that the use of fragment identifiers can be problematic [LC Comment - RDFa Core 1.1]
- Re: ISSUE-84 (Cool URIs and HTTPRange-14): The W3C TAG has asked us to mention that the use of fragment identifiers can be problematic [LC Comment - RDFa Core 1.1]
- Re: ISSUE-84 (Cool URIs and HTTPRange-14): The W3C TAG has asked us to mention that the use of fragment identifiers can be problematic [LC Comment - RDFa Core 1.1]
- Re: ISSUE-84 (Cool URIs and HTTPRange-14): The W3C TAG has asked us to mention that the use of fragment identifiers can be problematic [LC Comment - RDFa Core 1.1]
- Re: ISSUE-84 (Cool URIs and HTTPRange-14): The W3C TAG has asked us to mention that the use of fragment identifiers can be problematic [LC Comment - RDFa Core 1.1]
- Re: ISSUE-84 (Cool URIs and HTTPRange-14): The W3C TAG has asked us to mention that the use of fragment identifiers can be problematic [LC Comment - RDFa Core 1.1]
- Re: ISSUE-84 (Cool URIs and HTTPRange-14): The W3C TAG has asked us to mention that the use of fragment identifiers can be problematic [LC Comment - RDFa Core 1.1]
Official response to your LC comment (recorded as ISSUE-69)
Clarification on the resolution of ISSUE-69
Proposal, allow Colon in a Term
RDFa Default Profile Management
- Re: RDFa Default Profile Management
Preparing Official LC Responses
Last Call response for ISSUE-71: LC Comments from Shelley Powers
Last Call Response to ISSUE-63: Case-insensitive term matching
Last Call Response to ISSUE-46: Conversion of Plain Literals to IRIs
TERMorCURIEorAbsURIs definition problem
ISSUE-83 (CURIEs must require colon): CURIEs are dangerous when used in combination with @vocab and @about [LC Comment - RDFa Core 1.1]
- Re: ISSUE-83 (CURIEs must require colon): CURIEs are dangerous when used in combination with @vocab and @about [LC Comment - RDFa Core 1.1]
- Re: ISSUE-83 (CURIEs must require colon): CURIEs are dangerous when used in combination with @vocab and @about [LC Comment - RDFa Core 1.1]
- Re: ISSUE-83 (CURIEs must require colon): CURIEs are dangerous when used in combination with @vocab and @about [LC Comment - RDFa Core 1.1]
- Re: ISSUE-83 (CURIEs must require colon): CURIEs are dangerous when used in combination with @vocab and @about [LC Comment - RDFa Core 1.1]
- Re: ISSUE-83 (CURIEs must require colon): CURIEs are dangerous when used in combination with @vocab and @about [LC Comment - RDFa Core 1.1]
- Re: ISSUE-83: CURIEs must require colon
Problem(s) .. Prefix, colon, CURIE and term
Built-in infinite recursion in our spec? (related to ISSUE-73 and ISSUE-78)
- Re: Built-in infinite recursion in our spec? (related to ISSUE-73 and ISSUE-78)
- Re: Built-in infinite recursion in our spec? (related to ISSUE-73 and ISSUE-78)