Tuesday, 31 August 2010
Sunday, 29 August 2010
- Re: A possible design to incorporate collections and containers into RDFa? [ISSUE-16]
- Re: A possible design to incorporate collections and containers into RDFa? [ISSUE-16]
- Re: A possible design to incorporate collections and containers into RDFa? [ISSUE-16]
Saturday, 28 August 2010
- Re: A possible design to incorporate collections and containers into RDFa?
- Re: A possible design to incorporate collections and containers into RDFa? [ISSUE-16]
- Re: Question about RDFa processing rule 8 (@typeof)
- Re: Question about RDFa processing rule 8 (@typeof)
- Re: A possible design to incorporate collections and containers into RDFa? [ISSUE-16]
- Fwd: A possible design to incorporate collections and containers into RDFa?
Friday, 27 August 2010
- Re: A possible design to incorporate collections and containers into RDFa?
- Question about RDFa processing rule 8 (@typeof)
Thursday, 26 August 2010
- RDFa WG telecon minutes for 2010-08-26
- Re: Telecon Agenda - August 26th 2010, 1400 UTC
- Re: Format of @profile files (summarizing ISSUE-39, maybe moving forward...)
Wednesday, 25 August 2010
- Re: Format of @profile files (summarizing ISSUE-39, maybe moving forward...)
- A possible design to incorporate collections and containers into RDFa?
Tuesday, 24 August 2010
- Re: How are default profiles normatively established?
- Re: How are default profiles normatively established?
- Re: How are default profiles normatively established?
- Re: Format of @profile files (summarizing ISSUE-39, maybe moving forward...)
- Re: Format of @profile files (summarizing ISSUE-39, maybe moving forward...)
- Re: How are default profiles normatively established?
Monday, 23 August 2010
- Re: Format of @profile files (summarizing ISSUE-39, maybe moving forward...)
- Re: Format of @profile files (summarizing ISSUE-39, maybe moving forward...)
- How are default profiles normatively established?
- Format of @profile files (summarizing ISSUE-39, maybe moving forward...)
- Telecon Agenda - August 26th 2010, 1400 UTC
Friday, 20 August 2010
- Re: RDFa API - new editor's draft and ISSUE-33
- Re: RDFa API - new editor's draft and ISSUE-33
- Re: RDFa API - new editor's draft and ISSUE-33
- Re: RDFa API - new editor's draft and ISSUE-33
Thursday, 19 August 2010
- Re: longdesc URLs and RDFa
- Re: Telecon Agenda - August 19th 2010, 1400 UTC
- Re: RDFa API - new editor's draft and ISSUE-33
Wednesday, 18 August 2010
- Re: longdesc URLs and RDFa
- Re: longdesc URLs and RDFa
- Re: longdesc URLs and RDFa
- Re: longdesc URLs and RDFa
- Re: longdesc URLs and RDFa
- Re: longdesc URLs and RDFa
- Re: longdesc URLs and RDFa
- Re: longdesc URLs and RDFa
- Re: longdesc URLs and RDFa
- Re: longdesc URLs and RDFa
- Re: longdesc URLs and RDFa
- Re: longdesc URLs and RDFa
- Re: longdesc URLs and RDFa
- Re: longdesc URLs and RDFa
- Re: longdesc URLs and RDFa
- Re: longdesc URLs and RDFa
- Re: longdesc URLs and RDFa
- Re: longdesc URLs and RDFa
- Re: longdesc URLs and RDFa
- Re: longdesc URLs and RDFa
- Re: longdesc URLs and RDFa
- Re: longdesc URLs and RDFa
- Re: @cite (was: longdesc URLs and RDFa(
- Re: longdesc URLs and RDFa
- Re: @cite (was: longdesc URLs and RDFa(
- @cite (was: longdesc URLs and RDFa(
Tuesday, 17 August 2010
- Re: Telecon Agenda - August 19th 2010, 1400 UTC
- Re: longdesc URLs and RDFa
- RDFa API - new editor's draft
Monday, 16 August 2010
- Re: longdesc URLs and RDFa
- Re: longdesc URLs and RDFa
- Re: longdesc URLs and RDFa
- Re: longdesc URLs and RDFa
- Re: XHTML+RDFa DTD UA support (Was: Getting the XHTML+RDFa default profile to be interesting)
- Re: XHTML+RDFa DTD UA support (Was: Getting the XHTML+RDFa default profile to be interesting)
- Re: XHTML+RDFa DTD UA support (Was: Getting the XHTML+RDFa default profile to be interesting)
- Re: XHTML+RDFa DTD UA support (Was: Getting the XHTML+RDFa default profile to be interesting)
- Re: XHTML+RDFa DTD UA support (Was: Getting the XHTML+RDFa default profile to be interesting)
- XHTML+RDFa DTD UA support (Was: Getting the XHTML+RDFa default profile to be interesting)
Sunday, 15 August 2010
- Telecon Agenda - August 19th 2010, 1400 UTC
- Re: Getting the XHTML+RDFa default profile to be interesting
- Re: longdesc URLs and RDFa
- Re: longdesc URLs and RDFa
- Re: Getting the XHTML+RDFa default profile to be interesting
- Re: longdesc URLs and RDFa
- Re: longdesc URLs and RDFa
- Re: Getting the XHTML+RDFa default profile to be interesting
- Re: longdesc URLs and RDFa
- ISSUE-45 (cite and longdesc support): Consider supporting cite and longdesc attributes in XHTML+RDFa and HTML+RDFa [RDFa 1.1 in XHTML 1.1]
Saturday, 14 August 2010
- Re: longdesc URLs and RDFa
- Re: longdesc URLs and RDFa
- Re: longdesc URLs and RDFa
- Re: longdesc URLs and RDFa
- Re: longdesc URLs and RDFa
- Re: longdesc URLs and RDFa
- Re: longdesc URLs and RDFa
- Re: longdesc URLs and RDFa
- Re: longdesc URLs and RDFa
- Re: longdesc URLs and RDFa
- Re: longdesc URLs and RDFa
- longdesc URLs and RDFa
Friday, 13 August 2010
- Getting the XHTML+RDFa default profile to be interesting
- Re: further on ISSUE-39
- Re: further on ISSUE-39
- Re: further on ISSUE-39
- Re: further on ISSUE-39
- Re: further on ISSUE-39
- Re: Re: further on ISSUE-39
- RDFa WG telecon minutes for 2010-08-12
Thursday, 12 August 2010
- Re: ISSUE-42: RDFa API should use 'string' instead of 'DOMString' in the WebIDL
- Re: Comment on RDFa 1.1 Core: Profiles, term mappings, and URIs as literals (ISSUE-39)
- Re: ISSUE-44: Add a mechanism to the RDFa API to parse remote documents and place them into a DataStore.
- Re: ISSUE-43: Determine if DataParser interface needs a hasFeature("hcard") or hasFeature("hrecipe") mechanism.
- Re: ISSUE-29: Proposal to resolve DOM origin generalization
- ISSUE-44: Add a mechanism to the RDFa API to parse remote documents and place them into a DataStore.
- ISSUE-43: Determine if DataParser interface needs a hasFeature("hcard") or hasFeature("hrecipe") mechanism.
- Re: Re:
- ISSUE-42: RDFa API should use 'string' instead of 'DOMString' in the WebIDL
- Re: Comment on RDFa 1.1 Core: Profiles, term mappings, and URIs as literals (ISSUE-39)
- Re:
- Re: Comment on RDFa 1.1 Core: Profiles, term mappings, and URIs as literals (ISSUE-39)
- Re:
- Re: ISSUE-29: Proposal to resolve DOM origin generalization
- Re: Comment on RDFa 1.1 Core: Profiles, term mappings, and URIs as literals (ISSUE-39)
- Re: Comment on RDFa 1.1 Core: Profiles, term mappings, and URIs as literals (ISSUE-39)
- Re:
- [public-rdfa-wg] <none>
- ISSUE-29: Proposal to resolve DOM origin generalization
Monday, 9 August 2010
- ISSUE-28: Proposal to resolve Nathan's issue
- Re: CURIE and URI Processing vs Processor Status Warning
- Telecon Agenda - August 12th 2010, 1400 UTC
Sunday, 8 August 2010
- CURIE and URI Processing vs Processor Status Warning
- Re: Comment on RDFa 1.1 Core: Profiles, term mappings, and URIs as literals (ISSUE-39)
Saturday, 7 August 2010
Friday, 6 August 2010
- (Resending for tracker: ISSUE-39) Re: Comment on RDFa 1.1 Core: Profiles, term mappings, and URIs as literals
- Re: Comment on RDFa 1.1 Core: Profiles, term mappings, and URIs as literals
Thursday, 5 August 2010
- Re: Handling of missing @profile
- Re: Handling of missing @profile
- RDFa WG telecon minutes for 2010-08-05
- Re: ISSUE-40 Comment on RDFa 1.1 Core: Empty elements should not create literals
- Re: ISSUE-29: Re: When is equal and when is it nonequal (eg, the IRI interface)
- Re: Javascript prefix mapping via closures...
- Re: Comment on RDFa 1.1 Core: Empty elements should not create literals
- Javascript prefix mapping via closures...
- Re: ISSUE-29: Re: When is equal and when is it nonequal (eg, the IRI interface)
- Re: Comment on RDFa 1.1 Core: Empty elements should not create literals
- Re: Comment on RDFa 1.1 Core: Empty elements should not create literals
- ISSUE-41 (processor graph vocabulary): Processor Graph Vocabulary is under-defined [RDFa 1.1 Core]
- Re: Comment on RDFa 1.1 Core: Nested RDFa markup
- Re: ISSUE-29: Re: When is equal and when is it nonequal (eg, the IRI interface)
- Re: ISSUE-29: Re: When is equal and when is it nonequal (eg, the IRI interface)
- ISSUE-40 (no triples for empty elements): Empty elements should not create literals [RDFa 1.1 Core]
- ISSUE-39 (rdfa term mapping triples): Profiles, term mappings, and URIs as literals [RDFa 1.1 Core]
- Re: ISSUE-29: Re: When is equal and when is it nonequal (eg, the IRI interface)
- Re: ISSUE-29: Re: When is equal and when is it nonequal (eg, the IRI interface)
- Re: Comment on RDFa 1.1 Core: Empty elements should not create literals
- Re: Comment on RDFa 1.1 Core: Empty elements should not create literals
- Re: Comment on RDFa 1.1 Core: Profiles, term mappings, and URIs as literals
- Re: ISSUE-29: Re: When is equal and when is it nonequal (eg, the IRI interface)
- Re: Comment on RDFa 1.1 Core: Profiles, term mappings, and URIs as literals
- Comment on RDFa 1.1 Core: Nested RDFa markup
- Comment on RDFa 1.1 Core: Empty elements should not create literals
- Comment on RDFa 1.1 Core: Profiles, term mappings, and URIs as literals
- Re: ISSUE-29: Re: When is equal and when is it nonequal (eg, the IRI interface)
- Re: ISSUE-29: Re: When is equal and when is it nonequal (eg, the IRI interface)
- Processor Graph vocabulary
Wednesday, 4 August 2010
Tuesday, 3 August 2010
- Re: RDFa API FPWD published
- Heartbeat Drafts published
- Re: ISSUE-29: Re: When is equal and when is it nonequal (eg, the IRI interface)
- Re: ISSUE-29: Re: When is equal and when is it nonequal (eg, the IRI interface)
Monday, 2 August 2010
- Re: ISSUE-29: Re: When is equal and when is it nonequal (eg, the IRI interface)
- Re: ISSUE-29: Re: When is equal and when is it nonequal (eg, the IRI interface)
- Re: ISSUE-29: Re: When is equal and when is it nonequal (eg, the IRI interface)
- Re: The term "origin"
- Re: ISSUE-29: Re: When is equal and when is it nonequal (eg, the IRI interface)
- Re: ISSUE-29: Re: When is equal and when is it nonequal (eg, the IRI interface)
- Re: ISSUE-29: Re: When is equal and when is it nonequal (eg, the IRI interface)
- ISSUE-29: Re: When is equal and when is it nonequal (eg, the IRI interface)
- Re: The term "origin"
- Telecon Agenda - August 5th 2010, 1400 UTC
Sunday, 1 August 2010
- ISSUE-28: Re: New Issue(s)
- Re: ISSUE-28: Nathan's RDFa API Questions and Comments (e-mail 1)
- Re: ISSUE-28: Re: 3 Minor issues spotted
- ISSUE-38 (non-browser generalization of rdfa api): The RDFa API should elaborate on how it can operate in non-browser environments [RDFa 1.1 Core]
- ISSUE-28: Re: 3 Minor issues spotted
- ISSUE-28: Nathan's RDFa API Questions and Comments (e-mail 1)