Serializing Model worked for me using Spark Dataset API. Model was not
associated with any database.
Models were constructed from turtle string and then transformed to
another serializable form.
...
private final Encoder MODEL_ENCODER = Encoders.bean(Model.class);
...
URIs do not have semantic meaning, they are opaque identifiers.
https://www.w3.org/DesignIssues/Axioms.html#opaque
On Tue, 2 Jul 2019 at 17.06, Siddhesh Rane wrote:
> If the URL is some REST endpoint then you can map UUID in the URL to
> binary keys in the database.
> If your URLs are RDF
On 02/07/2019 18:06, Siddhesh Rane wrote:
If the URL is some REST endpoint then you can map UUID in the URL to
binary keys in the database.
If your URLs are RDF resource identifiers, then better to stick with
hyphenated UUID form that is standard.
Yes they are.
Just out of curiosity, RDF
If the URL is some REST endpoint then you can map UUID in the URL to
binary keys in the database.
If your URLs are RDF resource identifiers, then better to stick with
hyphenated UUID form that is standard.
Just out of curiosity, RDF is mostly for semantic data that has some meaning.
If you are
Thank you.
> Sent: Tuesday, July 02, 2019 at 3:26 PM
> From: "Andy Seaborne"
> To: users@jena.apache.org
> Subject: Re: RDFDataset dump inferred triples only
>
> Somehow subtract the base triples from the complete data.
>
> If there are no bnodes, get the base and complete to a file and use
>
This is handy to know, but in this case we are serving data over the id
URLs, so that's why https://example.com type.
On 02/07/2019 11:47, Claude Warren wrote:
I agree with Andy, but note that there is a URN specification for UUID (
https://tools.ietf.org/html/rfc4122)
So the URI would
One area where performance hit occurs is when the data being accessed
is not in memory, requiring disk IO.
Assuming database files are cached in RAM, you could fit more entries
in one page if the key size was smaller, reducing the probability of
cache misses.
Better way is to go with standard
Somehow subtract the base triples from the complete data.
If there are no bnodes, get the base and complete to a file and use
sort(1) and comm(1).
If there are bnodes, some (slow!) query with a GRAPH/FILTER (NOT) EXISTS
might do it.
Andy
On 02/07/2019 11:12, Dave Reynolds wrote:
On
Ok that explains. Don't remember seeing it on stack trace before...
On 02/07/2019 15:33, Andy Seaborne wrote:
On 02/07/2019 13:01, Mikael Pesonen wrote:
weird #011
Which is a tab - octal 011 is decimal 9.
--
Lingsoft - 30 years of Leading Language Management
www.lingsoft.fi
Speech
On 02/07/2019 13:01, Mikael Pesonen wrote:
weird #011
Which is a tab - octal 011 is decimal 9.
We have had the service running for few months without issues but now
got this. So there is exception and also weird #011 happening in log...
This same error happens now every time with this query.
Jul 2 07:59:37 insight-kaupk java[1043]: [2019-07-02 07:59:37]
Fuseki INFO [3457647]
On 02/07/2019 11:09, Laura Morales wrote:
Can I do this with one of the Jena command line tools?
Not that I know of, don't think there's a command line tool for running
a set rules over data.
Dave
Sent: Tuesday, July 02, 2019 at 11:34 AM
From: "Dave Reynolds"
To: users@jena.apache.org
Can I do this with one of the Jena command line tools?
> Sent: Tuesday, July 02, 2019 at 11:34 AM
> From: "Dave Reynolds"
> To: users@jena.apache.org
> Subject: Re: RDFDataset dump inferred triples only
>
> On 02/07/2019 09:19, Laura Morales wrote:
> > How can I dump to a .nt files *only* the
On 02/07/2019 09:19, Laura Morales wrote:
How can I dump to a .nt files *only* the inferred triples in a RDFDataset?
In other words, I have a RDFDataset with a GenericRuleReasoner InfModel, and I
would like to export all the inferred triples to a file.
If you are only using forward rules then
I agree with Andy, but note that there is a URN specification for UUID (
https://tools.ietf.org/html/rfc4122)
So the URI would be urn:uuid:
I used this in a recent project.
Claude
On Tue, Jul 2, 2019 at 8:53 AM Andy Seaborne wrote:
> I doubt one URI design vs another where it will make any
Thanks for replies. I was thinking of a case where there are billions of
triplets and search could be slightly faster because of shorter string
lenght. But yes, if the difference is few milliseconds here or there
it's not worth it...
On 02/07/2019 10:52, Andy Seaborne wrote:
I doubt one
How can I dump to a .nt files *only* the inferred triples in a RDFDataset?
In other words, I have a RDFDataset with a GenericRuleReasoner InfModel, and I
would like to export all the inferred triples to a file.
I doubt one URI design vs another where it will make any observable
difference.
Andy
On 01/07/2019 18:50, Siddhesh Rane wrote:
You could save the UUID as a 128 bit number in the database.
Conversion between alphanumeric and byte encoded UUIDs can be done on
the fly.
This would be the most
18 matches
Mail list logo
