Here's a vote for adding SPARQL Update support to SPIN, although I
admit I haven't thought through all the implications about making the
system "less safe and too complex".  I only know that I currently save
a lot of SPARQL Update queries to a model as 'sparql:query' strings,
and was hoping to move them into SPIN classes instead, especially
since sparql:query is listed as deprecated, but I see no way to do
that currently.

On Sep 10, 12:30 pm, Holger Knublauch <[email protected]> wrote:
> Hi Barb,
>
> currently, thespin:body of aSPINfunction can only be a SELECT or  
> ASK query. This is becauseSPINis currently a classical, monotonic  
> inferencing language that can only add new triples.
>
> I have thought about addingSPARQLUPDATEcalls to a future version,  
> and I would welcome customer feedback on whether this would be useful  
> (or make the system less safe and too complex).
>
> Meanwhile, the work-around is to use a SPARQLMotion body that does a  
> sml:PerformUpdate.
>
> Holger
>
> On Sep 10, 2009, at 9:05 AM, Barb wrote:
>
>
>
>
>
> > I've created a utility class (subclass ofspin:Functions) to house
> > various pieces of common business functionality.
> > One such function performs a delete of the ?selectedResource which is
> > being passed in as an argument.
> > I've created my function and am trying to enter my delete statement
> > into thespin:body but unfortunately it doesn't like it.
>
> > Thespin:body value range is sp:query (Ask, Construct, Describe and
> > Select) of which delete is not a member.
> > Can I perform a delete from aSPINfunction?
> > If so, how/where would I specify the delete statement?
>
> > Thanks,
>
> > Barb
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"TopBraid Composer Users" group.
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-composer-users?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to