[GitHub] [jena] afs opened a new pull request #542: JENA-1682: Update Apache fileupload version
afs opened a new pull request #542: JENA-1682: Update Apache fileupload version URL: https://github.com/apache/jena/pull/542 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] [Updated] (JENA-1682) Update version of Apache Commons fileupload
[ https://issues.apache.org/jira/browse/JENA-1682?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andy Seaborne updated JENA-1682: Summary: Update version of Apache Commons fileupload (was: Update version of Apache Commons Uploader) > Update version of Apache Commons fileupload > --- > > Key: JENA-1682 > URL: https://issues.apache.org/jira/browse/JENA-1682 > Project: Apache Jena > Issue Type: Task >Affects Versions: Jena 3.10.0 >Reporter: Andy Seaborne >Assignee: Andy Seaborne >Priority: Major > Fix For: Jena 3.11.0 > > > Version 1.4 is available. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (JENA-1682) Update version of Apache Commons Uploader
Andy Seaborne created JENA-1682: --- Summary: Update version of Apache Commons Uploader Key: JENA-1682 URL: https://issues.apache.org/jira/browse/JENA-1682 Project: Apache Jena Issue Type: Task Affects Versions: Jena 3.10.0 Reporter: Andy Seaborne Assignee: Andy Seaborne Fix For: Jena 3.11.0 Version 1.4 is available. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
Re: CMS diff: Fuseki : Main Server
Thank you! On 09/03/2019 23:47, Remi Chateauneu wrote: Clone URL (Committers only): https://cms.apache.org/redirect?new=anonymous;action=diff;uri=http://jena.apache.org/documentation%2Ffuseki2%2Ffuseki-main.md Remi Chateauneu Index: trunk/content/documentation/fuseki2/fuseki-main.md === --- trunk/content/documentation/fuseki2/fuseki-main.md (revision 1855070) +++ trunk/content/documentation/fuseki2/fuseki-main.md (working copy) @@ -1,6 +1,6 @@ Title: Fuseki : Main Server -Fuseki main is a packagign of Fuseki as trile store without a UI for administration. +Fuseki main is a packaging of Fuseki as triple store without a UI for administration. Fuseki can be run in the background by an application as an embedded server. The
Re: CMS diff: Jena RDF/XML How-To
Done - thank you for the link fixes. Andy On 04/03/2019 13:23, Jan wrote: Clone URL (Committers only): https://cms.apache.org/redirect?new=anonymous;action=diff;uri=http://jena.apache.org/documentation%2Fio%2Frdfxml_howto.mdtext Jan Index: trunk/content/documentation/io/rdfxml_howto.mdtext === --- trunk/content/documentation/io/rdfxml_howto.mdtext (revision 1854747) +++ trunk/content/documentation/io/rdfxml_howto.mdtext (working copy) @@ -336,7 +336,7 @@ `iri-rules` | Set the engine for checking and resolving. `"strict"` sets the IRI engine with rules for valid IRIs, XLink and RDF; it does not permit spaces in IRIs. `"iri"`sets the IRI engine to IRI ([RFC 3986](http://www.ietf.org/rfc/rfc3986.txt), [RFC 3987](http://www.ietf.org/rfc/rfc3987.txt)) `.` The default is `"lax"`(for backwards compatibility)`,` the rules for RDF URI references only, which does permit spaces although the use of spaces is not good practice. | String | `lax``strict``iri` `error-mode`| [`ARPOptions.setDefaultErrorMode()`](/documentation/javadoc/jena/org/apache/jena/rdf/arp/ARPOptions.html#setDefaultErrorMode()) [`ARPOptions.setLaxErrorMode()`](/documentation/javadoc/jena/org/apache/jena/rdf/arp/ARPOptions.html#setLaxErrorMode())[`ARPOptions.setStrictErrorMode()`](/documentation/javadoc/jena/org/apache/jena/rdf/arp/ARPOptions.html#setStrictErrorMode())[`ARPOptions.setStrictErrorMode(int)`](/documentation/javadoc/jena/org/apache/jena/rdf/arp/ARPOptions.html#setStrictErrorMode(int)) This allows a coarse-grained approach to control of error handling. Setting this property is equivalent to setting many of the fine-grained error handling properties. | `String` | `default``lax``strict``strict-ignore``strict-warning``strict-error``strict-fatal` `embedding` | [`ARPOptions.setEmbedding(boolean)`](/documentation/javadoc/jena/org/apache/jena/rdf/arp/ARPOptions.html#setEmbedding(boolean)) This sets ARP to look for RDF embedded within an enclosing XML document. | `String` or `Boolean` | `true``false` -`ERR_` `WARN_``IGN_` | See [`ARPErrorNumbers`](/documentation/javadoc/jena/org/apache/jena/rdf/arp/ARPErrorNumbers.html) for a complete list of the error conditions detected. Setting one of these properties is equivalent to the method [`ARPOptions.setErrorMode(int, int)`](/documentation/javadoc/jena/org/apache/jena/rdf/arp/ARPOptions.html#setErrorMode(int,%20int)). Thus fine-grained control over the behaviour in response to specific error conditions is possible.| `String` or `Integer` | [`EM_IGNORE`](/documentation/javadoc/jena/org/apache/jena/rdf/arp/ARPErrorNumbers.html#EM_IGNORE)[`EM_WARNING`](/documentation/javadoc/jena/org/apache/jena/rdf/arp/ARPErrorNumbers.html#EM_WARNING)[`EM_ERROR`](/documentation/javadoc/jena/org/apache/jena/rdf/arp/ARPErrorNumbers.html#EM_ERROR)[`EM_FATAL`](/documentation/javadoc/jena/org/apache/jena/rdf/arp/ARPErrorNumbers.html#EM_FATAL) +`ERR_` `WARN_``IGN_` | See [`ARPErrorNumbers`](/documentation/javadoc/jena/org/apache/jena/rdfxml/xmlinput/ARPErrorNumbers.html) for a complete list of the error conditions detected. Setting one of these properties is equivalent to the method [`ARPOptions.setErrorMode(int, int)`](/documentation/javadoc/jena/org/apache/jena/rdf/arp/ARPOptions.html#setErrorMode(int,%20int)). Thus fine-grained control over the behaviour in response to specific error conditions is possible.| `String` or `Integer` | [`EM_IGNORE`](/documentation/javadoc/jena/org/apache/jena/rdf/arp/ARPErrorNumbers.html#EM_IGNORE)[`EM_WARNING`](/documentation/javadoc/jena/org/apache/jena/rdf/arp/ARPErrorNumbers.html#EM_WARNING)[`EM_ERROR`](/documentation/javadoc/jena/org/apache/jena/rdf/arp/ARPErrorNumbers.html#EM_ERROR)[`EM_FATAL`](/documentation/javadoc/jena/org/apache/jena/rdf/arp/ARPErrorNumbers.html#EM_FATAL) As an example, if you are working in an environment with legacy RDF data that uses unqualified RDF attributes such as "about" instead
Re: CMS diff: Writing RDF in Apache Jena
Done - thanks for that correction. On 13/02/2019 16:28, David LJ wrote: Clone URL (Committers only): https://cms.apache.org/redirect?new=anonymous;action=diff;uri=http://jena.apache.org/documentation%2Fio%2Frdf-output.mdtext David LJ Index: trunk/content/documentation/io/rdf-output.mdtext === --- trunk/content/documentation/io/rdf-output.mdtext(revision 1853471) +++ trunk/content/documentation/io/rdf-output.mdtext(working copy) @@ -313,7 +313,7 @@ cases. What can be done, and how it can be, is explained in the -[sample code](https://github.com/apache/jena/tree/master/jena-arq/src-examples/arq/examples/riot/ExJsonLD.java). +[sample code](https://github.com/apache/jena/blob/master/jena-arq/src-examples/arq/examples/riot/Ex_WriteJsonLD.java). ### RDF Binary
Re: CMS diff: Jena Full Text Search
Done. On 25/02/2019 15:22, Chris Tomlinson wrote: Clone URL (Committers only): https://cms.apache.org/redirect?new=anonymous;action=diff;uri=http://jena.apache.org/documentation%2Fquery%2Ftext-query.mdtext Chris Tomlinson Index: trunk/content/documentation/query/text-query.mdtext === --- trunk/content/documentation/query/text-query.mdtext (revision 1854295) +++ trunk/content/documentation/query/text-query.mdtext (working copy) @@ -4,7 +4,7 @@ [Lucene](https://lucene.apache.org) or [ElasticSearch](https://www.elastic.co) (built on Lucene). It gives applications the ability to perform indexed full text -searches within SPARQL queries. Here is a compatibility table: +searches within SPARQL queries. Here is a version compatibility table: | Jena | Lucene | Solr | ElasticSearch | ||---|||
[jira] [Commented] (JENA-1679) Effective boolean value for "NaN"^^xsd:float/xsd:double should be false
[
https://issues.apache.org/jira/browse/JENA-1679?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16791481#comment-16791481
]
ASF subversion and git services commented on JENA-1679:
---
Commit 182fd838f84d489a0d9f2178627e585b2ba3e7bb in jena's branch
refs/heads/master from Andy Seaborne
[ https://gitbox.apache.org/repos/asf?p=jena.git;h=182fd83 ]
JENA-1679: EBV values for Nan (double and float)
> Effective boolean value for "NaN"^^xsd:float/xsd:double should be false
> ---
>
> Key: JENA-1679
> URL: https://issues.apache.org/jira/browse/JENA-1679
> Project: Apache Jena
> Issue Type: Bug
>Affects Versions: Jena 3.10.0
> Environment: Tested on Jena 3.9
>Reporter: Richard Cyganiak
>Assignee: Andy Seaborne
>Priority: Major
> Fix For: Jena 3.11.0
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> SPARQL 1.1 defines the [effective boolean
> value|https://www.w3.org/TR/sparql11-query/#ebv
> ] (EBV) of the special numeric value NaN as follows:
> {quote}
> If the argument is a numeric type or a typed literal with a datatype derived
> from a numeric type, and it has a valid lexical form, the EBV is false if the
> operand value is NaN or is numerically equal to zero; otherwise the EBV is
> true.
> {quote}
> Jena however treats it as {{true}}. The following queries both return
> {{true}} but should return {{false}} (using {{!(!expr))}} to get the EBV):
> {noformat}
> SELECT (!(!"NaN"^^) AS ?x) WHERE {}
> SELECT (!(!"NaN"^^) AS ?x) WHERE {}
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (JENA-1679) Effective boolean value for "NaN"^^xsd:float/xsd:double should be false
[
https://issues.apache.org/jira/browse/JENA-1679?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andy Seaborne updated JENA-1679:
Affects Version/s: Jena 3.10.0
Fix Version/s: Jena 3.11.0
> Effective boolean value for "NaN"^^xsd:float/xsd:double should be false
> ---
>
> Key: JENA-1679
> URL: https://issues.apache.org/jira/browse/JENA-1679
> Project: Apache Jena
> Issue Type: Bug
>Affects Versions: Jena 3.10.0
> Environment: Tested on Jena 3.9
>Reporter: Richard Cyganiak
>Assignee: Andy Seaborne
>Priority: Major
> Fix For: Jena 3.11.0
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> SPARQL 1.1 defines the [effective boolean
> value|https://www.w3.org/TR/sparql11-query/#ebv
> ] (EBV) of the special numeric value NaN as follows:
> {quote}
> If the argument is a numeric type or a typed literal with a datatype derived
> from a numeric type, and it has a valid lexical form, the EBV is false if the
> operand value is NaN or is numerically equal to zero; otherwise the EBV is
> true.
> {quote}
> Jena however treats it as {{true}}. The following queries both return
> {{true}} but should return {{false}} (using {{!(!expr))}} to get the EBV):
> {noformat}
> SELECT (!(!"NaN"^^) AS ?x) WHERE {}
> SELECT (!(!"NaN"^^) AS ?x) WHERE {}
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Resolved] (JENA-1679) Effective boolean value for "NaN"^^xsd:float/xsd:double should be false
[
https://issues.apache.org/jira/browse/JENA-1679?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andy Seaborne resolved JENA-1679.
-
Resolution: Fixed
> Effective boolean value for "NaN"^^xsd:float/xsd:double should be false
> ---
>
> Key: JENA-1679
> URL: https://issues.apache.org/jira/browse/JENA-1679
> Project: Apache Jena
> Issue Type: Bug
> Components: ARQ
>Affects Versions: Jena 3.10.0
> Environment: Tested on Jena 3.9
>Reporter: Richard Cyganiak
>Assignee: Andy Seaborne
>Priority: Major
> Fix For: Jena 3.11.0
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> SPARQL 1.1 defines the [effective boolean
> value|https://www.w3.org/TR/sparql11-query/#ebv
> ] (EBV) of the special numeric value NaN as follows:
> {quote}
> If the argument is a numeric type or a typed literal with a datatype derived
> from a numeric type, and it has a valid lexical form, the EBV is false if the
> operand value is NaN or is numerically equal to zero; otherwise the EBV is
> true.
> {quote}
> Jena however treats it as {{true}}. The following queries both return
> {{true}} but should return {{false}} (using {{!(!expr))}} to get the EBV):
> {noformat}
> SELECT (!(!"NaN"^^) AS ?x) WHERE {}
> SELECT (!(!"NaN"^^) AS ?x) WHERE {}
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Resolved] (JENA-1680) Clean code in jena-dboe-* modules.
[ https://issues.apache.org/jira/browse/JENA-1680?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andy Seaborne resolved JENA-1680. - Resolution: Fixed > Clean code in jena-dboe-* modules. > -- > > Key: JENA-1680 > URL: https://issues.apache.org/jira/browse/JENA-1680 > Project: Apache Jena > Issue Type: Task >Affects Versions: Jena 3.10.0 >Reporter: Andy Seaborne >Assignee: Andy Seaborne >Priority: Minor > Fix For: Jena 3.11.0 > > Time Spent: 20m > Remaining Estimate: 0h > > The git history is useful in finding when bugs appeared and the lineage > of a feature. That's the main reason a mass reformatting of code for > white space or style has a significant impact - it obscures the history > and some history is very long. > Packages jena-db/jena-dboe-* packages, and maybe jena-db/jena-tdb2, are > sufficiently new and their history short that it would not be too > disruptive. > The proposed cleaning is: > * trailing whitespace. > * replace "space semi-colon" with "semi-colon". > * convert to staggered opening braces > * turn double or more blank lines to single. > See also: [email on > dev@|https://lists.apache.org/thread.html/7aff88e1dc22bfb39467fc862e63ca1b88839dc8c69e9dec6ad078bd@%3Cdev.jena.apache.org%3E]. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (JENA-1679) Effective boolean value for "NaN"^^xsd:float/xsd:double should be false
[
https://issues.apache.org/jira/browse/JENA-1679?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andy Seaborne updated JENA-1679:
Component/s: TDB2
> Effective boolean value for "NaN"^^xsd:float/xsd:double should be false
> ---
>
> Key: JENA-1679
> URL: https://issues.apache.org/jira/browse/JENA-1679
> Project: Apache Jena
> Issue Type: Bug
> Components: TDB2
>Affects Versions: Jena 3.10.0
> Environment: Tested on Jena 3.9
>Reporter: Richard Cyganiak
>Assignee: Andy Seaborne
>Priority: Major
> Fix For: Jena 3.11.0
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> SPARQL 1.1 defines the [effective boolean
> value|https://www.w3.org/TR/sparql11-query/#ebv
> ] (EBV) of the special numeric value NaN as follows:
> {quote}
> If the argument is a numeric type or a typed literal with a datatype derived
> from a numeric type, and it has a valid lexical form, the EBV is false if the
> operand value is NaN or is numerically equal to zero; otherwise the EBV is
> true.
> {quote}
> Jena however treats it as {{true}}. The following queries both return
> {{true}} but should return {{false}} (using {{!(!expr))}} to get the EBV):
> {noformat}
> SELECT (!(!"NaN"^^) AS ?x) WHERE {}
> SELECT (!(!"NaN"^^) AS ?x) WHERE {}
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (JENA-1679) Effective boolean value for "NaN"^^xsd:float/xsd:double should be false
[
https://issues.apache.org/jira/browse/JENA-1679?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andy Seaborne updated JENA-1679:
Component/s: (was: TDB2)
ARQ
> Effective boolean value for "NaN"^^xsd:float/xsd:double should be false
> ---
>
> Key: JENA-1679
> URL: https://issues.apache.org/jira/browse/JENA-1679
> Project: Apache Jena
> Issue Type: Bug
> Components: ARQ
>Affects Versions: Jena 3.10.0
> Environment: Tested on Jena 3.9
>Reporter: Richard Cyganiak
>Assignee: Andy Seaborne
>Priority: Major
> Fix For: Jena 3.11.0
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> SPARQL 1.1 defines the [effective boolean
> value|https://www.w3.org/TR/sparql11-query/#ebv
> ] (EBV) of the special numeric value NaN as follows:
> {quote}
> If the argument is a numeric type or a typed literal with a datatype derived
> from a numeric type, and it has a valid lexical form, the EBV is false if the
> operand value is NaN or is numerically equal to zero; otherwise the EBV is
> true.
> {quote}
> Jena however treats it as {{true}}. The following queries both return
> {{true}} but should return {{false}} (using {{!(!expr))}} to get the EBV):
> {noformat}
> SELECT (!(!"NaN"^^) AS ?x) WHERE {}
> SELECT (!(!"NaN"^^) AS ?x) WHERE {}
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (JENA-1680) Clean code in jena-dboe-* modules.
[ https://issues.apache.org/jira/browse/JENA-1680?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16791480#comment-16791480 ] ASF subversion and git services commented on JENA-1680: --- Commit 01eec4c45600acef8f2bdac00f984578a9a24452 in jena's branch refs/heads/master from Andy Seaborne [ https://gitbox.apache.org/repos/asf?p=jena.git;h=01eec4c ] Merge pull request #540 from afs/code-clean JENA-1680: Code formatting jena-dboe-* > Clean code in jena-dboe-* modules. > -- > > Key: JENA-1680 > URL: https://issues.apache.org/jira/browse/JENA-1680 > Project: Apache Jena > Issue Type: Task >Affects Versions: Jena 3.10.0 >Reporter: Andy Seaborne >Assignee: Andy Seaborne >Priority: Minor > Fix For: Jena 3.11.0 > > Time Spent: 20m > Remaining Estimate: 0h > > The git history is useful in finding when bugs appeared and the lineage > of a feature. That's the main reason a mass reformatting of code for > white space or style has a significant impact - it obscures the history > and some history is very long. > Packages jena-db/jena-dboe-* packages, and maybe jena-db/jena-tdb2, are > sufficiently new and their history short that it would not be too > disruptive. > The proposed cleaning is: > * trailing whitespace. > * replace "space semi-colon" with "semi-colon". > * convert to staggered opening braces > * turn double or more blank lines to single. > See also: [email on > dev@|https://lists.apache.org/thread.html/7aff88e1dc22bfb39467fc862e63ca1b88839dc8c69e9dec6ad078bd@%3Cdev.jena.apache.org%3E]. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (JENA-1679) Effective boolean value for "NaN"^^xsd:float/xsd:double should be false
[
https://issues.apache.org/jira/browse/JENA-1679?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16791483#comment-16791483
]
ASF subversion and git services commented on JENA-1679:
---
Commit 66d14eda44dd0f37a9df31ed27c55c26600ff5f8 in jena's branch
refs/heads/master from Andy Seaborne
[ https://gitbox.apache.org/repos/asf?p=jena.git;h=66d14ed ]
Merge pull request #541 from afs/ebv-NaN
JENA-1679: EBV values for NaN (double and float)
> Effective boolean value for "NaN"^^xsd:float/xsd:double should be false
> ---
>
> Key: JENA-1679
> URL: https://issues.apache.org/jira/browse/JENA-1679
> Project: Apache Jena
> Issue Type: Bug
>Affects Versions: Jena 3.10.0
> Environment: Tested on Jena 3.9
>Reporter: Richard Cyganiak
>Assignee: Andy Seaborne
>Priority: Major
> Fix For: Jena 3.11.0
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> SPARQL 1.1 defines the [effective boolean
> value|https://www.w3.org/TR/sparql11-query/#ebv
> ] (EBV) of the special numeric value NaN as follows:
> {quote}
> If the argument is a numeric type or a typed literal with a datatype derived
> from a numeric type, and it has a valid lexical form, the EBV is false if the
> operand value is NaN or is numerically equal to zero; otherwise the EBV is
> true.
> {quote}
> Jena however treats it as {{true}}. The following queries both return
> {{true}} but should return {{false}} (using {{!(!expr))}} to get the EBV):
> {noformat}
> SELECT (!(!"NaN"^^) AS ?x) WHERE {}
> SELECT (!(!"NaN"^^) AS ?x) WHERE {}
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (JENA-1680) Clean code in jena-dboe-* modules.
[ https://issues.apache.org/jira/browse/JENA-1680?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16791478#comment-16791478 ] ASF subversion and git services commented on JENA-1680: --- Commit 83c52d4722c9a946566bfe01d10f0c79ba8333a8 in jena's branch refs/heads/master from Andy Seaborne [ https://gitbox.apache.org/repos/asf?p=jena.git;h=83c52d4 ] JENA-1680: Code formatting jena-dboe-* > Clean code in jena-dboe-* modules. > -- > > Key: JENA-1680 > URL: https://issues.apache.org/jira/browse/JENA-1680 > Project: Apache Jena > Issue Type: Task >Affects Versions: Jena 3.10.0 >Reporter: Andy Seaborne >Assignee: Andy Seaborne >Priority: Minor > Fix For: Jena 3.11.0 > > Time Spent: 10m > Remaining Estimate: 0h > > The git history is useful in finding when bugs appeared and the lineage > of a feature. That's the main reason a mass reformatting of code for > white space or style has a significant impact - it obscures the history > and some history is very long. > Packages jena-db/jena-dboe-* packages, and maybe jena-db/jena-tdb2, are > sufficiently new and their history short that it would not be too > disruptive. > The proposed cleaning is: > * trailing whitespace. > * replace "space semi-colon" with "semi-colon". > * convert to staggered opening braces > * turn double or more blank lines to single. > See also: [email on > dev@|https://lists.apache.org/thread.html/7aff88e1dc22bfb39467fc862e63ca1b88839dc8c69e9dec6ad078bd@%3Cdev.jena.apache.org%3E]. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[GitHub] [jena] afs merged pull request #541: JENA-1679: EBV values for NaN (double and float)
afs merged pull request #541: JENA-1679: EBV values for NaN (double and float) URL: https://github.com/apache/jena/pull/541 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
[GitHub] [jena] afs merged pull request #540: JENA-1680: Code formatting jena-dboe-*
afs merged pull request #540: JENA-1680: Code formatting jena-dboe-* URL: https://github.com/apache/jena/pull/540 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
