ISSUE-46 (conversion of plain literals to IRIs): Should plain literals that match fully qualified IRIs be automatically converted to IRIs [RDFa 1.1 Core]

ISSUE-46 (conversion of plain literals to IRIs): Should plain literals that match fully qualified IRIs be automatically converted to IRIs [RDFa 1.1 Core]

http://www.w3.org/2010/02/rdfa/track/issues/46

Raised by: Ivan Herman
On product: RDFa 1.1 Core

This issue was raised by two large RDFa adopters that would like to see the following markup

<meta property="foo:bar" content="http://example.org/baz" />

generate the following triple:

<> foo:bar <http://example.org/baz>

instead of what would be created in RDFa 1.0:

<> foo:bar "http://example.org/baz"

It's fairly clear that the author intended the first triple and not the second, however, RDFa does not allow a simple way to generate the first triple. The change request would make it such that when an IRI is detected as a plain literal, the value is converted to an IRI. If the author would prefer to generate a plain literal instead, datatype="" could be provided in those corner cases.

It has been suggested that we add this as an at-risk feature to RDFa Core and ask for broader community feedback.

Received on Sunday, 3 October 2010 17:47:32 UTC