W3C home > Mailing lists > Public > w3c-rdfcore-wg@w3.org > November 2002

Re: do bad datatype literals denote [was Re: Datatype test cases ...]

From: pat hayes <phayes@ai.uwf.edu>
Date: Wed, 20 Nov 2002 10:42:44 -0600
Message-Id: <p05111b01ba01656c845a@[]>
To: Brian McBride <bwm@hplb.hpl.hp.com>
Cc: w3c-rdfcore-wg@w3.org

>At 14:49 20/11/2002 +0000, Jan Grant wrote:
>>  >
>>>  We know that:
>>>    <a> <b> "foo"@@en#<datatype> .
>>>    <c> <d> "foo"@@fr#<datatype> .
>>>  entails
>>>    <a> <b> _:l .
>>>    <c> <d> _:l .
>>>  for all datatypes except rdf:XMLLiteral.
>>It does? Doh.
>I think so, but don't take my word for it.  Jeremy?

Oh, I thought that lang tags simply couldn't be attached to datatyped 
literals other than rdf:XMLLiterals, so this would be a syntax error. 
That's what the graph syntax rules seem to say. Is that wrong??

>>I still think that's broken; but I'll fix the test case.
>>Basically these cases outline the various issues - I'll correct them as
>Nah - see below - you got it right unless we know that datatype is 
>not rdf:XMLLiteral.  We know its not called that, but unless we make 
>a unique name assumption, we don't know that its not another name 
>for the same thing.

Thats why its best made a matter of syntax rather than something to 
do with the denotation. That is, the datatype label has to actually 
have the characters "XMLLiteral" in it.

>>NO. This is related to what Pat was complaining about. Basically, a
>>"Positive entailment test" with premise document P and consequent
>>document C passes if:
>>         - P has an interpretation (ie, contains no semantic errors
>>           wrt the constraints imposed by the interpretation rules used
>>           for the test case) AND
>>         - P entails C.
>>A "negative entailment test" passes if:
>>         - P has no valid interpretations (contains a semantic error) OR
>>         - P is ok but does not entail C.
>OK, so because its a neg entailment of the empty graph, then by this 
>rule, there can be no valid interpretations.  I thought the model 
>theory had bad datatype lex forms denoting something though, in 
>which case there is an interpretation.  Right, from 3.4 of the MT:
>[[For any typed literal "sss"^^ddd in G, if I(ddd) is in D and 'sss' 
>is not a valid lexical form for I(ddd) then IL("sss"^^ddd) is not in 
>[[(this) condition requires than an 'ill-formed' typed literal, i.e. 
>one where the literal string is not in the lexical space of the 
>datatype, not denote any literal value. Intuitively, such a name 
>does not denote any value, but in order to avoid the semantic 
>complexities which arise from empty names, we requires such a typed 
>literal to denote an 'arbitrary' value.]]
>Thus there are interpretations of the graph
>   http://www.w3.org/2000/10/rdf-tests/rdfcore/datatypes/test002.nt
>and the test does not work

It works but for a different reason. Perhaps I should spell this out 
more in the semantics doc.

Making the denotation be something arbitrary in this case (ie not a 
literal value, but otherwise it could be anything) means that the 
ONLY entailment you can get is what you would get from basic graph 
interpretations, which is replacing the bad literal by a new bnode:

aaa bbb "xxyzx"^^xsd:number .


aaa bbb _:newnode .

And you CAN post an error if you find the bad literal; but still, you 
do get this entailment.
(If we didnt get at least this, then datatypes would break basic 
graph entailment, which is why I wanted to make sure they denoted 
something. The alternative is to make them all denote some special 
weird value, which I did try in one draft, but which has all kinds of 
other problems.)

1. you always get the basic new-bnode entailment, for any node 
whatsoever, illformed or not.

2. If the literal is simple (not datatyped) then it might hav a lang 
tag, and in that case the identity of the literal is detemined by the 
pair of the literal string and the lang tag, so for example

aaa bbb "chat"@@fr .
ccc ddd "chat"@@en .

does not entail

aaa bbb _:x .
ccc ddd _:x .

3. if the literal is typed by datatype, datatype is a Datatype and 
you check the datatype and the literal is illformed, then 1. is *all* 
you can infer, and you are allowed to flag an error. (And you know 
that if anyone says that this thing is in rdfs:Literal, then they are 

3. If all the above but the typed literal is wellformed, then:
     3a. If its an rdf:XMLLiteral and there is a lang tag then you 
pass the tag to the XML parser, ie it is absorbed into the XML part 
of the literal.
     3b. you know the typed literal denotes something in the datatype class
     3c. you know it denotes a literal value

3c follows from 3b in RDFS since you know that the datatype class is 
a subclass of rdfs:Literal, but I thought Id mention it.

4. If all the above and you know from the datatype mavens that two 
datatype lexical forms denote the same value,  then you can 
substitute one of them for the other in any typed literal in any 

5 (??) If all the above and you know from the datatype mavens that 
some properties are true on some datatype values, then you can 
conclude some more triples using those properties. (Jos' idea) ??

Im not sure about the last one: do we want to go there?

>>I'm happy to revise this if you think it's necessary.
>Lets get confirmation first

IHMC					(850)434 8903   home
40 South Alcaniz St.			(850)202 4416   office
Pensacola              			(850)202 4440   fax
FL 32501           				(850)291 0667    cell
phayes@ai.uwf.edu	          http://www.coginst.uwf.edu/~phayes
s.pam@ai.uwf.edu   for spam
Received on Wednesday, 20 November 2002 11:42:49 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 20:24:18 UTC