- From: Eric Prud'hommeaux <eric@w3.org>
- Date: Mon, 19 Dec 2005 10:05:34 -0500
- To: Dan Connolly <connolly@w3.org>
- Cc: public-rdf-dawg@w3.org
- Message-ID: <20051219150534.GF7513@w3.org>
On Mon, Dec 19, 2005 at 09:02:59AM -0600, Dan Connolly wrote:
>
> Interesting proposal; persuing it seems to involve
> re-opening useMentionOp, which is perhaps a good thing.
> http://www.w3.org/2001/sw/DataAccess/issues#useMentionOp
Do you have a test case that illustrates this?
> On Mon, 2005-12-19 at 09:50 -0500, Eric Prud'hommeaux wrote:
> > We seem to be stopped on the issue that
> > "2"^^xsd:integer != "II"^^roman:numeral
> > will test true in a SPARQL implementation and false in an extended
> > SPARQL implementation. This comes from the overloaded = operator:
> > numeric = numeric
> > RDF term = RDF term
> > If the right side of the test is not recognized to be a numeric, the
> > test is whether they are the same RDF term (clearly not). Adding
> > roman:numeral support allows the right side to be numeric, and the
> > value is the same left side.
> >
> > PROPOSE: change
> > RDF term = RDF term
> > to
> > sameTermAs(RDF term, RDF term)
> > strike
> > RDF term != RDF term
> > and strike
> > [[
> > When selecting the operator definition for a given set of parameters,
> > the definition with the most specific parameters applies. For
> > instance, when evaluating xsd:integer = xsd:signedInt, the definition
> > for = with two numeric parameters applies, rather than the one with
> > two RDF terms. The table is arranged so that upper-most viable
> > candiate is the most specific.
> > ]]
--
-eric
office: +81.466.49.1170 W3C, Keio Research Institute at SFC,
Shonan Fujisawa Campus, Keio University,
5322 Endo, Fujisawa, Kanagawa 252-8520
JAPAN
+1.617.258.5741 NE43-344, MIT, Cambridge, MA 02144 USA
cell: +81.90.6533.3882
(eric@w3.org)
Feel free to forward this message to any list for any purpose other than
email address distribution.
Received on Monday, 19 December 2005 15:05:45 UTC