[jira] [Resolved] (JENA-1500) The basic in-memory dataset retains a memory of empty named graphs

2018-03-08 Thread Andy Seaborne (JIRA)

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

Andy Seaborne resolved JENA-1500.
-
   Resolution: Fixed
Fix Version/s: Jena 3.7.0

> The basic in-memory dataset retains a memory of empty named graphs
> --
>
> Key: JENA-1500
> URL: https://issues.apache.org/jira/browse/JENA-1500
> Project: Apache Jena
>  Issue Type: Bug
>Affects Versions: Jena 3.6.0
>Reporter: Andy Seaborne
>Assignee: Andy Seaborne
>Priority: Major
> Fix For: Jena 3.7.0
>
>
> See JENA-1499.
> This is aligning {{DatasetFactory.create()}}.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Commented] (JENA-1500) The basic in-memory dataset retains a memory of empty named graphs

2018-03-08 Thread ASF GitHub Bot (JIRA)

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

ASF GitHub Bot commented on JENA-1500:
--

Github user asfgit closed the pull request at:

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


> The basic in-memory dataset retains a memory of empty named graphs
> --
>
> Key: JENA-1500
> URL: https://issues.apache.org/jira/browse/JENA-1500
> Project: Apache Jena
>  Issue Type: Bug
>Affects Versions: Jena 3.6.0
>Reporter: Andy Seaborne
>Assignee: Andy Seaborne
>Priority: Major
>
> See JENA-1499.
> This is aligning {{DatasetFactory.create()}}.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[GitHub] jena pull request #372: Reformatting + two RiotChars functions.

2018-03-08 Thread asfgit
Github user asfgit closed the pull request at:

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


---


[jira] [Commented] (JENA-1500) The basic in-memory dataset retains a memory of empty named graphs

2018-03-08 Thread ASF subversion and git services (JIRA)

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

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

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

JENA-1500: Merge commit 'refs/pull/376/head' of https://github.com/apache/jena

This closes #376.


> The basic in-memory dataset retains a memory of empty named graphs
> --
>
> Key: JENA-1500
> URL: https://issues.apache.org/jira/browse/JENA-1500
> Project: Apache Jena
>  Issue Type: Bug
>Affects Versions: Jena 3.6.0
>Reporter: Andy Seaborne
>Assignee: Andy Seaborne
>Priority: Major
>
> See JENA-1499.
> This is aligning {{DatasetFactory.create()}}.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Commented] (JENA-1499) The TIM dataset retains a memory of named graphs after deleting all quads.

2018-03-08 Thread ASF subversion and git services (JIRA)

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

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

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

JENA-1500, JENA-1499: Tests for empty graph behaviour.


