stardog

问题 I don't quite understand why in SPARQL they haven't implemented the basic logic operators. However in most of the cases is possible to obtain the same result in a number of way. The purpose of this question is to have a quick reference for the possible way troughs that can substitute an "or" statement. Here's what I can think of: 1) UNION e.g: SELECT * WHERE { { ?s :propA ?o } UNION { ?s :propB ?o } } -not often suitable because it can became very verbose because SELECT * WHERE { { GRAPH ?g {

问题 I don't quite understand why in SPARQL they haven't implemented the basic logic operators. However in most of the cases is possible to obtain the same result in a number of way. The purpose of this question is to have a quick reference for the possible way troughs that can substitute an "or" statement. Here's what I can think of: 1) UNION e.g: SELECT * WHERE { { ?s :propA ?o } UNION { ?s :propB ?o } } -not often suitable because it can became very verbose because SELECT * WHERE { { GRAPH ?g {

问题 I am using Stardog to store a bunch of triples that come from different sources. I use Jena to collect and merge the data in a single Jena graph. All these triples are part of ABoxes. I am not sure Stardog will require that the TBox is also merged with the ABox graphs. I supposed it does because otherwise I cannot see how Stardog will do reasoning over the data. I have not seen any option to store and use the TBox apart as in some others triple stores. Do I need to include the TBox in the

问题 I am using Stardog to store a bunch of triples that come from different sources. I use Jena to collect and merge the data in a single Jena graph. All these triples are part of ABoxes. I am not sure Stardog will require that the TBox is also merged with the ABox graphs. I supposed it does because otherwise I cannot see how Stardog will do reasoning over the data. I have not seen any option to store and use the TBox apart as in some others triple stores. Do I need to include the TBox in the

问题 I am trying to query a stardog server using graphql below is my code. import { GraphQLSchema, GraphQLObjectType, GraphQLInt, GraphQLString, GraphQLList, GraphQLNonNull, GraphQLID, GraphQLFloat } from 'graphql'; import axios from 'axios'; var stardog = require("stardog"); let Noun = new GraphQLObjectType({ name: "Noun", description: "Basic information on a GitHub user", fields: () => ({ "c": { type: GraphQLString, resolve: (obj) => { console.log(obj); } } }) }); const query = new

问题 I have a SPARQL query that returns results in the Stardog query panel when inference is enabled, but not when it's disabled. When I try the query through python with SPARQLwrapper, I get no results. I tried with a different query, which doesn't rely on inference, and got the same results through the Stardog query panel without inference and through SPARQLwrapper. So I suspect reasoning is not being applied when I query through python, and that this is why there's no results. So my question is

问题 I'm trying to use federated queries with Jena via a Fuseki endpoint. With the SERVICE keyword in my SPARQL query, I'm connecting to a Stardog endpoint. As it's a secured URL, the endpoint is specified as follows: http://admin:admin@url. As this is not secure, Jena shows the following message: Code: 36/HAS_PASSWORD in USER: Including passwords in URIs is deprecated. According to the docs, you can specify srv:queryAuthUser and srv:queryAuthPwd for the credentials. Is there any way to do this

问题 Can somebody give one java example of sparql insert/Delete query in Stardog. there is only queryExecution.execSelect() method available. there is no queryExecution.execInsert() or queryExecution.execDelete() available. Please give one working example. EDIT I've found this this from stardog docs page. http://stardog.com/docs/#notes As of 1.1.5, Stardog's SPARQL 1.1 support does not include: UPDATE query language does that means no way out for editing a tuple once entered? 回答1: Stardog does not