Skip to first unread message
nickyvo...@gmail.com
Sep 6, 2016, 3:56:44 AM9/6/16
to Stardog
Hi,
Currently, we have been working on migrating our systems to the Stardog Graphstore. However, we encounter some issues using federated queries.
Because of the usage of different and variable graphstores and repositories, a lot of SPARQL queries are based on federated queries with service urls in ?serviceVariables.
However, Stardog does not support this construction. Using hardcoded references to endpoints is not really an option. My question, is how should we cope with this issue.
Is there an alternative way to deal with this federated service variables? And is using service variables something which is planned for future versions of Stardog?
Thanks,
Currently, we have been working on migrating our systems to the Stardog Graphstore. However, we encounter some issues using federated queries.
Because of the usage of different and variable graphstores and repositories, a lot of SPARQL queries are based on federated queries with service urls in ?serviceVariables.
However, Stardog does not support this construction. Using hardcoded references to endpoints is not really an option. My question, is how should we cope with this issue.
Is there an alternative way to deal with this federated service variables? And is using service variables something which is planned for future versions of Stardog?
Thanks,
Michael Grove
Sep 6, 2016, 10:45:24 AM9/6/16
to stardog
On Tue, Sep 6, 2016 at 3:56 AM, <nickyvo...@gmail.com> wrote:
> Hi,
>
> Currently, we have been working on migrating our systems to the Stardog
> Graphstore. However, we encounter some issues using federated queries.
> Because of the usage of different and variable graphstores and repositories,
> a lot of SPARQL queries are based on federated queries with service urls in
> ?serviceVariables.
>
> However, Stardog does not support this construction.
Correct.
> Hi,
>
> Currently, we have been working on migrating our systems to the Stardog
> Graphstore. However, we encounter some issues using federated queries.
> Because of the usage of different and variable graphstores and repositories,
> a lot of SPARQL queries are based on federated queries with service urls in
> ?serviceVariables.
>
> However, Stardog does not support this construction.
> Using hardcoded
> references to endpoints is not really an option. My question, is how should
> we cope with this issue.
issue the federated query.
> Is there an alternative way to deal with this federated service variables?
> And is using service variables something which is planned for future
> versions of Stardog?
roadmap. It's worth pointing out that while the use of a variable with
the SERVICE keyword is syntactically valid, the SPARQL spec does not
define any actual semantics for what that means.
Cheers,
Mike
>
>
> Thanks,
>
>
> --
> -- --
> You received this message because you are subscribed to the C&P "Stardog"
> group.
> To post to this group, send email to sta...@clarkparsia.com
> To unsubscribe from this group, send email to
> stardog+u...@clarkparsia.com
> For more options, visit this group at
> http://groups.google.com/a/clarkparsia.com/group/stardog?hl=en
Reply all
Reply to author
Forward
0 new messages