Jeff,
this was changed to support spin:source as a way of tracking the origin of a
constraint violation. See documentation of QueryWrapper.getSource():
/**
* Gets the SPIN Query or template call that has created this
QueryWrapper.
* @return the source
*/
If you need to create QueryWrappers manually, then you should pass in the SPIN
query RDF resource or the SPIN template that contains the constraint check. Or,
if you are not interested in the spin:source later, just pass in OWL.Thing or
something else :)
Holger
On Apr 17, 2010, at 7:54 AM, Schmitz, Jeffrey A wrote:
> Just realized that with the new libraries, there is a new SPIN api to upgrade
> to. In the api, the QueryWrapper constructor has changed and I'm unsure what
> exactly to pass in for the added 'source' parameter. What is this parameter
> supposed to be?
>
> Thanks,
> Jeff
>
>> -----Original Message-----
>> From: [email protected] [mailto:topbraid-
>> [email protected]] On Behalf Of Scott Henninger
>> Sent: Friday, April 16, 2010 2:16 PM
>> To: TopBraid Suite Users
>> Subject: [topbraid-users] Re: Named graphs in SDB
>>
>> Good! I was about to suggest looking into base URI conflicts. You can
>> check this in Composer with Windows > File Registry, sort by base URI
>> and look to see if there are any files with the same base URI you are
>> looking for. The "primary" will have a clean file icon in the File
>> Registry and others will have a yellow warning sign. Ensemble also has
>> a nice page for viewing the registry by project.
>>
>> What was probably happening was there were some imported files that
>> had base URI conflicts so the file you thought was being opened wasn't
>> the primary file and a file with "old" data was being accessed
>> instead.
>>
>> -- Scott
>>
>> On Apr 16, 12:55 pm, "Schmitz, Jeffrey A"
>> <[email protected]> wrote:
>>> Spoke too soon. It's not picking up what's actually in the database.
>> Honestly I'm not sure what it's doing, but I think it must be picking
>> up some previous state of the database, maybe because in the past I've
>> written a named graph to and RDF/XML file and then opened RDF/XML file
>> in TBC. Any ideas?
>>>
>>>
>>>
>>>> -----Original Message-----
>>>> From: [email protected] [mailto:topbraid-
>>>> [email protected]] On Behalf Of Schmitz, Jeffrey A
>>>> Sent: Friday, April 16, 2010 12:37 PM
>>>> To: [email protected]
>>>> Subject: RE: [topbraid-users] Re: Named graphs in SDB
>>>
>>>> That worked. I just went directly to connecting to one of my
>> existing
>>>> named graphs and it worked this time. Since we use some of your
>>>> ontologies in our application we have copies of them in our Eclipse
>>>> project. I'll have to remember to update them for each new version
>> of
>>>> TBC.
>>>
>>>> Thanks!
>>>> Jeff
>>
>> --
>> You received this message because you are subscribed to the Google
>> Group "TopBraid Suite Users", the topics of which include TopBraid
>> Composer,
>> TopBraid Live, TopBraid Ensemble, SPARQLMotion and SPIN.
>> To post to this group, send email to
>> [email protected]
>> To unsubscribe from this group, send email to
>> [email protected]
>> For more options, visit this group at
>> http://groups.google.com/group/topbraid-users?hl=en
>
> --
> You received this message because you are subscribed to the Google
> Group "TopBraid Suite Users", the topics of which include TopBraid Composer,
> TopBraid Live, TopBraid Ensemble, SPARQLMotion and SPIN.
> To post to this group, send email to
> [email protected]
> To unsubscribe from this group, send email to
> [email protected]
> For more options, visit this group at
> http://groups.google.com/group/topbraid-users?hl=en
--
You received this message because you are subscribed to the Google
Group "TopBraid Suite Users", the topics of which include TopBraid Composer,
TopBraid Live, TopBraid Ensemble, SPARQLMotion and SPIN.
To post to this group, send email to
[email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/topbraid-users?hl=en
