On test #286 Re: pyRdfa passes all the HTML5 tests again:-)

Gregg,

By making a wget on 286, I get

<!DOCTYPE html>
<html>
<head>
  <title>Test 0286</title>
</head>
<body>
  <span property="rdf:value" lang="lat" value="veni, vidi, vici" content="I came, I saw, I conquered">
    @value overrides @content.
  </span>
</body>
</html>

but the whole value/content issue is bound to the <data> element, isn't it? So I changed the test to use <data> and not <span>. With that change my test works...

I then looked at the HTML5+RDFa document, and I realized that, indeed, the text refers to @value in general. But I do not think we ever agreed in that and I actually would not think this would be a good idea. According to 

http://dev.w3.org/html5/spec/single-page.html#attributes-1

@value has different meanings for elements like <input>, <li>, <param>; in all those cases using @value instead of @content might be very strange indeed. So my proposal would be to change the HTML5+RDFa draft by restricting this @value->@content change only when bound to a <data> element. (That being said: is the <data> element still valid in HTML5? Wasn't this taken out at some point?)

Ivan 



On Mar 19, 2012, at 20:05 , Gregg Kellogg wrote:

>> I handled all the date stuffs. That was useful...
>> 
>> Can regenerate the earl report?
> 
> I updated the report. I ended up writing a customized Turtle serializer, as the number of triples was starting to choke my poor implementation (TSort of subjects wasn't helping).
> 
> Note, to do the update, run the tests and save the EARL source into the appropriate file within public/earl-reports. Then run "rake earl:collate earl:report". This generates a Respec source in public/earl-reports/earl.html. I then open in a browser and save XHTML source to index.html.
> 
>> It seems that I/we are done, until new tests come, right? I did one editorial modifications on one of the new tests, the <title> element was referring to another test. (Did a git push.)
> 
> Yes, there was another tag open/close bug I fixed as well, but pyRdfa still fails 0286 in XHTML mode.
> 
>> Seriously: I know anything can be improved, but I think that is the point when we should really stop and let various other implementations run their course. The fact that the test harness is stable becomes a real plus.
> 
> Agreed, I'm done.
> 
> Gregg
> 
>> Manu: we still have a pending issue on the URI used for license, a decision on that, unfortunately, influences a bunch of tests. We also have a pending issue that came up during the testing that would lead to a modification of the core:
>> 
>> http://www.w3.org/2010/02/rdfa/track/issues/133
>> 
>> do we want to wait until the end of the CR period to make a decision on that, ie, to modify the core or should we have an email decision on that?
>> 
>> Cheers
>> 
>> Ivan
>> 
>> ----
>> 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
>> 
>> 
>> 
>> 
>> 
> 


----
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

Attachments

Received on Tuesday, 20 March 2012 10:56:02 UTC