W3C home > Mailing lists > Public > public-rdfa-wg@w3.org > February 2012

ISSUE-128 (empty list of TERMorCURIEorAbsIRIs): Empty list of TERMorCURIEorAbsIRIs should be allowed more explicitly in the spec [3rd LC Comments - RDFa 1.1 Core]

From: RDF Web Applications Working Group Issue Tracker <sysbot+tracker@w3.org>
Date: Thu, 09 Feb 2012 10:30:19 +0000
Message-Id: <E1RvRGd-0007kQ-IX@nelson.w3.org>
To: public-rdfa-wg@w3.org
ISSUE-128 (empty list of TERMorCURIEorAbsIRIs): Empty list of TERMorCURIEorAbsIRIs should be allowed more explicitly in the spec [3rd LC Comments - RDFa 1.1 Core]

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

Raised by: Ivan Herman
On product: 3rd LC Comments - RDFa 1.1 Core

This is an editorial comment, I believe.

Copying from Mike Smith's comment:

That spec says that the value of the property attribute is:

"a white space separated list of TERMorCURIEorAbsIRIs"
http://www.w3.org/2010/02/rdfa/sources/rdfa-core/Overview-src.html#s_syntax

The empty string is not a valid term or CURIE or absolute IRI.

If the intention is that the empty string should be allowed as the value of
the property attribute, then the RDFa Core 1.1 spec needs to instead be
updated to say that the allowed value for the property attribute is,
"a white space separated list of *zero or more* TERMorCURIEorAbsIRIs".

Incidentally, that's true for the values of other attributes as well; the
spec needs to explicitly say either "zero or more" or "one or more" for
them. Lack of that language makes it ambiguous.

On the other hand, we (rarely) use empty @typeof or @datatype. Ie, the editorial changes proposed by Mike make sense to me.
Received on Thursday, 9 February 2012 10:30:24 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 17:05:30 UTC