> The TIM dataset retains a memory of named graphs after deleting all quads.
> --
>
> Key: JENA-1499
> URL: https://issues.apache.org/jira/browse/JENA-1499
> Project: Apache Jena
>  Issue Type: Bug
>Affects Versions: Jena 3.6.0
>Reporter: Andy Seaborne
>Assignee: A. Soroka
>Priority: Minor
>
> Illustration:
> {noformat}
> DatasetGraph dsg = DatasetGraphFactory.createTxnMem();
> Quad q = SSE.parseQuad("(:g :s :p :o)");
> dsg.add(q);
> dsg.delete(q);
> Iter.print(dsg.listGraphNodes());
> {noformat}
> prints {{http://example/g}}.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Commented] (JENA-1500) The basic in-memory dataset retains a memory of empty named graphs

2018-03-08 Thread ASF subversion and git services (JIRA)

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

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

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

JENA-1500: Hide empty graphs in default in-memory dataset.


> The basic in-memory dataset retains a memory of empty named graphs
> --
>
> Key: JENA-1500
> URL: https://issues.apache.org/jira/browse/JENA-1500
> Project: Apache Jena
>  Issue Type: Bug
>Affects Versions: Jena 3.6.0
>Reporter: Andy Seaborne
>Assignee: Andy Seaborne
>Priority: Major
>
> See JENA-1499.
> This is aligning {{DatasetFactory.create()}}.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[GitHub] jena pull request #376: JENA-1500: Plain in-memory dataset and empty graphs.

2018-03-08 Thread asfgit
Github user asfgit closed the pull request at:

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


---


[jira] [Commented] (JENA-1500) The basic in-memory dataset retains a memory of empty named graphs

2018-03-08 Thread ASF subversion and git services (JIRA)

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

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

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

JENA-1500, JENA-1499: Tests for empty graph behaviour.


> The basic in-memory dataset retains a memory of empty named graphs
> --
>
> Key: JENA-1500
> URL: https://issues.apache.org/jira/browse/JENA-1500
> Project: Apache Jena
>  Issue Type: Bug
>Affects Versions: Jena 3.6.0
>Reporter: Andy Seaborne
>Assignee: Andy Seaborne
>Priority: Major
>
> See JENA-1499.
> This is aligning {{DatasetFactory.create()}}.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Commented] (JENA-1501) Add systemd unit file for Fuseki

2018-03-08 Thread ASF GitHub Bot (JIRA)

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

ASF GitHub Bot commented on JENA-1501:
--

Github user jneubert commented on the issue:

https://github.com/apache/jena/pull/375
  
Thank you very much, Osma!
One small suggestion about the wording of the comment: Instead of ``Edit 
the line below to adjust memory size`` it could be perhaps more clear to write 
``Edit the line below to adjust the amount of memory for Fuseki`` for people 
who are not familiar with Java memory management and could assume the total 
memory size of their machine.


> Add systemd unit file for Fuseki
> 
>
> Key: JENA-1501
> URL: https://issues.apache.org/jira/browse/JENA-1501
> Project: Apache Jena
>  Issue Type: Improvement
>  Components: Fuseki
>Affects Versions: Jena 3.6.0
>Reporter: Osma Suominen
>Assignee: Osma Suominen
>Priority: Major
>
> As discussed on the users mailing list, we could add a systemd unit file for 
> Fuseki to make it easier to set it up on systemd based Linux installations.
> I will make a PR soon.
> Ping [~jneubert] who originally requested this



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[GitHub] jena issue #375: JENA-1501: add systemd unit file for Fuseki

2018-03-08 Thread jneubert
Github user jneubert commented on the issue:

https://github.com/apache/jena/pull/375
  
Thank you very much, Osma!
One small suggestion about the wording of the comment: Instead of ``Edit 
the line below to adjust memory size`` it could be perhaps more clear to write 
``Edit the line below to adjust the amount of memory for Fuseki`` for people 
who are not familiar with Java memory management and could assume the total 
memory size of their machine.


---


[jira] [Comment Edited] (JENA-1499) The TIM dataset retains a memory of named graphs after deleting all quads.

2018-03-08 Thread Andy Seaborne (JIRA)

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

Andy Seaborne edited comment on JENA-1499 at 3/8/18 3:59 PM:
-

The other case is the default in-memory dataset ({{DatasetFactory.create()}}.

It's a one line change to {{DatasetGraphMap.listGraphNodes}} to make not reveal 
empty graphs. 

{{containsGraph}} already works - it looks for quads not for graph in the map. 
(It could be slightly done as an override.)

JENA-1500 and PR#376 (which includes datasets tests including for here).

{noformat}
 == plain
 Contains: false
 – listGraphNodes
 (none)
 – dump
 (empty)
 
 == general
 Contains: true
 – listGraphNodes
 [http://example/g]
 – dump
 <[http://example/g]> {
 }
{noformat}

With PR 374, TIM and TDB are the same as "plain".


was (Author: andy.seaborne):
The other case is the default in-memory dataset ({{DatasetFactory.create()}}.

It's a one line change to {{DatasetGraphMap.listGraphNodes}} to make not reveal 
empty graphs.

{{containsGraph}} already works - it looks for quads not for graph in the map. 
(It could be slightly done as an override.)

{nofomat}
== default
Contains: false
-- listGraphNodes
(none)
-- dump
(empty)

== general
Contains: true
-- listGraphNodes
http://example/g
-- dump
 {
}
{nofomat}

With PR 374, TIM and TDB are the same as "default".


> The TIM dataset retains a memory of named graphs after deleting all quads.
> --
>
> Key: JENA-1499
> URL: https://issues.apache.org/jira/browse/JENA-1499
> Project: Apache Jena
>  Issue Type: Bug
>Affects Versions: Jena 3.6.0
>Reporter: Andy Seaborne
>Assignee: A. Soroka
>Priority: Minor
>
> Illustration:
> {noformat}
> DatasetGraph dsg = DatasetGraphFactory.createTxnMem();
> Quad q = SSE.parseQuad("(:g :s :p :o)");
> dsg.add(q);
> dsg.delete(q);
> Iter.print(dsg.listGraphNodes());
> {noformat}
> prints {{http://example/g}}.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Commented] (JENA-1500) The basic in-memory dataset retains a memory of empty named graphs

2018-03-08 Thread ASF GitHub Bot (JIRA)

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

ASF GitHub Bot commented on JENA-1500:
--

GitHub user afs opened a pull request:

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

JENA-1500: Plain in-memory dataset and empty graphs.

This PR will cause tests to fail under #374 goes in.

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

$ git pull https://github.com/afs/jena dataset-mem-align

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

https://github.com/apache/jena/pull/376.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 #376


commit 7130fd5e0ba08463ef38bd7d1e83b6861f82fc06
Author: Andy Seaborne 
Date:   2018-03-08T15:40:21Z

Remove duplicate

commit c06971febfd6b6d92cfbb97b9baa3781f1709dda
Author: Andy Seaborne 
Date:   2018-03-08T15:54:13Z

JENA-1500: Hide empty graphs in default in-memory dataset.

commit 29e0a4cc7fde649fd92fb72df3b35d44a491153d
Author: Andy Seaborne 
Date:   2018-03-08T15:54:45Z

JENA-1500, JENA-1499: Tests for empty graph behaviour.




> The basic in-memory dataset retains a memory of empty named graphs
> --
>
> Key: JENA-1500
> URL: https://issues.apache.org/jira/browse/JENA-1500
> Project: Apache Jena
>  Issue Type: Bug
>Affects Versions: Jena 3.6.0
>Reporter: Andy Seaborne
>Assignee: Andy Seaborne
>Priority: Major
>
> See JENA-1499.
> This is aligning {{DatasetFactory.create()}}.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[GitHub] jena pull request #376: JENA-1500: Plain in-memory dataset and empty graphs.

2018-03-08 Thread afs
GitHub user afs opened a pull request:

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

JENA-1500: Plain in-memory dataset and empty graphs.

This PR will cause tests to fail under #374 goes in.

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

$ git pull https://github.com/afs/jena dataset-mem-align

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

https://github.com/apache/jena/pull/376.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 #376


commit 7130fd5e0ba08463ef38bd7d1e83b6861f82fc06
Author: Andy Seaborne 
Date:   2018-03-08T15:40:21Z

Remove duplicate

commit c06971febfd6b6d92cfbb97b9baa3781f1709dda
Author: Andy Seaborne 
Date:   2018-03-08T15:54:13Z

JENA-1500: Hide empty graphs in default in-memory dataset.

commit 29e0a4cc7fde649fd92fb72df3b35d44a491153d
Author: Andy Seaborne 
Date:   2018-03-08T15:54:45Z

JENA-1500, JENA-1499: Tests for empty graph behaviour.




---


[jira] [Commented] (JENA-1501) Add systemd unit file for Fuseki

2018-03-08 Thread ASF GitHub Bot (JIRA)

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

ASF GitHub Bot commented on JENA-1501:
--

GitHub user osma opened a pull request:

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

JENA-1501: add systemd unit file for Fuseki

This adds a systemd unit file to the Fuseki2 distribution.

This is the same file that was circulated on the users list (in response to 
a question by @jneubert), but with reduced default memory setting (2GB), an ASF 
license header and some hopefully helpful comments about how to set it up.

See https://issues.apache.org/jira/browse/JENA-1501

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

$ git pull https://github.com/osma/jena fuseki-systemd-service

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

https://github.com/apache/jena/pull/375.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 #375


commit a85333a8c821927eb4a58463859b5f6caa2d94e4
Author: Osma Suominen 
Date:   2018-03-08T15:19:08Z

JENA-1501: add systemd unit file for Fuseki




> Add systemd unit file for Fuseki
> 
>
> Key: JENA-1501
> URL: https://issues.apache.org/jira/browse/JENA-1501
> Project: Apache Jena
>  Issue Type: Improvement
>  Components: Fuseki
>Affects Versions: Jena 3.6.0
>Reporter: Osma Suominen
>Assignee: Osma Suominen
>Priority: Major
>
> As discussed on the users mailing list, we could add a systemd unit file for 
> Fuseki to make it easier to set it up on systemd based Linux installations.
> I will make a PR soon.
> Ping [~jneubert] who originally requested this



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[GitHub] jena pull request #375: JENA-1501: add systemd unit file for Fuseki

2018-03-08 Thread osma
GitHub user osma opened a pull request:

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

JENA-1501: add systemd unit file for Fuseki

This adds a systemd unit file to the Fuseki2 distribution.

This is the same file that was circulated on the users list (in response to 
a question by @jneubert), but with reduced default memory setting (2GB), an ASF 
license header and some hopefully helpful comments about how to set it up.

See https://issues.apache.org/jira/browse/JENA-1501

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

$ git pull https://github.com/osma/jena fuseki-systemd-service

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

https://github.com/apache/jena/pull/375.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 #375


commit a85333a8c821927eb4a58463859b5f6caa2d94e4
Author: Osma Suominen 
Date:   2018-03-08T15:19:08Z

JENA-1501: add systemd unit file for Fuseki




---


[jira] [Created] (JENA-1501) Add systemd unit file for Fuseki

2018-03-08 Thread Osma Suominen (JIRA)
Osma Suominen created JENA-1501:
---

 Summary: Add systemd unit file for Fuseki
 Key: JENA-1501
 URL: https://issues.apache.org/jira/browse/JENA-1501
 Project: Apache Jena
  Issue Type: Improvement
  Components: Fuseki
Affects Versions: Jena 3.6.0
Reporter: Osma Suominen
Assignee: Osma Suominen


As discussed on the users mailing list, we could add a systemd unit file for 
Fuseki to make it easier to set it up on systemd based Linux installations.

I will make a PR soon.

Ping [~jneubert] who originally requested this



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Created] (JENA-1500) The basic in-memory dataset retains a memory of empty named graphs

2018-03-08 Thread Andy Seaborne (JIRA)
Andy Seaborne created JENA-1500:
---

 Summary: The basic in-memory dataset retains a memory of empty 
named graphs
 Key: JENA-1500
 URL: https://issues.apache.org/jira/browse/JENA-1500
 Project: Apache Jena
  Issue Type: Bug
Affects Versions: Jena 3.6.0
Reporter: Andy Seaborne
Assignee: Andy Seaborne


See JENA-1499.

This is aligning {{DatasetFactory.create()}}.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Commented] (JENA-1499) The TIM dataset retains a memory of named graphs after deleting all quads.

2018-03-08 Thread Andy Seaborne (JIRA)

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

Andy Seaborne commented on JENA-1499:
-

The other case is the default in-memory dataset ({{DatasetFactory.create()}}.

It's a one line change to {{DatasetGraphMap.listGraphNodes}} to make not reveal 
empty graphs.

{{containsGraph}} already works - it looks for quads not for graph in the map. 
(It could be slightly done as an override.)

{nofomat}
== default
Contains: false
-- listGraphNodes
(none)
-- dump
(empty)

== general
Contains: true
-- listGraphNodes
http://example/g
-- dump
 {
}
{nofomat}

With PR 374, TIM and TDB are the same as "default".


> The TIM dataset retains a memory of named graphs after deleting all quads.
> --
>
> Key: JENA-1499
> URL: https://issues.apache.org/jira/browse/JENA-1499
> Project: Apache Jena
>  Issue Type: Bug
>Affects Versions: Jena 3.6.0
>Reporter: Andy Seaborne
>Assignee: A. Soroka
>Priority: Minor
>
> Illustration:
> {noformat}
> DatasetGraph dsg = DatasetGraphFactory.createTxnMem();
> Quad q = SSE.parseQuad("(:g :s :p :o)");
> dsg.add(q);
> dsg.delete(q);
> Iter.print(dsg.listGraphNodes());
> {noformat}
> prints {{http://example/g}}.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[GitHub] jena pull request #374: JENA-1499: Pruning TIM indexes on tuple deletion

2018-03-08 Thread asfgit
Github user asfgit closed the pull request at:

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


---


[jira] [Commented] (JENA-1499) The TIM dataset retains a memory of named graphs after deleting all quads.

2018-03-08 Thread ASF subversion and git services (JIRA)

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

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

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

JENA-1499: Pruning TIM indexes on tuple deletion


> The TIM dataset retains a memory of named graphs after deleting all quads.
> --
>
> Key: JENA-1499
> URL: https://issues.apache.org/jira/browse/JENA-1499
> Project: Apache Jena
>  Issue Type: Bug
>Affects Versions: Jena 3.6.0
>Reporter: Andy Seaborne
>Assignee: A. Soroka
>Priority: Minor
>
> Illustration:
> {noformat}
> DatasetGraph dsg = DatasetGraphFactory.createTxnMem();
> Quad q = SSE.parseQuad("(:g :s :p :o)");
> dsg.add(q);
> dsg.delete(q);
> Iter.print(dsg.listGraphNodes());
> {noformat}
> prints {{http://example/g}}.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Commented] (JENA-1499) The TIM dataset retains a memory of named graphs after deleting all quads.

2018-03-08 Thread ASF GitHub Bot (JIRA)

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

ASF GitHub Bot commented on JENA-1499:
--

Github user asfgit closed the pull request at:

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


> The TIM dataset retains a memory of named graphs after deleting all quads.
> --
>
> Key: JENA-1499
> URL: https://issues.apache.org/jira/browse/JENA-1499
> Project: Apache Jena
>  Issue Type: Bug
>Affects Versions: Jena 3.6.0
>Reporter: Andy Seaborne
>Assignee: A. Soroka
>Priority: Minor
>
> Illustration:
> {noformat}
> DatasetGraph dsg = DatasetGraphFactory.createTxnMem();
> Quad q = SSE.parseQuad("(:g :s :p :o)");
> dsg.add(q);
> dsg.delete(q);
> Iter.print(dsg.listGraphNodes());
> {noformat}
> prints {{http://example/g}}.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


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

2018-03-08 Thread ASF GitHub Bot (JIRA)

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

ASF GitHub Bot commented on JENA-632:
-

Github user afs commented on the issue:

https://github.com/apache/jena/pull/114
  
The JSON ecosystem moves fast! GraphQL is now significant and how that 
might be used is also very interesting. There are different ways to use GraphQL 
and maybe it is not the solution to all needs anyway - this ticket is more 
about result sets in easy-to-consume JSON than other work in the GraphQL-RDF 
area and more about JSON services.

To move this ticket forward, how about putting the feature in with a big 
label saying "Experimental - subject to change" and _really_ mean it?  By 
getting it out, it generates feedback, requirements and insight. 

You can ask for result sets in JSON but the JSON 
(http://www.w3.org/TR/sparql11-results-json/) or JSON-LD graphs but that isn't 
what general data consumers would consider to be "easy-to-consume".

Is the RDF literal to JSON aligned with:
[RDF-JS 
mapping](http://jena.staging.apache.org/documentation/query/javascript-functions.html#arguments-and-function-results)?
 (which only came along recently).


> 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
(v7.6.3#76005)


[GitHub] jena issue #114: JENA-632: Generate JSON from SPARQL directly

2018-03-08 Thread afs
Github user afs commented on the issue:

https://github.com/apache/jena/pull/114
  
The JSON ecosystem moves fast! GraphQL is now significant and how that 
might be used is also very interesting. There are different ways to use GraphQL 
and maybe it is not the solution to all needs anyway - this ticket is more 
about result sets in easy-to-consume JSON than other work in the GraphQL-RDF 
area and more about JSON services.

To move this ticket forward, how about putting the feature in with a big 
label saying "Experimental - subject to change" and _really_ mean it?  By 
getting it out, it generates feedback, requirements and insight. 

You can ask for result sets in JSON but the JSON 
(http://www.w3.org/TR/sparql11-results-json/) or JSON-LD graphs but that isn't 
what general data consumers would consider to be "easy-to-consume".

Is the RDF literal to JSON aligned with:
[RDF-JS 
mapping](http://jena.staging.apache.org/documentation/query/javascript-functions.html#arguments-and-function-results)?
 (which only came along recently).


---