- From: Patrick Stickler <patrick.stickler@nokia.com>
- Date: Mon, 23 Sep 2002 20:03:25 +0300
- To: "ext Jos De_Roo" <jos.deroo.jd@belgium.agfa.com>
- Cc: "Dave Beckett" <dave.beckett@bristol.ac.uk>, "ext Jeremy Carroll" <jjc@hplb.hpl.hp.com>, "RDF Core" <w3c-rdfcore-wg@w3.org>
[Patrick Stickler, Nokia/Finland, (+358 50) 483 9453, patrick.stickler@nokia.com] ----- Original Message ----- From: "ext Jos De_Roo" <jos.deroo.jd@belgium.agfa.com> To: "Patrick Stickler" <patrick.stickler@nokia.com> Cc: "Dave Beckett" <dave.beckett@bristol.ac.uk>; "ext Jeremy Carroll" <jjc@hplb.hpl.hp.com>; "RDF Core" <w3c-rdfcore-wg@w3.org> Sent: 23 September, 2002 16:47 Subject: Re: Proposed N-Triples changes for datatypes & (untidy) literals > > [...] > > > I'm still not convinced, though, that the above could not be > > made to entail itself in the MT, since the systemID of the > > implicitly typed literal (the _:x in _:x"foo") acts > > like a bnode nodeID of a datatype, and can be treated in > > like manner. > > I think so > indeed > _:a eg:name _:x"Patrick Stickler" . > entails > _:b eg:name _:y"Patrick Stickler" . Right > PS however (and again) > _:a eg:name "Patrick Stickler" . > does *not* entail > _:b eg:name _:y"Patrick Stickler" . Agreed And again, we wouldn't have to worry about this because if all implicitly typed literals are prefixed with unique systemIDs, we would never get _:a eg:name "Patrick Stickler" . in the graph, so no worries. Cheers, Patrick
Received on Monday, 23 September 2002 13:04:31 UTC