Assert and Retract

[PaulBrownMagic]

Hi,

Are there any plans to implement rdf_assert/3 and rdf_retractall/4 to create SPARQL insert and delete queries? I couldn't find them in the docs and testing in the obvious way threw errors.

Kind regards,
Paul

[cmungall]

How would you expect this to work?

A translation of rdf_assert(rdf(S,P,O)) to SPARQL should be straightforward

It's not clear how asserted terms whose predicates are used in rules should be handled.

Perhaps these could be rewritten such that if we have

name(X,Y):- rdf(X,foaf:name,Y).

and say rdf_assert(name(id:123,"fred")) then the appropriate SPARQL using foaf:name would be used?

[PaulBrownMagic]

As sparqlprog mirrors rdf/3 in a query like endpoint ?? rdf(S, P, O). I'd expect it to mirror rdf_assert/3 in the same way: endpoint ?? rdf_assert(S, P, O)., also endpoint ?? rdf_retractall(S, P, O).

A rule then would be:

assert_name(X, Y) :- rdf_assert(X, foaf:name, Y).

?- endpoint ?? assert_name(id:123, "fred").

Mirroring the existing predicates in SWI's semweb library increases transferability, but your idea has a certain elegance to it. Personally, I'd just be happy to have the feature, no matter the implementation.

[cmungall]

Ah, I see. It may be possible to support both. We'd have to be clear about the semantics of translating a program that includes both query and update components, but this should be doable I am not sure when I might get to this though...

…

On Mon, Nov 11, 2019 at 2:55 PM Paul Brown ***@***.***> wrote: As sparqlprog mirrors rdf/3 in a query like endpoint ?? rdf(S, P, O). I'd expect it to mirror rdf_assert/3 in the same way: endpoint ?? rdf_assert(S, P, O)., also endpoint ?? rdf_retractall(S, P, O). A rule then would be: assert_name(X, Y) :- rdf_assert(X, foaf:name, Y). ?- endpoint ?? assert_name(id:123, "fred"). Mirroring the existing predicates in SWI's semweb library increases transferability, but your idea has a certain elegance to it. Personally, I'd just be happy to have the feature, no matter the implementation. — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#10?email_source=notifications&email_token=AAAMMOL357TXVE6UDRA7SCTQTHPFLA5CNFSM4JL3RACKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEDYNL4Y#issuecomment-552654323>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAAMMOOLZEMMZODIVN7YXR3QTHPFLANCNFSM4JL3RACA> .