public-rdfa-wg@w3.org from August 2010 by subject

(no subject)

(Resending for tracker: ISSUE-39) Re: Comment on RDFa 1.1 Core: Profiles, term mappings, and URIs as literals

@cite (was: longdesc URLs and RDFa(

[public-rdfa-wg] <none>

A possible design to incorporate collections and containers into RDFa?

A possible design to incorporate collections and containers into RDFa? [ISSUE-16]

Comment on RDFa 1.1 Core: Empty elements should not create literals

Comment on RDFa 1.1 Core: Nested RDFa markup

Comment on RDFa 1.1 Core: Profiles, term mappings, and URIs as literals

Comment on RDFa 1.1 Core: Profiles, term mappings, and URIs as literals (ISSUE-39)

CURIE and URI Processing vs Processor Status Warning

Format of @profile files (summarizing ISSUE-39, maybe moving forward...)

further on ISSUE-39

Fwd: A possible design to incorporate collections and containers into RDFa?

Getting the XHTML+RDFa default profile to be interesting

Handling of missing @profile

Heartbeat Drafts published

How are default profiles normatively established?

ISSUE-28: Nathan's RDFa API Questions and Comments (e-mail 1)

ISSUE-28: Proposal to resolve Nathan's issue

ISSUE-28: Re: 3 Minor issues spotted

ISSUE-28: Re: New Issue(s)

ISSUE-29: Proposal to resolve DOM origin generalization

ISSUE-29: Re: When is equal and when is it nonequal (eg, the IRI interface)

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-39 (rdfa term mapping triples): Profiles, term mappings, and URIs as literals [RDFa 1.1 Core]

ISSUE-40 (no triples for empty elements): Empty elements should not create literals [RDFa 1.1 Core]

ISSUE-40 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]

ISSUE-42: RDFa API should use 'string' instead of 'DOMString' in the WebIDL

ISSUE-43: Determine if DataParser interface needs a hasFeature("hcard") or hasFeature("hrecipe") mechanism.

ISSUE-44: Add a mechanism to the RDFa API to parse remote documents and place them into a DataStore.

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]

Javascript prefix mapping via closures...

longdesc URLs and RDFa

Processor Graph vocabulary

Question about RDFa processing rule 8 (@typeof)

RDFa API - new editor's draft

RDFa API - new editor's draft and ISSUE-33

RDFa API FPWD published

RDFa WG telecon minutes for 2010-08-05

RDFa WG telecon minutes for 2010-08-12

RDFa WG telecon minutes for 2010-08-26

Telecon Agenda - August 12th 2010, 1400 UTC

Telecon Agenda - August 19th 2010, 1400 UTC

Telecon Agenda - August 26th 2010, 1400 UTC

Telecon Agenda - August 5th 2010, 1400 UTC

Telecon Agenda - September 2nd 2010, 1400 UTC

The term "origin"

XHTML+RDFa DTD UA support (Was: Getting the XHTML+RDFa default profile to be interesting)

Last message date: Tuesday, 31 August 2010 13:01:58 UTC