Andy - done.
On Wed, Mar 4, 2020 at 12:25 PM Andy Seaborne wrote:
> java.net.URI is not perfect and it is also a mixture of RFC2396, RFC3896
> and some pragmatics.
>
> Jena's own jena-iri gets it right.
>
>// NB The argument order can catch you out.
>IRI iri = IRIResolver.resolve("pictur
java.net.URI is not perfect and it is also a mixture of RFC2396, RFC3896
and some pragmatics.
Jena's own jena-iri gets it right.
// NB The argument order can catch you out.
IRI iri = IRIResolver.resolve("picture.jpg", "http://mysite.net"; );
System.out.println(iri);
but jsonld-java uses
Thanks for the reference Martynas! According to the section referenced,
the following two URLs are equivalent.
http://example.com
http://example.com/
I can modify my own code to do the check and fix it for myself, but I
would think URI.resolve should treat them as equivalents and not
URI.resolve() will not assume anything.
Base URI normally ends with a /. Don’t know if this is the best reference,
but close:
https://tools.ietf.org/html/rfc3986#section-6.2.3
You need to check the URI RFC and its resolution algorithm.
On Wed, 4 Mar 2020 at 16.57, Erich Bremer wrote:
> This al
This also works:
URI uri = new URI("http://mysite.net";);
System.out.println(uri.resolve("/picture.jpg"));
but if no trailing "/" and no leading "/" on path will yield the
concatenated http://mysite.netpicture.jpg which then gets tossed and a
blank node is formed.
Should URI.reso
The program works if I specify the base with a trailing slash as "
http://mysite.net/";
I ran through the code and the problem appears to be here:
https://github.com/jsonld-java/jsonld-java/blob/66012db2f53b009cedeae50c83b5594b9dd05e11/core/src/main/java/com/github/jsonldjava/utils/JsonLdUrl.java#L
The error is
[2020-03-04 16:51:56] Fuseki INFO [553] POST
http://insight-dev.lingsoft.fi/ds?graph=https://resource.lingsoft.fi/graph/lsauth-demo
[2020-03-04 16:51:56] Fuseki ERROR [line: 1, col: 34] Undefined
prefix: ebucore
[2020-03-04 16:51:56] Fuseki INFO [553] 400 Parse erro
Same thing:
Source JSONLD
{
"@context": [
"http://schema.org";
],
"@graph": [
{
"@type": "CreativeWork",
"@id": "picture.jpg"
},
{
"@id": "./",
"@type": "DataSet"
}
]
}
AFTER loading
The exact command is
curl -X POST -H "Content-type: text/turtle" --data-binary
@/tmp/subtitle.ttl
https://xxx.fi/fuseki/ds?graph=https://example.com/graph/demo
and according to ngrep result was returned before the entire sending.
This https://xxx.fi/fuseki/ds is proxy address pointing to
I will try with the other library to check.
On Wed, Mar 4, 2020 at 4:29 AM Rob Vesse wrote:
> This may be an upstream bug or it could be a bug in how we configure the
> underlying parser
>
> Jena's JSON-LD support is based upon the
> https://github.com/jsonld-java/jsonld-java library so you coul
What makes your tech support think that?
What operation is being called?
Andy
On 04/03/2020 13:36, Mikael Pesonen wrote:
Hi,
We have reverse proxy on Fuseki.
I'm getting this error occasionally when posting data to fuseki dataset
endpoint and data is containing some error. Instead of Fu
Hi,
We have reverse proxy on Fuseki.
I'm getting this error occasionally when posting data to fuseki dataset
endpoint and data is containing some error. Instead of Fuseki response
400 client gets 502. Our technical support thinks this might be because
Fuseki sends respond before receiving th
This may be an upstream bug or it could be a bug in how we configure the
underlying parser
Jena's JSON-LD support is based upon the
https://github.com/jsonld-java/jsonld-java library so you could try and
reproduce your test case just using their library directly which would
determine if it is
13 matches
Mail list logo
