W3C home > Mailing lists > Public > public-rdfa-wg@w3.org > March 2013

Re: RDFa parser behavior for @value in light of Issue-145

From: Ivan Herman <ivan@w3.org>
Date: Tue, 5 Mar 2013 09:12:26 +0100
Cc: Faye Harris <fayeharris@google.com>, public-rdfa-wg <public-rdfa-wg@w3.org>
Message-Id: <BF748D20-5F42-4566-9E53-77E9C38D964F@w3.org>
To: Gregg Kellogg <gregg@greggkellogg.com>

On Mar 4, 2013, at 21:40 , Gregg Kellogg <gregg@greggkellogg.com> wrote:

> 
> On Mar 4, 2013, at 10:50 AM, Faye Harris <fayeharris@google.com> wrote:
> 
>> Hi!
>> 
>> The resolution of Issue-145 says that a HTML+RDFa 1.1 parser should not process @value. Test 286 has also been removed. Does that mean it would be non-conforming for a parser to process an @value attribute? If so, I'd recommend reinstating Test 286 as a negative test, where nothing is extracted.
> 
> The WG has always taken the stance that a processor is free to produce more triples (this is why SPARQL is used to test results, rather than explicit triples). The removal of @value is just reflecting that HTML5 no longer has the <data> element with which it made sense. If you want to continue to process that, i don't see any issues for my part. However, this is just my opinion.
> 

I agree.

Ivan

> Gregg
> 
>> Thanks,
>> -- Faye
> 


----
Ivan Herman, W3C Semantic Web Activity Lead
Home: http://www.w3.org/People/Ivan/
mobile: +31-641044153
FOAF: http://www.ivan-herman.net/foaf.rdf
Received on Tuesday, 5 March 2013 08:12:44 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:19:58 UTC