Re: a question about turtle as it appears in the test manifests

Ooh, silly me, of course, false is ... not true.

peter



On Wed, Oct 2, 2013 at 3:33 PM, Gregg Kellogg <gregg@greggkellogg.net>wrote:

> On Oct 2, 2013, at 2:33 PM, Peter Patel-Schneider <pfpschneider@gmail.com>
> wrote:
>
> > The test manifest files contain portions like:
> >
> > <#xxx>
> >   mf:result false .
> >
> >
> > is this legal Turtle?
>
> Yes, from <http://www.w3.org/TR/turtle/#booleans>:
>
> [[[
> Boolean values may be written as either 'true' or 'false' (case-sensitive)
> and represent RDF literals with the datatype xsd:boolean.
>
> @prefix : <http://example.org/stats> .
> <http://somecountry.example/census2007>
>     :isLandlocked false .           # xsd:boolean
>
> ]]]
>
> Another issue is if the range of ms:result allows a literal, but this
> isn't a syntactic issue. I think the test-manifest schema [1] is actually
> wrong, as :result is defined twice, the second of which is probably
> intended to be :status
>
> [[[
> :result rdf:type rdf:Property ;
>     rdfs:comment "The expected outcome" ;
>     rdfs:domain  :ManifestEntry ;
>     # rdfs:range   ?? ;
>     .
>
> :result rdf:type rdf:Property ;
>     rdfs:comment "The test status" ;
>     rdfs:domain  :ManifestEntry ;
>     rdfs:range   :TestStatus ;
>     .
> ]]]
>
> Perhaps one reasoning test should be if the test manifest itself is valid
> WRT the vocabularies it uses.
>
> Gregg
>
> [1] http://www.w3.org/2001/sw/DataAccess/tests/test-manifest#
>
> > peter
> >
>
>