Re: Use PREFIXes by default

The choice of prefixes in returned RDF is up to the server. IIRC the prefixes are those in the storage with the ones from the query added. Calculating which prefixes are actually used, given a large set of prefixes needs a scan of the whole of the results before sending any (RDF/XML, Turtle,

Re: Inline Values and XSD Time Series

On 27/02/18 11:41, Marco Neumann wrote: Hi Andy, (I presume you wrote the following below) could you please elaborate on the significance of this contribution in TDB? Hi Marco, For certain XSD datatypes, the value is stored in the NodeId (64 bits, minus the datatype indicator - 56 bits for

Re: AW: URI of anonymous classes

Jos, this reminds me of a similar issue I had: https://www.mail-archive.com/users@jena.apache.org/msg06279.html Ideally you should have explicit rdfs:isDefinedBy statements for each term, linking them to their defining ontology. On Tue, Feb 27, 2018 at 7:59 PM, Jos Lehmann <

NullPointerExceptions in v3.6.0

I've got a small application that follows the standard recommended pattern: // initialise dataset / model ... try { // ... add statements StmtIterator r = this.my_model.listStatements(); System.out.println(r.toList().size()); this.dataset.commit(); } catch

AW: AW: URI of anonymous classes

Hi Lorenz If you could be more specific it would help. The restrictions I am working with don't seem to have a URI, so I can't tell if, in the input ontologies, they belong to the imported ontology or to the importing ontology. I.e.: WHEN DOING: ExtendedIterator properties =

URI of anonymous classes

Hi there I am rewriting an ontology using jena. I rewrite each import. When rewriting an importing ontology, anonymous classes (e.g. restrictions or disjointness axioms) of the imported ontology appear twice in the importing ontology, because to re-write the importing ontology I am working

Re: Configuring fuseki with TDB2 and OWL reasoning

TBH we are still prototyping and it seems that the use cases are limited class generalisation, inverse ,symmetric and transitive properties. Something - I started thinking - I can simulate with a RDBMS ... But then I would loose that sweet SPARQL... 2018-02-26 17:00 GMT-05:00 Andy Seaborne

future work: reasinging

For my work, the most important feature would be "same-as" (like Laura), with the same justification. Afterwards, I would use reasoning that is achievable with simple construct queries and then store the result. An actual example: construct {?tok a ?pattern .} FROM

AW: URI of anonymous classes

As an integration to my question (see Ursprüngliche Nachricht) please see further down the ouput of re-writing the importing ontology*. The same intersection is repeated. Yet, Protege is able to tell that one of the two intesections comes from the imported ontology the other from the importing

Re: Use PREFIXes by default

Do these libraries also add PREFIXes for the output? For example I send a query, get a XML or JSON-LD back, and the library automatically applies known prefixes to the JSON-LD?     Sent: Tuesday, February 27, 2018 at 12:08 PM From: "Osma Suominen" To: 

Re: Use PREFIXes by default

What I meant is that it can be a good idea to keep this feature on the client if libraries can apply PREFIXes that I define on the client side. If I'm correct the results that are returned by Fuseki contains only the same PREFIXes that were defined in the input. But the results can have data

Re: Use PREFIXes by default

ajs6f kirjoitti 25.02.2018 klo 23:46: If you are not concerned about performance, why not add those prefixes client-side? Some client-side libraries do this. With EasyRdf (for PHP), you declare your prefixes once, and the library knows about the common ones so you don't have to declare

Inline Values and XSD Time Series

Hi Andy, (I presume you wrote the following below) could you please elaborate on the significance of this contribution in TDB? "The xsd:dateTime and xsd:date ranges cover about 8000 years from year zero with a precision down to 1 millisecond. Timezone information is retained to an accuracy of 15

Re: AW: URI of anonymous classes

You can get access to imported models via OntModel::getImportedModel(String uri) or OntModel::listSubModels(boolean withImports) Javadoc[1] is always your friend. [1] https://jena.apache.org/documentation/javadoc/jena/org/apache/jena/ontology/OntModel.html On 27.02.2018 11:48, Jos Lehmann

Re: Use PREFIXes by default

Laura Morales kirjoitti 27.02.2018 klo 13:48: Do these libraries also add PREFIXes for the output? For example I send a query, get a XML or JSON-LD back, and the library automatically applies known prefixes to the JSON-LD? Isn't that the responsibility of the SPARQL endpoint? For XML, the

Re: Use PREFIXes by default

I don't think sending results without prefixes is possible, as it would make them invalid in respect to their format. Sounds like a really bad idea TBH. On Tue, Feb 27, 2018 at 12:48 PM, Laura Morales wrote: > Do these libraries also add PREFIXes for the output? For example I

Jena Property Table

Hello Jena team, I have a query regarding Jena Property table, it is deprecated, is any alternative provided for this? Should I use it in my project or not? Please help me. Regards, Samita P : Please consider the environment before printing this e-mail

Re: Use PREFIXes by default

> The choice of prefixes in returned RDF is up to the server. IIRC the > prefixes are those in the storage with the ones from the query added. Storage: do you mean those saved in TDB or does Fuseki have a place where it can store known prefixes to apply to the output?

Re: AW: AW: URI of anonymous classes

Models in Jena contain the statements, thus, you should be able to determine which model contains the statement. On 27.02.2018 19:59, Jos Lehmann wrote: > Hi Lorenz > > If you could be more specific it would help. > > The restrictions I am working with don't seem to have a URI, so I can't tell