On 07/02/13 21:31, Adrian Gschwend wrote:
On 07.02.13 19:22, Andy Seaborne wrote:
Hi Andy,
Can't test but my guess is that the some of the ?munidstr coming back
from DBpedia are not valid integer strings.
ah didn't think of that.
That makes:
BIND(xsd:int(str(?munidstr)) AS ?munid)
leave ?munid unbound so the rest of the query is unconnected with the
SERVICE part. That will mix up the data.
Could this already be the case if some values are strings and some are
indeed integers? IIRC DBpedia was not really constant on this particular
predicate.
No - ints cast to ints is legal.
The casting in ARQ is quite generous - any lexical form that is a legal
integer works. This is more than the standard (XQuery F&O requires);
But no white space, no non-numbers, no decimal separators, no thousands
separators.
Signified says in a comment on that answers.semanticweb.com question
that Samstagern has a non-integer value.
DBpedia is down, looks like the cluster has lost a machine (careless!),
so I can't find out what it is.
Andy
cu
Adrian
