[jira] [Commented] (JENA-1082) Add to org.apache.jena.rdf.model.ModelCon interface a listLiteralStatements method that accepts ints.

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/JENA-1082?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15074143#comment-15074143
 ] 

ASF GitHub Bot commented on JENA-1082:
--

GitHub user ramiromagalhaes opened a pull request:

https://github.com/apache/jena/pull/116

Fixes JENA-1082.

Proposal to fix JENA-1082 issue that further overloads 
ModelCon#listLiteralStatements() method. The only required implementation of 
such method follows the same idea behind of other listLiteralStatements() 
methods.

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/ramiromagalhaes/jena JENA-1082

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/jena/pull/116.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #116


commit 2d1e7a0235f91990f31c00c9242a532783f74866
Author: Ramiro Pereira de Magalhães 
Date:   2015-12-29T18:00:07Z

Fixes JENA-1082.




> Add to org.apache.jena.rdf.model.ModelCon interface a listLiteralStatements 
> method that accepts ints.
> -
>
> Key: JENA-1082
> URL: https://issues.apache.org/jira/browse/JENA-1082
> Project: Apache Jena
>  Issue Type: Improvement
>  Components: Core
>Affects Versions: Jena 3.0.0
>Reporter: Ramiro Pereira de Magalhães
>Priority: Minor
>
> Add to org.apache.jena.rdf.model.ModelCon interface a {{StmtIterator 
> listLiteralStatements(Resource subject, Property predicate, int object );}} 
> method.
> Implement such method in classes that implement such interface. This method 
> should be able to list literal integer statements, like the other 
> listLiteralStatement methods do to other types.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (JENA-1107) Improve jena-base lib.Tuple

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/JENA-1107?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15074130#comment-15074130
 ] 

ASF GitHub Bot commented on JENA-1107:
--

Github user afs commented on a diff in the pull request:

https://github.com/apache/jena/pull/115#discussion_r48558378
  
