[GitHub] [jena] afs commented on issue #584: JENA-1734: Add $FUSEKI_BASE/extra to the fuseki-server classpath.
afs commented on issue #584: JENA-1734: Add $FUSEKI_BASE/extra to the fuseki-server classpath. URL: https://github.com/apache/jena/pull/584#issuecomment-526357832 FYI: See #595 - more work for Fuseki configuration allowing for custom functionality. This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[jira] [Commented] (JENA-1745) Update version of jackson-databind to 2.9.9.3
[ https://issues.apache.org/jira/browse/JENA-1745?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16918737#comment-16918737 ] ASF subversion and git services commented on JENA-1745: --- Commit 3f22bdc7aebe3fd3a552be4d85e45a69914330c4 in jena's branch refs/heads/jena1745-jackson-databind from Andy Seaborne [ https://gitbox.apache.org/repos/asf?p=jena.git;h=3f22bdc ] JENA-1745: Update jackson-dadatbind version > Update version of jackson-databind to 2.9.9.3 > - > > Key: JENA-1745 > URL: https://issues.apache.org/jira/browse/JENA-1745 > Project: Apache Jena > Issue Type: Improvement >Reporter: Andy Seaborne >Priority: Major > > (2.9.9.3 was released 2019-08-06) > 2.9.9.3 addresses CVE-2019-14379. > h1. -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Commented] (JENA-1745) Update version of jackson-databind to 2.9.9.3
[ https://issues.apache.org/jira/browse/JENA-1745?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16918745#comment-16918745 ] ASF subversion and git services commented on JENA-1745: --- Commit 43dbb96c8a1664330ad018bebb0ed4dd6695e039 in jena's branch refs/heads/jena1745-jackson-databind from Andy Seaborne [ https://gitbox.apache.org/repos/asf?p=jena.git;h=43dbb96 ] JENA-1745: Update jackson-databind version > Update version of jackson-databind to 2.9.9.3 > - > > Key: JENA-1745 > URL: https://issues.apache.org/jira/browse/JENA-1745 > Project: Apache Jena > Issue Type: Improvement >Reporter: Andy Seaborne >Priority: Major > > (2.9.9.3 was released 2019-08-06) > 2.9.9.3 addresses CVE-2019-14379. > h1. -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Created] (JENA-1745) Update version of jackson-databind to 2.9.9.3
Andy Seaborne created JENA-1745: --- Summary: Update version of jackson-databind to 2.9.9.3 Key: JENA-1745 URL: https://issues.apache.org/jira/browse/JENA-1745 Project: Apache Jena Issue Type: Improvement Reporter: Andy Seaborne (2.9.9.3 was released 2019-08-06) 2.9.9.3 addresses CVE-2019-14379. h1. -- This message was sent by Atlassian Jira (v8.3.2#803003)
[GitHub] [jena] afs opened a new pull request #596: JENA-1744: Split as a Curie
afs opened a new pull request #596: JENA-1744: Split as a Curie URL: https://github.com/apache/jena/pull/596 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[jira] [Comment Edited] (JENA-1744) JSON-LD writing handles non-qname property URI badly.
[
https://issues.apache.org/jira/browse/JENA-1744?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16918459#comment-16918459
]
Andy Seaborne edited comment on JENA-1744 at 8/29/19 9:58 AM:
--
Changing to a "curie" split will produce:
{noformat}
{
"@id" : "http://somewhere/s1;,
"(prop1)" : "123",
"(prop2)" : "456",
"@context" : {
"(prop2)" : {
"@id" : "http://example/ns/(prop2)"
},
"(prop1)" : {
"@id" : "http://example/ns/(prop1)"
}
}
}
{noformat}
The JSON keys are "(prop1)" and "(prop2)".
was (Author: andy.seaborne):
Changing to a "curie" split will produce:
{noformat}
{
"@graph" : [ {
"@id" : "http://somewhere/s1;,
"(prop1)" : "prop 1"
}, {
"@id" : "http://somewhere/s2;,
"(prop2)" : "prop 2"
} ],
"@context" : {
"(prop2)" : {
"@id" : "http://example/ns/(prop2)"
},
"(prop1)" : {
"@id" : "http://example/ns/(prop1)"
}
}
}
{noformat}
The object keys are "(prop1)" and "(prop2)".
> JSON-LD writing handles non-qname property URI badly.
> -
>
> Key: JENA-1744
> URL: https://issues.apache.org/jira/browse/JENA-1744
> Project: Apache Jena
> Issue Type: Improvement
> Components: RIOT
>Affects Versions: Jena 3.12.0
>Reporter: Andy Seaborne
>Assignee: Andy Seaborne
>Priority: Major
>
> Example Turtle file, no prefixes:
> {noformat}
> "123" .
> "456" .
> {noformat}
> produces ({{riot --pretty JSONLD D.ttl}}) the JSON LD
> {noformat}
> {
> "@id" : "http://somewhere/s1;,
> "http://example/ns/(prop1)" : "123",
> "" : "456",
> "@context" : {
> "" : {
> "@id" : "http://example/ns/(prop2)"
> }
> }
> }
> {noformat}
> which parses back to to the original RDF triples correctly.
> However, the treatment of the two properties is asymmetric - one is context
> "" and one is full URI as "http://example/ns/(prop1)".
> This can create problems downstream if the JSON-LD is treated as JSON (the
> motivating case is ingesting extracted RDF data into a BI-tool via it's JSON
> adapter).
> The [JSONLD writer (line
> 321)|https://github.com/apache/jena/blob/0dde76f777e55109a75db87c855bfc17e40c9d4a/jena-arq/src/main/java/org/apache/jena/riot/writer/JsonLDWriter.java#L321]
> uses "{{p.getLocalName()}}" to choose JSON-LD field name. In both cases, it
> is "" because "()" are legal in a URI but not legal for an RDF qname
> localname. The XML-split is the pair (full-URI, "").
> JSON-LD does not need the restrictions need for RDF/XML. The split can be
> made at the "/". JSON-LD uses [curies|https://www.w3.org/TR/curie/].
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
[jira] [Updated] (JENA-1744) JSON-LD writing handles non-qname property URI badly.
[
https://issues.apache.org/jira/browse/JENA-1744?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andy Seaborne updated JENA-1744:
Description:
Example Turtle file, no prefixes:
{noformat}
"123" .
"456" .
{noformat}
produces ({{riot --pretty JSONLD D.ttl}}) the JSON LD
{noformat}
{
"@id" : "http://somewhere/s1;,
"http://example/ns/(prop1)" : "123",
"" : "456",
"@context" : {
"" : {
"@id" : "http://example/ns/(prop2)"
}
}
}
{noformat}
which parses back to to the original RDF triples correctly.
However, the treatment of the two properties is asymmetric - one is context ""
and one is full URI as "http://example/ns/(prop1)".
This can create problems downstream if the JSON-LD is treated as JSON (the
motivating case is ingesting extracted RDF data into a BI-tool via it's JSON
adapter).
The [JSONLD writer (line
321)|https://github.com/apache/jena/blob/0dde76f777e55109a75db87c855bfc17e40c9d4a/jena-arq/src/main/java/org/apache/jena/riot/writer/JsonLDWriter.java#L321]
uses "{{p.getLocalName()}}" to choose JSON-LD field name. In both cases, it is
"" because "()" are legal in a URI but not legal for an RDF qname localname.
The XML-split is the pair (full-URI, "").
JSON-LD does not need the restrictions need for RDF/XML. The split can be made
at the "/". JSON-LD uses [curies|https://www.w3.org/TR/curie/].
was:
Example Turtle file, no prefixes:
{noformat}
"123" .
"456" .
{noformat}
produces ({{riot --pretty JSONLD D.ttl}}) the JSON LD
{noformat}
{noformat}
which parses back to to the original RDF triples correctly.
However, the treatment of the two properties is asymmetric - one is context ""
and one is full URI as "http://example/ns/(prop1)".
This can create problems downstream if the JSON-LD is treated as JSON (the
motivating case is ingesting extracted RDF data into a BI-tool via it's JSON
adapter).
The [JSONLD writer (line
321)|https://github.com/apache/jena/blob/0dde76f777e55109a75db87c855bfc17e40c9d4a/jena-arq/src/main/java/org/apache/jena/riot/writer/JsonLDWriter.java#L321]
uses "{{p.getLocalName()}}" to choose JSON-LD field name. In both cases, it is
"" because "()" are legal in a URI but not legal for an RDF qname localname.
The XML-split is the pair (full-URI, "").
JSON-LD does not need the restrictions need for RDF/XML. The split can be made
at the "/". JSON-LD uses [curies|https://www.w3.org/TR/curie/].
> JSON-LD writing handles non-qname property URI badly.
> -
>
> Key: JENA-1744
> URL: https://issues.apache.org/jira/browse/JENA-1744
> Project: Apache Jena
> Issue Type: Improvement
> Components: RIOT
>Affects Versions: Jena 3.12.0
>Reporter: Andy Seaborne
>Assignee: Andy Seaborne
>Priority: Major
>
> Example Turtle file, no prefixes:
> {noformat}
> "123" .
> "456" .
> {noformat}
> produces ({{riot --pretty JSONLD D.ttl}}) the JSON LD
> {noformat}
> {
> "@id" : "http://somewhere/s1;,
> "http://example/ns/(prop1)" : "123",
> "" : "456",
> "@context" : {
> "" : {
> "@id" : "http://example/ns/(prop2)"
> }
> }
> }
> {noformat}
> which parses back to to the original RDF triples correctly.
> However, the treatment of the two properties is asymmetric - one is context
> "" and one is full URI as "http://example/ns/(prop1)".
> This can create problems downstream if the JSON-LD is treated as JSON (the
> motivating case is ingesting extracted RDF data into a BI-tool via it's JSON
> adapter).
> The [JSONLD writer (line
> 321)|https://github.com/apache/jena/blob/0dde76f777e55109a75db87c855bfc17e40c9d4a/jena-arq/src/main/java/org/apache/jena/riot/writer/JsonLDWriter.java#L321]
> uses "{{p.getLocalName()}}" to choose JSON-LD field name. In both cases, it
> is "" because "()" are legal in a URI but not legal for an RDF qname
> localname. The XML-split is the pair (full-URI, "").
> JSON-LD does not need the restrictions need for RDF/XML. The split can be
> made at the "/". JSON-LD uses [curies|https://www.w3.org/TR/curie/].
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
[jira] [Updated] (JENA-1744) JSON-LD writing handles non-qname property URI badly.
[
https://issues.apache.org/jira/browse/JENA-1744?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andy Seaborne updated JENA-1744:
Description:
Example Turtle file, no prefixes:
{noformat}
"123" .
"456" .
{noformat}
produces ({{riot --pretty JSONLD D.ttl}}) the JSON LD
{noformat}
{noformat}
which parses back to to the original RDF triples correctly.
However, the treatment of the two properties is asymmetric - one is context ""
and one is full URI as "http://example/ns/(prop1)".
This can create problems downstream if the JSON-LD is treated as JSON (the
motivating case is ingesting extracted RDF data into a BI-tool via it's JSON
adapter).
The [JSONLD writer (line
321)|https://github.com/apache/jena/blob/0dde76f777e55109a75db87c855bfc17e40c9d4a/jena-arq/src/main/java/org/apache/jena/riot/writer/JsonLDWriter.java#L321]
uses "{{p.getLocalName()}}" to choose JSON-LD field name. In both cases, it is
"" because "()" are legal in a URI but not legal for an RDF qname localname.
The XML-split is the pair (full-URI, "").
JSON-LD does not need the restrictions need for RDF/XML. The split can be made
at the "/". JSON-LD uses [curies|https://www.w3.org/TR/curie/].
was:
Example Turtle file, no prefixes:
{noformat}
"prop 1" .
"prop 2" .
{noformat}
produces ({{riot --pretty JSONLD D.ttl}}) the JSON LD
{noformat}
{
"@graph" : [ {
"@id" : "http://somewhere/s1;,
"http://example/ns/(prop1)" : "prop 1"
}, {
"@id" : "http://somewhere/s2;,
"" : "prop 2"
} ],
"@context" : {
"" : {
"@id" : "http://example/ns/(prop2)"
}
}
}
{noformat}
which parses back to to the original RDF triples correctly.
However, the treatment of the two properties is asymmetric - one is context ""
and one is full URI as "http://example/ns/(prop1)".
This can create problems downstream if the JSON-LD is treated as JSON (the
motivating case is ingesting extracted RDF data into a BI-tool via it's JSON
adapter).
The [JSONLD writer (line
321)|https://github.com/apache/jena/blob/0dde76f777e55109a75db87c855bfc17e40c9d4a/jena-arq/src/main/java/org/apache/jena/riot/writer/JsonLDWriter.java#L321]
uses "{{p.getLocalName()}}" to choose JSON-LD field name. In both cases, it is
"" because "()" are legal in a URI but not legal for an RDF qname localname.
The XML-split is the pair (full-URI, "").
JSON-LD does not need the restrictions need for RDF/XML. The split can be made
at the "/". JSON-LD uses [curies|https://www.w3.org/TR/curie/].
> JSON-LD writing handles non-qname property URI badly.
> -
>
> Key: JENA-1744
> URL: https://issues.apache.org/jira/browse/JENA-1744
> Project: Apache Jena
> Issue Type: Improvement
> Components: RIOT
>Affects Versions: Jena 3.12.0
>Reporter: Andy Seaborne
>Assignee: Andy Seaborne
>Priority: Major
>
> Example Turtle file, no prefixes:
> {noformat}
> "123" .
> "456" .
> {noformat}
> produces ({{riot --pretty JSONLD D.ttl}}) the JSON LD
> {noformat}
> {noformat}
> which parses back to to the original RDF triples correctly.
> However, the treatment of the two properties is asymmetric - one is context
> "" and one is full URI as "http://example/ns/(prop1)".
> This can create problems downstream if the JSON-LD is treated as JSON (the
> motivating case is ingesting extracted RDF data into a BI-tool via it's JSON
> adapter).
> The [JSONLD writer (line
> 321)|https://github.com/apache/jena/blob/0dde76f777e55109a75db87c855bfc17e40c9d4a/jena-arq/src/main/java/org/apache/jena/riot/writer/JsonLDWriter.java#L321]
> uses "{{p.getLocalName()}}" to choose JSON-LD field name. In both cases, it
> is "" because "()" are legal in a URI but not legal for an RDF qname
> localname. The XML-split is the pair (full-URI, "").
> JSON-LD does not need the restrictions need for RDF/XML. The split can be
> made at the "/". JSON-LD uses [curies|https://www.w3.org/TR/curie/].
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
[jira] [Commented] (JENA-1744) JSON-LD writing handles non-qname property URI badly.
[
https://issues.apache.org/jira/browse/JENA-1744?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16918459#comment-16918459
]
Andy Seaborne commented on JENA-1744:
-
Changing to a "curie" split will produce:
{noformat}
{
"@graph" : [ {
"@id" : "http://somewhere/s1;,
"(prop1)" : "prop 1"
}, {
"@id" : "http://somewhere/s2;,
"(prop2)" : "prop 2"
} ],
"@context" : {
"(prop2)" : {
"@id" : "http://example/ns/(prop2)"
},
"(prop1)" : {
"@id" : "http://example/ns/(prop1)"
}
}
}
{noformat}
The object keys are "(prop1)" and "(prop2)".
> JSON-LD writing handles non-qname property URI badly.
> -
>
> Key: JENA-1744
> URL: https://issues.apache.org/jira/browse/JENA-1744
> Project: Apache Jena
> Issue Type: Improvement
> Components: RIOT
>Affects Versions: Jena 3.12.0
>Reporter: Andy Seaborne
>Assignee: Andy Seaborne
>Priority: Major
>
> Example Turtle file, no prefixes:
> {noformat}
> "prop 1" .
> "prop 2" .
> {noformat}
> produces ({{riot --pretty JSONLD D.ttl}}) the JSON LD
> {noformat}
> {
> "@graph" : [ {
> "@id" : "http://somewhere/s1;,
> "http://example/ns/(prop1)" : "prop 1"
> }, {
> "@id" : "http://somewhere/s2;,
> "" : "prop 2"
> } ],
> "@context" : {
> "" : {
> "@id" : "http://example/ns/(prop2)"
> }
> }
> }
> {noformat}
> which parses back to to the original RDF triples correctly.
> However, the treatment of the two properties is asymmetric - one is context
> "" and one is full URI as "http://example/ns/(prop1)".
> This can create problems downstream if the JSON-LD is treated as JSON (the
> motivating case is ingesting extracted RDF data into a BI-tool via it's JSON
> adapter).
> The [JSONLD writer (line
> 321)|https://github.com/apache/jena/blob/0dde76f777e55109a75db87c855bfc17e40c9d4a/jena-arq/src/main/java/org/apache/jena/riot/writer/JsonLDWriter.java#L321]
> uses "{{p.getLocalName()}}" to choose JSON-LD field name. In both cases, it
> is "" because "()" are legal in a URI but not legal for an RDF qname
> localname. The XML-split is the pair (full-URI, "").
> JSON-LD does not need the restrictions need for RDF/XML. The split can be
> made at the "/". JSON-LD uses [curies|https://www.w3.org/TR/curie/].
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
[jira] [Updated] (JENA-1744) JSON-LD writing handles non-qname property URI badly.
[
https://issues.apache.org/jira/browse/JENA-1744?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andy Seaborne updated JENA-1744:
Description:
Example Turtle file, no prefixes:
{noformat}
"prop 1" .
"prop 2" .
{noformat}
produces ({{riot --pretty JSONLD D.ttl}}) the JSON LD
{noformat}
{
"@graph" : [ {
"@id" : "http://somewhere/s1;,
"http://example/ns/(prop1)" : "prop 1"
}, {
"@id" : "http://somewhere/s2;,
"" : "prop 2"
} ],
"@context" : {
"" : {
"@id" : "http://example/ns/(prop2)"
}
}
}
{noformat}
which parses back to to the original RDF triples correctly.
However, the treatment of the two properties is asymmetric - one is context ""
and one is full URI as "http://example/ns/(prop1)".
This can create problems downstream if the JSON-LD is treated as JSON (the
motivating case is ingesting extracted RDF data into a BI-tool via it's JSON
adapter).
The [JSONLD writer (line
321)|https://github.com/apache/jena/blob/0dde76f777e55109a75db87c855bfc17e40c9d4a/jena-arq/src/main/java/org/apache/jena/riot/writer/JsonLDWriter.java#L321]
uses "{{p.getLocalName()}}" to choose JSON-LD field name. In both cases, it is
"" because "()" are legal in a URI but not legal for an RDF qname localname.
The XML-split is the pair (full-URI, "").
JSON-LD does not need the restrictions need for RDF/XML. The split can be made
at the "/". JSON-LD uses [curies|https://www.w3.org/TR/curie/].
was:
Example Turtle file, no prefixes:
{noformat}
"prop 1" .
"prop 2" .
{noformat}
produces ({{riot --pretty JSONLD D.ttl}}) the JSON LD
{noformat}
{
"@graph" : [ {
"@id" : "http://somewhere/s1;,
"http://example/ns/(prop1)" : "prop 1"
}, {
"@id" : "http://somewhere/s2;,
"" : "prop 2"
} ],
"@context" : {
"" : {
"@id" : "http://example/ns/(prop2)"
}
}
}
{noformat}
which parses back to to the original RDF triples correctly.
However, the treatment of the two properties is asymmetric - one is context ""
and one is full URI as "http://example/ns/(prop1)".
This can creat problems downstream if the JSON-LD is treated as JSON (the
motivating case is ingesting into a BI-tool via it's JSON adapter).
This is because the [JSONLD writer (line
321)|https://github.com/apache/jena/blob/0dde76f777e55109a75db87c855bfc17e40c9d4a/jena-arq/src/main/java/org/apache/jena/riot/writer/JsonLDWriter.java#L321]
uses "{{p.getLocalName()}}" to choose JSON-LD field name. In both cases it is
"" because "()" are legal in a URI but not legal for an RDF qname localname.
The XML-split is (full-URI, "").
> JSON-LD writing handles non-qname property URI badly.
> -
>
> Key: JENA-1744
> URL: https://issues.apache.org/jira/browse/JENA-1744
> Project: Apache Jena
> Issue Type: Improvement
> Components: RIOT
>Affects Versions: Jena 3.12.0
>Reporter: Andy Seaborne
>Assignee: Andy Seaborne
>Priority: Major
>
> Example Turtle file, no prefixes:
> {noformat}
> "prop 1" .
> "prop 2" .
> {noformat}
> produces ({{riot --pretty JSONLD D.ttl}}) the JSON LD
> {noformat}
> {
> "@graph" : [ {
> "@id" : "http://somewhere/s1;,
> "http://example/ns/(prop1)" : "prop 1"
> }, {
> "@id" : "http://somewhere/s2;,
> "" : "prop 2"
> } ],
> "@context" : {
> "" : {
> "@id" : "http://example/ns/(prop2)"
> }
> }
> }
> {noformat}
> which parses back to to the original RDF triples correctly.
> However, the treatment of the two properties is asymmetric - one is context
> "" and one is full URI as "http://example/ns/(prop1)".
> This can create problems downstream if the JSON-LD is treated as JSON (the
> motivating case is ingesting extracted RDF data into a BI-tool via it's JSON
> adapter).
> The [JSONLD writer (line
> 321)|https://github.com/apache/jena/blob/0dde76f777e55109a75db87c855bfc17e40c9d4a/jena-arq/src/main/java/org/apache/jena/riot/writer/JsonLDWriter.java#L321]
> uses "{{p.getLocalName()}}" to choose JSON-LD field name. In both cases, it
> is "" because "()" are legal in a URI but not legal for an RDF qname
> localname. The XML-split is the pair (full-URI, "").
> JSON-LD does not need the restrictions need for RDF/XML. The split can be
> made at the "/". JSON-LD uses [curies|https://www.w3.org/TR/curie/].
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
[jira] [Created] (JENA-1744) JSON-LD writing handles non-qname property URI badly.
Andy Seaborne created JENA-1744:
---
Summary: JSON-LD writing handles non-qname property URI badly.
Key: JENA-1744
URL: https://issues.apache.org/jira/browse/JENA-1744
Project: Apache Jena
Issue Type: Improvement
Components: RIOT
Affects Versions: Jena 3.12.0
Reporter: Andy Seaborne
Assignee: Andy Seaborne
Example Turtle file, no prefixes:
{noformat}
"prop 1" .
"prop 2" .
{noformat}
produces ({{riot --pretty JSONLD D.ttl}}) the JSON LD
{noformat}
{
"@graph" : [ {
"@id" : "http://somewhere/s1;,
"http://example/ns/(prop1)" : "prop 1"
}, {
"@id" : "http://somewhere/s2;,
"" : "prop 2"
} ],
"@context" : {
"" : {
"@id" : "http://example/ns/(prop2)"
}
}
}
{noformat}
which parses back to to the original RDF triples correctly.
However, the treatment of the two properties is asymmetric - one is context ""
and one is full URI as "http://example/ns/(prop1)".
This can creat problems downstream if the JSON-LD is treated as JSON (the
motivating case is ingesting into a BI-tool via it's JSON adapter).
This is because the [JSONLD writer (line
321)|https://github.com/apache/jena/blob/0dde76f777e55109a75db87c855bfc17e40c9d4a/jena-arq/src/main/java/org/apache/jena/riot/writer/JsonLDWriter.java#L321]
uses "{{p.getLocalName()}}" to choose JSON-LD field name. In both cases it is
"" because "()" are legal in a URI but not legal for an RDF qname localname.
The XML-split is (full-URI, "").
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
[jira] [Commented] (JENA-1740) Extending Apache Jena with more geospatial functions
[ https://issues.apache.org/jira/browse/JENA-1740?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16918396#comment-16918396 ] Greg Albiston commented on JENA-1740: - Ideally the textual data formats would be treated with a similar approach to the GeometryLiterals. It will depend upon how costly they are to deserialise but should be possible to re-use/re-purpose the current caching for them. > Extending Apache Jena with more geospatial functions > > > Key: JENA-1740 > URL: https://issues.apache.org/jira/browse/JENA-1740 > Project: Apache Jena > Issue Type: Improvement >Reporter: Timo Homburg >Priority: Minor > > Hello, > I am the developer of a project which I named postgis-jena > (https://github.com/i3mainz/postgis-jena), originally aimed at extending > JenaARQ with query functions common in databases such as POSTGIS but now > going beyond that approach and also integrating support for raster data > (still WIP). I am building up work being done by Greg Albistons extension > geosparql-jena. > Is this extension of interest for Apache Jena as a plugin or in another > context? -- This message was sent by Atlassian Jira (v8.3.2#803003)
