RE: [topbraid-users] typing issue

2014-05-28 Thread Bohms, H.M. (Michel)
[mailto:topbraid-users@googlegroups.com] On Behalf Of Holger Knublauch Sent: woensdag 28 mei 2014 0:45 To: topbraid-users@googlegroups.com Subject: Re: [topbraid-users] typing issue On 5/28/2014 1:17, Bohms, H.M. (Michel) wrote: CONSTRUCT { ?eNeighbourhood depc:hasComplexProperty ?ppuri . ?ppuri

RE: [topbraid-users] typing issue

2014-05-28 Thread Bohms, H.M. (Michel)
: Re: [topbraid-users] typing issue On 5/28/2014 1:17, Bohms, H.M. (Michel) wrote: CONSTRUCT { ?eNeighbourhood depc:hasComplexProperty ?ppuri . ?ppuria depc:ProfileProperty; depc:valueKind Nominal^^xsd:string; depc:valueOrigin Derived^^xsd:string

Re: [topbraid-users] typing issue

2014-05-28 Thread Holger Knublauch
: woensdag 28 mei 2014 0:45 To: topbraid-users@googlegroups.com Subject: Re: [topbraid-users] typing issue On 5/28/2014 1:17, Bohms, H.M. (Michel) wrote: CONSTRUCT { ?eNeighbourhood depc:hasComplexProperty ?ppuri . ?ppuria depc:ProfileProperty; depc:valueKind Nominal

RE: [topbraid-users] typing issue

2014-05-28 Thread Bohms, H.M. (Michel)
28 mei 2014 12:10 To: topbraid-users@googlegroups.com Subject: Re: [topbraid-users] typing issue How did you attach the query? It needs to be via spin:rule Sent from my iPad On May 28, 2014, at 20:04, Bohms, H.M. (Michel) michel.bo...@tno.nlmailto:michel.bo...@tno.nl wrote: Hi Holger, Works

Re: [topbraid-users] typing issue

2014-05-28 Thread Scott Henninger
: [topbraid-users] typing issue On 5/28/2014 1:17, Bohms, H.M. (Michel) wrote: CONSTRUCT { ?eNeighbourhood depc:hasComplexProperty ?ppuri . ?ppuri

[topbraid-users] typing issue

2014-05-27 Thread Bohms, H.M. (Michel)
Asserted it looks like: [cid:image001.png@01CF79CF.7D391D80] When infered with spin I get: [cid:image002.png@01CF79CF.7D391D80] With query: CONSTRUCT { ?eNeighbourhood depc:hasComplexProperty ?ppuri . ?ppuria depc:ProfileProperty; depc:valueKind Nominal^^xsd:string;

Re: [topbraid-users] typing issue

2014-05-27 Thread Scott Henninger
Michel; Yes, the type should be float (for both, actually) and the sum aggregate will default to float if any of the values are floating point (see SPARQL 1.1 specs for more). In terms of the fully qualified URI, chances are that depc:e-Production does not have a