Re: Contribution proposal for Jena: support of a datatype for quantity values
On 15/06/18 14:49, Maxime Lefrançois wrote: Dear all, Regarding our contribution proposal to enable extensions to override SPARQL operators in Jena We finally got the agreement from our institution to contribute to the Apache foundation. Question 1: what is the procedure to upload the form? Normally, the act of providing a contribution like a patch or small feature is enough. The individual is making the contribution and it is their responsibility to know this is open source. This also covers code in email to Apache mailing lists (but not elsewhere and not stackoverflow). It sounds like your institution would prefer an explicit declaration. These are the Individual Contributor License Agreement (ICLA) and Corporate Contributor License Agreement (CCLA). Ideally, you should provide an ICLA as well as the institution submitting an CCLA as you are also an individual here - it will cover working on the contribution after submission. The CCLA has a section to name the contribution and an optional section for naming people - it isn't an open ended commitment. On the ICLA, you don't need to request an Apache id. It will cover all Apache projects. The forms are available at: https://www.apache.org/licenses/ For completeness - there is the Apache Software Grant for an existing body of work that may have existed a open source. (e.g. This is used when a project joins Apache). Andy (if this is a duplicate, it is because I got a network error on sending)
Re: Contribution proposal for Jena: support of a datatype for quantity values
On 15/06/18 14:49, Maxime Lefrançois wrote: Dear all, Regarding our contribution proposal to enable extensions to override SPARQL operators in Jena We finally got the agreement from our institution to contribute to the Apache foundation. Question 1: what is the procedure to upload the form? Normally, the act of providing a contribution like a patch or small feature is enough. The individual is making the contribution and it is their responsibility to know this is open source. This also covers code in email to Apache mailing lists (but not elsewhere and not stackoverflow). It sounds like your institution would prefer an explicit declaration. These are the Individual Contributor License Agreement (ICLA) and Corporate Contributor License Agreement (CCLA). Ideally, you should provide an ICLA as well as the institution submitting an CCLA as you are also an individual here - it will cover working on the contribution after submission. The CCLA has a section to name the contribution and an optional section for naming people - it isn't an open ended commitment. On the ICLA, you don't need to request an Apache id. It will cover all Apache projects. The forms are available at: https://www.apache.org/licenses/ For completeness - there is the Apache Software Grant for an existing body of work that may have existed a open source. (e.g. This is used when a project joins Apache). Andy
[jira] [Resolved] (JENA-1563) ResultSetReaderJSON does not accept "lang"+"datatype" on the same literal.
[
https://issues.apache.org/jira/browse/JENA-1563?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andy Seaborne resolved JENA-1563.
-
Resolution: Fixed
Assignee: Andy Seaborne
Fix Version/s: Jena 3.8.0
> ResultSetReaderJSON does not accept "lang"+"datatype" on the same literal.
> --
>
> Key: JENA-1563
> URL: https://issues.apache.org/jira/browse/JENA-1563
> Project: Apache Jena
> Issue Type: Bug
>Affects Versions: Jena 3.7.0
>Reporter: Andy Seaborne
>Assignee: Andy Seaborne
>Priority: Major
> Fix For: Jena 3.8.0
>
>
> Reported by Philip Coates by [email date 2018-06-08 on
> dev@|https://lists.apache.org/thread.html/de8a84a612b978a1dcadd54d1d84eea0a944fc36fd52019f5eb0be3b@%3Cdev.jena.apache.org%3E].
> Example:
> {noformat}
> {
> "xml:lang" : "en" ,
> "datatype" : "http://www.w3.org/1999/02/22-rdf-syntax-ns#langString; ,
> "type" : "literal" ,
> "value" : "phototaxis"
> }
> {noformat}
> The {{"datatype"}} is not needed because {{"xml:lang"}} implies it. The RDF
> specs recommend that daatypes are not added when there is a language tag.
> Jena can be lenient and accept this when {{"datatype"}} is rdf:langString
> (anything else is incorrect).
> For reference: {{"datatype"}} xsd:string isn't necessary either but is
> accepted (it happens from RDF 1.0 systems).
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (JENA-1563) ResultSetReaderJSON does not accept "lang"+"datatype" on the same literal.
[
https://issues.apache.org/jira/browse/JENA-1563?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16514749#comment-16514749
]
ASF GitHub Bot commented on JENA-1563:
--
Github user asfgit closed the pull request at:
https://github.com/apache/jena/pull/435
> ResultSetReaderJSON does not accept "lang"+"datatype" on the same literal.
> --
>
> Key: JENA-1563
> URL: https://issues.apache.org/jira/browse/JENA-1563
> Project: Apache Jena
> Issue Type: Bug
>Affects Versions: Jena 3.7.0
>Reporter: Andy Seaborne
>Priority: Major
>
> Reported by Philip Coates by [email date 2018-06-08 on
> dev@|https://lists.apache.org/thread.html/de8a84a612b978a1dcadd54d1d84eea0a944fc36fd52019f5eb0be3b@%3Cdev.jena.apache.org%3E].
> Example:
> {noformat}
> {
> "xml:lang" : "en" ,
> "datatype" : "http://www.w3.org/1999/02/22-rdf-syntax-ns#langString; ,
> "type" : "literal" ,
> "value" : "phototaxis"
> }
> {noformat}
> The {{"datatype"}} is not needed because {{"xml:lang"}} implies it. The RDF
> specs recommend that daatypes are not added when there is a language tag.
> Jena can be lenient and accept this when {{"datatype"}} is rdf:langString
> (anything else is incorrect).
> For reference: {{"datatype"}} xsd:string isn't necessary either but is
> accepted (it happens from RDF 1.0 systems).
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[GitHub] jena pull request #435: JENA-1563: Accept lang and dt=rdf:langString
Github user asfgit closed the pull request at: https://github.com/apache/jena/pull/435 ---