--- Diff: 
jena-base/src/main/java/org/apache/jena/atlas/lib/tuple/Tuple.java ---
@@ -0,0 +1,73 @@
+/*
+ * Licensed to the Apache Software Foundation (ASF) under one
+ * or more contributor license agreements.  See the NOTICE file
+ * distributed with this work for additional information
+ * regarding copyright ownership.  The ASF licenses this file
+ * to you under the Apache License, Version 2.0 (the
+ * "License"); you may not use this file except in compliance
+ * with the License.  You may obtain a copy of the License at
+ *
+ * http://www.apache.org/licenses/LICENSE-2.0
+ *
+ * Unless required by applicable law or agreed to in writing, software
+ * distributed under the License is distributed on an "AS IS" BASIS,
+ * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ * See the License for the specific language governing permissions and
+ * limitations under the License.
+ */
+
+package org.apache.jena.atlas.lib.tuple;
+
+import java.util.List ;
+import java.util.function.Consumer ;
+import java.util.stream.Stream ;
+
+import org.apache.jena.atlas.lib.ArrayUtils ;
+
+/** A Tuple is the same class of item */
+public interface Tuple extends Iterable {
+/** Get the i'th element, for i in the range 0 to len()-1 
+ * @throws IndexOutOfBoundsException for i out of range 
+ */
+public X get(int i) ;
+
+/** length : elements are 0 to len()-1 */ 
+public int len() ;
+
+/** Convert to a List */
+public default List asList() {
+return new TupleList<>(this) ;
+}
+
+/** stream */
+public default Stream stream() { 
--- End diff --

Good point.


> Improve jena-base lib.Tuple
> ---
>
> Key: JENA-1107
> URL: https://issues.apache.org/jira/browse/JENA-1107
> Project: Apache Jena
>  Issue Type: Improvement
>Reporter: Andy Seaborne
>Assignee: Andy Seaborne
>Priority: Minor
>
> Tuples, which are immutable, value-equality fixed length sequences of 
> instances of the same type, accessed by index.
> They are like {{T[]}} but immutable, with .equals based on contents, and 
> could be improved to work independently of their original use in TDB.
> Proposal:
> #  Make Tuple an interface (simpler than current), with special 
> implementations for low number of elements.
> # {{ColumnMap}} ==> {{TupleMap}} and sort out the naming as much as possible 
> to use as a way to manage index mapping, not just rewriting Tuples.
> An intermediate step is to move {{ColumnMap}} into TDB.
> This is not a proposal to add it to {{Triple}} or {{Quad}}.
> {{Triple}} is not the same as a 3-length {{Tuple}}.  Triple elements 
> are accessed by name ({{getSubject}} etc), not index.  SPO is just one 
> possible order in which to think about triples but it has no special status. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[GitHub] jena pull request: JENA-1107 : Improve Tuple.

[afs]

Github user afs commented on a diff in the pull request:

https://github.com/apache/jena/pull/115#discussion_r48558378
  
--- Diff: 
jena-base/src/main/java/org/apache/jena/atlas/lib/tuple/Tuple.java ---
@@ -0,0 +1,73 @@
+/*
+ * Licensed to the Apache Software Foundation (ASF) under one
+ * or more contributor license agreements.  See the NOTICE file
+ * distributed with this work for additional information
+ * regarding copyright ownership.  The ASF licenses this file
+ * to you under the Apache License, Version 2.0 (the
+ * "License"); you may not use this file except in compliance
+ * with the License.  You may obtain a copy of the License at
+ *
+ * http://www.apache.org/licenses/LICENSE-2.0
+ *
+ * Unless required by applicable law or agreed to in writing, software
+ * distributed under the License is distributed on an "AS IS" BASIS,
+ * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ * See the License for the specific language governing permissions and
+ * limitations under the License.
+ */
+
+package org.apache.jena.atlas.lib.tuple;
+
+import java.util.List ;
+import java.util.function.Consumer ;
+import java.util.stream.Stream ;
+
+import org.apache.jena.atlas.lib.ArrayUtils ;
+
+/** A Tuple is the same class of item */
+public interface Tuple extends Iterable {
+/** Get the i'th element, for i in the range 0 to len()-1 
+ * @throws IndexOutOfBoundsException for i out of range 
+ */
+public X get(int i) ;
+
+/** length : elements are 0 to len()-1 */ 
+public int len() ;
+
+/** Convert to a List */
+public default List asList() {
+return new TupleList<>(this) ;
+}
+
+/** stream */
+public default Stream stream() { 
--- End diff --

Good point.


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] jena pull request: JENA-1107 : Improve Tuple.

[afs]

Github user afs commented on a diff in the pull request:

https://github.com/apache/jena/pull/115#discussion_r48558360
  
--- Diff: 
jena-base/src/main/java/org/apache/jena/atlas/lib/tuple/Tuple.java ---
@@ -0,0 +1,73 @@
+/*
+ * Licensed to the Apache Software Foundation (ASF) under one
+ * or more contributor license agreements.  See the NOTICE file
+ * distributed with this work for additional information
+ * regarding copyright ownership.  The ASF licenses this file
+ * to you under the Apache License, Version 2.0 (the
+ * "License"); you may not use this file except in compliance
+ * with the License.  You may obtain a copy of the License at
+ *
+ * http://www.apache.org/licenses/LICENSE-2.0
+ *
+ * Unless required by applicable law or agreed to in writing, software
+ * distributed under the License is distributed on an "AS IS" BASIS,
+ * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ * See the License for the specific language governing permissions and
+ * limitations under the License.
+ */
+
+package org.apache.jena.atlas.lib.tuple;
+
+import java.util.List ;
+import java.util.function.Consumer ;
+import java.util.stream.Stream ;
+
+import org.apache.jena.atlas.lib.ArrayUtils ;
+
+/** A Tuple is the same class of item */
+public interface Tuple extends Iterable {
+/** Get the i'th element, for i in the range 0 to len()-1 
+ * @throws IndexOutOfBoundsException for i out of range 
+ */
+public X get(int i) ;
+
+/** length : elements are 0 to len()-1 */ 
+public int len() ;
+
+/** Convert to a List */
+public default List asList() {
+return new TupleList<>(this) ;
+}
+
+/** stream */
+public default Stream stream() { 
+return asList().stream() ;
+}
+
+/** forEach */
+@Override
+public default void forEach(Consumer action) { 
+asList().forEach(action) ;
+}
+
+/** Copy the Tuple into the array */ 
+public default void copyInto(X[] array) {
+copyInto(array, 0, len());
+}
+
+/** Copy the Tuple into the array */ 
+public default void copyInto(X[] array, int start) {
+copyInto(array, start, len());
+}
+
+/** Copy the Tuple into the array */ 
+public void copyInto(X[] array, int start, int length) ;
--- End diff --

I can move that (and iterator()) into the interface.  

(Now TupleBase is needed (because you can't default methods from Object in 
an interface) some of all can go there if it keeps the source clean.)


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] jena pull request: Fixes JENA-1082.

[ramiromagalhaes]

GitHub user ramiromagalhaes opened a pull request:

https://github.com/apache/jena/pull/116

Fixes JENA-1082.

Proposal to fix JENA-1082 issue that further overloads 
ModelCon#listLiteralStatements() method. The only required implementation of 
such method follows the same idea behind of other listLiteralStatements() 
methods.

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/ramiromagalhaes/jena JENA-1082

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/jena/pull/116.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #116


commit 2d1e7a0235f91990f31c00c9242a532783f74866
Author: Ramiro Pereira de Magalhães 
Date:   2015-12-29T18:00:07Z

Fixes JENA-1082.




---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] jena pull request: Fixes JENA-1082.

[asfgit]

Github user asfgit closed the pull request at:

https://github.com/apache/jena/pull/116


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[jira] [Commented] (JENA-1107) Improve jena-base lib.Tuple

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/JENA-1107?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15074317#comment-15074317
 ] 

ASF GitHub Bot commented on JENA-1107:
--

Github user asfgit closed the pull request at:

https://github.com/apache/jena/pull/115


> Improve jena-base lib.Tuple
> ---
>
> Key: JENA-1107
> URL: https://issues.apache.org/jira/browse/JENA-1107
> Project: Apache Jena
>  Issue Type: Improvement
>Reporter: Andy Seaborne
>Assignee: Andy Seaborne
>Priority: Minor
>
> Tuples, which are immutable, value-equality fixed length sequences of 
> instances of the same type, accessed by index.
> They are like {{T[]}} but immutable, with .equals based on contents, and 
> could be improved to work independently of their original use in TDB.
> Proposal:
> #  Make Tuple an interface (simpler than current), with special 
> implementations for low number of elements.
> # {{ColumnMap}} ==> {{TupleMap}} and sort out the naming as much as possible 
> to use as a way to manage index mapping, not just rewriting Tuples.
> An intermediate step is to move {{ColumnMap}} into TDB.
> This is not a proposal to add it to {{Triple}} or {{Quad}}.
> {{Triple}} is not the same as a 3-length {{Tuple}}.  Triple elements 
> are accessed by name ({{getSubject}} etc), not index.  SPO is just one 
> possible order in which to think about triples but it has no special status. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (JENA-1082) Add to org.apache.jena.rdf.model.ModelCon interface a listLiteralStatements method that accepts ints.

[ASF subversion and git services (JIRA)]

[ 
https://issues.apache.org/jira/browse/JENA-1082?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15074314#comment-15074314
 ] 

ASF subversion and git services commented on JENA-1082:
---

Commit bd9fdd2e40997b67e1f3f8ff755deb05400b1ca7 in jena's branch 
refs/heads/master from [~ramiromagalhaes]
[ https://git-wip-us.apache.org/repos/asf?p=jena.git;h=bd9fdd2 ]

Fixes JENA-1082.


> Add to org.apache.jena.rdf.model.ModelCon interface a listLiteralStatements 
> method that accepts ints.
> -
>
> Key: JENA-1082
> URL: https://issues.apache.org/jira/browse/JENA-1082
> Project: Apache Jena
>  Issue Type: Improvement
>  Components: Core
>Affects Versions: Jena 3.0.0
>Reporter: Ramiro Pereira de Magalhães
>Assignee: Andy Seaborne
>Priority: Minor
> Fix For: Jena 3.1.0
>
>
> Add to org.apache.jena.rdf.model.ModelCon interface a {{StmtIterator 
> listLiteralStatements(Resource subject, Property predicate, int object );}} 
> method.
> Implement such method in classes that implement such interface. This method 
> should be able to list literal integer statements, like the other 
> listLiteralStatement methods do to other types.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (JENA-1082) Add to org.apache.jena.rdf.model.ModelCon interface a listLiteralStatements method that accepts ints.

[ASF subversion and git services (JIRA)]

[ 
https://issues.apache.org/jira/browse/JENA-1082?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15074315#comment-15074315
 ] 

ASF subversion and git services commented on JENA-1082:
---

Commit 068113ec9c16bea6bb4409e348c8b3de40148e93 in jena's branch 
refs/heads/master from [~andy.seaborne]
[ https://git-wip-us.apache.org/repos/asf?p=jena.git;h=068113e ]

Align with jena-core change (JENA-1082)


> Add to org.apache.jena.rdf.model.ModelCon interface a listLiteralStatements 
> method that accepts ints.
> -
>
> Key: JENA-1082
> URL: https://issues.apache.org/jira/browse/JENA-1082
> Project: Apache Jena
>  Issue Type: Improvement
>  Components: Core
>Affects Versions: Jena 3.0.0
>Reporter: Ramiro Pereira de Magalhães
>Assignee: Andy Seaborne
>Priority: Minor
> Fix For: Jena 3.1.0
>
>
> Add to org.apache.jena.rdf.model.ModelCon interface a {{StmtIterator 
> listLiteralStatements(Resource subject, Property predicate, int object );}} 
> method.
> Implement such method in classes that implement such interface. This method 
> should be able to list literal integer statements, like the other 
> listLiteralStatement methods do to other types.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[GitHub] jena pull request: JENA-1107 : Improve Tuple.

[asfgit]

Github user asfgit closed the pull request at:

https://github.com/apache/jena/pull/115


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[jira] [Commented] (JENA-1107) Improve jena-base lib.Tuple

[ASF subversion and git services (JIRA)]

[ 
https://issues.apache.org/jira/browse/JENA-1107?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15074316#comment-15074316
 ] 

ASF subversion and git services commented on JENA-1107:
---

Commit d3603482019d9bfd0295f96f5a767f4cebc3e71a in jena's branch 
refs/heads/master from [~andy.seaborne]
[ https://git-wip-us.apache.org/repos/asf?p=jena.git;h=d360348 ]

JENA-1107: Improve Tuple. Merge commit 'refs/pull/115/head'

This closes #115.


> Improve jena-base lib.Tuple
> ---
>
> Key: JENA-1107
> URL: https://issues.apache.org/jira/browse/JENA-1107
> Project: Apache Jena
>  Issue Type: Improvement
>Reporter: Andy Seaborne
>Assignee: Andy Seaborne
>Priority: Minor
>
> Tuples, which are immutable, value-equality fixed length sequences of 
> instances of the same type, accessed by index.
> They are like {{T[]}} but immutable, with .equals based on contents, and 
> could be improved to work independently of their original use in TDB.
> Proposal:
> #  Make Tuple an interface (simpler than current), with special 
> implementations for low number of elements.
> # {{ColumnMap}} ==> {{TupleMap}} and sort out the naming as much as possible 
> to use as a way to manage index mapping, not just rewriting Tuples.
> An intermediate step is to move {{ColumnMap}} into TDB.
> This is not a proposal to add it to {{Triple}} or {{Quad}}.
> {{Triple}} is not the same as a 3-length {{Tuple}}.  Triple elements 
> are accessed by name ({{getSubject}} etc), not index.  SPO is just one 
> possible order in which to think about triples but it has no special status. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (JENA-1107) Improve jena-base lib.Tuple

[ASF subversion and git services (JIRA)]

[ 
https://issues.apache.org/jira/browse/JENA-1107?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15074313#comment-15074313
 ] 

ASF subversion and git services commented on JENA-1107:
---

Commit c665f63004fee2d465f2cbcb48d2defd17e12858 in jena's branch 
refs/heads/master from [~andy.seaborne]
[ https://git-wip-us.apache.org/repos/asf?p=jena.git;h=c665f63 ]

JENA-1107: Changes due to reworking Tuple.

> Improve jena-base lib.Tuple
> ---
>
> Key: JENA-1107
> URL: https://issues.apache.org/jira/browse/JENA-1107
> Project: Apache Jena
>  Issue Type: Improvement
>Reporter: Andy Seaborne
>Assignee: Andy Seaborne
>Priority: Minor
>
> Tuples, which are immutable, value-equality fixed length sequences of 
> instances of the same type, accessed by index.
> They are like {{T[]}} but immutable, with .equals based on contents, and 
> could be improved to work independently of their original use in TDB.
> Proposal:
> #  Make Tuple an interface (simpler than current), with special 
> implementations for low number of elements.
> # {{ColumnMap}} ==> {{TupleMap}} and sort out the naming as much as possible 
> to use as a way to manage index mapping, not just rewriting Tuples.
> An intermediate step is to move {{ColumnMap}} into TDB.
> This is not a proposal to add it to {{Triple}} or {{Quad}}.
> {{Triple}} is not the same as a 3-length {{Tuple}}.  Triple elements 
> are accessed by name ({{getSubject}} etc), not index.  SPO is just one 
> possible order in which to think about triples but it has no special status. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (JENA-1082) Add to org.apache.jena.rdf.model.ModelCon interface a listLiteralStatements method that accepts ints.

[ASF subversion and git services (JIRA)]

[ 
https://issues.apache.org/jira/browse/JENA-1082?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15074284#comment-15074284
 ] 

ASF subversion and git services commented on JENA-1082:
---

Commit f2b5681c6e0f7aa80dfa8299b429e8b0b22b422a in jena's branch 
refs/heads/master from [~andy.seaborne]
[ https://git-wip-us.apache.org/repos/asf?p=jena.git;h=f2b5681 ]

JENA-1082: Merge commit 'refs/pull/116/head' of github.com:apache/jena

This closes #116.


> Add to org.apache.jena.rdf.model.ModelCon interface a listLiteralStatements 
> method that accepts ints.
> -
>
> Key: JENA-1082
> URL: https://issues.apache.org/jira/browse/JENA-1082
> Project: Apache Jena
>  Issue Type: Improvement
>  Components: Core
>Affects Versions: Jena 3.0.0
>Reporter: Ramiro Pereira de Magalhães
>Priority: Minor
>
> Add to org.apache.jena.rdf.model.ModelCon interface a {{StmtIterator 
> listLiteralStatements(Resource subject, Property predicate, int object );}} 
> method.
> Implement such method in classes that implement such interface. This method 
> should be able to list literal integer statements, like the other 
> listLiteralStatement methods do to other types.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (JENA-1082) Add to org.apache.jena.rdf.model.ModelCon interface a listLiteralStatements method that accepts ints.

[ASF subversion and git services (JIRA)]

[ 
https://issues.apache.org/jira/browse/JENA-1082?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15074283#comment-15074283
 ] 

ASF subversion and git services commented on JENA-1082:
---

Commit 2d1e7a0235f91990f31c00c9242a532783f74866 in jena's branch 
refs/heads/master from [~ramiromagalhaes]
[ https://git-wip-us.apache.org/repos/asf?p=jena.git;h=2d1e7a0 ]

Fixes JENA-1082.


> Add to org.apache.jena.rdf.model.ModelCon interface a listLiteralStatements 
> method that accepts ints.
> -
>
> Key: JENA-1082
> URL: https://issues.apache.org/jira/browse/JENA-1082
> Project: Apache Jena
>  Issue Type: Improvement
>  Components: Core
>Affects Versions: Jena 3.0.0
>Reporter: Ramiro Pereira de Magalhães
>Priority: Minor
>
> Add to org.apache.jena.rdf.model.ModelCon interface a {{StmtIterator 
> listLiteralStatements(Resource subject, Property predicate, int object );}} 
> method.
> Implement such method in classes that implement such interface. This method 
> should be able to list literal integer statements, like the other 
> listLiteralStatement methods do to other types.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Resolved] (JENA-1082) Add to org.apache.jena.rdf.model.ModelCon interface a listLiteralStatements method that accepts ints.

[Andy Seaborne (JIRA)]

 [ 
https://issues.apache.org/jira/browse/JENA-1082?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Andy Seaborne resolved JENA-1082.
-
   Resolution: Fixed
 Assignee: Andy Seaborne
Fix Version/s: Jena 3.1.0

Thank you.

PR applied.


> Add to org.apache.jena.rdf.model.ModelCon interface a listLiteralStatements 
> method that accepts ints.
> -
>
> Key: JENA-1082
> URL: https://issues.apache.org/jira/browse/JENA-1082
> Project: Apache Jena
>  Issue Type: Improvement
>  Components: Core
>Affects Versions: Jena 3.0.0
>Reporter: Ramiro Pereira de Magalhães
>Assignee: Andy Seaborne
>Priority: Minor
> Fix For: Jena 3.1.0
>
>
> Add to org.apache.jena.rdf.model.ModelCon interface a {{StmtIterator 
> listLiteralStatements(Resource subject, Property predicate, int object );}} 
> method.
> Implement such method in classes that implement such interface. This method 
> should be able to list literal integer statements, like the other 
> listLiteralStatement methods do to other types.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (JENA-1082) Add to org.apache.jena.rdf.model.ModelCon interface a listLiteralStatements method that accepts ints.

[ASF subversion and git services (JIRA)]

[ 
https://issues.apache.org/jira/browse/JENA-1082?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15074297#comment-15074297
 ] 

ASF subversion and git services commented on JENA-1082:
---

Commit 6fbecf1e35024b51f1f3031c9b5c8e960e2237d4 in jena's branch 
refs/heads/master from [~andy.seaborne]
[ https://git-wip-us.apache.org/repos/asf?p=jena.git;h=6fbecf1 ]

Align with jena-core change (JENA-1082)


> Add to org.apache.jena.rdf.model.ModelCon interface a listLiteralStatements 
> method that accepts ints.
> -
>
> Key: JENA-1082
> URL: https://issues.apache.org/jira/browse/JENA-1082
> Project: Apache Jena
>  Issue Type: Improvement
>  Components: Core
>Affects Versions: Jena 3.0.0
>Reporter: Ramiro Pereira de Magalhães
>Assignee: Andy Seaborne
>Priority: Minor
> Fix For: Jena 3.1.0
>
>
> Add to org.apache.jena.rdf.model.ModelCon interface a {{StmtIterator 
> listLiteralStatements(Resource subject, Property predicate, int object );}} 
> method.
> Implement such method in classes that implement such interface. This method 
> should be able to list literal integer statements, like the other 
> listLiteralStatement methods do to other types.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (JENA-914) Get Jena working on Android

[Bruno P. Kinoshita (JIRA)]

[ 
https://issues.apache.org/jira/browse/JENA-914?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15074609#comment-15074609
 ] 

Bruno P. Kinoshita commented on JENA-914:
-

Was reading the news today when I saw one saying that the next Android version 
will use OpenJDK (here's the article - 
http://venturebeat.com/2015/12/29/google-confirms-next-android-version-wont-use-oracles-proprietary-java-apis/).

I'm not using Jena on Android, but remembered about this issue. Depending on 
release schedules, and the time/effort to fix this issue, we may see it fixed 
eventually by the adoption of OpenJDK in Android (I think).

> Get Jena working on Android
> ---
>
> Key: JENA-914
> URL: https://issues.apache.org/jira/browse/JENA-914
> Project: Apache Jena
>  Issue Type: Improvement
>  Components: ARQ, TDB
> Environment: Android
>Reporter: Sören Brunk
>Priority: Minor
>  Labels: android
>
> Currently, Jena can't be used on Android as is, due to multiple issues caused 
> by differences between the standard JVM and Android's Dalvik VM.
> The main issues are
> # Package conflicts
> ## The StAX API (javax.xml.stream is missing on Android). It's not possible 
> to just provide the classes as including packages from core Java namespaces 
> doesn't work.
> ## Android provides an ancient version of httpclient that is incompatible 
> with version 4.2 required by Jena.
> # TDB uses java.lang.ManagementFactory in ProcessUtils which isn't available 
> on Android. It's possible to use android.os.Process instead but that requires 
> a dependency on the Android SDK.
> There is a [project|https://github.com/seus-inf/jena-android] that does some 
> post-processing on the Jena packages to create a variant that runs on 
> Android. Some of it might be of use to get Android support into mainline.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (JENA-632) Generate JSON from SPARQL directly.

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/JENA-632?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15073784#comment-15073784
 ] 

ASF GitHub Bot commented on JENA-632:
-

Github user afs commented on the pull request:

https://github.com/apache/jena/pull/114#issuecomment-167763543
  
Main comment : the grammar changes haven't been put inside `#ifdef ARQ` so 
they happen in strict SPARQL 1.1 as well as the extended ARQ language.

Keeping the SPARQL 1.1 parser exactly as the SPARQL 1.1 spec is important. 
There should just be some noise changes and no more.  (see for example the 
construct-quad changes).


> Generate JSON from SPARQL directly.
> ---
>
> Key: JENA-632
> URL: https://issues.apache.org/jira/browse/JENA-632
> Project: Apache Jena
>  Issue Type: Improvement
>  Components: ARQ, Fuseki
>Reporter: Andy Seaborne
>Assignee: Bruno P. Kinoshita
>Priority: Minor
>  Labels: java, javacc
>  Time Spent: 0.5h
>  Remaining Estimate: 0h
>
> The capability to generate JSON directly from a SPARQL (or extended SPARQL) 
> query would enable the creation of JSON data API over published linked data.
> This project would cover:
> # Design and publication of a design.
> # Refinement of design based on community feed
> # Implementation, including testing.
> # Refinement of implementation based on community feed
> Skills required: Java, some parser work, design and discussion with the user 
> community, basic understanding of HTTP and content negotiation.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[GitHub] jena pull request: JENA-632: Generate JSON from SPARQL directly

[afs]

Github user afs commented on the pull request:

https://github.com/apache/jena/pull/114#issuecomment-167763543
  
Main comment : the grammar changes haven't been put inside `#ifdef ARQ` so 
they happen in strict SPARQL 1.1 as well as the extended ARQ language.

Keeping the SPARQL 1.1 parser exactly as the SPARQL 1.1 spec is important. 
There should just be some noise changes and no more.  (see for example the 
construct-quad changes).


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[jira] [Commented] (JENA-632) Generate JSON from SPARQL directly.

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/JENA-632?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15073765#comment-15073765
 ] 

ASF GitHub Bot commented on JENA-632:
-

Github user afs commented on a diff in the pull request:

https://github.com/apache/jena/pull/114#discussion_r48532056
  
--- Diff: jena-arq/Grammar/master.jj ---
@@ -100,6 +100,38 @@ import org.apache.jena.sparql.core.Quad ;
 public class CLASS extends PARSERBASE
 {
 boolean allowAggregatesInExpressions = false ;
+
--- End diff --

This looks like debug code - could it go elsewhere?


> Generate JSON from SPARQL directly.
> ---
>
> Key: JENA-632
> URL: https://issues.apache.org/jira/browse/JENA-632
> Project: Apache Jena
>  Issue Type: Improvement
>  Components: ARQ, Fuseki
>Reporter: Andy Seaborne
>Assignee: Bruno P. Kinoshita
>Priority: Minor
>  Labels: java, javacc
>  Time Spent: 0.5h
>  Remaining Estimate: 0h
>
> The capability to generate JSON directly from a SPARQL (or extended SPARQL) 
> query would enable the creation of JSON data API over published linked data.
> This project would cover:
> # Design and publication of a design.
> # Refinement of design based on community feed
> # Implementation, including testing.
> # Refinement of implementation based on community feed
> Skills required: Java, some parser work, design and discussion with the user 
> community, basic understanding of HTTP and content negotiation.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[GitHub] jena pull request: JENA-632: Generate JSON from SPARQL directly

[afs]

Github user afs commented on a diff in the pull request:

https://github.com/apache/jena/pull/114#discussion_r48532880
  
--- Diff: 
jena-arq/src/main/java/org/apache/jena/sparql/lang/sparql_11/SPARQLParser11Constants.java
 ---
@@ -431,6 +433,7 @@
 "\"select\"",
 "\"distinct\"",
 "\"reduced\"",
+"\"json\"",
--- End diff --

This the new JSON construct sneaking into pure SPARQL 1.1


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] jena pull request: JENA-632: Generate JSON from SPARQL directly

[afs]

Github user afs commented on a diff in the pull request:

https://github.com/apache/jena/pull/114#discussion_r48532962
  
--- Diff: jena-arq/Grammar/master.jj ---
@@ -100,6 +100,38 @@ import org.apache.jena.sparql.core.Quad ;
 public class CLASS extends PARSERBASE
 {
 boolean allowAggregatesInExpressions = false ;
+
+public static void main(String args[]) {
+while (true) {
--- End diff --

This looks like debug code - could it go elsewhere?


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[jira] [Commented] (JENA-632) Generate JSON from SPARQL directly.

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/JENA-632?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15073782#comment-15073782
 ] 

ASF GitHub Bot commented on JENA-632:
-

Github user afs commented on a diff in the pull request:

https://github.com/apache/jena/pull/114#discussion_r48532962
  
--- Diff: jena-arq/Grammar/master.jj ---
@@ -100,6 +100,38 @@ import org.apache.jena.sparql.core.Quad ;
 public class CLASS extends PARSERBASE
 {
 boolean allowAggregatesInExpressions = false ;
+
+public static void main(String args[]) {
+while (true) {
--- End diff --

This looks like debug code - could it go elsewhere?


> Generate JSON from SPARQL directly.
> ---
>
> Key: JENA-632
> URL: https://issues.apache.org/jira/browse/JENA-632
> Project: Apache Jena
>  Issue Type: Improvement
>  Components: ARQ, Fuseki
>Reporter: Andy Seaborne
>Assignee: Bruno P. Kinoshita
>Priority: Minor
>  Labels: java, javacc
>  Time Spent: 0.5h
>  Remaining Estimate: 0h
>
> The capability to generate JSON directly from a SPARQL (or extended SPARQL) 
> query would enable the creation of JSON data API over published linked data.
> This project would cover:
> # Design and publication of a design.
> # Refinement of design based on community feed
> # Implementation, including testing.
> # Refinement of implementation based on community feed
> Skills required: Java, some parser work, design and discussion with the user 
> community, basic understanding of HTTP and content negotiation.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[GitHub] jena pull request: JENA-632: Generate JSON from SPARQL directly

[afs]

Github user afs commented on a diff in the pull request:

https://github.com/apache/jena/pull/114#discussion_r48532056
  
--- Diff: jena-arq/Grammar/master.jj ---
@@ -100,6 +100,38 @@ import org.apache.jena.sparql.core.Quad ;
 public class CLASS extends PARSERBASE
 {
 boolean allowAggregatesInExpressions = false ;
+
--- End diff --

This looks like debug code - could it go elsewhere?


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[jira] [Commented] (JENA-632) Generate JSON from SPARQL directly.

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/JENA-632?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15073779#comment-15073779
 ] 

ASF GitHub Bot commented on JENA-632:
-

Github user afs commented on a diff in the pull request:

https://github.com/apache/jena/pull/114#discussion_r48532825
  
--- Diff: jena-arq/Grammar/master.jj ---
@@ -100,6 +100,38 @@ import org.apache.jena.sparql.core.Quad ;
 public class CLASS extends PARSERBASE
--- End diff --

Please update tokens.txt as well - it is used to generate HTML.


> Generate JSON from SPARQL directly.
> ---
>
> Key: JENA-632
> URL: https://issues.apache.org/jira/browse/JENA-632
> Project: Apache Jena
>  Issue Type: Improvement
>  Components: ARQ, Fuseki
>Reporter: Andy Seaborne
>Assignee: Bruno P. Kinoshita
>Priority: Minor
>  Labels: java, javacc
>  Time Spent: 0.5h
>  Remaining Estimate: 0h
>
> The capability to generate JSON directly from a SPARQL (or extended SPARQL) 
> query would enable the creation of JSON data API over published linked data.
> This project would cover:
> # Design and publication of a design.
> # Refinement of design based on community feed
> # Implementation, including testing.
> # Refinement of implementation based on community feed
> Skills required: Java, some parser work, design and discussion with the user 
> community, basic understanding of HTTP and content negotiation.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[GitHub] jena pull request: JENA-632: Generate JSON from SPARQL directly

[afs]

Github user afs commented on a diff in the pull request:

https://github.com/apache/jena/pull/114#discussion_r48532825
  
--- Diff: jena-arq/Grammar/master.jj ---
@@ -100,6 +100,38 @@ import org.apache.jena.sparql.core.Quad ;
 public class CLASS extends PARSERBASE
--- End diff --

Please update tokens.txt as well - it is used to generate HTML.


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[jira] [Commented] (JENA-632) Generate JSON from SPARQL directly.

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/JENA-632?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15073777#comment-15073777
 ] 

ASF GitHub Bot commented on JENA-632:
-

Github user afs commented on a diff in the pull request:

https://github.com/apache/jena/pull/114#discussion_r48532742
  
--- Diff: jena-arq/Grammar/master.jj ---
@@ -2166,6 +2227,17 @@ String String() : { Token t ; String lex ; }
 }
 }
 
+Number Number() : { Token t ; Number number ; }
+{
--- End diff --

Number -> JSONNumber

But will rule NumericLiteral work here? Then parse the lexical form to a 
number.

However, generally, working in nodes is probably going to be easier because 
bindings map variables to Nodes.


> Generate JSON from SPARQL directly.
> ---
>
> Key: JENA-632
> URL: https://issues.apache.org/jira/browse/JENA-632
> Project: Apache Jena
>  Issue Type: Improvement
>  Components: ARQ, Fuseki
>Reporter: Andy Seaborne
>Assignee: Bruno P. Kinoshita
>Priority: Minor
>  Labels: java, javacc
>  Time Spent: 0.5h
>  Remaining Estimate: 0h
>
> The capability to generate JSON directly from a SPARQL (or extended SPARQL) 
> query would enable the creation of JSON data API over published linked data.
> This project would cover:
> # Design and publication of a design.
> # Refinement of design based on community feed
> # Implementation, including testing.
> # Refinement of implementation based on community feed
> Skills required: Java, some parser work, design and discussion with the user 
> community, basic understanding of HTTP and content negotiation.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)