Re: [RDFa TC] interpretation of TC results

Benjee's idea is indeed nice and might solve this issue. I still believe 
that having the general setup available when needed is worthwhile. There 
might be tests (either in the current set or some others coming up) 
where the unbound trick may not work that easily...

My two cents...

Ivan

Hausenblas, Michael wrote:
> 
> Benji,
> 
> Thanks for this additional branch - nice idea!
> So, if I get you right I need to additionally add a the 'xhv:validRel'
> fragment to the XHTML+RDFa input document?
> Hm. Seems doable. Any comments from others?
> 
> Cheers,
>  Michael
> ----------------------------------------------------------
>  Michael Hausenblas, MSc.
>  Institute of Information Systems & Information Management
>  JOANNEUM RESEARCH Forschungsgesellschaft mbH
>   
>  http://www.joanneum.at/iis/
> ----------------------------------------------------------
>  
> 
>> -----Original Message-----
>> From: Benjamin Nowack [mailto:bnowack@semsol.com] 
>> Sent: Monday, March 03, 2008 12:05 PM
>> To: Hausenblas, Michael; public-rdf-in-xhtml-tf@w3.org
>> Subject: Re: [RDFa TC] interpretation of TC results
>> Importance: High
>>
>>
>> Hi,
>> What about tweaking the input doc and query to make things
>> pass on TRUE again?
>>
>> [[
>> ASK WHERE {
>>   <#res> xhv:validRel <#val1> .
>>   OPTIONAL { <#res> xhv:invalidRel ?val2 . }
>>   FILTER (!bound(?val2))
>> }
>> ]]
>>
>> Best,
>> Benji
>>
>>
>> On 03.03.2008 10:49:32, Hausenblas, Michael wrote:
>>>
>>> All,
>>>
>>> As noticed recently [1] we have at least one TC (86) making 
>> it necessary
>>> to explicitly interpret the result of the SPARQL ASK query. 
>> Until now an
>>> RDFa extractor test would be done as so:
>>>
>>> 1. fetch a TC(i), ie. 
>>> a) the input document in XHTML+RDFa TCI(i), and
>>> b) the SPARQL ASK query TCQ(i)
>>>
>>> 2. apply the SPARQL ASK query TCQ(i) the output of the 
>> XHTML+RDFa -> RDF
>>> conversion, TCR(i)
>>>
>>> 3. if this query yields 'YES' (that is: the triples are present), the
>>> implementation has passed this TC(i)
>>>
>>> There was an (implicit) assumption that TCQ(i) yielding 'YES' means
>>> 'PASSED'. As TC 86 [1] shows, this is not true in all cases. 
>> To overcome
>>> this, I'd like to propose two alternative solutions, seeming 
>> practically
>>> doable. We could:
>>>
>>> I) Use the http://www.w3.org/2006/03/test-description#expectedResults
>>> property to additionally capture the expected answers (YES or NO, as
>>> string literal), OR
>>>
>>> II) Move the SPARQL ASK query TCQ(i) to a second
>>> http://www.w3.org/2006/03/test-description#informationResource
> Input, and
>>> change the
>>> http://www.w3.org/2006/03/test-description#informationResource
> Results to
>>> capture the expected answers (YES or NO, again as string literal)
>>>
>>>
>>> In the following I give the prospective rendering of the 
>> modified TC for
>>> each approach (I and II), above:
>>>
>>> _[ I ]__________________________________________________________
>>>
>>> <Test0086> rdf:type test:TestCase;
>>>   dc:contributor "Ivan Herman";
>>>   dc:title "NO triple for a non-reserved @rel value";
>>>   test:informationResourceInput <0086.xhtml>;
>>>   test:informationResourceResults <0086.sparql>;
>>>   test:expectedResults 'NO';
>>>   test:purpose "Test that NO triple should be generated for a
>>> non-reserved @rel value";
>>>   test:reviewStatus test:approved;
>>> ________________________________________________________________
>>>
>>> OR
>>>
>>> _[ II ]_________________________________________________________
>>>
>>> <Test0086> rdf:type test:TestCase;
>>>   dc:contributor "Ivan Herman";
>>>   dc:title "NO triple for a non-reserved @rel value";
>>>   test:informationResourceInput <0086.xhtml>;
>>>   test:informationResourceInput <0086.sparql>;
>>>   test:informationResourceResults <0086.result>;
>>>   test:purpose "Test that NO triple should be generated for a
>>> non-reserved @rel value";
>>>   test:reviewStatus test:approved;
>>>
>>>
>>> 0086.result would then contain a single (string) entry: 'NO'
>>> ________________________________________________________________
>>>
>>>
>>> Please let me know how to proceed. Any thoughts?
>>>
>>> Cheers,
>>>  Michael
>>>
>>>
>>> [1] http://www.w3.org/2008/02/21-rdfa-irc.html#T16-26-22
>>>
>>> ----------------------------------------------------------
>>> Michael Hausenblas, MSc.
>>> Institute of Information Systems & Information Management
>>> JOANNEUM RESEARCH Forschungsgesellschaft mbH
>>> Steyrergasse 17, A-8010 Graz, AUSTRIA
>>>
>>> <office>
>>>    phone: +43-316-876-1193 (fax:-1191)   
>>>   e-mail: michael.hausenblas@joanneum.at
>>>      web: http://www.joanneum.at/iis/ 
>>>
>>> <private>
>>>   mobile: +43-660-7621761
>>>      web: http://www.sw-app.org/ 
>>> ----------------------------------------------------------
>>>
>>
> 

-- 

Ivan Herman, W3C Semantic Web Activity Lead
Home: http://www.w3.org/People/Ivan/
PGP Key: http://www.ivan-herman.net/pgpkey.html
FOAF: http://www.ivan-herman.net/foaf.rdf