Duration comparison question

When I compare 28 days to 1 month and 365 days to 1 year in Fuseki 1.1.1 , I get the following: SELECT ("P28D"^^ ="P1M"^^ as ?same) {} | same | | true | SELECT ("P365D"^^

Re: RDF/XML-ABBREV problems with inline node expansion

Hi Tony, Yes, I understood this was a different question. My point is that your example of what output you need seems to be pretty close to the basic writer with no expansion of linked resources at all and the only obvious difference being the in-lining of types. Taking the basic writer and a

Re: RDF/XML-ABBREV problems with inline node expansion

Hi Dave: Actually this is a different problem from my initial query (which was indeed about multiple typed nodes and selecting a preferred form - we'll take that one away). This is a completely separate issue and relates to the way that the RDF/XML-ABBREV serializer works. As noted we have encou

Re: RDF/XML-ABBREV problems with inline node expansion

Hi Tony, If what you actually need is the basic writer plus in-lining of (selected) RDF types then you could consider developing your own. If I recall correctly the RDF/XML basic (non-ABBREV) writer is actually very simple and easy to specialize by inheritance. Then you could contribute your e

Re: RDF/XML-ABBREV problems with inline node expansion

Hi Martynas: We want the RDF/XML-ABBREV format for RDF typed nodes. We'd prefer not getting inline expansion as the XML is then more regular and easier to query with XML tooling. (For the use case see our ISWC 2014 presentation here [1]. We're modelling in RDF and querying in XML. We're chasing s

Re: RDF/XML-ABBREV problems with inline node expansion

So what is the difference between Jena's RDF/XML and Rapper's RDF/XML? The only thing I can see that Rapper inlines RDF type and Jena uses rdf:Description. That can be easily fixed using XML tools such as XSLT. The question is, why do you need such specific output? On Mon, Nov 17, 2014 at 3:39 PM

Re: RDF/XML-ABBREV problems with inline node expansion

Hi Martynas: As said: > The basic RDF/XML output from Jena is not what we need. We just need a >better, more regular, RDF/XML-ABBREV such as the rapper output. Cheers, Tony On 17/11/2014 14:35, "Martynas Jusevičius" wrote: >Tony, > >have you tried dropping the -ABBREV and simply using RDF

Re: RDF/XML-ABBREV problems with inline node expansion

Tony, have you tried dropping the -ABBREV and simply using RDF/XML? Martynas graphityhq.com On Mon, Nov 17, 2014 at 3:26 PM, Hammond, Tony wrote: > Hi: > > I've got another couple questions about RDF/XML-ABBREV format. > > When using the RDF/XML-ABBREV serializer to output a pretty-printed gra

RDF/XML-ABBREV problems with inline node expansion

Hi: I've got another couple questions about RDF/XML-ABBREV format. When using the RDF/XML-ABBREV serializer to output a pretty-printed graph on our subject taxonomy but we get object nodes expanded inline on their first mention. See example output below [1] where I've shown only the URI referen

re: Problem with spatial query

A colleague has identified a resolution. If we index the items in SOLR with a comma between lat and long rather than a space, then they're properly handled. Thanks Tim

Re: Problem with Pellet and Jena's OntProperty.listRange()

Hi, Your code looks fine and since it works with Jena without Pellet that suggests this is a Pellet issue and should be reported to the Pellet folks. One work around you could try is to explicitly call a rebind() after the changes to age. I don't know if Pellet supports this or why it might