[GitHub] [jena-site] afs commented on a change in pull request #28: Add link to Fuseki Server Protocol page

[GitBox]

afs commented on a change in pull request #28:
URL: https://github.com/apache/jena-site/pull/28#discussion_r519199757



##
File path: source/documentation/fuseki2/__index.md
##
@@ -35,6 +35,7 @@ transactional persistent storage layer, and incorporates
 - [As a Docker container](fuseki-main#fuseki-docker)
 - [As an embedded SPARQL server](fuseki-embedded.html)
 - [Security and data access control](fuseki-data-access-control.html)
+- [Fuseki Server Protocol (REST API)](fuseki-server-protocol.html)

Review comment:
   The pages were reorged 2 months ago - there is a page for 
[Fuseki/webapp](https://jena.apache.org/documentation/fuseki2/fuseki-webapp.html)
 and a page for 
[Fuseki/main](https://jena.apache.org/documentation/fuseki2/fuseki-main.html), 
which includes docker, and for Fuseki+GeoSPARQL.
   
   There are traditional ways to run services and modern ones, not that we see 
many instances of multiple webapps in a single Tomcat installation these days.
   
   The many modules are a maven effect and, yes, there are quite a few of them. 
Each module does one step, so while one or two steps could be combined into one 
module, by the time we have core code, webapp, command line, different 
packagings, it all mounts up. Might be slightly easier in gradle but we get the 
release process from Apache parent POM.
   
   I can add a page for the module dependencies if that helps.
   





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

[GitHub] [jena-site] rvesse commented on a change in pull request #28: Add link to Fuseki Server Protocol page

[GitBox]

rvesse commented on a change in pull request #28:
URL: https://github.com/apache/jena-site/pull/28#discussion_r517435484



##
File path: source/documentation/fuseki2/__index.md
##
@@ -35,6 +35,7 @@ transactional persistent storage layer, and incorporates
 - [As a Docker container](fuseki-main#fuseki-docker)
 - [As an embedded SPARQL server](fuseki-embedded.html)
 - [Security and data access control](fuseki-data-access-control.html)
+- [Fuseki Server Protocol (REST API)](fuseki-server-protocol.html)

Review comment:
   TBH I struggle to understand the relationship between the many Fuseki 
modules these days, do we have any documentation that actually explains that 
because even as someone relatively familiar with the code base I find this 
confusing





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

[GitHub] [jena-site] afs commented on a change in pull request #28: Add link to Fuseki Server Protocol page

[GitBox]

afs commented on a change in pull request #28:
URL: https://github.com/apache/jena-site/pull/28#discussion_r516970029



##
File path: source/documentation/fuseki2/__index.md
##
@@ -35,6 +35,7 @@ transactional persistent storage layer, and incorporates
 - [As a Docker container](fuseki-main#fuseki-docker)
 - [As an embedded SPARQL server](fuseki-embedded.html)
 - [Security and data access control](fuseki-data-access-control.html)
+- [Fuseki Server Protocol (REST API)](fuseki-server-protocol.html)

Review comment:
   This only applies to fuseki-webapp but putting it here implies it 
applies to both forms.
   
   See 1d3953a1 - it has been incomplete for a long while and is replaced by 
the both-server `fuseki-server-info.html`
   
   It was:
   ```
   [Server Admin Protocol](fuseki-server-protocol.html)
   ```
   
   It may not be the way to have admin for fuseki-main, and quite possibly that 
would only have some of the functionality. To create space for Fuseki to 
evolve, at least only put in the fuseki-webapp section.
   
   





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

[GitHub] [jena-site] afs commented on a change in pull request #28: Add link to Fuseki Server Protocol page

[GitBox]

afs commented on a change in pull request #28:
URL: https://github.com/apache/jena-site/pull/28#discussion_r516970029



##
File path: source/documentation/fuseki2/__index.md
##
@@ -35,6 +35,7 @@ transactional persistent storage layer, and incorporates
 - [As a Docker container](fuseki-main#fuseki-docker)
 - [As an embedded SPARQL server](fuseki-embedded.html)
 - [Security and data access control](fuseki-data-access-control.html)
+- [Fuseki Server Protocol (REST API)](fuseki-server-protocol.html)

Review comment:
   This only applies to fuseki-webapp but putting it here implies it 
applies to both forms.
   
   See 1d3953a1 - it has been incomplete for a long while.
   
   ```
   [Server Admin Protocol](fuseki-server-protocol.html)
   ```
   
   It may not be the way to have admin for fuseki-main, and quite possibly that 
would only have some of the functionality. To create space for Fuseki to 
evolve, at least only put in the fuseki-webapp section.
   
   





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

[GitHub] [jena-site] afs merged pull request #27: Update streaming-io.md

[GitBox]

afs merged pull request #27:
URL: https://github.com/apache/jena-site/pull/27


   



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

[GitHub] [jena-site] rvesse opened a new pull request #28: Add link to Fuseki Server Protocol page

[GitBox]

rvesse opened a new pull request #28:
URL: https://github.com/apache/jena-site/pull/28


   Make the Fuseki Server Protocol page visible from the Fuseki 2 landing page



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

[GitHub] [jena-site] afs commented on a change in pull request #27: Update streaming-io.md

[GitBox]

afs commented on a change in pull request #27:
URL: https://github.com/apache/jena-site/pull/27#discussion_r506567700



##
File path: source/documentation/io/streaming-io.md
##
@@ -87,7 +87,7 @@ an `StreamRDF` backed by a stream-based writer
 which can be done as:
 
 StreamRDF writer = StreamRDFWriter.getWriterStream(output, lang) ;
-StreamOps.graphToStream(writer, model.getGraph()) ;
+StreamRDFOps.graphToStream(writer, model.getGraph()) ;

Review comment:
   `StreamRDFOps` is the right name so when this is merged, it'll be right.





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

[GitHub] [jena-site] kinow commented on a change in pull request #27: Update streaming-io.md

[GitBox]

kinow commented on a change in pull request #27:
URL: https://github.com/apache/jena-site/pull/27#discussion_r506096005



##
File path: source/documentation/io/streaming-io.md
##
@@ -87,7 +87,7 @@ an `StreamRDF` backed by a stream-based writer
 which can be done as:
 
 StreamRDF writer = StreamRDFWriter.getWriterStream(output, lang) ;
-StreamOps.graphToStream(writer, model.getGraph()) ;
+StreamRDFOps.graphToStream(writer, model.getGraph()) ;

Review comment:
   @afs this line is not in #22 , but the other line is in #22. 





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

[GitHub] [jena-site] LorenzBuehmann opened a new pull request #27: Update streaming-io.md

[GitBox]

LorenzBuehmann opened a new pull request #27:
URL: https://github.com/apache/jena-site/pull/27


   Update necessary due to renaming of StreamOps to StreamRDFOps



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

[GitHub] [jena-site] kinow closed pull request #26: new file

[GitBox]

kinow closed pull request #26:
URL: https://github.com/apache/jena-site/pull/26


   



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

[GitHub] [jena-site] jmalak27032000 opened a new pull request #26: new file

[GitBox]

jmalak27032000 opened a new pull request #26:
URL: https://github.com/apache/jena-site/pull/26


   



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

[GitHub] [jena-site] kinow merged pull request #25: Fix links in Permission examples page

[GitBox]

kinow merged pull request #25:
URL: https://github.com/apache/jena-site/pull/25


   



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

[GitHub] [jena-site] afs commented on pull request #22: Turtle writer options

[GitBox]

afs commented on pull request #22:
URL: https://github.com/apache/jena-site/pull/22#issuecomment-705521367


   This is for 3.17.0 - I'll note when things need to wait for a release next 
time.
   
   https://issues.apache.org/jira/browse/JENA-1968



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

[GitHub] [jena-site] afs merged pull request #24: Fix YAML title

[GitBox]

afs merged pull request #24:
URL: https://github.com/apache/jena-site/pull/24


   



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

[GitHub] [jena-site] afs commented on pull request #24: Fix YAML title

[GitBox]

afs commented on pull request #24:
URL: https://github.com/apache/jena-site/pull/24#issuecomment-706026146


   Thanks!



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

[GitHub] [jena-site] kinow commented on pull request #22: Turtle writer options

[GitBox]

kinow commented on pull request #22:
URL: https://github.com/apache/jena-site/pull/22#issuecomment-705466786


   Are we waiting for a PR in Jena before merging this one @afs ?



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

[GitHub] [jena-site] afs commented on pull request #24: Fix YAML title

[GitBox]

afs commented on pull request #24:
URL: https://github.com/apache/jena-site/pull/24#issuecomment-706026146


   Thanks!



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

[GitHub] [jena-site] afs merged pull request #24: Fix YAML title

[GitBox]

afs merged pull request #24:
URL: https://github.com/apache/jena-site/pull/24


   



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

[GitHub] [jena-site] afs commented on pull request #22: Turtle writer options

[GitBox]

afs commented on pull request #22:
URL: https://github.com/apache/jena-site/pull/22#issuecomment-705521367


   This is for 3.17.0 - I'll note when things need to wait for a release next 
time.
   
   https://issues.apache.org/jira/browse/JENA-1968



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

[GitHub] [jena-site] kinow commented on pull request #22: Turtle writer options

[GitBox]

kinow commented on pull request #22:
URL: https://github.com/apache/jena-site/pull/22#issuecomment-705466786


   Are we waiting for a PR in Jena before merging this one @afs ?



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

[GitHub] [jena-site] kinow opened a new pull request #25: Fix links in Permission examples page

[GitBox]

kinow opened a new pull request #25:
URL: https://github.com/apache/jena-site/pull/25


   For markdown, `` creates an automatic-link. I replaced the `[link]` 
occurrences by this format.
   
   Also changed the link to commons-collections. Happy to update the PR if 
necessary :+1: wasn't sure what would be the correct values for these links…



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

[GitHub] [jena-site] kinow opened a new pull request #24: Fix YAML title

[GitBox]

kinow opened a new pull request #24:
URL: https://github.com/apache/jena-site/pull/24


   Tried building the site with `hugo` and got:
   
   ```
   Error: Error building site: 
"/home/kinow/Development/java/jena/jena-site/source/documentation/fuseki2/fuseki-docker.md:2:1":
 failed to unmarshal YAML: yaml: mapping values are not allowed in this context
   
   ```
   
   Another file in the same directory has a title similar with the "colon" 
character, but wrapped in quotes. So I just used the same approach in the files 
failing, until I got:
   
   ```bash
   $ hugo
   
  | EN   
   ---+--
 Pages| 233  
 Paginator pages  |   0  
 Non-page files   |   0  
 Static files | 135  
 Processed images |   0  
 Aliases  |   0  
 Sitemaps |   1  
 Cleaned  |   0 
   ```



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

[GitHub] [jena-site] afs merged pull request #23: Fuseki doc updates

[GitBox]

afs merged pull request #23:
URL: https://github.com/apache/jena-site/pull/23


   



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

[GitHub] [jena-site] afs merged pull request #23: Fuseki doc updates

[GitBox]

afs merged pull request #23:
URL: https://github.com/apache/jena-site/pull/23


   



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

[GitHub] [jena-site] afs commented on a change in pull request #22: Turtle writer options

[GitBox]

afs commented on a change in pull request #22:
URL: https://github.com/apache/jena-site/pull/22#discussion_r491679653



##
File path: source/documentation/io/rdf-output.md
##
@@ -240,7 +241,58 @@ but always writes one complete triple on one line (no use 
of `;`).
 | TURTLE_FLAT |
 | TRIG_FLAT   |
 
-### N-Triples and N-Quads
+### Turtle and Trig format options {#opt-turtle-trig}
+
+Some context settings affect the output of Turtle and TriG writers. Unless
+otherwise noted, the settign applies to both Turtle and TriG.
+
+| Context setting | Cmd line | Values |
+|-|--|--|
+| RIOT.symTurtleDirectiveStyle | "ttl:directiveStyle" | "sparql", "rdf11", 
"at", "n3" |
+| RIOT.symTurtleOmitBase   | "ttl:omitBase"   | "true", "false" |
+
+ 

Review comment:
   Somewhat crude really! But to tweak the CSS, and then have it ripple out 
across the site is a somewhat bigger task.





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

[GitHub] [jena-site] afs commented on a change in pull request #23: Fuseki doc updates

[GitBox]

afs commented on a change in pull request #23:
URL: https://github.com/apache/jena-site/pull/23#discussion_r491888081



##
File path: source/documentation/fuseki2/fuseki-webapp.md
##
@@ -1,48 +1,71 @@
 ---
-title: Running Fuseki
+title: Running Fuseki with UI
 ---
 
-Fuseki can be run in a number of ways:
+Fuseki/UI can be run in a number of ways:
 
 * [As a standalone server](#fuseki-standalone-server)
 * [As a service](#fuseki-service) run by the operation system, for example, 
started when the machine
 * [As a Web Application](#fuseki-web-application) inside a container such as 
Apache Tomcat or Jetty
 boots.
-* [As a configurable SPARQL server](#fuseki-main)
-* [As a deployment and development standalone server](#fuseki-server)
+
+Fuseki is also packaged as a plain server ["Fuseki Main"](fuseki-main.html)
+with no UI for use as a configurable SPARQL server, for [building as a Docker
+container](fuseki-docker.html), and as a deployment and development standalone
+server.
+
+Both packaging used the same configuration file format, and in standalone 
server
+mode, the same command line arguments.
 
 See "[Fuseki Configuration](fuseki-configuration.html)" for information on
-how to provide datasets and configure services.
+how to provide datasets and configure services usoing the configuration file.
 
 ## Fuseki as a Standalone Server {#fuseki-standalone-server}
 
 This is running Fuseki from the command line.
 
-fuseki-server [--mem | --loc=DIR] [[--update] /NAME]
-
-fuseki-server --config=CONFIG
+To publish at http://host:3030/NAME:
 
 where `/NAME` is the dataset publishing name at this server in URI space.
 
+TDB1 database:
+
+fuseki-server [--loc=DIR] [[--update] /NAME]
+
 The argument `--tdb2` puts the command line handling into "TDB2 mode".
 A dataset created with `--loc` is a TDB2 dataset.
+TDB2 database:
+
+fuseki-server --tdb2 [--loc=DIR] [[--update] /NAME]
+
+In-memory, non-peristent database (always updatable):
+
+fuseki-server --mem /NAME
+
+Load a file at start and provide it read-only:
+
+fuseki-server --file=MyData.ttl /NAME
+
+where "MyData.ttl" can be any RDF format, both triples or quads. 
+
+Administrative functions are only avilable from "localhost".

Review comment:
   Shiro!

##
File path: source/documentation/fuseki2/fuseki-config-endpoint.md
##
@@ -146,13 +173,15 @@ A GSP operation has `?default` or `?graph=`.
 Quads operations have no query string and a have a `Content-Type` for a data in
 a RDF triples or quads syntax.
 
+Quads operations only apply to requests sen tot he dataset URL.

Review comment:
   (The statement isn't actually correct! I just tested it and quads work 
on a named endpoint.)

##
File path: source/documentation/fuseki2/fuseki-data-services.md
##
@@ -17,7 +17,7 @@ update
 GSP including direct naming for GSP
 
 in addition:
-
+fuse

Review comment:
   "fuseki-data-services" is linked to the documentation and it looks like 
it has largely been overtaken. The bit about active/offline isn't accurate. 
I'll delete "fuseki-data-services".
   

##
File path: source/documentation/fuseki2/fuseki-config-endpoint.md
##
@@ -121,6 +93,61 @@ without a configuration file is:
 | `fuseki:upload` | HTML form file upload |
 | `fuseki:no-op`  | An operation that causes a 400 or 404 error |
 
+Custom extensions can be added (see [Programmatic 
configuration](fuseki-main.html#build) of the Fuseki server). To be able to 
uniquely identify the operation, these are usually 
+
+fuseki:endpoint [ 
+fuseki:operation fuseki:shacl ;
+fuseki:name  "shacl" ;
+] ;
+
+See the section ["Integration with Apache Jena 
Fuseki"](https://jena.apache.org/documentation/shacl/#integration-with-apache-jena-fuseki)
 for details of the SHACL support. While this operation is part of the standard 
Fuseki distribution, this operation is added during system initialization, 
using the custom operation support.

Review comment:
   Good point. We can make it 
"/documentation/shacl/#integration-with-apache-jena-fuseki" . I like the rooted 
path because if the Fuseki docs get structured in some way, the "external" link 
will still work.





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

[GitHub] [jena-site] afs commented on pull request #23: Fuseki doc updates

[GitBox]

afs commented on pull request #23:
URL: https://github.com/apache/jena-site/pull/23#issuecomment-695997248


   Bruno - thank you very much for the review.



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

[GitHub] [jena-site] kinow commented on pull request #23: Fuseki doc updates

[GitBox]

kinow commented on pull request #23:
URL: https://github.com/apache/jena-site/pull/23#issuecomment-696054046


   > Bruno - thank you very much for the review.
   
   Don't mention it Andy. You did all the hard work here! :+1: 



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

[GitHub] [jena-site] kinow commented on a change in pull request #23: Fuseki doc updates

[GitBox]

kinow commented on a change in pull request #23:
URL: https://github.com/apache/jena-site/pull/23#discussion_r491734641



##
File path: source/documentation/fuseki2/fuseki-config-endpoint.md
##
@@ -121,6 +93,61 @@ without a configuration file is:
 | `fuseki:upload` | HTML form file upload |
 | `fuseki:no-op`  | An operation that causes a 400 or 404 error |
 
+Custom extensions can be added (see [Programmatic 
configuration](fuseki-main.html#build) of the Fuseki server). To be able to 
uniquely identify the operation, these are usually 
+
+fuseki:endpoint [ 
+fuseki:operation fuseki:shacl ;
+fuseki:name  "shacl" ;
+] ;
+
+See the section ["Integration with Apache Jena 
Fuseki"](https://jena.apache.org/documentation/shacl/#integration-with-apache-jena-fuseki)
 for details of the SHACL support. While this operation is part of the standard 
Fuseki distribution, this operation is added during system initialization, 
using the custom operation support.
+
+### Command Line Equivalents
+
+The standard set of service installed by running the server from the command 
line
+without a configuration file is for a read-only:
+
+<#service1> rdf:type fuseki:Service ;
+fuseki:name "dataset" ;
+fuseki:endpoint [ fuseki:operation fuseki:query ; ];
+fuseki:endpoint [ fuseki:operation fuseki:query ; fuseki:name "sparql" 
];
+fuseki:endpoint [ fuseki:operation fuseki:query ; fuseki:name "query" 
];
+
+fuseki:endpoint [ fuseki:operation fuseki:gsp-r ; ];
+fuseki:endpoint [ fuseki:operation fuseki:gsp-r ; fuseki:name "get" ];
+fuseki:dataset ...
+
+which supports requests such as:
+
+http://host:port/dataset?query=...
+
+http://host:port/dataset/sparql?query=...
+
+http://host:port/dataset?default
+
+http://host:port/dataset/get?default
+
+and for an updateatable dataset (command line `--mem` for an in-memory dataset;

Review comment:
   updatable? Or updateable?

##
File path: source/documentation/fuseki2/fuseki-webapp.md
##
@@ -1,48 +1,71 @@
 ---
-title: Running Fuseki
+title: Running Fuseki with UI
 ---
 
-Fuseki can be run in a number of ways:
+Fuseki/UI can be run in a number of ways:
 
 * [As a standalone server](#fuseki-standalone-server)
 * [As a service](#fuseki-service) run by the operation system, for example, 
started when the machine
 * [As a Web Application](#fuseki-web-application) inside a container such as 
Apache Tomcat or Jetty
 boots.
-* [As a configurable SPARQL server](#fuseki-main)
-* [As a deployment and development standalone server](#fuseki-server)
+
+Fuseki is also packaged as a plain server ["Fuseki Main"](fuseki-main.html)
+with no UI for use as a configurable SPARQL server, for [building as a Docker
+container](fuseki-docker.html), and as a deployment and development standalone
+server.
+
+Both packaging used the same configuration file format, and in standalone 
server
+mode, the same command line arguments.
 
 See "[Fuseki Configuration](fuseki-configuration.html)" for information on
-how to provide datasets and configure services.
+how to provide datasets and configure services usoing the configuration file.

Review comment:
   s/usoing/using

##
File path: source/documentation/fuseki2/fuseki-config-endpoint.md
##
@@ -1,17 +1,8 @@
 ---
-title: Fuseki Configuration - New Syntax
+title: Fuseki Data Service Configuration Syntax
 ---
 
-Apache Jena 3.13.0 introduces a new syntax for the facilities of a Fuseki 
service.
-
-The [previous syntax](fuseki-configuration.html) is still valid.
-
-The new syntax enables more configuration options:
-
-* setting the context on a per-endpoint basis
-* having multiple operations at the service access point, switching based on
-operation type
-* a more general structure for adding custom services
+Data service provide a number of operations on a dataset. These can be 
explicitly named endpoints or operations at he URL of the dataset.  New 
operations can be configured in; these typically have their own named endpoints.

Review comment:
   "Data service provides" or "Data services provide" I think?
   
   Also s/or operations at he/or operations at the/

##
File path: source/documentation/fuseki2/fuseki-config-endpoint.md
##
@@ -146,13 +173,15 @@ A GSP operation has `?default` or `?graph=`.
 Quads operations have no query string and a have a `Content-Type` for a data in
 a RDF triples or quads syntax.
 
+Quads operations only apply to requests sen tot he dataset URL.

Review comment:
   s/sen tot he/sent to the/

##
File path: source/documentation/fuseki2/fuseki-webapp.md
##
@@ -1,48 +1,71 @@
 ---
-title: Running Fuseki
+title: Running Fuseki with UI
 ---
 
-Fuseki can be run in a number of ways:
+Fuseki/UI can be run in a number of ways:
 
 * [As a standalone server](#fuseki-standalone-server)
 * [As a service](#fuseki-service) run by

[GitHub] [jena-site] kinow commented on a change in pull request #22: Turtle writer options

[GitBox]

kinow commented on a change in pull request #22:
URL: https://github.com/apache/jena-site/pull/22#discussion_r491678810



##
File path: source/documentation/io/rdf-output.md
##
@@ -240,7 +241,58 @@ but always writes one complete triple on one line (no use 
of `;`).
 | TURTLE_FLAT |
 | TRIG_FLAT   |
 
-### N-Triples and N-Quads
+### Turtle and Trig format options {#opt-turtle-trig}
+
+Some context settings affect the output of Turtle and TriG writers. Unless
+otherwise noted, the settign applies to both Turtle and TriG.
+
+| Context setting | Cmd line | Values |
+|-|--|--|
+| RIOT.symTurtleDirectiveStyle | "ttl:directiveStyle" | "sparql", "rdf11", 
"at", "n3" |
+| RIOT.symTurtleOmitBase   | "ttl:omitBase"   | "true", "false" |
+
+ 

Review comment:
   Ha, nice trick!

##
File path: source/documentation/io/rdf-output.md
##
@@ -240,7 +241,58 @@ but always writes one complete triple on one line (no use 
of `;`).
 | TURTLE_FLAT |
 | TRIG_FLAT   |
 
-### N-Triples and N-Quads
+### Turtle and Trig format options {#opt-turtle-trig}
+
+Some context settings affect the output of Turtle and TriG writers. Unless
+otherwise noted, the settign applies to both Turtle and TriG.

Review comment:
   s/the settign/the setting

##
File path: source/documentation/io/rdf-output.md
##
@@ -240,7 +241,58 @@ but always writes one complete triple on one line (no use 
of `;`).
 | TURTLE_FLAT |
 | TRIG_FLAT   |
 
-### N-Triples and N-Quads
+### Turtle and Trig format options {#opt-turtle-trig}
+
+Some context settings affect the output of Turtle and TriG writers. Unless
+otherwise noted, the settign applies to both Turtle and TriG.
+
+| Context setting | Cmd line | Values |
+|-|--|--|
+| RIOT.symTurtleDirectiveStyle | "ttl:directiveStyle" | "sparql", "rdf11", 
"at", "n3" |
+| RIOT.symTurtleOmitBase   | "ttl:omitBase"   | "true", "false" |
+
+ 
+
+| Directive Style | Effect |
+|--|---|
+| "sparql", "rdf11"| Use `PREFIX` and `BASE` in output.   |
+| "at", "n3"   | Use `@prefix` and `@base` in output. |
+| unset| Use `@prefix` and `@base` in output. |
+
+ 
+
+ Format Option Usage
+
+# _Setting directive style_
+```
+riot --set ttl:directiveStyle=sparql --pretty Turtle file1.rdf file2.nt ...
+```
+and in code:
+```
+  RDFWriter.create()
+ .set(RIOT.symTurtleDirectiveStyle, "sparql")
+ .lang(Lang.TTL)
+ .source(model)
+ .output(System.out);
+```
+# _Base URI_
+
+Output can be written with relative URIs and no base. Note: such output is not
+portable; it's meaning depends on the base URI at the time of reading.

Review comment:
   s/it's/its





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

[GitHub] [jena-site] kinow commented on pull request #23: Fuseki doc updates

[GitBox]

kinow commented on pull request #23:
URL: https://github.com/apache/jena-site/pull/23#issuecomment-696054046


   > Bruno - thank you very much for the review.
   
   Don't mention it Andy. You did all the hard work here! :+1: 



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

[GitHub] [jena-site] afs commented on pull request #23: Fuseki doc updates

[GitBox]

afs commented on pull request #23:
URL: https://github.com/apache/jena-site/pull/23#issuecomment-695997248


   Bruno - thank you very much for the review.



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

[GitHub] [jena-site] afs commented on a change in pull request #23: Fuseki doc updates

[GitBox]

afs commented on a change in pull request #23:
URL: https://github.com/apache/jena-site/pull/23#discussion_r491895603



##
File path: source/documentation/fuseki2/fuseki-config-endpoint.md
##
@@ -121,6 +93,61 @@ without a configuration file is:
 | `fuseki:upload` | HTML form file upload |
 | `fuseki:no-op`  | An operation that causes a 400 or 404 error |
 
+Custom extensions can be added (see [Programmatic 
configuration](fuseki-main.html#build) of the Fuseki server). To be able to 
uniquely identify the operation, these are usually 
+
+fuseki:endpoint [ 
+fuseki:operation fuseki:shacl ;
+fuseki:name  "shacl" ;
+] ;
+
+See the section ["Integration with Apache Jena 
Fuseki"](https://jena.apache.org/documentation/shacl/#integration-with-apache-jena-fuseki)
 for details of the SHACL support. While this operation is part of the standard 
Fuseki distribution, this operation is added during system initialization, 
using the custom operation support.

Review comment:
   Good point. We can make it 
"/documentation/shacl/#integration-with-apache-jena-fuseki" . I like the rooted 
path because if the Fuseki docs get structured in some way, the "external" link 
will still work.





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

[GitHub] [jena-site] afs commented on a change in pull request #23: Fuseki doc updates

[GitBox]

afs commented on a change in pull request #23:
URL: https://github.com/apache/jena-site/pull/23#discussion_r491895432



##
File path: source/documentation/fuseki2/fuseki-data-services.md
##
@@ -17,7 +17,7 @@ update
 GSP including direct naming for GSP
 
 in addition:
-
+fuse

Review comment:
   "fuseki-data-services" is linked to the documentation and it looks like 
it has largely been overtaken. The bit about active/offline isn't accurate. 
I'll delete "fuseki-data-services".
   





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

[GitHub] [jena-site] afs commented on a change in pull request #23: Fuseki doc updates

[GitBox]

afs commented on a change in pull request #23:
URL: https://github.com/apache/jena-site/pull/23#discussion_r491889145



##
File path: source/documentation/fuseki2/fuseki-config-endpoint.md
##
@@ -146,13 +173,15 @@ A GSP operation has `?default` or `?graph=`.
 Quads operations have no query string and a have a `Content-Type` for a data in
 a RDF triples or quads syntax.
 
+Quads operations only apply to requests sen tot he dataset URL.

Review comment:
   (The statement isn't actually correct! I just tested it and quads work 
on a named endpoint.)





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

[GitHub] [jena-site] afs commented on a change in pull request #23: Fuseki doc updates

[GitBox]

afs commented on a change in pull request #23:
URL: https://github.com/apache/jena-site/pull/23#discussion_r491888081



##
File path: source/documentation/fuseki2/fuseki-webapp.md
##
@@ -1,48 +1,71 @@
 ---
-title: Running Fuseki
+title: Running Fuseki with UI
 ---
 
-Fuseki can be run in a number of ways:
+Fuseki/UI can be run in a number of ways:
 
 * [As a standalone server](#fuseki-standalone-server)
 * [As a service](#fuseki-service) run by the operation system, for example, 
started when the machine
 * [As a Web Application](#fuseki-web-application) inside a container such as 
Apache Tomcat or Jetty
 boots.
-* [As a configurable SPARQL server](#fuseki-main)
-* [As a deployment and development standalone server](#fuseki-server)
+
+Fuseki is also packaged as a plain server ["Fuseki Main"](fuseki-main.html)
+with no UI for use as a configurable SPARQL server, for [building as a Docker
+container](fuseki-docker.html), and as a deployment and development standalone
+server.
+
+Both packaging used the same configuration file format, and in standalone 
server
+mode, the same command line arguments.
 
 See "[Fuseki Configuration](fuseki-configuration.html)" for information on
-how to provide datasets and configure services.
+how to provide datasets and configure services usoing the configuration file.
 
 ## Fuseki as a Standalone Server {#fuseki-standalone-server}
 
 This is running Fuseki from the command line.
 
-fuseki-server [--mem | --loc=DIR] [[--update] /NAME]
-
-fuseki-server --config=CONFIG
+To publish at http://host:3030/NAME:
 
 where `/NAME` is the dataset publishing name at this server in URI space.
 
+TDB1 database:
+
+fuseki-server [--loc=DIR] [[--update] /NAME]
+
 The argument `--tdb2` puts the command line handling into "TDB2 mode".
 A dataset created with `--loc` is a TDB2 dataset.
+TDB2 database:
+
+fuseki-server --tdb2 [--loc=DIR] [[--update] /NAME]
+
+In-memory, non-peristent database (always updatable):
+
+fuseki-server --mem /NAME
+
+Load a file at start and provide it read-only:
+
+fuseki-server --file=MyData.ttl /NAME
+
+where "MyData.ttl" can be any RDF format, both triples or quads. 
+
+Administrative functions are only avilable from "localhost".

Review comment:
   Shiro!





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

[GitHub] [jena-site] kinow commented on a change in pull request #23: Fuseki doc updates

[GitBox]

kinow commented on a change in pull request #23:
URL: https://github.com/apache/jena-site/pull/23#discussion_r491734641



##
File path: source/documentation/fuseki2/fuseki-config-endpoint.md
##
@@ -121,6 +93,61 @@ without a configuration file is:
 | `fuseki:upload` | HTML form file upload |
 | `fuseki:no-op`  | An operation that causes a 400 or 404 error |
 
+Custom extensions can be added (see [Programmatic 
configuration](fuseki-main.html#build) of the Fuseki server). To be able to 
uniquely identify the operation, these are usually 
+
+fuseki:endpoint [ 
+fuseki:operation fuseki:shacl ;
+fuseki:name  "shacl" ;
+] ;
+
+See the section ["Integration with Apache Jena 
Fuseki"](https://jena.apache.org/documentation/shacl/#integration-with-apache-jena-fuseki)
 for details of the SHACL support. While this operation is part of the standard 
Fuseki distribution, this operation is added during system initialization, 
using the custom operation support.
+
+### Command Line Equivalents
+
+The standard set of service installed by running the server from the command 
line
+without a configuration file is for a read-only:
+
+<#service1> rdf:type fuseki:Service ;
+fuseki:name "dataset" ;
+fuseki:endpoint [ fuseki:operation fuseki:query ; ];
+fuseki:endpoint [ fuseki:operation fuseki:query ; fuseki:name "sparql" 
];
+fuseki:endpoint [ fuseki:operation fuseki:query ; fuseki:name "query" 
];
+
+fuseki:endpoint [ fuseki:operation fuseki:gsp-r ; ];
+fuseki:endpoint [ fuseki:operation fuseki:gsp-r ; fuseki:name "get" ];
+fuseki:dataset ...
+
+which supports requests such as:
+
+http://host:port/dataset?query=...
+
+http://host:port/dataset/sparql?query=...
+
+http://host:port/dataset?default
+
+http://host:port/dataset/get?default
+
+and for an updateatable dataset (command line `--mem` for an in-memory dataset;

Review comment:
   updatable? Or updateable?

##
File path: source/documentation/fuseki2/fuseki-webapp.md
##
@@ -1,48 +1,71 @@
 ---
-title: Running Fuseki
+title: Running Fuseki with UI
 ---
 
-Fuseki can be run in a number of ways:
+Fuseki/UI can be run in a number of ways:
 
 * [As a standalone server](#fuseki-standalone-server)
 * [As a service](#fuseki-service) run by the operation system, for example, 
started when the machine
 * [As a Web Application](#fuseki-web-application) inside a container such as 
Apache Tomcat or Jetty
 boots.
-* [As a configurable SPARQL server](#fuseki-main)
-* [As a deployment and development standalone server](#fuseki-server)
+
+Fuseki is also packaged as a plain server ["Fuseki Main"](fuseki-main.html)
+with no UI for use as a configurable SPARQL server, for [building as a Docker
+container](fuseki-docker.html), and as a deployment and development standalone
+server.
+
+Both packaging used the same configuration file format, and in standalone 
server
+mode, the same command line arguments.
 
 See "[Fuseki Configuration](fuseki-configuration.html)" for information on
-how to provide datasets and configure services.
+how to provide datasets and configure services usoing the configuration file.

Review comment:
   s/usoing/using

##
File path: source/documentation/fuseki2/fuseki-config-endpoint.md
##
@@ -1,17 +1,8 @@
 ---
-title: Fuseki Configuration - New Syntax
+title: Fuseki Data Service Configuration Syntax
 ---
 
-Apache Jena 3.13.0 introduces a new syntax for the facilities of a Fuseki 
service.
-
-The [previous syntax](fuseki-configuration.html) is still valid.
-
-The new syntax enables more configuration options:
-
-* setting the context on a per-endpoint basis
-* having multiple operations at the service access point, switching based on
-operation type
-* a more general structure for adding custom services
+Data service provide a number of operations on a dataset. These can be 
explicitly named endpoints or operations at he URL of the dataset.  New 
operations can be configured in; these typically have their own named endpoints.

Review comment:
   "Data service provides" or "Data services provide" I think?
   
   Also s/or operations at he/or operations at the/

##
File path: source/documentation/fuseki2/fuseki-config-endpoint.md
##
@@ -146,13 +173,15 @@ A GSP operation has `?default` or `?graph=`.
 Quads operations have no query string and a have a `Content-Type` for a data in
 a RDF triples or quads syntax.
 
+Quads operations only apply to requests sen tot he dataset URL.

Review comment:
   s/sen tot he/sent to the/

##
File path: source/documentation/fuseki2/fuseki-webapp.md
##
@@ -1,48 +1,71 @@
 ---
-title: Running Fuseki
+title: Running Fuseki with UI
 ---
 
-Fuseki can be run in a number of ways:
+Fuseki/UI can be run in a number of ways:
 
 * [As a standalone server](#fuseki-standalone-server)
 * [As a service](#fuseki-service) run by

[GitHub] [jena-site] afs opened a new pull request #23: Fuseki doc updates

[GitBox]

afs opened a new pull request #23:
URL: https://github.com/apache/jena-site/pull/23


   These changes:
   * Document the new "endpoint style configuration better, and downplay the 
old "service*" style.
   * Separate out the Fuseki/main documentation from being mixed in the 
Fuseki/UI (full) documentation.



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

[GitHub] [jena-site] afs commented on a change in pull request #22: Turtle writer options

[GitBox]

afs commented on a change in pull request #22:
URL: https://github.com/apache/jena-site/pull/22#discussion_r491679653



##
File path: source/documentation/io/rdf-output.md
##
@@ -240,7 +241,58 @@ but always writes one complete triple on one line (no use 
of `;`).
 | TURTLE_FLAT |
 | TRIG_FLAT   |
 
-### N-Triples and N-Quads
+### Turtle and Trig format options {#opt-turtle-trig}
+
+Some context settings affect the output of Turtle and TriG writers. Unless
+otherwise noted, the settign applies to both Turtle and TriG.
+
+| Context setting | Cmd line | Values |
+|-|--|--|
+| RIOT.symTurtleDirectiveStyle | "ttl:directiveStyle" | "sparql", "rdf11", 
"at", "n3" |
+| RIOT.symTurtleOmitBase   | "ttl:omitBase"   | "true", "false" |
+
+ 

Review comment:
   Somewhat crude really! But to tweak the CSS, and then have it ripple out 
across the site is a somewhat bigger task.





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

[GitHub] [jena-site] kinow commented on a change in pull request #22: Turtle writer options

[GitBox]

kinow commented on a change in pull request #22:
URL: https://github.com/apache/jena-site/pull/22#discussion_r491678810



##
File path: source/documentation/io/rdf-output.md
##
@@ -240,7 +241,58 @@ but always writes one complete triple on one line (no use 
of `;`).
 | TURTLE_FLAT |
 | TRIG_FLAT   |
 
-### N-Triples and N-Quads
+### Turtle and Trig format options {#opt-turtle-trig}
+
+Some context settings affect the output of Turtle and TriG writers. Unless
+otherwise noted, the settign applies to both Turtle and TriG.
+
+| Context setting | Cmd line | Values |
+|-|--|--|
+| RIOT.symTurtleDirectiveStyle | "ttl:directiveStyle" | "sparql", "rdf11", 
"at", "n3" |
+| RIOT.symTurtleOmitBase   | "ttl:omitBase"   | "true", "false" |
+
+ 

Review comment:
   Ha, nice trick!

##
File path: source/documentation/io/rdf-output.md
##
@@ -240,7 +241,58 @@ but always writes one complete triple on one line (no use 
of `;`).
 | TURTLE_FLAT |
 | TRIG_FLAT   |
 
-### N-Triples and N-Quads
+### Turtle and Trig format options {#opt-turtle-trig}
+
+Some context settings affect the output of Turtle and TriG writers. Unless
+otherwise noted, the settign applies to both Turtle and TriG.

Review comment:
   s/the settign/the setting

##
File path: source/documentation/io/rdf-output.md
##
@@ -240,7 +241,58 @@ but always writes one complete triple on one line (no use 
of `;`).
 | TURTLE_FLAT |
 | TRIG_FLAT   |
 
-### N-Triples and N-Quads
+### Turtle and Trig format options {#opt-turtle-trig}
+
+Some context settings affect the output of Turtle and TriG writers. Unless
+otherwise noted, the settign applies to both Turtle and TriG.
+
+| Context setting | Cmd line | Values |
+|-|--|--|
+| RIOT.symTurtleDirectiveStyle | "ttl:directiveStyle" | "sparql", "rdf11", 
"at", "n3" |
+| RIOT.symTurtleOmitBase   | "ttl:omitBase"   | "true", "false" |
+
+ 
+
+| Directive Style | Effect |
+|--|---|
+| "sparql", "rdf11"| Use `PREFIX` and `BASE` in output.   |
+| "at", "n3"   | Use `@prefix` and `@base` in output. |
+| unset| Use `@prefix` and `@base` in output. |
+
+ 
+
+ Format Option Usage
+
+# _Setting directive style_
+```
+riot --set ttl:directiveStyle=sparql --pretty Turtle file1.rdf file2.nt ...
+```
+and in code:
+```
+  RDFWriter.create()
+ .set(RIOT.symTurtleDirectiveStyle, "sparql")
+ .lang(Lang.TTL)
+ .source(model)
+ .output(System.out);
+```
+# _Base URI_
+
+Output can be written with relative URIs and no base. Note: such output is not
+portable; it's meaning depends on the base URI at the time of reading.

Review comment:
   s/it's/its





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

[GitHub] [jena-site] afs opened a new pull request #22: Turtle writer options

[GitBox]

afs opened a new pull request #22:
URL: https://github.com/apache/jena-site/pull/22


   



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

[GitHub] [jena-site] rvesse merged pull request #21: Update "Getting Started With Fuseki"

[GitBox]

rvesse merged pull request #21:
URL: https://github.com/apache/jena-site/pull/21


   



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

[GitHub] [jena-site] langston-barrett opened a new pull request #21: Update "Getting Started With Fuseki"

[GitBox]

langston-barrett opened a new pull request #21:
URL: https://github.com/apache/jena-site/pull/21


   



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

[GitHub] [jena-site] afs merged pull request #20: SHACL-C writer information

[GitBox]

afs merged pull request #20:
URL: https://github.com/apache/jena-site/pull/20


   



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

[GitHub] [jena-site] kinow commented on a change in pull request #20: SHACL-C writer information

[GitBox]

kinow commented on a change in pull request #20:
URL: https://github.com/apache/jena-site/pull/20#discussion_r468972233



##
File path: source/documentation/shacl/__index.md
##
@@ -110,11 +119,22 @@ according to the shapes provided.
 
 ## SHACL Compact Syntax
 
-Jena can read 
-[SHACL Compact Syntax](https://w3c.github.io/shacl/shacl-compact-syntax/).
-The file extensions are `.shc` and `.shaclc` and there is a registered language
+Apache Jena supports
+[SHACL Compact Syntax 
(SHACL-C)](https://w3c.github.io/shacl/shacl-compact-syntax/)
+for both reading and writing.
+
+The file extensions for SHACL-C are `.shc` and `.shaclc` and there is a 
registered language
 constant `Lang.SHACLC`.
 
 RDFDataMgr.load("shapes.shc");
 
 RDFDataMgr.read("file:compactShapes", Lang.SHACLC);
+
+RDFDataMgr.write(System.out, shapesGraph, Lang.SHACLC);
+
+SHACL-C is managed by the SHACL Community Group. It does not cover all 
possible shapes.
+When outputing SHACL-C, SHACL shapes not expressible in SHACL-C will cause an

Review comment:
   outputting? (not sure now :confused: )





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

[GitHub] [jena-site] afs opened a new pull request #20: SHACL-C writer information

[GitBox]

afs opened a new pull request #20:
URL: https://github.com/apache/jena-site/pull/20


   ... and other updates.



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

[GitHub] [jena-site] kinow merged pull request #18: Fixing some typos

[GitBox]

kinow merged pull request #18:
URL: https://github.com/apache/jena-site/pull/18


   



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

[GitHub] [jena-site] kinow merged pull request #19: Fix link to Phil McCarthy article on IBM website

[GitBox]

kinow merged pull request #19:
URL: https://github.com/apache/jena-site/pull/19


   



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

[GitHub] [jena-site] crookstonmet opened a new pull request #19: Fix link to Phil McCarthy article on IBM website

[GitBox]

crookstonmet opened a new pull request #19:
URL: https://github.com/apache/jena-site/pull/19


   The original link appears to be broken -- googling found the updated link, 
which looks right.



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

[GitHub] [jena-site] kinow opened a new pull request #18: Fixing some typos

[GitBox]

kinow opened a new pull request #18:
URL: https://github.com/apache/jena-site/pull/18


   Syncing repositories, updating indexes, and re-running static analysis. 
Spell checker found a few typos, fixed in this PR :+1: 



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

[GitHub] [jena-site] rlenferink commented on pull request #17: Added Jenkinsfile to put deployment configuration in version control

[GitBox]

rlenferink commented on pull request #17:
URL: https://github.com/apache/jena-site/pull/17#issuecomment-665205857


   Happy to help 😃 



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

[GitHub] [jena-site] afs merged pull request #17: Added Jenkinsfile to put deployment configuration in version control

[GitBox]

afs merged pull request #17:
URL: https://github.com/apache/jena-site/pull/17


   



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

[GitHub] [jena-site] afs commented on pull request #17: Added Jenkinsfile to put deployment configuration in version control

[GitBox]

afs commented on pull request #17:
URL: https://github.com/apache/jena-site/pull/17#issuecomment-665205467


   Thanks Roy - I'm also taking the setup notes and putting them in a txt file 
in the jena-site repo.
   



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

[GitHub] [jena-site] kinow commented on pull request #17: Added Jenkinsfile to put deployment configuration in version control

[GitBox]

kinow commented on pull request #17:
URL: https://github.com/apache/jena-site/pull/17#issuecomment-663846558


   > > Similar discussion ongoing in Commons about using a `Jenkinsfile`, 
GitHub actions, etc.
   > > I'm a bit rusty on Jenkins, but looks good to me +1
   > 
   > While GitHub actions could be used in this case for testing whether the 
setup builds, it won't let us push changes to this repo. That is why I went 
with Jenkins, because the `git-websites` labeled nodes allow us to push to the 
`asf-site` branch (which is needed for website deployment).
   > 
   > For e.g. general development GitHub actions works pretty well (e.g. 
[@celix](https://github.com/apache/celix/tree/master/.github/workflows) we're 
using GH actions as well if you need examples :) )
   
   I don't have strong preference :-) and I think we are already using Jenkins 
for CI in Jena, so it'd make sense to have this `Jenkinsfile` in the jena-site 
repo :+1: 



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

[GitHub] [jena-site] rlenferink commented on pull request #17: Added Jenkinsfile to put deployment configuration in version control

[GitBox]

rlenferink commented on pull request #17:
URL: https://github.com/apache/jena-site/pull/17#issuecomment-663844965


   > Similar discussion ongoing in Commons about using a `Jenkinsfile`, GitHub 
actions, etc.
   > 
   > I'm a bit rusty on Jenkins, but looks good to me 👍
   
   While GitHub actions could be used in this case for testing whether the 
setup builds, it won't let us push changes to this repo. That is why I went 
with Jenkins, because the `git-websites` labeled nodes allow us to push to the 
`asf-site` branch (which is needed for website deployment).
   
   For e.g. general development GitHub actions works pretty well (e.g. 
[@celix](https://github.com/apache/celix/tree/master/.github/workflows) we're 
using GH actions as well if you need examples :) )



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

[GitHub] [jena-site] rlenferink opened a new pull request #17: Added Jenkinsfile to put deployment configuration in version control

[GitBox]

rlenferink opened a new pull request #17:
URL: https://github.com/apache/jena-site/pull/17


   This puts the job configuration for deploying the Jena website in version 
control.
   
   It is created as multi-branch pipeline so that branches other than master 
will be tested as well (whether they build using Hugo). Deployment (copy from 
master -> asf-site) only happens on the 'master' branch.
   
   ---
   
   Steps to do to correctly setup the Jenkins job:
   - Create a new multibranch pipeline (e.g. 'site').
   - Set the gitbox url -> `https://gitbox.apache.org/repos/asf/jena-site.git` 
and use the `jenkins (master pub key)` credentials.
   - In the 'Scan Multibranch Pipeline Triggers' check the 'Periodically if not 
otherwise run' checkbox and enter a sane value (e.g. 15 minutes). This is 
needed because webhooks are not delivered to ci-builds (yet).
   - Save the job and click the 'Scan Multibranch Pipeline Now' button to 
trigger an initial scan.
   
   Output should be similar to:
   - https://ci-builds.apache.org/job/Celix/job/site/
   - https://ci-builds.apache.org/job/Celix/job/site/job/master/8/console
   
   ---
   
   /cc @afs 



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

[GitHub] [jena-site] afs merged pull request #16: Align SHACLC doc

[GitBox]

afs merged pull request #16:
URL: https://github.com/apache/jena-site/pull/16


   



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

[GitHub] [jena-site] afs opened a new pull request #16: Align SHACLC doc

[GitBox]

afs opened a new pull request #16:
URL: https://github.com/apache/jena-site/pull/16


   



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

[GitHub] [jena-site] afs merged pull request #15: Download for 3.16.0

[GitBox]

afs merged pull request #15:
URL: https://github.com/apache/jena-site/pull/15


   



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

[GitHub] [jena-site] afs merged pull request #14: Updates for 3.16.0

[GitBox]

afs merged pull request #14:
URL: https://github.com/apache/jena-site/pull/14


   



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

[GitHub] [jena-site] afs opened a new pull request #15: Download for 3.16.0

[GitBox]

afs opened a new pull request #15:
URL: https://github.com/apache/jena-site/pull/15


   



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

[GitHub] [jena-site] afs commented on pull request #14: Updates for 3.16.0

[GitBox]

afs commented on pull request #14:
URL: https://github.com/apache/jena-site/pull/14#issuecomment-651246527


   @kinow - thanks for the comments!



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

[GitHub] [jena-site] rvesse merged pull request #13: [JENA-1927] Add FAQ around TDB 1 vs 2 lock file error

[GitBox]

rvesse merged pull request #13:
URL: https://github.com/apache/jena-site/pull/13


   



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

[GitHub] [jena-site] kinow commented on pull request #14: Updates for 3.16.0

[GitBox]

kinow commented on pull request #14:
URL: https://github.com/apache/jena-site/pull/14#issuecomment-650824737


   A few comments with possible typos I think, but looks good! Looking forward 
to 3.16!



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

[GitHub] [jena-site] kinow edited a comment on pull request #14: Updates for 3.16.0

[GitBox]

kinow edited a comment on pull request #14:
URL: https://github.com/apache/jena-site/pull/14#issuecomment-650824737


   A few comments with possible typos I think, but looks good! Looking forward 
to 3.16! Thanks Andy!



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

[GitHub] [jena-site] kinow commented on a change in pull request #14: Updates for 3.16.0

[GitBox]

kinow commented on a change in pull request #14:
URL: https://github.com/apache/jena-site/pull/14#discussion_r446699985



##
File path: source/documentation/io/rdf-input.md
##
@@ -113,9 +99,20 @@ add data into an existing model or dataset.
 // Read into an existing Model
 RDFDataMgr.read(model, "data2.ttl") ;
 
-### Example 3 : Using RDFParser
+### Example 2 : Common usage {#model-usage}
+
+The original Jena Model API operation for reade and write provide another way 
to the same machinery:

Review comment:
   s/reade/read and s/provide/provides ?

##
File path: source/documentation/notes/stream-manager.md
##
@@ -0,0 +1,105 @@
+---
+title: The Jena StreamManager and LocationMapper
+---
+
+The StreamManager is a utility to find and read files into models.
+There is a standard global StreamManager and applications may also
+define specific ones by constructing addition StreamManagers.

Review comment:
   s/addition/additional

##
File path: source/documentation/notes/stream-manager.md
##
@@ -0,0 +1,105 @@
+---
+title: The Jena StreamManager and LocationMapper
+---
+
+The StreamManager is a utility to find and read files into models.
+There is a standard global StreamManager and applications may also
+define specific ones by constructing addition StreamManagers.
+
+The LocationMapper provides alternative locations for RDF data.
+
+## The Stream Manager
+
+Files are named by a string, according to the conventions of their
+storage system. Typically this is by URI. There are a number of
+storage system adapters provided:
+
+- File locator (with own current directory)
+- URL locator (HTTP and FTP)
+- Class loader locator
+- Zip file locator
+
+The global stream manager has a file location, a URL locator and a
+class loader (tried in that order).
+
+A StreamManager can have an associated LocationMapper that transforms
+names before use. This means local copies of documents can be used
+transparently to the rest of the application.
+
+A StreamManager provides an "open" operation to get an `InputStream`
+to the resource.
+
+## The LocationMapper configuration file
+
+Location mapping files are RDF - they may be written in RDF/XML, Turtle
+(file suffix `.ttl`) or N-Triples (file suffix `.nt`). The default
+is RDF/XML unless one of these suffices is found.
+
+@prefix lm:  .
+
+[] lm:mapping
+   [ lm:name "file:foo.ttl" ; lm:altName "file:etc/foo.ttl" ] ,
+   [ lm:prefix "file:etc/" ;  lm:altPrefix "file:ETC/" ] ,
+   [ lm:name "file:etc/foo.ttl" ; lm:altName "file:DIR/foo.ttl" ]
+   .
+
+There are two types of location mapping: exact match renaming and
+prefix renaming. When trying to find an alternative location, a
+LocationMapper first tries for an exact match; if none is found,
+the LocationMapper will search for the longest matching prefix. If
+two are the same length, there is no guarantee on order tried;
+there is no implied order in a location mapper configuration file
+(it sets up two hash tables).
+
+In the example above, `file:etc/foo.ttl` becomes `file:DIR/foo.ttl`
+because that is an exact match. The prefix match of file:etc/ is
+ignored.
+
+All string tests are done case sensitively because the primary use
+is for URLs.
+
+Notes:
+
+- Property values are not URIs, but strings. This is a system
+  feature, not an RDF feature. Prefix mapping is name rewriting;
+  alternate names are not treated as equivalent resources in the rest
+  of Jena. While application writers are encouraged to use URIs to
+  identify files, this is not always possible.
+- There is no check to see if the alternative system resource is
+  equivalent to the original.
+
+A LocationMapper finds its configuration file by looking for the
+following files, in order:
+
+- `location-mapping.ttl`
+- `location-mapping.rdf`
+- `etc/location-mapping.rdf`
+- `etc/location-mapping.ttl`"

Review comment:
   extra " ?

##
File path: source/documentation/io/rdf-input.md
##
@@ -81,24 +80,11 @@ The following is a suggested Apache httpd .htaccess file:
 AddType  application/trix+xml.trix
 AddType  application/rdf+thrift  .trdf
 
-### Example 1 : Common usage
+### Example 1 : Using the RDFDataMgr {#using-rdfdatamgr}
 
-In this example, a file in the current directory is read as Turtle.
+`RDFDataMgr` provide operations to load, read and write models and datasets.

Review comment:
   s/provide/provides ?

##
File path: source/documentation/io/rdf-input.md
##
@@ -137,23 +134,35 @@ The parsers log to a logger called 
`org.apache.jena.riot`.  To avoid `WARN`
 messages, set this to `ERROR` in the logging system of the application.
 
 ## StreamManager and LocationMapper
-
+
+Operations to read RDF data can be redirected to local copies and to other 
URLs.
+This is useful to provide local copies of remote resources.
+
 By default, the `RDFDataMgr` uses the glob

[GitHub] [jena-site] afs opened a new pull request #14: Updates for 3.16.0

[GitBox]

afs opened a new pull request #14:
URL: https://github.com/apache/jena-site/pull/14


   



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

[GitHub] [jena-site] rvesse commented on a change in pull request #13: [JENA-1927] Add FAQ around TDB 1 vs 2 lock file error

[GitBox]

rvesse commented on a change in pull request #13:
URL: https://github.com/apache/jena-site/pull/13#discussion_r446201644



##
File path: source/documentation/tdb/faqs.md
##
@@ -181,4 +192,24 @@ RAM, trading off against requests by other applications.  
But it also means
 the database files are not properly deleted until the JVM exits.  A new
 dataset can not be created in the same location (directory on disk).
 
-The workaround is to use a different location.
\ No newline at end of file
+The workaround is to use a different location.
+
+##  What is the *Unable to check TDB lock owner, the lock file contents appear 
to be for a TDB2 database. Please try loading this location as a TDB2 database* 
error? {#tdb2-lock}
+
+As described elsewhere in this FAQ (see [Lock Exceptions](#lock-exception) 
+and [No Lock Warning](#no-lock-warning)) TDB uses a lock file to ensure that 
multiple 
+JVMs don't try to use the same TDB database simultaneously as this can lead to 
+data corruption.  However with the introduction of [TDB2](../tdb2/) there are 
now two
+versions of TDB, TDB2 also uses a lock file however it uses a slightly 
different
+format for that file.
+
+This error means that you have tried to open a [TDB2](../tdb2/) database as a 
TDB1 
+database which is not permitted.  Please adjust your usage of Jena libraries 
or command
+line tools to use TDB2 code/arguments as appropriate.
+
+For example if [Using TDB2 with Fuseki](../tdb2/tdb2_fuseki.html) you would 
need to use
+the `--tdb2` option.
+
+## My question isn't answered here? {#not-answered}
+
+If your question isn't answered here please get in touch with the project, 
please check out the [Ask](../help_and_support/index.html) page for ways to ask 
for further help.

Review comment:
   Good spot, fixed





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

[GitHub] [jena-site] kinow commented on a change in pull request #13: [JENA-1927] Add FAQ around TDB 1 vs 2 lock file error

[GitBox]

kinow commented on a change in pull request #13:
URL: https://github.com/apache/jena-site/pull/13#discussion_r446056041



##
File path: source/documentation/tdb/faqs.md
##
@@ -181,4 +192,24 @@ RAM, trading off against requests by other applications.  
But it also means
 the database files are not properly deleted until the JVM exits.  A new
 dataset can not be created in the same location (directory on disk).
 
-The workaround is to use a different location.
\ No newline at end of file
+The workaround is to use a different location.
+
+##  What is the *Unable to check TDB lock owner, the lock file contents appear 
to be for a TDB2 database. Please try loading this location as a TDB2 database* 
error? {#tdb2-lock}
+
+As described elsewhere in this FAQ (see [Lock Exceptions](#lock-exception) 
+and [No Lock Warning](#no-lock-warning)) TDB uses a lock file to ensure that 
multiple 
+JVMs don't try to use the same TDB database simultaneously as this can lead to 
+data corruption.  However with the introduction of [TDB2](../tdb2/) there are 
now two
+versions of TDB, TDB2 also uses a lock file however it uses a slightly 
different
+format for that file.
+
+This error means that you have tried to open a [TDB2](../tdb2/) database as a 
TDB1 
+database which is not permitted.  Please adjust your usage of Jena libraries 
or command
+line tools to use TDB2 code/arguments as appropriate.
+
+For example if [Using TDB2 with Fuseki](../tdb2/tdb2_fuseki.html) you would 
need to use
+the `--tdb2` option.
+
+## My question isn't answered here? {#not-answered}
+
+If your question isn't answered here please get in touch with the project, 
please check out the [Ask](../help_and_support/index.html) page for ways to ask 
for further help.

Review comment:
   `../help_and_support/index.html` needs a further `../` I think?





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

[GitHub] [jena-site] rvesse opened a new pull request #13: [JENA-1927] Add FAQ around TDB 1 vs 2 lock file error

[GitBox]

rvesse opened a new pull request #13:
URL: https://github.com/apache/jena-site/pull/13


   Adds an entry to the FAQ for the TDB lock file version mismatch 
   error to make it easier for users to understand what this error means
   and how to go about resolving it.



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

[GitHub] [jena-site] kinow merged pull request #12: Small typo fix.

[GitBox]

kinow merged pull request #12:
URL: https://github.com/apache/jena-site/pull/12


   



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

[GitHub] [jena-site] kinow commented on pull request #12: Small typo fix.

[GitBox]

kinow commented on pull request #12:
URL: https://github.com/apache/jena-site/pull/12#issuecomment-636312078


   Merged, thanks!



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

[GitHub] [jena-site] egonw opened a new pull request #12: Small typo fix.

[GitBox]

egonw opened a new pull request #12:
URL: https://github.com/apache/jena-site/pull/12


   



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

[GitHub] [jena-site] afs merged pull request #11: 3.15.0: RDF* pages ; download version

[GitBox]

afs merged pull request #11:
URL: https://github.com/apache/jena-site/pull/11


   



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

[GitHub] [jena-site] afs merged pull request #10: Updates for using log4j2

[GitBox]

afs merged pull request #10:
URL: https://github.com/apache/jena-site/pull/10


   



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

[GitHub] [jena-site] afs merged pull request #3: Versions of Lucene and ES for Jena 3.15.0

[GitBox]

afs merged pull request #3:
URL: https://github.com/apache/jena-site/pull/3


   



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

[GitHub] [jena-site] kinow commented on a change in pull request #11: 3.15.0: RDF* pages ; download version

[GitBox]

kinow commented on a change in pull request #11:
URL: https://github.com/apache/jena-site/pull/11#discussion_r426916031



##
File path: source/documentation/rdfstar/__index.md
##
@@ -0,0 +1,118 @@
+---
+title: Support of RDF*
+slug: index
+---
+[RDF\*](https://arxiv.org/abs/1406.3399) is an extension to RDF that provides
+a way for one triple to refer to another triple. Another resource about RDF\* 
is
+[Olaf Hartig's blog 
entry](https://blog.liu.se/olafhartig/2019/01/10/position-statement-rdf-star-and-sparql-star/).
+
+Example:
+
+```turtle
+<< :john foaf:name "John Smith" >> dct:source  .
+```
+
+The part `<< :john foaf:name "John Smith" >>` is a triple term and refers to 
the triple with subject `:john`, property `foaf:name` and object `"John Smith"`.
+
+Triple terms can be in the subject or object position.
+
+Jena provides support for RDF\* and the related SPARQL\*.
+
+Support for RDF* is experimentation in Jena 3.15.0 (released May 2020):
+
+* Turtle, N-Triples, TriG and N-Quads extended for Triple Terms syntax.  There 
is no output in RDF/XML.
+* SPARQL extended with Triple Term syntax for graph matching (in code, use 
`Syntax.syntaxARQ`).
+* SPARQL Result formats for JSON and XML extended to support Triple Terms in 
results.
+* Support in memory-based storage (graphs and datasets).
+* Support in the Model API.
+
+All this is active by default in Fuseki.
+
+This support is experimental and subject to change. The aim is to follow the 
definition of RDF* as well as emerging _de facto_ consensus in other 
implementations.
+
+Later releases will extend support to persistent storage in 
[TDB1](/documentation/tdb) and [TDB2](/documentation/tdb2/).
+
+## RDF\*
+
+RDF\* syntax for triple terms is added to the parsers for Turtle, N-Triples, 
TriG and N-Quads.
+
+Datasets may have graphs that have triple terms that refer to triples 
anywhere, not just in the same graph.
+
+## SPARQL\*
+
+Matches for triple terms:
+
+```sparql
+SELECT ?name { <<:john foaf:name ?name >> dct:source 
 }
+```
+
+Insert triples terms into the default graph to record the graph source.
+
+```sparql
+INSERT { <> dct:source  }
+WHERE {
+GRAPH  {
+?s ?p ?o
+}
+}
+```
+
+### SPARQL Functions related to triple terms
+
+These functions cause an expression error if passed the wrong type of 
arguments. `afn:`
+is a prefix for ``.
+
+| Function | Description |
+|  | --- |
+| `afn:subject(?t)`| Return the subject of the triple term 
 |
+| `afn:predicate(?t)`  | Return the predicate (property) of the triple 
term |
+| `afn:object(?t)` | Return the object of the triple term  
 |
+| `afn:triple(?s, ?p, ?o)` | Create a triple term from s/p/o   
 |
+| `afn:isTriple(?t)`   | Return true if the argument value is a triple 
term |
+
+### SPARQL results
+
+The syntaxes for SPARQL results from a SELECT query, 
`application/sparql-results+json`,
+`application/sparql-results+xml` are extended to include triple terms:
+
+The triple term `<< _:b0  123  >>` is encoded, in
+`application/sparql-results+json` as:
+
+```json
+{
+  "type": "triple" ,
+  "value": {
+"subject":   { "type": "bnode" , "value": "b0" } ,
+"property":  { "type": "uri" , "value": "http://example/p"; } ,
+"object":{ "type": "literal" , "datatype": 
"http://www.w3.org/2001/XMLSchema#integer"; , "value": "123" }
+}
+```
+
+and similarly in `application/sparql-results+xml`:
+
+```xml
+
+  
+b0
+  
+  
+http://example/p
+  
+  
+http://www.w3.org/2001/XMLSchema#integer";>123
+  
+
+```
+
+## Model API
+
+RDF* triple terms are treated as `Resource` to preserve the typed Model API.
+They are occur in the subject and object positions.

Review comment:
   s/They are occur/They occur/?





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

[GitHub] [jena-site] afs opened a new pull request #11: 3.15.0: RDF* pages ; download version

[GitBox]

afs opened a new pull request #11:
URL: https://github.com/apache/jena-site/pull/11


   



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

[GitHub] [jena-site] mgillis commented on pull request #9: Update fuseki configuration notes

[GitBox]

mgillis commented on pull request #9:
URL: https://github.com/apache/jena-site/pull/9#issuecomment-623687058


   @kinow Thanks for taking a look. I agree this has some overlap with the 
other section, but I wasn't sure where to put this and it took me some digging 
to find it, I wanted to record it somewhere.
   
   You're right about the typos and such -- I took the descriptions directly 
from the existing documentation in the code and didn't edit them. I can fix 
them up, just might not have time for a couple of days.



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

[GitHub] [jena-site] kinow commented on a change in pull request #9: Update fuseki configuration notes

[GitBox]

kinow commented on a change in pull request #9:
URL: https://github.com/apache/jena-site/pull/9#discussion_r419040132



##
File path: source/documentation/fuseki2/fuseki-configuration.md
##
@@ -124,9 +124,71 @@ An in-memory dataset, with data in the default graph taken 
from a local file.
 ## tdb:unionDefaultGraph true ;
  .
 
+ TDB2
+
+<#dataset> rdf:type  tdb:DatasetTDB2 ;
+tdb:location "/some/path" ;
+# this can also have unionDefaultGraph, etc.

Review comment:
   Maybe use the same example above from TDB? Copying that part with the 
timeout (quite sure it's the same syntax, there's another example in [the 
docs](https://jena.apache.org/documentation/fuseki2/fuseki-config-endpoint.html)).
   
   Same for `unionDefaultGraph`. Maybe just leave it commented out.

##
File path: source/documentation/fuseki2/fuseki-configuration.md
##
@@ -124,9 +124,71 @@ An in-memory dataset, with data in the default graph taken 
from a local file.
 ## tdb:unionDefaultGraph true ;
  .
 
+ TDB2
+
+<#dataset> rdf:type  tdb:DatasetTDB2 ;
+tdb:location "/some/path" ;
+# this can also have unionDefaultGraph, etc.
+ .
+
  Inference
 
-> @@
+An inference reasoner can be layered on top of a dataset as defined above. The 
type of reasoner must be selected carefully and should not include more 
reasoning than is required by the application, as extensive reasoning can be 
detrimental to performance.
+
+You have to build up layers of dataset, inference model, and graph.
+
+<#dataset> rdf:type ja:RDFDataset;
+ ja:defaultGraph <#inferenceModel>
+ .
+ 
+<#inferenceModel> rdf:type  ja:InfModel;
+ ja:reasoner [ ja:reasonerURL  ];

Review comment:
   Maybe make a reference somewhere in the docs that this one here, is one 
of the values from the reasoners listed in the next section?

##
File path: source/documentation/fuseki2/fuseki-configuration.md
##
@@ -124,9 +124,71 @@ An in-memory dataset, with data in the default graph taken 
from a local file.
 ## tdb:unionDefaultGraph true ;
  .
 
+ TDB2
+
+<#dataset> rdf:type  tdb:DatasetTDB2 ;
+tdb:location "/some/path" ;
+# this can also have unionDefaultGraph, etc.
+ .
+
  Inference
 
-> @@
+An inference reasoner can be layered on top of a dataset as defined above. The 
type of reasoner must be selected carefully and should not include more 
reasoning than is required by the application, as extensive reasoning can be 
detrimental to performance.
+
+You have to build up layers of dataset, inference model, and graph.
+
+<#dataset> rdf:type ja:RDFDataset;
+ ja:defaultGraph <#inferenceModel>
+ .
+ 
+<#inferenceModel> rdf:type  ja:InfModel;
+ ja:reasoner [ ja:reasonerURL  ];
+ ja:baseModel <#baseModel>;
+ .
+<#baseModel> rdf:type tdb:GraphTDB2;  # for example.
+ tdb2:location "/some/path/to/store/data/to";
+ # etc
+ .
+
+
+# Possible reasoners:
+
+* **Generic Rule Reasoner**: `http://jena.hpl.hp.com/2003/GenericRuleReasoner`
+  
+  The specific rule set and mode configuration can be set either be method 
calls to the created reasoner or though parameters in the configuration Model.

Review comment:
   "can be set either be method"... by method?
   
   "or though"... or through? (not a native speaker, so take it with a grain of 
salt)





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

[GitHub] [jena-site] mgillis opened a new pull request #9: Update fuseki configuration notes

[GitBox]

mgillis opened a new pull request #9:
URL: https://github.com/apache/jena-site/pull/9


   Add reasoner and tdb2 info



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

[GitHub] [jena-site] kinow opened a new pull request #8: Fix some typos

[GitBox]

kinow opened a new pull request #8:
URL: https://github.com/apache/jena-site/pull/8


   Not an English native speaker, so feel free to change committing directly, 
or point me if some entries need to be changed or removed please :-)
   
   Found a Fueski in a recent pull request, and added a note to run the site 
through the spell&grammar checkers to see what could be fixed during the lunch 
break.
   
   Bruno



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

[GitHub] [jena-site] kinow commented on a change in pull request #7: Replace absolute URLs with relative URLs (with absolute path)

[GitBox]

kinow commented on a change in pull request #7:
URL: https://github.com/apache/jena-site/pull/7#discussion_r417892277



##
File path: source/documentation/archive/serving_data/fuseki1.md
##
@@ -0,0 +1,450 @@
+---
+title: "Fuseki: serving RDF data over HTTP"
+---
+
+## See the [Fuseki2 documentation](/documentation/fuseki2/).
+
+
+> This page covers Fuseki v1.
+> Fuseki1 is deprecated and has been retired. 
+> The last release of Jena with this module is Jena 3.9.0.
+> See 
[jena-fuseki1/README.md](https://github.com/apache/jena/tree/master/fuseki1).
+> This is the original documentation.
+
+
+Fuseki is a SPARQL server. It provides REST-style SPARQL HTTP Update, SPARQL 
Query,
+and SPARQL Update using the SPARQL protocol over HTTP.
+
+The relevant SPARQL standards are:
+
+-   [SPARQL 1.1 Query](http://www.w3.org/TR/sparql11-query/)
+-   [SPARQL 1.1 Update](http://www.w3.org/TR/sparql11-update/)
+-   [SPARQL 1.1 Protocol](http://www.w3.org/TR/sparql11-protocol/)
+-   [SPARQL 1.1 Graph Store HTTP 
Protocol](http://www.w3.org/TR/sparql11-http-rdf-update/)
+
+## Contents
+
+-   [Download](#download-fuseki1)
+-   [Getting Started](#getting-started-with-fuseki)
+-   [Security](#security-and-access-control)
+-   [Logging](#logging)
+-   [Server URI scheme](#server-uri-scheme)
+-   [Running a Fuseki Server](#running-a-fuseki-server)
+-   [Fuseki Configuration File](#fuseki-configuration-file)
+-   [SPARQL Over HTTP](#sparql-over-http)
+-   [Use from Java](#use-from-java)
+-   [Development System](#development-system)
+
+## Download Fuseki1
+
+Binaries for Fuseki1 are available from the 
+[maven
+repositories](http://central.maven.org/maven2/org/apache/jena/jena-fuseki1/).
+
+The source code is available in the Apache Jena source release.
+
+## Getting Started With Fuseki
+
+This section provides a brief guide to getting up and running with
+a simple server installation. It uses the
+[SOH (SPARQL over HTTP)](../fuseki2/soh.html) scripts included in the
+download.
+
+1.  [Download](/download/#jena-fuseki) the latest `jena-fuseki-*-distribution` 
+2.  Unpack the downloaded file with `unzip` or `tar zxfv`
+3.  (Linux) `chmod +x fuseki-server s-*`
+4.  Run a server
+
+ ./fuseki-server --update --mem /ds
+
+The server logging goes to the console:
+
+09:25:41 INFO  Fuseki   :: Dataset: in-memory
+09:25:41 INFO  Fuseki   :: Update enabled
+09:25:41 INFO  Fuseki   :: Fuseki development
+09:25:41 INFO  Fuseki   :: Jetty 7.2.1.v2010
+09:25:41 INFO  Fuseki   :: Dataset = /ds
+09:25:41 INFO  Fuseki   :: Started 2011/01/06 09:25:41 GMT on 
port 3030
+
+## User Interface
+
+The Fuseki download includes a number of services:
+
+-   SPARQL Query, SPARQL Update, and file upload to a selected
+dataset.
+-   Link to the documentation (here).
+-   Validators for SPARQL query and update and for non-RDF/XML
+formats.
+
+For the control panel:
+
+1.  In a browser, go to `http://localhost:3030/`
+2.  Click on *Control Panel*
+3.  Select the dataset (if set up above, there is only one choice).
+
+The page offers SPARQL operations and file upload acting on the
+selected dataset.
+
+## Script Control
+
+In a new window:
+
+Load some RDF data into the default graph of the server:
+
+s-put http://localhost:3030/ds/data default books.ttl
+
+Get it back:
+
+s-get http://localhost:3030/ds/data default
+
+Query it with SPARQL using the .../query endpoint.
+
+s-query --service http://localhost:3030/ds/query 'SELECT * {?s ?p ?o}'
+
+Update it with SPARQL using the .../update endpoint.
+
+s-update --service http://localhost:3030/ds/update 'CLEAR DEFAULT'
+
+## Security and Access Control
+
+Fuseki does not currently offer security and access control itself.
+
+Authentication and control of the number of concurrent requests can
+be added using an Apache server and either blocking the Fuseki port
+to outside traffic (e.g. on Amazon's EC2) or by listening only the
+`localhost` network interface. This is especially important for update
+endpoints (SPARQL Update, SPARQL Graph Store protocol with
+PUT/POST/DELETE enabled).
+
+Data can be updated without access control if the server is started
+with the `--update` argument. If started without that argument, data
+is read-only.
+
+## Logging
+
+Fuseki uses
+[Log4J](http://logging.apache.org/log4j/)
+for logging. There are two main logging channels:
+
+1.  The general server messages: `org.apache.jena.fuseki.Server`
+2.  A channel for all request messages: `org.apache.jena.fuseki.Fuseki`
+
+The default settings are (this is an extract of a log4j properties
+file):
+
+# Fuseki
+# Server log.
+log4j.logger.org.apache.jena.fuseki.Server=INFO
+# Request log.
+log4j.logger.org.apache.jena.fuseki.Fuseki=INFO
+# Internal logs
+log4j.logger.org.apache.jena.fuseki=INFO
+
+## Server URI scheme
+
+This details the service URIs for Fuseki:
+

[GitHub] [jena-site] kinow commented on a change in pull request #7: Replace absolute URLs with relative URLs (with absolute path)

[GitBox]

kinow commented on a change in pull request #7:
URL: https://github.com/apache/jena-site/pull/7#discussion_r417892277



##
File path: source/documentation/archive/serving_data/fuseki1.md
##
@@ -0,0 +1,450 @@
+---
+title: "Fuseki: serving RDF data over HTTP"
+---
+
+## See the [Fuseki2 documentation](/documentation/fuseki2/).
+
+
+> This page covers Fuseki v1.
+> Fuseki1 is deprecated and has been retired. 
+> The last release of Jena with this module is Jena 3.9.0.
+> See 
[jena-fuseki1/README.md](https://github.com/apache/jena/tree/master/fuseki1).
+> This is the original documentation.
+
+
+Fuseki is a SPARQL server. It provides REST-style SPARQL HTTP Update, SPARQL 
Query,
+and SPARQL Update using the SPARQL protocol over HTTP.
+
+The relevant SPARQL standards are:
+
+-   [SPARQL 1.1 Query](http://www.w3.org/TR/sparql11-query/)
+-   [SPARQL 1.1 Update](http://www.w3.org/TR/sparql11-update/)
+-   [SPARQL 1.1 Protocol](http://www.w3.org/TR/sparql11-protocol/)
+-   [SPARQL 1.1 Graph Store HTTP 
Protocol](http://www.w3.org/TR/sparql11-http-rdf-update/)
+
+## Contents
+
+-   [Download](#download-fuseki1)
+-   [Getting Started](#getting-started-with-fuseki)
+-   [Security](#security-and-access-control)
+-   [Logging](#logging)
+-   [Server URI scheme](#server-uri-scheme)
+-   [Running a Fuseki Server](#running-a-fuseki-server)
+-   [Fuseki Configuration File](#fuseki-configuration-file)
+-   [SPARQL Over HTTP](#sparql-over-http)
+-   [Use from Java](#use-from-java)
+-   [Development System](#development-system)
+
+## Download Fuseki1
+
+Binaries for Fuseki1 are available from the 
+[maven
+repositories](http://central.maven.org/maven2/org/apache/jena/jena-fuseki1/).
+
+The source code is available in the Apache Jena source release.
+
+## Getting Started With Fuseki
+
+This section provides a brief guide to getting up and running with
+a simple server installation. It uses the
+[SOH (SPARQL over HTTP)](../fuseki2/soh.html) scripts included in the
+download.
+
+1.  [Download](/download/#jena-fuseki) the latest `jena-fuseki-*-distribution` 
+2.  Unpack the downloaded file with `unzip` or `tar zxfv`
+3.  (Linux) `chmod +x fuseki-server s-*`
+4.  Run a server
+
+ ./fuseki-server --update --mem /ds
+
+The server logging goes to the console:
+
+09:25:41 INFO  Fuseki   :: Dataset: in-memory
+09:25:41 INFO  Fuseki   :: Update enabled
+09:25:41 INFO  Fuseki   :: Fuseki development
+09:25:41 INFO  Fuseki   :: Jetty 7.2.1.v2010
+09:25:41 INFO  Fuseki   :: Dataset = /ds
+09:25:41 INFO  Fuseki   :: Started 2011/01/06 09:25:41 GMT on 
port 3030
+
+## User Interface
+
+The Fuseki download includes a number of services:
+
+-   SPARQL Query, SPARQL Update, and file upload to a selected
+dataset.
+-   Link to the documentation (here).
+-   Validators for SPARQL query and update and for non-RDF/XML
+formats.
+
+For the control panel:
+
+1.  In a browser, go to `http://localhost:3030/`
+2.  Click on *Control Panel*
+3.  Select the dataset (if set up above, there is only one choice).
+
+The page offers SPARQL operations and file upload acting on the
+selected dataset.
+
+## Script Control
+
+In a new window:
+
+Load some RDF data into the default graph of the server:
+
+s-put http://localhost:3030/ds/data default books.ttl
+
+Get it back:
+
+s-get http://localhost:3030/ds/data default
+
+Query it with SPARQL using the .../query endpoint.
+
+s-query --service http://localhost:3030/ds/query 'SELECT * {?s ?p ?o}'
+
+Update it with SPARQL using the .../update endpoint.
+
+s-update --service http://localhost:3030/ds/update 'CLEAR DEFAULT'
+
+## Security and Access Control
+
+Fuseki does not currently offer security and access control itself.
+
+Authentication and control of the number of concurrent requests can
+be added using an Apache server and either blocking the Fuseki port
+to outside traffic (e.g. on Amazon's EC2) or by listening only the
+`localhost` network interface. This is especially important for update
+endpoints (SPARQL Update, SPARQL Graph Store protocol with
+PUT/POST/DELETE enabled).
+
+Data can be updated without access control if the server is started
+with the `--update` argument. If started without that argument, data
+is read-only.
+
+## Logging
+
+Fuseki uses
+[Log4J](http://logging.apache.org/log4j/)
+for logging. There are two main logging channels:
+
+1.  The general server messages: `org.apache.jena.fuseki.Server`
+2.  A channel for all request messages: `org.apache.jena.fuseki.Fuseki`
+
+The default settings are (this is an extract of a log4j properties
+file):
+
+# Fuseki
+# Server log.
+log4j.logger.org.apache.jena.fuseki.Server=INFO
+# Request log.
+log4j.logger.org.apache.jena.fuseki.Fuseki=INFO
+# Internal logs
+log4j.logger.org.apache.jena.fuseki=INFO
+
+## Server URI scheme
+
+This details the service URIs for Fuseki:
+

[GitHub] [jena-site] afs commented on a change in pull request #7: Replace absolute URLs with relative URLs (with absolute path)

[GitBox]

afs commented on a change in pull request #7:
URL: https://github.com/apache/jena-site/pull/7#discussion_r417875065



##
File path: source/documentation/archive/serving_data/fuseki1.md
##
@@ -0,0 +1,450 @@
+---
+title: "Fuseki: serving RDF data over HTTP"
+---
+
+## See the [Fuseki2 documentation](/documentation/fuseki2/).
+
+
+> This page covers Fuseki v1.
+> Fuseki1 is deprecated and has been retired. 
+> The last release of Jena with this module is Jena 3.9.0.
+> See 
[jena-fuseki1/README.md](https://github.com/apache/jena/tree/master/fuseki1).
+> This is the original documentation.
+
+
+Fuseki is a SPARQL server. It provides REST-style SPARQL HTTP Update, SPARQL 
Query,
+and SPARQL Update using the SPARQL protocol over HTTP.
+
+The relevant SPARQL standards are:
+
+-   [SPARQL 1.1 Query](http://www.w3.org/TR/sparql11-query/)
+-   [SPARQL 1.1 Update](http://www.w3.org/TR/sparql11-update/)
+-   [SPARQL 1.1 Protocol](http://www.w3.org/TR/sparql11-protocol/)
+-   [SPARQL 1.1 Graph Store HTTP 
Protocol](http://www.w3.org/TR/sparql11-http-rdf-update/)
+
+## Contents
+
+-   [Download](#download-fuseki1)
+-   [Getting Started](#getting-started-with-fuseki)
+-   [Security](#security-and-access-control)
+-   [Logging](#logging)
+-   [Server URI scheme](#server-uri-scheme)
+-   [Running a Fuseki Server](#running-a-fuseki-server)
+-   [Fuseki Configuration File](#fuseki-configuration-file)
+-   [SPARQL Over HTTP](#sparql-over-http)
+-   [Use from Java](#use-from-java)
+-   [Development System](#development-system)
+
+## Download Fuseki1
+
+Binaries for Fuseki1 are available from the 
+[maven
+repositories](http://central.maven.org/maven2/org/apache/jena/jena-fuseki1/).
+
+The source code is available in the Apache Jena source release.
+
+## Getting Started With Fuseki
+
+This section provides a brief guide to getting up and running with
+a simple server installation. It uses the
+[SOH (SPARQL over HTTP)](../fuseki2/soh.html) scripts included in the
+download.
+
+1.  [Download](/download/#jena-fuseki) the latest `jena-fuseki-*-distribution` 
+2.  Unpack the downloaded file with `unzip` or `tar zxfv`
+3.  (Linux) `chmod +x fuseki-server s-*`
+4.  Run a server
+
+ ./fuseki-server --update --mem /ds
+
+The server logging goes to the console:
+
+09:25:41 INFO  Fuseki   :: Dataset: in-memory
+09:25:41 INFO  Fuseki   :: Update enabled
+09:25:41 INFO  Fuseki   :: Fuseki development
+09:25:41 INFO  Fuseki   :: Jetty 7.2.1.v2010
+09:25:41 INFO  Fuseki   :: Dataset = /ds
+09:25:41 INFO  Fuseki   :: Started 2011/01/06 09:25:41 GMT on 
port 3030
+
+## User Interface
+
+The Fuseki download includes a number of services:
+
+-   SPARQL Query, SPARQL Update, and file upload to a selected
+dataset.
+-   Link to the documentation (here).
+-   Validators for SPARQL query and update and for non-RDF/XML
+formats.
+
+For the control panel:
+
+1.  In a browser, go to `http://localhost:3030/`
+2.  Click on *Control Panel*
+3.  Select the dataset (if set up above, there is only one choice).
+
+The page offers SPARQL operations and file upload acting on the
+selected dataset.
+
+## Script Control
+
+In a new window:
+
+Load some RDF data into the default graph of the server:
+
+s-put http://localhost:3030/ds/data default books.ttl
+
+Get it back:
+
+s-get http://localhost:3030/ds/data default
+
+Query it with SPARQL using the .../query endpoint.
+
+s-query --service http://localhost:3030/ds/query 'SELECT * {?s ?p ?o}'
+
+Update it with SPARQL using the .../update endpoint.
+
+s-update --service http://localhost:3030/ds/update 'CLEAR DEFAULT'
+
+## Security and Access Control
+
+Fuseki does not currently offer security and access control itself.
+
+Authentication and control of the number of concurrent requests can
+be added using an Apache server and either blocking the Fuseki port
+to outside traffic (e.g. on Amazon's EC2) or by listening only the
+`localhost` network interface. This is especially important for update
+endpoints (SPARQL Update, SPARQL Graph Store protocol with
+PUT/POST/DELETE enabled).
+
+Data can be updated without access control if the server is started
+with the `--update` argument. If started without that argument, data
+is read-only.
+
+## Logging
+
+Fuseki uses
+[Log4J](http://logging.apache.org/log4j/)
+for logging. There are two main logging channels:
+
+1.  The general server messages: `org.apache.jena.fuseki.Server`
+2.  A channel for all request messages: `org.apache.jena.fuseki.Fuseki`
+
+The default settings are (this is an extract of a log4j properties
+file):
+
+# Fuseki
+# Server log.
+log4j.logger.org.apache.jena.fuseki.Server=INFO
+# Request log.
+log4j.logger.org.apache.jena.fuseki.Fuseki=INFO
+# Internal logs
+log4j.logger.org.apache.jena.fuseki=INFO
+
+## Server URI scheme
+
+This details the service URIs for Fuseki:
+
+-

[GitHub] [jena-site] afs commented on a change in pull request #7: Replace absolute URLs with relative URLs (with absolute path)

[GitBox]

afs commented on a change in pull request #7:
URL: https://github.com/apache/jena-site/pull/7#discussion_r417864170



##
File path: source/tutorials/sparql.md
##
@@ -9,7 +9,7 @@ language through examples but does not aim to be complete.
 If you are looking for a short introduction to SPARQL and Jena try
 [Search RDF data with 
SPARQL](http://www.ibm.com/developerworks/xml/library/j-sparql/).  If you are 
looking to execute SPARQL queries in code and already known SPARQL then you 
likely want to read the [ARQ Documentation][1] instead.
 
-[1]: https://jena.apache.org/documentation/query/index.html
+[1]: /documentation/query/index.html

Review comment:
   The only issue I have with Hugo ATM is that it does not add ".html" to a 
link like the deployed website does.





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

[GitHub] [jena-site] afs commented on pull request #3: Versions of Lucene and ES for Jena 3.15.0

[GitBox]

afs commented on pull request #3:
URL: https://github.com/apache/jena-site/pull/3#issuecomment-621708568


   I should have noted in the description that this is waiting for 3.15.0 when 
the changes to versions are in the current release.



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

[GitHub] [jena-site] kinow commented on pull request #3: Versions of Lucene and ES for Jena 3.15.0

[GitBox]

kinow commented on pull request #3:
URL: https://github.com/apache/jena-site/pull/3#issuecomment-621484193


   Safe to merge this one I think @afs ?



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

[GitHub] [jena-site] kinow commented on a change in pull request #7: Replace absolute URLs with relative URLs (with absolute path)

[GitBox]

kinow commented on a change in pull request #7:
URL: https://github.com/apache/jena-site/pull/7#discussion_r417610458



##
File path: source/tutorials/sparql.md
##
@@ -9,7 +9,7 @@ language through examples but does not aim to be complete.
 If you are looking for a short introduction to SPARQL and Jena try
 [Search RDF data with 
SPARQL](http://www.ibm.com/developerworks/xml/library/j-sparql/).  If you are 
looking to execute SPARQL queries in code and already known SPARQL then you 
likely want to read the [ARQ Documentation][1] instead.
 
-[1]: https://jena.apache.org/documentation/query/index.html
+[1]: /documentation/query/index.html

Review comment:
   Tested this one locally, and worked fine. It was also a good opportunity 
to set up `hugo` on my laptop. Assuming others will work too.

##
File path: source/documentation/tdb2/__index.md
##
@@ -3,11 +3,10 @@ title: TDB2
 slug: index
 ---
 
-TDB2 is a component of
-[Apache Jena](http://jena.apache.org) for RDF storage
-and query.  It support the full range of Jena APIs.
-TDB2 can be used as a high performance RDF store on a single machine.
-TDB2 can be used with Apache Jena Fuseki.
+TDB2 is a component of [Apache Jena](https://jena.apache.org) for RDF storage

Review comment:
   Thanks! That saves 1 hop as it won't have the HTTP redirect. While 
harmless, when running scanners like the W3C link checker or other analyzers 
that resolve links, having less redirects helps!

##
File path: source/documentation/archive/serving_data/fuseki1.md
##
@@ -0,0 +1,450 @@
+---
+title: "Fuseki: serving RDF data over HTTP"
+---
+
+## See the [Fuseki2 documentation](/documentation/fuseki2/).
+
+
+> This page covers Fuseki v1.
+> Fuseki1 is deprecated and has been retired. 
+> The last release of Jena with this module is Jena 3.9.0.
+> See 
[jena-fuseki1/README.md](https://github.com/apache/jena/tree/master/fuseki1).
+> This is the original documentation.
+
+
+Fuseki is a SPARQL server. It provides REST-style SPARQL HTTP Update, SPARQL 
Query,
+and SPARQL Update using the SPARQL protocol over HTTP.
+
+The relevant SPARQL standards are:
+
+-   [SPARQL 1.1 Query](http://www.w3.org/TR/sparql11-query/)
+-   [SPARQL 1.1 Update](http://www.w3.org/TR/sparql11-update/)
+-   [SPARQL 1.1 Protocol](http://www.w3.org/TR/sparql11-protocol/)
+-   [SPARQL 1.1 Graph Store HTTP 
Protocol](http://www.w3.org/TR/sparql11-http-rdf-update/)
+
+## Contents
+
+-   [Download](#download-fuseki1)
+-   [Getting Started](#getting-started-with-fuseki)
+-   [Security](#security-and-access-control)
+-   [Logging](#logging)
+-   [Server URI scheme](#server-uri-scheme)
+-   [Running a Fuseki Server](#running-a-fuseki-server)
+-   [Fuseki Configuration File](#fuseki-configuration-file)
+-   [SPARQL Over HTTP](#sparql-over-http)
+-   [Use from Java](#use-from-java)
+-   [Development System](#development-system)
+
+## Download Fuseki1
+
+Binaries for Fuseki1 are available from the 
+[maven
+repositories](http://central.maven.org/maven2/org/apache/jena/jena-fuseki1/).
+
+The source code is available in the Apache Jena source release.
+
+## Getting Started With Fuseki
+
+This section provides a brief guide to getting up and running with
+a simple server installation. It uses the
+[SOH (SPARQL over HTTP)](../fuseki2/soh.html) scripts included in the
+download.
+
+1.  [Download](/download/#jena-fuseki) the latest `jena-fuseki-*-distribution` 
+2.  Unpack the downloaded file with `unzip` or `tar zxfv`
+3.  (Linux) `chmod +x fuseki-server s-*`
+4.  Run a server
+
+ ./fuseki-server --update --mem /ds
+
+The server logging goes to the console:
+
+09:25:41 INFO  Fuseki   :: Dataset: in-memory
+09:25:41 INFO  Fuseki   :: Update enabled
+09:25:41 INFO  Fuseki   :: Fuseki development
+09:25:41 INFO  Fuseki   :: Jetty 7.2.1.v2010
+09:25:41 INFO  Fuseki   :: Dataset = /ds
+09:25:41 INFO  Fuseki   :: Started 2011/01/06 09:25:41 GMT on 
port 3030
+
+## User Interface
+
+The Fuseki download includes a number of services:
+
+-   SPARQL Query, SPARQL Update, and file upload to a selected
+dataset.
+-   Link to the documentation (here).
+-   Validators for SPARQL query and update and for non-RDF/XML
+formats.
+
+For the control panel:
+
+1.  In a browser, go to `http://localhost:3030/`
+2.  Click on *Control Panel*
+3.  Select the dataset (if set up above, there is only one choice).
+
+The page offers SPARQL operations and file upload acting on the
+selected dataset.
+
+## Script Control
+
+In a new window:
+
+Load some RDF data into the default graph of the server:
+
+s-put http://localhost:3030/ds/data default books.ttl
+
+Get it back:
+
+s-get http://localhost:3030/ds/data default
+
+Query it with SPARQL using the .../query endpoint.
+
+s-query --service http://localhost:3030/ds/query 'SELECT * {?s ?p ?o}'
+
+Update it with SPARQL using th

[GitHub] [jena-site] afs opened a new pull request #7: Replace absolute URLs with relative URLs (with absolute path)

[GitBox]

afs opened a new pull request #7:
URL: https://github.com/apache/jena-site/pull/7


   and then they work with `hugo server` on `localhost:1414`.
   
   Left "/documentation" in URLs because it was a lot more change to what the 
position-relative URL would be.



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

[GitHub] [jena-site] afs commented on a change in pull request #6: Inference fixes

[GitBox]

afs commented on a change in pull request #6:
URL: https://github.com/apache/jena-site/pull/6#discussion_r416893615



##
File path: static/.htaccess
##
@@ -7,3 +7,8 @@ AddType  application/owl+xml .owl
 
 AddType  text/trig   .trig
 AddType  application/n-quads .nq
+
+RewriteEngine on
+# Switch http to https
+RewriteCond %{HTTPS} !=on
+RewriteRule ^(.*)$ https://%{SERVER_NAME}%{REQUEST_URI} [L,R]

Review comment:
   Fixed!





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

[GitHub] [jena-site] kinow commented on a change in pull request #6: Inference fixes

[GitBox]

kinow commented on a change in pull request #6:
URL: https://github.com/apache/jena-site/pull/6#discussion_r416889868



##
File path: static/.htaccess
##
@@ -7,3 +7,8 @@ AddType  application/owl+xml .owl
 
 AddType  text/trig   .trig
 AddType  application/n-quads .nq
+
+RewriteEngine on
+# Switch http to https
+RewriteCond %{HTTPS} !=on
+RewriteRule ^(.*)$ https://%{SERVER_NAME}%{REQUEST_URI} [L,R]

Review comment:
   nit pick :grimacing: no newline at end of file reported here





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

[GitHub] [jena-site] afs opened a new pull request #6: Inference fixes

[GitBox]

afs opened a new pull request #6:
URL: https://github.com/apache/jena-site/pull/6


   and `.htaccess` for http to https switching.



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

[GitHub] [jena-site] afs merged pull request #5: improve grammer of streaming-io docs

[GitBox]

afs merged pull request #5: improve grammer of streaming-io docs
URL: https://github.com/apache/jena-site/pull/5
 
 
   


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-site] afs commented on issue #5: improve grammer of streaming-io docs

[GitBox]

afs commented on issue #5: improve grammer of streaming-io docs
URL: https://github.com/apache/jena-site/pull/5#issuecomment-612803307
 
 
   Thanks!


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-site] thadguidry opened a new pull request #5: improve grammer of streaming-io docs

[GitBox]

thadguidry opened a new pull request #5: improve grammer of streaming-io docs
URL: https://github.com/apache/jena-site/pull/5
 
 
   


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-site] afs merged pull request #4: Create .asf.yaml

[GitBox]

afs merged pull request #4: Create .asf.yaml
URL: https://github.com/apache/jena-site/pull/4
 
 
   


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-site] rlenferink opened a new pull request #4: Create .asf.yaml

[GitBox]

rlenferink opened a new pull request #4: Create .asf.yaml
URL: https://github.com/apache/jena-site/pull/4
 
 
   Added the .asf.yaml file for setting repository metadata.
   
   Info: 
https://cwiki.apache.org/confluence/display/INFRA/.asf.yaml+features+for+git+repositories#id-.asf.yamlfeaturesforgitrepositories-Repositorymetadata


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-site] rlenferink commented on issue #2: Moved breadcrumbs from javascript to be Hugo generated

[GitBox]

rlenferink commented on issue #2: Moved breadcrumbs from javascript to be Hugo 
generated
URL: https://github.com/apache/jena-site/pull/2#issuecomment-597296593
 
 
   Thankx Andy!


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-site] afs commented on issue #2: Moved breadcrumbs from javascript to be Hugo generated

[GitBox]

afs commented on issue #2: Moved breadcrumbs from javascript to be Hugo 
generated
URL: https://github.com/apache/jena-site/pull/2#issuecomment-597293754
 
 
   SCM polling is enabled.


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