: Nicholas Car
Date: Thursday, 4 May 2023 at 10:58
To: users@jena.apache.org
Subject: Re: Binary literals
Hi Rob,
Thanks for this: it is pretty much as I thought!
I think we will be able to cater for WKB then in GeoSPARQL 1.3 with just hex
encoding of the value and ^^geo:wkbLiteral
string
> encoded is irrelevant.
> >
> > Regards,
> >
> > Rob Vesse
> >
> > From: Nicholas Car n...@kurrawong.net
> >
> > Date: Wednesday, 3 May 2023 at 23:22
> > To: users@jena.apache.org users@jena.apache.org
> >
> > Subject: Re: Binary li
My 2 cents: Base 64 might be preferable to Hex encoding since it is inherently
more compact
Rob
From: Nicholas Car
Date: Thursday, 4 May 2023 at 10:58
To: users@jena.apache.org
Subject: Re: Binary literals
Hi Rob,
Thanks for this: it is pretty much as I thought!
I think we will be able
ata into its own internal
> index structures that will be very efficient to access, at which point
> whether the binary data was originally string encoded is irrelevant.
>
> Regards,
>
> Rob Vesse
>
> From: Nicholas Car n...@kurrawong.net
>
> Date: Wednes
binary data was originally string encoded is irrelevant.
Regards,
Rob Vesse
From: Nicholas Car
Date: Wednesday, 3 May 2023 at 23:22
To: users@jena.apache.org
Subject: Re: Binary literals
I see Base64 is an XSD option too, but I’m most interested in “true” binary, as
opposed to binary-as-text options,
ena users,
>
> How can I store binary literals in RDF and in Jena/Fuseki?
>
> There is xsd:hexBinary for arbitrary binary data but is there a better/more
> efficient/another way to store binary literals in Jena?
>
> The reason I ask is that a future version of GeoSPARQL might want
Dear Jena users,
How can I store binary literals in RDF and in Jena/Fuseki?
There is xsd:hexBinary for arbitrary binary data but is there a better/more
efficient/another way to store binary literals in Jena?
The reason I ask is that a future version of GeoSPARQL might want to include
WKB
