non-prefixed @rel

Hi all,

Last time, we got a bit stuck on the issue of non-prefixed @rel.

Concretely, I believe we agree on the end-goal: rel="next" should yield
xh:next, while rel="myfoorel" should not yield any spurious triple in
the "default graph."

The key question is, thus, how to actually implement this and how to
extend it to @property. Here's my attempt to find wording acceptable to
everyone:

========
Ben's Non-Prefixed @rel Proposal

rel="X"

  - if X is a XHTML 1.1 reserved value, it is re-written in a
pre-processing stage as rel="xh:X", where xh maps to
http://www.w3.org/1999/xhtml/vocab#.

  - if X is a prefixed value, it is processed normally.

  - if X is a non-prefixed, non-reserved value, it is ignored by any
baseline RDFa parser, though other conformant parsers may choose to
generate a triple *outside* of the default graph, as per [RDFa Parser
Conformance].

The same rules apply to each value in a space-separated set of values for X.

The same rules apply to @rev, which has the same backwards compatibility
issues as @rel.

For consistency, the same rules apply to @property and @instanceof.
========

As a side note, here's the RDFa Syntax document [1] statement on [RDFa
Parser Conformance], which, combined with the above wording, seems
enough to capture what we want:

"A conforming RDFa Processor MAY make available additional triples that
have been generated using rules not described here, but these triples
MUST be made available in one or more additional RDF [graph]s, and not
in the default [graph]."

Thoughts?

-Ben

[1] http://www.w3.org/MarkUp/2007/ED-rdfa-syntax-20070921/

Received on Wednesday, 10 October 2007 23:19:04 UTC