[GitHub] [jena-site] kinow commented on pull request #136: Upgrade to Bootstrap 5

[GitBox]

kinow commented on PR #136:
URL: https://github.com/apache/jena-site/pull/136#issuecomment-1383146708

   Rebased.


-- 
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.

To unsubscribe, e-mail: dev-unsubscr...@jena.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [jena-site] kinow merged pull request #142: Remove Elephas Javadoc link (404)

[GitBox]

kinow merged PR #142:
URL: https://github.com/apache/jena-site/pull/142


-- 
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.

To unsubscribe, e-mail: dev-unsubscr...@jena.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [jena-site] kinow commented on pull request #136: Upgrade to Bootstrap 5

[GitBox]

kinow commented on PR #136:
URL: https://github.com/apache/jena-site/pull/136#issuecomment-1381069405

   To review: simply run `hugo server watch` to render it locally. I modified 
the RDF API to use backticks and chose a programming language for the editor to 
have different code highlight. Also tested a few other pages with the 
breadcrumb, icons (getting started), code, tables, etc.
   
   But it would still be good for others to take a look if the rest of the 
content is rendering correctly.
   
   Icons were not a drop-in replacement. So anywhere we had icons before, will 
need to be manually adjusted to the new Bootstrap icons.
   
   I also tested mobile/responsive, including the navigation menu. The only 
breaking changes, I think, were:
   
   - Moved three top menu items to the right as I think we could separate all 
into two categories
   - The Jena logo at the top menu is slightly bigger
   - The getting started used Jena's logo for each entry, but I used icons as 
in the top level menu
   
   Glad to adjust it based on any feedback :+1: 
   
   -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.

To unsubscribe, e-mail: dev-unsubscr...@jena.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [jena-site] kinow commented on pull request #136: Upgrade to Bootstrap 5

[GitBox]

kinow commented on PR #136:
URL: https://github.com/apache/jena-site/pull/136#issuecomment-1381067100

   @afs, others, I think this is ready for review :+1: It should create a 
better experience for readers, and also make it look a little closer to Fuseki 
UI (fonts, elements, etc.). I will prepare another PR after this one is merged 
to propose a change to table of contents.
   
   Some screenshots of before/after for posterity.
   
   ![Screen Shot 2023-01-12 at 23 28 
34-fullpage](https://user-images.githubusercontent.com/304786/212195372-574806c3-53a8-4b82-b204-3a93d38b20ac.png)
   ![Screen Shot 2023-01-12 at 23 29 
01-fullpage](https://user-images.githubusercontent.com/304786/212195378-c98ba9ea-8620-4f42-97c4-477364e4cf4e.png)
   ![Screen Shot 2023-01-12 at 23 29 
20-fullpage](https://user-images.githubusercontent.com/304786/212195381-775bcf4b-30ee-4011-aafc-82f4a4e47a08.png)
   
   ![Screen Shot 2023-01-12 at 23 28 
48-fullpage](https://user-images.githubusercontent.com/304786/212195420-687df207-89b9-4ea8-b8e8-3b45030828da.png)
   ![Screen Shot 2023-01-12 at 23 29 
08-fullpage](https://user-images.githubusercontent.com/304786/212195423-7a84a03e-7dfa-4ebd-919b-ce0578c194a9.png)
   ![Screen Shot 2023-01-12 at 23 29 
31-fullpage](https://user-images.githubusercontent.com/304786/212195426-3d94b13d-2c24-4ac7-a717-07c787d0607f.png)
   
   
   Cheers


-- 
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.

To unsubscribe, e-mail: dev-unsubscr...@jena.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [jena-site] afs commented on pull request #141: fix typo

[GitBox]

afs commented on PR #141:
URL: https://github.com/apache/jena-site/pull/141#issuecomment-1374940957

   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.

To unsubscribe, e-mail: dev-unsubscr...@jena.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [jena-site] afs merged pull request #141: fix typo

[GitBox]

afs merged PR #141:
URL: https://github.com/apache/jena-site/pull/141


-- 
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.

To unsubscribe, e-mail: dev-unsubscr...@jena.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [jena-site] kinow merged pull request #140: Fix typos, grammar

[GitBox]

kinow merged PR #140:
URL: https://github.com/apache/jena-site/pull/140


-- 
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.

To unsubscribe, e-mail: dev-unsubscr...@jena.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [jena-site] kinow commented on pull request #140: Fix typos, grammar

[GitBox]

kinow commented on PR #140:
URL: https://github.com/apache/jena-site/pull/140#issuecomment-1374765916

   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.

To unsubscribe, e-mail: dev-unsubscr...@jena.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [jena-site] afs merged pull request #139: Update system-initialization.md

[GitBox]

afs merged PR #139:
URL: https://github.com/apache/jena-site/pull/139


-- 
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.

To unsubscribe, e-mail: dev-unsubscr...@jena.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [jena-site] kinow commented on a diff in pull request #139: Update system-initialization.md

[GitBox]

kinow commented on code in PR #139:
URL: https://github.com/apache/jena-site/pull/139#discussion_r1064026267


##
source/documentation/notes/system-initialization.md:
##
@@ -2,54 +2,76 @@
 title: Apache Jena Initialization
 ---
 
-Jena has a simple initialization sequence that is
+Jena has an initialization sequence that is
 used to setup components available at runtime.
 
 Application code is welcome to also use this mechanism. This
-must be done with care. Java initialization can lead to
-visibility of uninitialized data.
+must be done with care. During Jena initialization, there can be 
+visibility of uninitialized data in class static members.
 
 The standard initialization sequence is  
 Core -> RIOT -> ARQ -> TDB -> other (including jena text)
 
-The sequence from core to TDB should be executed before application
-components. See below for how to control the order.
+The sequence from 0 to level 500 is the Jena platform
+initialization. Application may use the jena initialization mechanism and it is
+recommended to place initialzation code above level 500.
 
 Initialization occurs when `JenaSystem.init()` is first called.  Jena ensures 
that this
 is done when the application first uses any Jena code by using class
 initializers.
 
+Application can call `JenaSystem.init()`. 
+
 See [notes on repacking Jena code](jena-repack.html) for how to deal
-with ServiceLoader files in repacked jars.
+with `ServiceLoader` files in repacked jars.
 
 ## Initialization code
 
-Initialization code is an implementation of `JenaSubsystemLifecycle`.
-For use in the default initialization, the class must have a zero-argument 
constructor
+Initialization code is an implementation of `JenaSubsystemLifecycle` which
+itself extends `SubsystemLifecycle`.
+
+For use in the default initialization, the class must have a zero-argument
+constructor and implement:
 
+```java
 public interface JenaSubsystemLifecycle {
 public void start() ;
 public void stop() ;
 default public int level() { return  ; }
 }
+```
 
-The code also supply a level, indicating its place in the order of 
initialization.
+The code should supply a level, indicating its place in the order of 
initialization.
 The levels used by Jena are:
 
 * 0 - reserved
 * 10 - Used by jena-core
+* 15 - CLI Commands registry
 * 20 - RIOT
 * 30 - ARQ
-* 40 - TDB
-*  - other
+* 40 - Text indexing
+* 40 - TDB1
+* 42 - TDB2
+* 60 - Additional HTTP configuration
+* 60 - RDFPatch
+* 96 - SHACL
+* 96 - ShEx
+* 101 - Fuseki
+*  - Default.
+
+Levels up to 500 are considered to be "Jena system level", Application code
+should use level above 500.
+
+Fuseki initialization includes [Fuseki
+Modules](/documentation/fuseki2/fuseki-modules) which uses `SubsystemLifecycle`
+with a different Java interface.
 
 ## The Initialization Process
 
-The process followed by `JenaSystem.init()` is to obtain an instance of
-`JenaSubsystemRegistry`, ask it to `load()` initialization code, then call
-that code in an order based on declared level. The order of invocation
-of different initialization code within the same level is undefined
-and may be different from run to run.
+The process followed by `JenaSystem.init()` is to load all java `ServiceLoader`
+regsitered `JenaSubsystemLifecycle`, sort into level order, then call `init` on

Review Comment:
   s/regsitered/registered



##
source/documentation/notes/system-initialization.md:
##
@@ -2,54 +2,76 @@
 title: Apache Jena Initialization
 ---
 
-Jena has a simple initialization sequence that is
+Jena has an initialization sequence that is
 used to setup components available at runtime.
 
 Application code is welcome to also use this mechanism. This
-must be done with care. Java initialization can lead to
-visibility of uninitialized data.
+must be done with care. During Jena initialization, there can be 
+visibility of uninitialized data in class static members.
 
 The standard initialization sequence is  
 Core -> RIOT -> ARQ -> TDB -> other (including jena text)
 
-The sequence from core to TDB should be executed before application
-components. See below for how to control the order.
+The sequence from 0 to level 500 is the Jena platform
+initialization. Application may use the jena initialization mechanism and it is
+recommended to place initialzation code above level 500.

Review Comment:
   s/initialzation/initialization



-- 
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.

To unsubscribe, e-mail: dev-unsubscr...@jena.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [jena-site] kinow merged pull request #138: Fix link to AddNewReader example in RIOT docs

[GitBox]

kinow merged PR #138:
URL: https://github.com/apache/jena-site/pull/138


-- 
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.

To unsubscribe, e-mail: dev-unsubscr...@jena.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [jena-site] Ostrzyciel opened a new pull request, #138: Fix link to AddNewReader example in RIOT docs

[GitBox]

Ostrzyciel opened a new pull request, #138:
URL: https://github.com/apache/jena-site/pull/138

   The link previously led to an example about something else.


-- 
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.

To unsubscribe, e-mail: dev-unsubscr...@jena.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [jena-site] afs commented on pull request #137: fix end tag

[GitBox]

afs commented on PR #137:
URL: https://github.com/apache/jena-site/pull/137#issuecomment-1371516380

   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.

To unsubscribe, e-mail: dev-unsubscr...@jena.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [jena-site] afs merged pull request #137: fix end tag

[GitBox]

afs merged PR #137:
URL: https://github.com/apache/jena-site/pull/137


-- 
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.

To unsubscribe, e-mail: dev-unsubscr...@jena.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [jena-site] afs merged pull request #117: Improved backup docs https://github.com/apache/jena/issues/1500

[GitBox]

afs merged PR #117:
URL: https://github.com/apache/jena-site/pull/117


-- 
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.

To unsubscribe, e-mail: dev-unsubscr...@jena.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [jena-site] afs merged pull request #115: Documentation of AsyncParserBuilder

[GitBox]

afs merged PR #115:
URL: https://github.com/apache/jena-site/pull/115


-- 
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.

To unsubscribe, e-mail: dev-unsubscr...@jena.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [jena-site] afs merged pull request #118: ServiceEnhancer: Revision initiated by JENA-1517

[GitBox]

afs merged PR #118:
URL: https://github.com/apache/jena-site/pull/118


-- 
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.

To unsubscribe, e-mail: dev-unsubscr...@jena.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [jena-site] afs merged pull request #123: update jena-repack.md: add a bit more information (gradle), cleanup

[GitBox]

afs merged PR #123:
URL: https://github.com/apache/jena-site/pull/123


-- 
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.

To unsubscribe, e-mail: dev-unsubscr...@jena.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [jena-site] afs merged pull request #124: change ShexMap to ShapeMap

[GitBox]

afs merged PR #124:
URL: https://github.com/apache/jena-site/pull/124


-- 
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.

To unsubscribe, e-mail: dev-unsubscr...@jena.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [jena-site] afs closed pull request #126: Note change of StandardAnalyzer stop words at Lucene 9

[GitBox]

afs closed pull request #126: Note change of StandardAnalyzer stop words at 
Lucene 9
URL: https://github.com/apache/jena-site/pull/126


-- 
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.

To unsubscribe, e-mail: dev-unsubscr...@jena.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [jena-site] afs commented on pull request #126: Note change of StandardAnalyzer stop words at Lucene 9

[GitBox]

afs commented on PR #126:
URL: https://github.com/apache/jena-site/pull/126#issuecomment-1369597339

   Done via website update for 4.7.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.

To unsubscribe, e-mail: dev-unsubscr...@jena.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [jena-site] afs closed pull request #132: Documentation for LATERAL

[GitBox]

afs closed pull request #132: Documentation for LATERAL
URL: https://github.com/apache/jena-site/pull/132


-- 
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.

To unsubscribe, e-mail: dev-unsubscr...@jena.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [jena-site] afs commented on pull request #132: Documentation for LATERAL

[GitBox]

afs commented on PR #132:
URL: https://github.com/apache/jena-site/pull/132#issuecomment-1369596211

   Done via website update for 4.7.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.

To unsubscribe, e-mail: dev-unsubscr...@jena.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [jena-site] afs commented on pull request #131: RDF Patch documentation

[GitBox]

afs commented on PR #131:
URL: https://github.com/apache/jena-site/pull/131#issuecomment-1369593432

   Done via website update.


-- 
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.

To unsubscribe, e-mail: dev-unsubscr...@jena.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [jena-site] afs closed pull request #131: RDF Patch documentation

[GitBox]

afs closed pull request #131: RDF Patch documentation
URL: https://github.com/apache/jena-site/pull/131


-- 
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.

To unsubscribe, e-mail: dev-unsubscr...@jena.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [jena-site] afs merged pull request #133: main branch for Jena 4.7.0

[GitBox]

afs merged PR #133:
URL: https://github.com/apache/jena-site/pull/133


-- 
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.

To unsubscribe, e-mail: dev-unsubscr...@jena.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [jena-site] kinow merged pull request #135: Use backticks with a language to format the code

[GitBox]

kinow merged PR #135:
URL: https://github.com/apache/jena-site/pull/135


-- 
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.

To unsubscribe, e-mail: dev-unsubscr...@jena.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [jena-site] kinow commented on pull request #135: Use backticks with a language to format the code

[GitBox]

kinow commented on PR #135:
URL: https://github.com/apache/jena-site/pull/135#issuecomment-1366569205

   > Actually, not having to `<`/`>` so much is good reason on its own!
   
   Thanks @afs! I will slowly migrate the rest of the site to use this syntax 
then :slightly_smiling_face: 


-- 
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.

To unsubscribe, e-mail: dev-unsubscr...@jena.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [jena-site] kinow opened a new pull request, #136: Upgrade to Bootstrap 5

[GitBox]

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

   This will take a while, but I think I can slowly add more commits and 
changes here until our site is upgraded to the latest version of Bootstrap.
   
   I already liked how the text looked with the new fonts. Luckily we don't 
rely a lot on the Bootstrap styles, and our docs are quite simple. So it 
shouldn't be too hard.
   
   Once this is done, I will combine with another change I have stashed to add 
an automatic table of contents with Hugo, fixed on the sidebar (as right now I 
have to scroll up and down to navigate the contents :grimacing: ) - 
https://github.com/apache/jena-site/compare/main...kinow:sidebar-toc?expand=1
   
   Cheers
   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.

To unsubscribe, e-mail: dev-unsubscr...@jena.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [jena-site] kinow opened a new pull request, #135: Use backticks with a language to format the code

[GitBox]

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

   Shall we start using backticks to format the code now that that's supported 
in Hugo? That way we can slowly start migrating the old content, perhaps also 
reviewing it while doing so.
   
   Cheers
   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.

To unsubscribe, e-mail: dev-unsubscr...@jena.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [jena-site] kinow merged pull request #134: Update some links to https

[GitBox]

kinow merged PR #134:
URL: https://github.com/apache/jena-site/pull/134


-- 
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.

To unsubscribe, e-mail: dev-unsubscr...@jena.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [jena-site] afs commented on pull request #133: main branch for Jena 4.7.0

[GitBox]

afs commented on PR #133:
URL: https://github.com/apache/jena-site/pull/133#issuecomment-1361093466

   The hope is to move some of the jena-site update steps from being done after 
the release to being able to do them at any time during the voting period.
   


-- 
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.

To unsubscribe, e-mail: dev-unsubscr...@jena.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [jena-site] kinow commented on pull request #133: main branch for Jena 4.7.0

[GitBox]

kinow commented on PR #133:
URL: https://github.com/apache/jena-site/pull/133#issuecomment-1359950734

   I hope that doesn't complicate more the release process (mostly managed by 
you, thanks for that!)


-- 
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.

To unsubscribe, e-mail: dev-unsubscr...@jena.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [jena-site] afs opened a new pull request, #133: main branch for Jena 4.7.0

[GitBox]

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

   (trying out a process to do jena-site preparation ahead of the 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.

To unsubscribe, e-mail: dev-unsubscr...@jena.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [jena-site] afs commented on pull request #132: Documentation for LATERAL

[GitBox]

afs commented on PR #132:
URL: https://github.com/apache/jena-site/pull/132#issuecomment-1325337964

   Thank you both. Fixed done and fixed commit pushed.


-- 
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.

To unsubscribe, e-mail: dev-unsubscr...@jena.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [jena-site] afs commented on a diff in pull request #132: Documentation for LATERAL

[GitBox]

afs commented on code in PR #132:
URL: https://github.com/apache/jena-site/pull/132#discussion_r1030641717


##
source/documentation/query/lateral-join.md:
##
@@ -0,0 +1,174 @@
+---
+title: ARQ - Lateral Join
+---
+
+Lateral joins using the keyword `LATERAL` were introduced in Apache jena 4.7.0.
+
+A `LATERAL` join is like a foreach loop, looping on the results from the
+left-hand side (LHS), the pattern before the `LATERAL` keyword, and executing
+the right-hand side (RHS) query pattern once for each row, with the variables
+from the input LHS in-scope during each RHS evaluation.
+
+A regular join only executes the RHS once, and the variables from the LHS are
+used for the join condition after evaluation of the left and right
+sub-patterns.
+
+Another way to think of a lateral join is as a `flatmap`.
+
+Examples:
+```
+## Get exactly one label for each subject with type `:T`
+SELECT * {
+   ?s rdf:type :T
+   LATERAL {
+ SELECT * { ?s rdfs:label ?label } LIMIT 1
+   }
+}
+```
+
+```
+## Get zero or one labels for each subject.
+SELECT * {
+   ?s ?p ?o
+   LATERAL { OPTIONAL { SELECT * ?s rdfs:label ?label } LIMIT 1}
+   }
+}
+```
+
+ Syntax
+
+The `LATERAL` keyword which takes the graph pattern so far in the group, from
+the `{` starting of the current block, and a `{ }` block afterwards.
+
+ Evaluation
+
+[Substituting variables](https://afs.github.io/substitute.html) from the LHS 
into the RHS (with the same restrictions), then executing the pattern, gives 
the evaluation of `LATERAL`

Review Comment:
   Eventually!
   
   It is a better/fixed way to do EXISTS and LATERAL but Jena does not 
currently have a specific implementation.
   
   It's on my ToDo list.
   



##
source/documentation/query/lateral-join.md:
##
@@ -0,0 +1,174 @@
+---
+title: ARQ - Lateral Join
+---
+
+Lateral joins using the keyword `LATERAL` were introduced in Apache jena 4.7.0.
+
+A `LATERAL` join is like a foreach loop, looping on the results from the
+left-hand side (LHS), the pattern before the `LATERAL` keyword, and executing
+the right-hand side (RHS) query pattern once for each row, with the variables
+from the input LHS in-scope during each RHS evaluation.
+
+A regular join only executes the RHS once, and the variables from the LHS are
+used for the join condition after evaluation of the left and right
+sub-patterns.
+
+Another way to think of a lateral join is as a `flatmap`.
+
+Examples:
+```
+## Get exactly one label for each subject with type `:T`
+SELECT * {
+   ?s rdf:type :T
+   LATERAL {
+ SELECT * { ?s rdfs:label ?label } LIMIT 1
+   }
+}
+```
+
+```
+## Get zero or one labels for each subject.
+SELECT * {
+   ?s ?p ?o
+   LATERAL { OPTIONAL { SELECT * ?s rdfs:label ?label } LIMIT 1}
+   }
+}
+```
+
+ Syntax
+
+The `LATERAL` keyword which takes the graph pattern so far in the group, from
+the `{` starting of the current block, and a `{ }` block afterwards.
+
+ Evaluation
+
+[Substituting variables](https://afs.github.io/substitute.html) from the LHS 
into the RHS (with the same restrictions), then executing the pattern, gives 
the evaluation of `LATERAL`

Review Comment:
   Done



-- 
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.

To unsubscribe, e-mail: dev-unsubscr...@jena.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [jena-site] rvesse commented on a diff in pull request #132: Documentation for LATERAL

[GitBox]

rvesse commented on code in PR #132:
URL: https://github.com/apache/jena-site/pull/132#discussion_r1030195581


##
source/documentation/query/lateral-join.md:
##
@@ -0,0 +1,174 @@
+---
+title: ARQ - Lateral Join
+---
+
+Lateral joins using the keyword `LATERAL` were introduced in Apache jena 4.7.0.
+
+A `LATERAL` join is like a foreach loop, looping on the results from the
+left-hand side (LHS), the pattern before the `LATERAL` keyword, and executing
+the right-hand side (RHS) query pattern once for each row, with the variables
+from the input LHS in-scope during each RHS evaluation.
+
+A regular join only executes the RHS once, and the variables from the LHS are
+used for the join condition after evaluation of the left and right
+sub-patterns.
+
+Another way to think of a lateral join is as a `flatmap`.
+
+Examples:
+```
+## Get exactly one label for each subject with type `:T`
+SELECT * {
+   ?s rdf:type :T
+   LATERAL {
+ SELECT * { ?s rdfs:label ?label } LIMIT 1
+   }
+}
+```
+
+```
+## Get zero or one labels for each subject.
+SELECT * {
+   ?s ?p ?o
+   LATERAL { OPTIONAL { SELECT * ?s rdfs:label ?label } LIMIT 1}
+   }
+}
+```
+
+ Syntax
+
+The `LATERAL` keyword which takes the graph pattern so far in the group, from
+the `{` starting of the current block, and a `{ }` block afterwards.
+
+ Evaluation
+
+[Substituting variables](https://afs.github.io/substitute.html) from the LHS 
into the RHS (with the same restrictions), then executing the pattern, gives 
the evaluation of `LATERAL`
+
+ Variable assignment
+
+There needs to be a new syntax restriction: there can no variable introduced by
+`AS` (`BIND`, or sub-query) or `VALUES` in-scope at the top level of the
+`LATERAL` RHS, that is the same name as any
+[in-scope](https://www.w3.org/TR/sparql11-query/#variableScope) variable from
+the LHS.
+
+Such a variable assignment would conflict with the variable being set in
+variables of the row being joined.
+
+```
+## ** Illegal **
+SELECT * {
+   ?s ?p ?o
+   LATERAL { BIND( 123 AS ?o) }
+}
+```
+
+See [SPARQL Grammar note 
12](https://www.w3.org/TR/sparql11-query/#sparqlGrammar).
+
+In ARQ, [LET](assignment.html) would work.
+`LET` for a variable that is bound acts like a filter.
+
+ Variable Scopes
+
+In looping on the input, a lateral join makes the bindings of variables in the 
current row
+available to the right hand side pattern, settign their value from the top 
down.
+
+In SPARQL, it is possible to have variables of the same name which are not
+exposed within a sub-select. These are not lateral-joined to a variable of the
+same name from the LHS.
+
+This is not speciifc to lateral joins. In
+```
+SELECT * {
+  ?s rdf:type :T 
+  { SELECT ?label { ?s rdfs:label ?label } }
+```
+the inner `?s` can be replaced by `?z` without changing the results because the
+inner `?s` is not joined to the outer `?s` but instead is hidden by the 
`SELECT ?label`.
+```
+SELECT * {
+  ?s rdf:type :T 
+  { SELECT ?label { ?z rdfs:label ?label } }
+```
+
+The same rule applies to lateral joins.
+```
+SELECT * {
+   ?s rdf:type :T 
+   LATERAL {
+ SELECT ?label { ?s rdfs:label ?label } LIMIT 1
+   }
+}
+```
+
+The inner `?s` in the `SELECT ?label` is not the outer `?s` because the `SELECT
+?label` does not pass out `?s`. As a sub-query the `?s` could be any name 
except
+`?label` for the same results.
+
+### Notes
+
+There is a similarity to filter `NOT EXISTS`/`EXISTS` expressed as the 
not-legal `FILTER ( ASK { pattern } )` where the variables of the row being 
filtered are available to "pattern". This is similar to ab SQL [correlated 
subquery](https://en.wikipedia.org/wiki/Correlated_subquery).

Review Comment:
   ```suggestion
   There is a similarity to filter `NOT EXISTS`/`EXISTS` expressed as the 
non-legal `FILTER ( ASK { pattern } )` where the variables of the row being 
filtered are available to "pattern". This is similar to a SQL [correlated 
subquery](https://en.wikipedia.org/wiki/Correlated_subquery).
   ```



##
source/documentation/query/lateral-join.md:
##
@@ -0,0 +1,174 @@
+---
+title: ARQ - Lateral Join
+---
+
+Lateral joins using the keyword `LATERAL` were introduced in Apache jena 4.7.0.
+
+A `LATERAL` join is like a foreach loop, looping on the results from the
+left-hand side (LHS), the pattern before the `LATERAL` keyword, and executing
+the right-hand side (RHS) query pattern once for each row, with the variables
+from the input LHS in-scope during each RHS evaluation.
+
+A regular join only executes the RHS once, and the variables from the LHS are
+used for the join condition after evaluation of the left and right
+sub-patterns.
+
+Another way to think of a lateral join is as a `flatmap`.
+
+Examples:
+```
+## Get exactly one label for each subject with type `:T`
+SELECT * {
+   ?s rdf:type :T
+   LATERAL {
+ SELECT * { ?s rdfs:label ?label } LIMIT 1
+   }
+}
+```
+
+```
+## Get zero or one labels for each subject.
+SELECT * {
+   

[GitHub] [jena-site] kinow commented on a diff in pull request #132: Documentation for LATERAL

[GitBox]

kinow commented on code in PR #132:
URL: https://github.com/apache/jena-site/pull/132#discussion_r1028512381


##
source/documentation/query/lateral-join.md:
##
@@ -0,0 +1,174 @@
+---
+title: ARQ - Lateral Join
+---
+
+Lateral joins using the keyword `LATERAL` were introduced in Apache jena 4.7.0.

Review Comment:
   s/jena/Jena



##
source/documentation/query/lateral-join.md:
##
@@ -0,0 +1,174 @@
+---
+title: ARQ - Lateral Join
+---
+
+Lateral joins using the keyword `LATERAL` were introduced in Apache jena 4.7.0.
+
+A `LATERAL` join is like a foreach loop, looping on the results from the
+left-hand side (LHS), the pattern before the `LATERAL` keyword, and executing
+the right-hand side (RHS) query pattern once for each row, with the variables
+from the input LHS in-scope during each RHS evaluation.
+
+A regular join only executes the RHS once, and the variables from the LHS are
+used for the join condition after evaluation of the left and right
+sub-patterns.
+
+Another way to think of a lateral join is as a `flatmap`.
+
+Examples:
+```
+## Get exactly one label for each subject with type `:T`
+SELECT * {
+   ?s rdf:type :T
+   LATERAL {
+ SELECT * { ?s rdfs:label ?label } LIMIT 1
+   }
+}
+```
+
+```
+## Get zero or one labels for each subject.
+SELECT * {
+   ?s ?p ?o
+   LATERAL { OPTIONAL { SELECT * ?s rdfs:label ?label } LIMIT 1}
+   }
+}
+```
+
+ Syntax
+
+The `LATERAL` keyword which takes the graph pattern so far in the group, from
+the `{` starting of the current block, and a `{ }` block afterwards.
+
+ Evaluation
+
+[Substituting variables](https://afs.github.io/substitute.html) from the LHS 
into the RHS (with the same restrictions), then executing the pattern, gives 
the evaluation of `LATERAL`

Review Comment:
   Period? `.` :grimacing: 



##
source/documentation/query/lateral-join.md:
##
@@ -0,0 +1,174 @@
+---
+title: ARQ - Lateral Join
+---
+
+Lateral joins using the keyword `LATERAL` were introduced in Apache jena 4.7.0.
+
+A `LATERAL` join is like a foreach loop, looping on the results from the
+left-hand side (LHS), the pattern before the `LATERAL` keyword, and executing
+the right-hand side (RHS) query pattern once for each row, with the variables
+from the input LHS in-scope during each RHS evaluation.
+
+A regular join only executes the RHS once, and the variables from the LHS are
+used for the join condition after evaluation of the left and right
+sub-patterns.
+
+Another way to think of a lateral join is as a `flatmap`.
+
+Examples:
+```
+## Get exactly one label for each subject with type `:T`
+SELECT * {
+   ?s rdf:type :T
+   LATERAL {
+ SELECT * { ?s rdfs:label ?label } LIMIT 1
+   }
+}
+```
+
+```
+## Get zero or one labels for each subject.
+SELECT * {
+   ?s ?p ?o
+   LATERAL { OPTIONAL { SELECT * ?s rdfs:label ?label } LIMIT 1}
+   }
+}
+```
+
+ Syntax
+
+The `LATERAL` keyword which takes the graph pattern so far in the group, from
+the `{` starting of the current block, and a `{ }` block afterwards.
+
+ Evaluation
+
+[Substituting variables](https://afs.github.io/substitute.html) from the LHS 
into the RHS (with the same restrictions), then executing the pattern, gives 
the evaluation of `LATERAL`
+
+ Variable assignment
+
+There needs to be a new syntax restriction: there can no variable introduced by
+`AS` (`BIND`, or sub-query) or `VALUES` in-scope at the top level of the
+`LATERAL` RHS, that is the same name as any
+[in-scope](https://www.w3.org/TR/sparql11-query/#variableScope) variable from
+the LHS.
+
+Such a variable assignment would conflict with the variable being set in
+variables of the row being joined.
+
+```
+## ** Illegal **
+SELECT * {
+   ?s ?p ?o
+   LATERAL { BIND( 123 AS ?o) }
+}
+```
+
+See [SPARQL Grammar note 
12](https://www.w3.org/TR/sparql11-query/#sparqlGrammar).
+
+In ARQ, [LET](assignment.html) would work.
+`LET` for a variable that is bound acts like a filter.
+
+ Variable Scopes
+
+In looping on the input, a lateral join makes the bindings of variables in the 
current row
+available to the right hand side pattern, settign their value from the top 
down.
+
+In SPARQL, it is possible to have variables of the same name which are not
+exposed within a sub-select. These are not lateral-joined to a variable of the
+same name from the LHS.
+
+This is not speciifc to lateral joins. In
+```
+SELECT * {
+  ?s rdf:type :T 
+  { SELECT ?label { ?s rdfs:label ?label } }
+```
+the inner `?s` can be replaced by `?z` without changing the results because the
+inner `?s` is not joined to the outer `?s` but instead is hidden by the 
`SELECT ?label`.
+```
+SELECT * {
+  ?s rdf:type :T 
+  { SELECT ?label { ?z rdfs:label ?label } }
+```
+
+The same rule applies to lateral joins.
+```
+SELECT * {
+   ?s rdf:type :T 
+   LATERAL {
+ SELECT ?label { ?s rdfs:label ?label } LIMIT 1
+   }
+}
+```
+
+The inner `?s` in the `SELECT ?label` is not the outer `?s` because the `SELECT
+?la

[GitHub] [jena-site] afs opened a new pull request, #132: Documentation for LATERAL

[GitBox]

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

   Documentation for https://github.com/apache/jena/pull/1631


-- 
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.

To unsubscribe, e-mail: dev-unsubscr...@jena.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [jena-site] rvesse merged pull request #128: Add a Security Advisories page to the website

[GitBox]

rvesse merged PR #128:
URL: https://github.com/apache/jena-site/pull/128


-- 
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.

To unsubscribe, e-mail: dev-unsubscr...@jena.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [jena-site] rvesse commented on pull request #128: Add a Security Advisories page to the website

[GitBox]

rvesse commented on PR #128:
URL: https://github.com/apache/jena-site/pull/128#issuecomment-1321776342

   > Looks good.
   > 
   > One major suggestion - remove text about fixed on main.
   > 
   > Otherwise, minor suggestions.
   
   Think all your suggestions should now be applied


-- 
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.

To unsubscribe, e-mail: dev-unsubscr...@jena.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [jena-site] rvesse commented on a diff in pull request #128: Add a Security Advisories page to the website

[GitBox]

rvesse commented on code in PR #128:
URL: https://github.com/apache/jena-site/pull/128#discussion_r1027782365


##
source/about_jena/security-advisories.md:
##
@@ -0,0 +1,103 @@
+---
+title: Jena Security Advisories
+---
+
+# Security Issue Policy
+
+## Process
+
+Jena follows the standard [ASF Security for 
Committers](https://www.apache.org/security/committers.html) policy for
+reporting and addressing security issues.
+
+If you think you have identified a Security issue in our project please refer 
to that policy for how to report it, and
+the process that the Jena Project Management Committee (PMC) will follow in 
addressing the issue.
+
+## Single Supported Version
+
+As a project with a relatively small developer community Apache Jena only has 
the resources to maintain a single release

Review Comment:
   Suggestions applied



-- 
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.

To unsubscribe, e-mail: dev-unsubscr...@jena.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [jena-site] rvesse commented on a diff in pull request #128: Add a Security Advisories page to the website

[GitBox]

rvesse commented on code in PR #128:
URL: https://github.com/apache/jena-site/pull/128#discussion_r1027782162


##
source/about_jena/contributions.md:
##
@@ -11,7 +11,7 @@ This list is provided for information purposes only, and is 
not meant as an
 endorsement of the mentioned projects by the Jena team.
 
 If you wish your contribution to appear on this page, please raise a
-Jira issue with the details to be published.
+Jira or GitHub issue with the details to be published.

Review Comment:
   Done



-- 
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.

To unsubscribe, e-mail: dev-unsubscr...@jena.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [jena-site] rvesse commented on a diff in pull request #128: Add a Security Advisories page to the website

[GitBox]

rvesse commented on code in PR #128:
URL: https://github.com/apache/jena-site/pull/128#discussion_r1027781427


##
source/about_jena/security-advisories.md:
##
@@ -0,0 +1,103 @@
+---
+title: Jena Security Advisories
+---
+
+# Security Issue Policy
+
+## Process

Review Comment:
   Have added a brief into paragraph



-- 
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.

To unsubscribe, e-mail: dev-unsubscr...@jena.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [jena-site] afs commented on a diff in pull request #128: Add a Security Advisories page to the website

[GitBox]

afs commented on code in PR #128:
URL: https://github.com/apache/jena-site/pull/128#discussion_r1026914338


##
source/about_jena/security-advisories.md:
##
@@ -0,0 +1,103 @@
+---
+title: Jena Security Advisories
+---
+
+# Security Issue Policy
+
+## Process

Review Comment:
   The title becomes an H1 on the page. So that's two H1 then an H2.
   
   ---
   
![image](https://user-images.githubusercontent.com/101362/202807156-428892d1-c5a3-4929-95de-f38a6b3a7ed4.png)
   
   ---
   
   For appearance, drop the "# " ; adds some text to separate the H1 from the 
H2 Process.



##
source/about_jena/contributions.md:
##
@@ -11,7 +11,7 @@ This list is provided for information purposes only, and is 
not meant as an
 endorsement of the mentioned projects by the Jena team.
 
 If you wish your contribution to appear on this page, please raise a
-Jira issue with the details to be published.
+Jira or GitHub issue with the details to be published.

Review Comment:
   Slightly better to github first as it's the main channel now.



##
source/about_jena/security-advisories.md:
##
@@ -0,0 +1,103 @@
+---
+title: Jena Security Advisories
+---
+
+# Security Issue Policy
+
+## Process
+
+Jena follows the standard [ASF Security for 
Committers](https://www.apache.org/security/committers.html) policy for
+reporting and addressing security issues.
+
+If you think you have identified a Security issue in our project please refer 
to that policy for how to report it, and
+the process that the Jena Project Management Committee (PMC) will follow in 
addressing the issue.
+
+## Single Supported Version
+
+As a project with a relatively small developer community Apache Jena only has 
the resources to maintain a single release

Review Comment:
   ```suggestion
   As a project, Apache Jena only has the resources to maintain a single release
   ```
   No need to apologise!



##
source/about_jena/security-advisories.md:
##
@@ -0,0 +1,103 @@
+---
+title: Jena Security Advisories
+---
+
+# Security Issue Policy
+
+## Process
+
+Jena follows the standard [ASF Security for 
Committers](https://www.apache.org/security/committers.html) policy for
+reporting and addressing security issues.
+
+If you think you have identified a Security issue in our project please refer 
to that policy for how to report it, and
+the process that the Jena Project Management Committee (PMC) will follow in 
addressing the issue.
+
+## Single Supported Version
+
+As a project with a relatively small developer community Apache Jena only has 
the resources to maintain a single release
+version.  Therefore any accepted security issue reported will be fixed by 
developing a fix for our `main` branch.  We
+will then make a release with the fix in a timeframe appropriate to the 
severity of the issue.  

Review Comment:
   ```suggestion
   version.  Any accepted security issue will be fixed in a future release in a 
timeframe appropriate to the severity of the issue.  
   ```
   We're suppose to not highlight security code fixes until the CVE is public 
(e.g. no git commit reference). Being git, we can't have private branches built 
no need to highlight the development.



-- 
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.

To unsubscribe, e-mail: dev-unsubscr...@jena.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [jena-site] kinow commented on pull request #131: RDF Patch documentation

[GitBox]

kinow commented on PR #131:
URL: https://github.com/apache/jena-site/pull/131#issuecomment-1318746965

   > @kinow Thank you very much for the review. Should all be done now.
   
   Nice @afs! RDF Patch, LATERAL JOIN. Interesting features coming to Jena! 
Thank you!!!


-- 
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.

To unsubscribe, e-mail: dev-unsubscr...@jena.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [jena-site] afs commented on a diff in pull request #131: RDF Patch documentation

[GitBox]

afs commented on code in PR #131:
URL: https://github.com/apache/jena-site/pull/131#discussion_r1025159994


##
source/documentation/rdf-patch/__index.md:
##
@@ -0,0 +1,191 @@
+---
+title: RDF Patch
+slug: index
+---
+
+This page describes RDF Patch. An RDF Patch is a set of changes to an
+[RDF dataset](https://www.w3.org/TR/rdf11-concepts/#section-dataset).
+The change are for triples, quads and prefixes.
+
+Changes to triples involving blank nodes are handled by using their system
+identifier which uniquely identifies a blank node. Unlike RDF syntaxes, blank
+nodes are not generated afresh each time the document is parsed.
+
+## Example
+
+This example ensures certain prefixes are in the dataset and adds some
+basic triples for a new subclass of ``.
+
+```
+TX .
+PA "rdf" "http://www.w3.org/1999/02/22-rdf-syntax-ns#"; .
+PA "owl" "http://www.w3.org/2002/07/owl#"; .
+PA "rdfs" "http://www.w3.org/2000/01/rdf-schema#"; .
+A   
 .
+A   
 .
+A   
"SubClass" .
+TC .
+```
+
+## Structure
+
+The text format for an RDF Patch is N-Triples-like: it is a series of
+rows, each row ends with a `.` (DOT).  The tokens on a row are keywords,
+URIs, blank nodes, writen with their label (see below) or RDF Literals,
+in N-triples syntax.  A keyword follows the same rules as
+Turtle prefix declarations without a trailing `:`.
+
+A line has an operation code, then some number of items depending on 
+the operation.
+
+| Operation |   |
+| - | - |
+| `H`  | Header |
+| `TX``TC``TA` | Change block: transactions|
+| `PA``PD` | Change: Prefix add and delete |
+| `A``D`| Change: Add and delete triples and quads |
+
+The general structure of an RDF patch is a header (possible empty), then a
+number of change blocks.
+
+Each change block is a transaction. Transactions can be explicit recorded ('TX'
+start, `TC` commit) to include multiple transaction in one patch. They are not
+required. If not present, the patch should be applied atomically to the data.
+
+```
+header
+TX
+Quad, triple or prefix changes
+TC or TA
+```
+
+Multiple transaction blocks are allowed for multiple sets of changes in one
+patch.
+
+A binary version based on [RDF Thrift](../io/rdf-binary/) is provided.
+Parsing binary compared to text for N-triples achieves a x3-x4 increase in
+throughput.
+
+### Header
+
+The header provides for basic information about patch. It is a series of
+(key, value) pairs.
+
+It is better to put complex metadata in a separate file and link to it
+from the header, but certain information is best kept with the patch. An 
example
+used by Delta is to keep the identifer of the global version id of the dataset

Review Comment:
   Revised that 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.

To unsubscribe, e-mail: dev-unsubscr...@jena.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [jena-site] afs commented on a diff in pull request #131: RDF Patch documentation

[GitBox]

afs commented on code in PR #131:
URL: https://github.com/apache/jena-site/pull/131#discussion_r1025158734


##
source/documentation/rdf-patch/__index.md:
##
@@ -0,0 +1,191 @@
+---
+title: RDF Patch
+slug: index
+---
+
+This page describes RDF Patch. An RDF Patch is a set of changes to an
+[RDF dataset](https://www.w3.org/TR/rdf11-concepts/#section-dataset).
+The change are for triples, quads and prefixes.
+
+Changes to triples involving blank nodes are handled by using their system
+identifier which uniquely identifies a blank node. Unlike RDF syntaxes, blank
+nodes are not generated afresh each time the document is parsed.
+
+## Example
+
+This example ensures certain prefixes are in the dataset and adds some
+basic triples for a new subclass of ``.
+
+```
+TX .
+PA "rdf" "http://www.w3.org/1999/02/22-rdf-syntax-ns#"; .
+PA "owl" "http://www.w3.org/2002/07/owl#"; .
+PA "rdfs" "http://www.w3.org/2000/01/rdf-schema#"; .
+A   
 .
+A   
 .
+A   
"SubClass" .
+TC .
+```
+
+## Structure
+
+The text format for an RDF Patch is N-Triples-like: it is a series of
+rows, each row ends with a `.` (DOT).  The tokens on a row are keywords,
+URIs, blank nodes, writen with their label (see below) or RDF Literals,
+in N-triples syntax.  A keyword follows the same rules as
+Turtle prefix declarations without a trailing `:`.
+
+A line has an operation code, then some number of items depending on 
+the operation.
+
+| Operation |   |
+| - | - |
+| `H`  | Header |
+| `TX``TC``TA` | Change block: transactions|
+| `PA``PD` | Change: Prefix add and delete |
+| `A``D`| Change: Add and delete triples and quads |
+
+The general structure of an RDF patch is a header (possible empty), then a
+number of change blocks.
+
+Each change block is a transaction. Transactions can be explicit recorded ('TX'
+start, `TC` commit) to include multiple transaction in one patch. They are not
+required. If not present, the patch should be applied atomically to the data.
+
+```
+header
+TX
+Quad, triple or prefix changes
+TC or TA
+```
+
+Multiple transaction blocks are allowed for multiple sets of changes in one
+patch.
+
+A binary version based on [RDF Thrift](../io/rdf-binary/) is provided.
+Parsing binary compared to text for N-triples achieves a x3-x4 increase in
+throughput.
+
+### Header
+
+The header provides for basic information about patch. It is a series of
+(key, value) pairs.
+
+It is better to put complex metadata in a separate file and link to it
+from the header, but certain information is best kept with the patch. An 
example
+used by Delta is to keep the identifer of the global version id of the dataset

Review Comment:
   Delta is [RDF Delta](https://afs.github.io/rdf-delta)  - the whole change 
propagation, replication and high-availability system. 
   
   There should not be any mention of it in this patch 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.

To unsubscribe, e-mail: dev-unsubscr...@jena.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [jena-site] kinow commented on a diff in pull request #131: RDF Patch documentation

[GitBox]

kinow commented on code in PR #131:
URL: https://github.com/apache/jena-site/pull/131#discussion_r1024499875


##
source/documentation/rdf-patch/__index.md:
##
@@ -0,0 +1,191 @@
+---
+title: RDF Patch
+slug: index
+---
+
+This page describes RDF Patch. An RDF Patch is a set of changes to an
+[RDF dataset](https://www.w3.org/TR/rdf11-concepts/#section-dataset).
+The change are for triples, quads and prefixes.
+
+Changes to triples involving blank nodes are handled by using their system
+identifier which uniquely identifies a blank node. Unlike RDF syntaxes, blank
+nodes are not generated afresh each time the document is parsed.
+
+## Example
+
+This example ensures certain prefixes are in the dataset and adds some
+basic triples for a new subclass of ``.
+
+```
+TX .
+PA "rdf" "http://www.w3.org/1999/02/22-rdf-syntax-ns#"; .
+PA "owl" "http://www.w3.org/2002/07/owl#"; .
+PA "rdfs" "http://www.w3.org/2000/01/rdf-schema#"; .
+A   
 .
+A   
 .
+A   
"SubClass" .
+TC .
+```
+
+## Structure
+
+The text format for an RDF Patch is N-Triples-like: it is a series of
+rows, each row ends with a `.` (DOT).  The tokens on a row are keywords,
+URIs, blank nodes, writen with their label (see below) or RDF Literals,
+in N-triples syntax.  A keyword follows the same rules as
+Turtle prefix declarations without a trailing `:`.
+
+A line has an operation code, then some number of items depending on 
+the operation.
+
+| Operation |   |
+| - | - |
+| `H`  | Header |
+| `TX``TC``TA` | Change block: transactions|
+| `PA``PD` | Change: Prefix add and delete |
+| `A``D`| Change: Add and delete triples and quads |
+
+The general structure of an RDF patch is a header (possible empty), then a
+number of change blocks.
+
+Each change block is a transaction. Transactions can be explicit recorded ('TX'
+start, `TC` commit) to include multiple transaction in one patch. They are not
+required. If not present, the patch should be applied atomically to the data.
+
+```
+header
+TX
+Quad, triple or prefix changes
+TC or TA
+```
+
+Multiple transaction blocks are allowed for multiple sets of changes in one
+patch.
+
+A binary version based on [RDF Thrift](../io/rdf-binary/) is provided.
+Parsing binary compared to text for N-triples achieves a x3-x4 increase in
+throughput.
+
+### Header
+
+The header provides for basic information about patch. It is a series of
+(key, value) pairs.
+
+It is better to put complex metadata in a separate file and link to it
+from the header, but certain information is best kept with the patch. An 
example
+used by Delta is to keep the identifer of the global version id of the dataset
+so that patches are applied in the right order.
+
+A header section can be used to provide additional information. In this example
+a patch has an identifier and refers to a previous patch. This might be used to
+create a log of patches, a log being a sequnce of chnages to apply in-order.
+
+```
+H id  .
+H prev  .
+TX .
+PA "rdf" "http://www.w3.org/1999/02/22-rdf-syntax-ns#"; .
+PA "owl" "http://www.w3.org/2002/07/owl#"; .
+PA "rdfs" "http://www.w3.org/2000/01/rdf-schema#"; .
+A   
 .
+A   
 .
+A   
"SubClass" .
+TC .
+```
+
+Header format:
+```
+H word RDFTerm .
+```
+where `word` is a string in quotes, or an unquoted string (no spaces, starts 
with a letter,
+same as a prefix without the colon).
+
+The header is ended by the first non `H` line or the end of the patch.
+
+### Transactions
+
+```
+TX .
+TC .
+```
+
+These delimit a block of quad, triple and prefix changes.
+
+Abort, `TA` is provided so that changes can be streamed, not obliging the
+application to buffer change and wait to confirm the action is
+committed.
+
+Transactions should be applied atomically when a patch is applied.
+
+### Changes
+
+A change is an add or delete of a quad or a prefix.
+
+ Prefixes
+
+Prefixes do not apply to the data of the patch. They are
+changes to the data the patch is applied to.
+
+The prefix name is without the trailing colon. It can be given as a
+quoted string or unquoted string (keyword) with the same limitations as
+Turtle on the prefix name.
+
+```
+PA rdf  .
+```
+
+`PA` is adding a prefix, `PD` is deleting a prefix.
+
+ Quads and Triples
+
+Triples and quads are written like N-Quads, 3 

[GitHub] [jena-site] afs opened a new pull request, #131: RDF Patch documentation

[GitBox]

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

   Companion to https://github.com/apache/jena/pull/1619.


-- 
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.

To unsubscribe, e-mail: dev-unsubscr...@jena.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [jena-site] kinow merged pull request #130: Corrected spelling error in fuseki-webapp.md

[GitBox]

kinow merged PR #130:
URL: https://github.com/apache/jena-site/pull/130


-- 
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.

To unsubscribe, e-mail: dev-unsubscr...@jena.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [jena-site] kinow merged pull request #129: Fix typos in README.md

[GitBox]

kinow merged PR #129:
URL: https://github.com/apache/jena-site/pull/129


-- 
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.

To unsubscribe, e-mail: dev-unsubscr...@jena.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [jena-site] furkanakkurt1335 opened a new pull request, #129: Fix typos in README.md

[GitBox]

furkanakkurt1335 opened a new pull request, #129:
URL: https://github.com/apache/jena-site/pull/129

   as a _n_ operating system
   
   comes in ~~in~~ two forms


-- 
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.

To unsubscribe, e-mail: dev-unsubscr...@jena.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [jena-site] rvesse commented on a diff in pull request #128: Add a Security Advisories page to the website

[GitBox]

rvesse commented on code in PR #128:
URL: https://github.com/apache/jena-site/pull/128#discussion_r1022797382


##
source/about_jena/security-advisories.md:
##
@@ -0,0 +1,103 @@
+---
+title: Jena Security Advisories
+---
+
+# Security Issue Policy
+
+## Process
+
+Jena follows the standard [ASF Security for 
Committers](https://www.apache.org/security/committers.html) policy for
+reporting and addressing security issues.
+
+If you think you have identified a Security issue in our project please refer 
to that policy for how to report it, and
+the process that the Jena Project Management Committe (PMC) will follow in 
addressing the issue.

Review Comment:
   Fixed



##
source/about_jena/security-advisories.md:
##
@@ -0,0 +1,103 @@
+---
+title: Jena Security Advisories
+---
+
+# Security Issue Policy
+
+## Process
+
+Jena follows the standard [ASF Security for 
Committers](https://www.apache.org/security/committers.html) policy for
+reporting and addressing security issues.
+
+If you think you have identified a Security issue in our project please refer 
to that policy for how to report it, and
+the process that the Jena Project Management Committe (PMC) will follow in 
addressing the issue.
+
+## Single Supported Version
+
+As a project with a relatively small developer community Apache Jena only has 
the resources to maintain a single release
+version.  Therefore any accepted security issue reported will be fixed by 
developing a fix for our `main` branch.  We
+will then make a release with the fix in a timeframe appropriate to the 
severity of the issue.  
+
+## Standard Mitigation Advice
+
+Note that as a project our guidance to users is **always** to use the newest 
Jena version available to ensure you have
+any security fixes we have made available.
+
+Where more specific mitigations are available these will be denoted in the 
individual CVEs.
+
+## End of Life (EOL) Components
+
+Where a security advisory is issued for a component that is already EOL 
(sometimes referred to as archived or retired
+within our documentation) then we will not fix the issue but instead reiterate 
our previous recommendations that users
+cease using the EOL component and migrate to actively supported components.
+
+Such issues will follow the [CVE EOL Assignment
+Process](https://cve.mitre.org/cve/cna/CVE_Program_End_of_Life_EOL_Assignment_Process.html)
 and will be clearly denoted
+by the **UNSUPPORTED WHEN ASSIGNED** text at the start of the description.
+
+## Security Issues in Dependencies
+
+For our dependencies the project relies primarily upon GitHub Dependabot 
Alerts to be made aware of available dependency
+updates, whether security related or otherwise.  When a security related 
update is released and our analysis shows that
+Jena users may be affected we endeavour to take the dependency upgrade ASAP 
and make a new release in timeframe
+appropriate to the severity of the issue.
+
+# Jena CVEs
+
+The following CVEs specifically relate to the Jena codebase itself and have 
been addressed by the project. Per our
+policy above we advise users to always utilise the latest Jena release 
available.
+
+Please refer to the individual CVE links for further details and mitigations.
+
+## CVE-2022-45136 - JDBC Serialisation in Apache Jena SDB
+
+[CVE-2022-45136](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-45136)
 affects all versions of [Jena
+SDB](../documentation/archive/sdb/) up to and including the final 3.17.0 
release
+
+Apache Jena SDB has been EOL since December 2020 and we recommend any 
remaining users migrate to [Jena TDB
+2](../documentation/tdb2/) or other 3rd party vendor alternatives.
+
+Apache Jena would like to thank Crilwa & LaNyer640 for reporting this issue
+
+## CVE-2022-28890 - Processing External DTDs
+
+[CVE-2022-28890](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-28890)
 affects the RDF/XML parser in Jena 4.4.0
+only
+
+Users should upgrade to latest Jena 4.x [release](../download/) available.
+
+Apache Jena would like to thank Feras Daragma, Avishag Shapira & Amit Laish 
(GE Digital, Cyber Security Lab) for their
+report.
+
+## CVE-2021-39239 - XML External Entity (XXE) Vulnerability
+
+[CVE-2021-39239](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-39239)
 affects XML parsing up to Jena 4.1.0
+
+Users should upgrade to latest Jena 4.x [release](../download/) available.
+
+## CVE-2021-33192 - Display information UI XSS in Apache Jena Fuseki
+
+[CVE-2021-33192](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-33192)
 affected
+[Fuseki](../documentation/fuseki2/) 2.0.0 through 4.0.0
+
+Users should upgrade to latest Jena 4.x [release](../download/) available.
+
+# CVEs in Jena Dependencies
+
+The following advisories are CVE's in Jena's dependencies that may affect 
users of Jena, as with Jena specific CVEs our

Review Comment:
   Fixed



-- 
This is an automated message from the Apache Git Service.
To respond to the message

[GitHub] [jena-site] kinow commented on a diff in pull request #128: Add a Security Advisories page to the website

[GitBox]

kinow commented on code in PR #128:
URL: https://github.com/apache/jena-site/pull/128#discussion_r1022617678


##
source/about_jena/security-advisories.md:
##
@@ -0,0 +1,103 @@
+---
+title: Jena Security Advisories
+---
+
+# Security Issue Policy
+
+## Process
+
+Jena follows the standard [ASF Security for 
Committers](https://www.apache.org/security/committers.html) policy for
+reporting and addressing security issues.
+
+If you think you have identified a Security issue in our project please refer 
to that policy for how to report it, and
+the process that the Jena Project Management Committe (PMC) will follow in 
addressing the issue.

Review Comment:
   Committee?



##
source/about_jena/security-advisories.md:
##
@@ -0,0 +1,103 @@
+---
+title: Jena Security Advisories
+---
+
+# Security Issue Policy
+
+## Process
+
+Jena follows the standard [ASF Security for 
Committers](https://www.apache.org/security/committers.html) policy for
+reporting and addressing security issues.
+
+If you think you have identified a Security issue in our project please refer 
to that policy for how to report it, and
+the process that the Jena Project Management Committe (PMC) will follow in 
addressing the issue.
+
+## Single Supported Version
+
+As a project with a relatively small developer community Apache Jena only has 
the resources to maintain a single release
+version.  Therefore any accepted security issue reported will be fixed by 
developing a fix for our `main` branch.  We
+will then make a release with the fix in a timeframe appropriate to the 
severity of the issue.  
+
+## Standard Mitigation Advice
+
+Note that as a project our guidance to users is **always** to use the newest 
Jena version available to ensure you have
+any security fixes we have made available.
+
+Where more specific mitigations are available these will be denoted in the 
individual CVEs.
+
+## End of Life (EOL) Components
+
+Where a security advisory is issued for a component that is already EOL 
(sometimes referred to as archived or retired
+within our documentation) then we will not fix the issue but instead reiterate 
our previous recommendations that users
+cease using the EOL component and migrate to actively supported components.
+
+Such issues will follow the [CVE EOL Assignment
+Process](https://cve.mitre.org/cve/cna/CVE_Program_End_of_Life_EOL_Assignment_Process.html)
 and will be clearly denoted
+by the **UNSUPPORTED WHEN ASSIGNED** text at the start of the description.
+
+## Security Issues in Dependencies
+
+For our dependencies the project relies primarily upon GitHub Dependabot 
Alerts to be made aware of available dependency
+updates, whether security related or otherwise.  When a security related 
update is released and our analysis shows that
+Jena users may be affected we endeavour to take the dependency upgrade ASAP 
and make a new release in timeframe
+appropriate to the severity of the issue.
+
+# Jena CVEs
+
+The following CVEs specifically relate to the Jena codebase itself and have 
been addressed by the project. Per our
+policy above we advise users to always utilise the latest Jena release 
available.
+
+Please refer to the individual CVE links for further details and mitigations.
+
+## CVE-2022-45136 - JDBC Serialisation in Apache Jena SDB
+
+[CVE-2022-45136](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-45136)
 affects all versions of [Jena
+SDB](../documentation/archive/sdb/) up to and including the final 3.17.0 
release
+
+Apache Jena SDB has been EOL since December 2020 and we recommend any 
remaining users migrate to [Jena TDB
+2](../documentation/tdb2/) or other 3rd party vendor alternatives.
+
+Apache Jena would like to thank Crilwa & LaNyer640 for reporting this issue
+
+## CVE-2022-28890 - Processing External DTDs
+
+[CVE-2022-28890](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-28890)
 affects the RDF/XML parser in Jena 4.4.0
+only
+
+Users should upgrade to latest Jena 4.x [release](../download/) available.
+
+Apache Jena would like to thank Feras Daragma, Avishag Shapira & Amit Laish 
(GE Digital, Cyber Security Lab) for their
+report.
+
+## CVE-2021-39239 - XML External Entity (XXE) Vulnerability
+
+[CVE-2021-39239](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-39239)
 affects XML parsing up to Jena 4.1.0
+
+Users should upgrade to latest Jena 4.x [release](../download/) available.
+
+## CVE-2021-33192 - Display information UI XSS in Apache Jena Fuseki
+
+[CVE-2021-33192](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-33192)
 affected
+[Fuseki](../documentation/fuseki2/) 2.0.0 through 4.0.0
+
+Users should upgrade to latest Jena 4.x [release](../download/) available.
+
+# CVEs in Jena Dependencies
+
+The following advisories are CVE's in Jena's dependencies that may affect 
users of Jena, as with Jena specific CVEs our

Review Comment:
   CVEs (for consistency? 😬)



-- 
This is an automated message from the Apache Git Service.
T

[GitHub] [jena-site] rvesse opened a new pull request, #128: Add a Security Advisories page to the website

[GitBox]

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

   Adds a new Security Advisories page that lists the CVEs we have issued as 
well as any significant CVEs in our dependencies that users should be aware of.
   
   Also makes an attempt to describe our policy around handling of security 
issues


-- 
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.

To unsubscribe, e-mail: dev-unsubscr...@jena.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [jena-site] afs merged pull request #120: Fuseki optimizer and logging documentation improvements

[GitBox]

afs merged PR #120:
URL: https://github.com/apache/jena-site/pull/120


-- 
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.

To unsubscribe, e-mail: dev-unsubscr...@jena.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [jena-site] afs commented on pull request #120: Fuseki optimizer and logging documentation improvements

[GitBox]

afs commented on PR #120:
URL: https://github.com/apache/jena-site/pull/120#issuecomment-1312415087

   Missed [the requested 
change](https://github.com/apache/jena-site/pull/120#issuecomment-1270001532) 
happening.
   
   @eroux - 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.

To unsubscribe, e-mail: dev-unsubscr...@jena.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [jena-site] rvesse closed pull request #127: Add retired notice to each SDB page

[GitBox]

rvesse closed pull request #127: Add retired notice to each SDB page
URL: https://github.com/apache/jena-site/pull/127


-- 
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.

To unsubscribe, e-mail: dev-unsubscr...@jena.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [jena-site] afs commented on pull request #124: change ShexMap to ShapeMap

[GitBox]

afs commented on PR #124:
URL: https://github.com/apache/jena-site/pull/124#issuecomment-1302185198

   This will be merged when Jena 4.7.0 is released.


-- 
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.

To unsubscribe, e-mail: dev-unsubscr...@jena.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [jena-site] kinow merged pull request #125: Fixed navigation link for "Download with UI" href

[GitBox]

kinow merged PR #125:
URL: https://github.com/apache/jena-site/pull/125


-- 
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.

To unsubscribe, e-mail: dev-unsubscr...@jena.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [jena-site] ericprud opened a new pull request, #124: GH-1592 change ShexMap to ShapeMap

[GitBox]

ericprud opened a new pull request, #124:
URL: https://github.com/apache/jena-site/pull/124

   Change `ShexMap` type in documentation examples to `ShapeMap`
   `.shexmap` files are renamed to `.smap` in accordance with emerging 
convention.
   
   Accompanies apache/jena#1589
   


-- 
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.

To unsubscribe, e-mail: dev-unsubscr...@jena.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [jena-site] eroux commented on pull request #120: Fuseki optimizer and logging documentation improvements

[GitBox]

eroux commented on PR #120:
URL: https://github.com/apache/jena-site/pull/120#issuecomment-1270001532

   @afs thanks for the review! I've added `none.opt` back


-- 
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.

To unsubscribe, e-mail: dev-unsubscr...@jena.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [jena-site] afs commented on a diff in pull request #120: Fuseki optimizer and logging documentation improvements

[GitBox]

afs commented on code in PR #120:
URL: https://github.com/apache/jena-site/pull/120#discussion_r988988704


##
source/documentation/fuseki2/fuseki-logging.md:
##
@@ -53,6 +53,16 @@ which defaults to `/etc/fuseki` on Linux.
 For the standalone webapp server, `FUSEKI_BASE` defaults to directory `run/`
 within the directory where the server is run.
 
+The property `fuseki.loglogging` can also be set to `true` for additional 
logging.

Review Comment:
   @OyvindLGjesdal -- would you like to put in a PR?
   
   The "meta" logging isn't the focus of this PR.
   
   Merely FYI:
   There is a companion setup in  `LogCtl`: `JENA_LOGLOGGING` `jena.loglogging`.
   
   But Fuseki logging is more exposed to the runtime environment and a bit more 
complicated especially in war file form.



-- 
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.

To unsubscribe, e-mail: dev-unsubscr...@jena.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [jena-site] OyvindLGjesdal commented on a diff in pull request #120: Fuseki optimizer and logging documentation improvements

[GitBox]

OyvindLGjesdal commented on code in PR #120:
URL: https://github.com/apache/jena-site/pull/120#discussion_r93398


##
source/documentation/fuseki2/fuseki-logging.md:
##
@@ -53,6 +53,16 @@ which defaults to `/etc/fuseki` on Linux.
 For the standalone webapp server, `FUSEKI_BASE` defaults to directory `run/`
 within the directory where the server is run.
 
+The property `fuseki.loglogging` can also be set to `true` for additional 
logging.

Review Comment:
   Would it be worth also mentioning the fuseki environment variable 
`FUSEKI_LOGLOGGING ` .ie.
   
   The property `fuseki.loglogging` or the environment variable 
`FUSEKI_LOGLOGGING` can also be set to `true` for additional logging? 
   
   I see it used in 
https://github.com/apache/jena/blob/main/jena-fuseki2/jena-fuseki-core/src/main/java/org/apache/jena/fuseki/system/FusekiLogging.java#L68
   



-- 
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.

To unsubscribe, e-mail: dev-unsubscr...@jena.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [jena-site] OyvindLGjesdal commented on a diff in pull request #120: Fuseki optimizer and logging documentation improvements

[GitBox]

OyvindLGjesdal commented on code in PR #120:
URL: https://github.com/apache/jena-site/pull/120#discussion_r93398


##
source/documentation/fuseki2/fuseki-logging.md:
##
@@ -53,6 +53,16 @@ which defaults to `/etc/fuseki` on Linux.
 For the standalone webapp server, `FUSEKI_BASE` defaults to directory `run/`
 within the directory where the server is run.
 
+The property `fuseki.loglogging` can also be set to `true` for additional 
logging.

Review Comment:
   Would it be worth mentioning the fuseki environment variable 
`FUSEKI_LOGLOGGING ` also, .ie.
   
   The property `fuseki.loglogging` or the environment variable 
`FUSEKI_LOGLOGGING` can also be set to `true` for additional logging? 
   
   I see it used in 
https://github.com/apache/jena/blob/main/jena-fuseki2/jena-fuseki-core/src/main/java/org/apache/jena/fuseki/system/FusekiLogging.java#L68
   



-- 
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.

To unsubscribe, e-mail: dev-unsubscr...@jena.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [jena-site] OyvindLGjesdal commented on a diff in pull request #120: Fuseki optimizer and logging documentation improvements

[GitBox]

OyvindLGjesdal commented on code in PR #120:
URL: https://github.com/apache/jena-site/pull/120#discussion_r93398


##
source/documentation/fuseki2/fuseki-logging.md:
##
@@ -53,6 +53,16 @@ which defaults to `/etc/fuseki` on Linux.
 For the standalone webapp server, `FUSEKI_BASE` defaults to directory `run/`
 within the directory where the server is run.
 
+The property `fuseki.loglogging` can also be set to `true` for additional 
logging.

Review Comment:
   Would it be worth mentioning the fuseki environment variable 
`FUSEKI_LOGLOGGING also`, .ie.
   
   The property `fuseki.loglogging` or the environment variable 
`FUSEKI_LOGLOGGING` can also be set to `true` for additional logging? 
   
   I see it used in 
https://github.com/apache/jena/blob/main/jena-fuseki2/jena-fuseki-core/src/main/java/org/apache/jena/fuseki/system/FusekiLogging.java#L68
   



-- 
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.

To unsubscribe, e-mail: dev-unsubscr...@jena.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [jena-site] afs commented on a diff in pull request #120: Fuseki optimizer and logging documentation improvements

[GitBox]

afs commented on code in PR #120:
URL: https://github.com/apache/jena-site/pull/120#discussion_r988784347


##
source/documentation/tdb/optimizer.md:
##
@@ -65,18 +65,20 @@ Optimizer control files
 
 | File name   | Effect   |
 | --- |  |
-| `none.opt`  | No reordering - execute triple patterns in the order in the 
query |

Review Comment:
   Please leave `none.opt` in.
   
   The issue is that there is reordering in the optimizer as well which helps 
put filter in better places. `none.opt` still applies at the TDB level.



-- 
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.

To unsubscribe, e-mail: dev-unsubscr...@jena.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [jena-site] sszuev commented on a diff in pull request #123: update jena-repack.md: add a bit more information (gradle), cleanup

[GitBox]

sszuev commented on code in PR #123:
URL: https://github.com/apache/jena-site/pull/123#discussion_r983144693


##
source/documentation/notes/jena-repack.md:
##
@@ -27,32 +28,42 @@ for Fuseki.  It uses the maven shade plugin with a 
`transformer`.
 
 This is an extract from the POM:
 
-
-  org.apache.maven.plugins
-  maven-shade-plugin
-  
-...
-
-  
-  ... other transformers ...
-
-
+```xml
+
+  org.apache.maven.plugins
+  maven-shade-plugin
+  
+...
+
+  
+  ... other transformers ...
+
+  
+
+```
 See
 
[jena-fuseki2/jena-fuseki-server/pom.xml](https://github.com/apache/jena/blob/main/jena-fuseki2/jena-fuseki-server/pom.xml)
 for the complete shade plugin setup used by Fuseki.
 
-If doing manually, create a single file in your application jar the
-all lines of all the services resource files. The order does not matter
-- Jena calls modules in the right order.
-
-For Gradle, the [shadowJar plugin](https://imperceptiblethoughts.com/shadow/)
+ Gradle
+For Gradle, the [shadowJar 
plugin](https://plugins.gradle.org/plugin/com.github.johnrengelman.shadow)
 has the
 
[mergeServiceFiles](https://imperceptiblethoughts.com/shadow/configuration/merging/#merging-service-descriptor-files)
 operation.
 
-// Merging Service Files
-shadowJar {
-  mergeServiceFiles()
-  . . .
-}
+```groovy
+plugins {
+  ...
+  id "com.github.johnrengelman.shadow" version "7.1.2"
+}
+shadowJar {
+  mergeServiceFiles()
+}
+...
+```
+
+ Manual assembling
+If doing manually, create a single file 
(`META-INF/services/org.apache.jena.sys.JenaSubsystemLifecycle`) in your 
application jar containing the
+all lines of all the services resource files. The order does not matter.

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.

To unsubscribe, e-mail: dev-unsubscr...@jena.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [jena-site] kinow commented on a diff in pull request #123: update jena-repack.md: add a bit more information (gradle), cleanup

[GitBox]

kinow commented on code in PR #123:
URL: https://github.com/apache/jena-site/pull/123#discussion_r982854792


##
source/documentation/notes/jena-repack.md:
##
@@ -27,32 +28,42 @@ for Fuseki.  It uses the maven shade plugin with a 
`transformer`.
 
 This is an extract from the POM:
 
-
-  org.apache.maven.plugins
-  maven-shade-plugin
-  
-...
-
-  
-  ... other transformers ...
-
-
+```xml
+
+  org.apache.maven.plugins
+  maven-shade-plugin
+  
+...
+
+  
+  ... other transformers ...
+
+  
+
+```
 See
 
[jena-fuseki2/jena-fuseki-server/pom.xml](https://github.com/apache/jena/blob/main/jena-fuseki2/jena-fuseki-server/pom.xml)
 for the complete shade plugin setup used by Fuseki.
 
-If doing manually, create a single file in your application jar the
-all lines of all the services resource files. The order does not matter
-- Jena calls modules in the right order.
-
-For Gradle, the [shadowJar plugin](https://imperceptiblethoughts.com/shadow/)
+ Gradle
+For Gradle, the [shadowJar 
plugin](https://plugins.gradle.org/plugin/com.github.johnrengelman.shadow)
 has the
 
[mergeServiceFiles](https://imperceptiblethoughts.com/shadow/configuration/merging/#merging-service-descriptor-files)
 operation.
 
-// Merging Service Files
-shadowJar {
-  mergeServiceFiles()
-  . . .
-}
+```groovy
+plugins {
+  ...
+  id "com.github.johnrengelman.shadow" version "7.1.2"
+}
+shadowJar {
+  mergeServiceFiles()
+}
+...
+```
+
+ Manual assembling
+If doing manually, create a single file 
(`META-INF/services/org.apache.jena.sys.JenaSubsystemLifecycle`) in your 
application jar containing the
+all lines of all the services resource files. The order does not matter.

Review Comment:
   s/containing the all lines/containing the lines ?



-- 
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.

To unsubscribe, e-mail: dev-unsubscr...@jena.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [jena-site] sszuev opened a new pull request, #123: update jena-repack.md: add a bit more information (gradle), cleanup

[GitBox]

sszuev opened a new pull request, #123:
URL: https://github.com/apache/jena-site/pull/123

   minor changes in jena-repack.md


-- 
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.

To unsubscribe, e-mail: dev-unsubscr...@jena.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [jena-site] kinow merged pull request #122: Fix file extensions table formatting

[GitBox]

kinow merged PR #122:
URL: https://github.com/apache/jena-site/pull/122


-- 
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.

To unsubscribe, e-mail: dev-unsubscr...@jena.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [jena-site] kinow merged pull request #121: Fix InfModel javadoc link

[GitBox]

kinow merged PR #121:
URL: https://github.com/apache/jena-site/pull/121


-- 
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.

To unsubscribe, e-mail: dev-unsubscr...@jena.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [jena-site] eroux opened a new pull request, #120: Fuseki optimizer and logging documentation improvements

[GitBox]

eroux opened a new pull request, #120:
URL: https://github.com/apache/jena-site/pull/120

   - document use of context keys `arq:logExec` and `arq:optReorderBGP`
   - changing some `lg4j.properties` to `log4j2.properties`


-- 
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.

To unsubscribe, e-mail: dev-unsubscr...@jena.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [jena-site] ieugen commented on pull request #117: Improved backup docs https://github.com/apache/jena/issues/1500

[GitBox]

ieugen commented on PR #117:
URL: https://github.com/apache/jena-site/pull/117#issuecomment-1249539957

   > (separately we're discussing changing the publication pipeline to have a 
branch for future changes; we only have a per-PR staging at the moment). 
   
   This sounds great. Thanks.
   p.s. I did not have time to work on the backup stuff, plan to do that this 
year.


-- 
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.

To unsubscribe, e-mail: dev-unsubscr...@jena.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [jena-site] afs commented on pull request #117: Improved backup docs https://github.com/apache/jena/issues/1500

[GitBox]

afs commented on PR #117:
URL: https://github.com/apache/jena-site/pull/117#issuecomment-1249349319

   Thanks! Looks good.
   
   Because this refers to 4.7.0, it won't get merged to main just yet.
   
   (separately we're discussing changing the publication pipeline to have a 
branch for future changes; we only have a per-PR staging at the moment).


-- 
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.

To unsubscribe, e-mail: dev-unsubscr...@jena.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [jena-site] ieugen commented on pull request #117: Improved backup docs https://github.com/apache/jena/issues/1500

[GitBox]

ieugen commented on PR #117:
URL: https://github.com/apache/jena-site/pull/117#issuecomment-1245123615

   done.


-- 
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.

To unsubscribe, e-mail: dev-unsubscr...@jena.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [jena-site] afs commented on a diff in pull request #117: Improved backup docs https://github.com/apache/jena/issues/1500

[GitBox]

afs commented on code in PR #117:
URL: https://github.com/apache/jena-site/pull/117#discussion_r968188010


##
source/documentation/tdb2/tdb2_admin.md:
##
@@ -67,3 +67,13 @@ continue to be serviced.
 
 There is also a command line tool `tdb2.tdbbackup` to run the
 backup process on a database not in use.
+

Review Comment:
   Yes please.
   (either drop this PR or rebase the changes on top of 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.

To unsubscribe, e-mail: dev-unsubscr...@jena.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [jena-site] ieugen commented on a diff in pull request #117: Improved backup docs https://github.com/apache/jena/issues/1500

[GitBox]

ieugen commented on code in PR #117:
URL: https://github.com/apache/jena-site/pull/117#discussion_r967691017


##
source/documentation/tdb2/tdb2_admin.md:
##
@@ -67,3 +67,13 @@ continue to be serviced.
 
 There is also a command line tool `tdb2.tdbbackup` to run the
 backup process on a database not in use.
+

Review Comment:
   I am a bit confused. 
   You want me to drop this PR and put the same text in fuseki docs here: 
https://github.com/apache/jena-site/blob/main/source/documentation/fuseki2/fuseki-server-protocol.md
 ? 
   
   



-- 
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.

To unsubscribe, e-mail: dev-unsubscr...@jena.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [jena-site] afs commented on pull request #119: Deploy website from branch 'publish'

[GitBox]

afs commented on PR #119:
URL: https://github.com/apache/jena-site/pull/119#issuecomment-1240694615

   Good point - we can repurpose `asf-staging` so it does not have only one PR 
on it.
   
   Maybe even align the names because `https://jena.staged.apache.org/` fools 
me every time!
   
   Do we need (on a shared place) a per-PR preview?
   local hugo is pretty good because gives a faster edit-preview cycle, at the 
cost of install hugo locally.
   


-- 
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.

To unsubscribe, e-mail: dev-unsubscr...@jena.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [jena-site] rvesse commented on pull request #119: Deploy website from branch 'publish'

[GitBox]

rvesse commented on PR #119:
URL: https://github.com/apache/jena-site/pull/119#issuecomment-1240681284

   Probably need to consider which branches we publish the staging site from as 
well?
   
   Currently anything other than `main` goes to the Staging site, so maybe 
change that to have only `main` go to the Staging site.  Downside of that is 
that you can't then preview a given PR on the staging site until it merges to 
`main`
   
   WDYT?


-- 
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.

To unsubscribe, e-mail: dev-unsubscr...@jena.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [jena-site] afs commented on pull request #118: ServiceEnhancer: Revision initiated by JENA-1517

[GitBox]

afs commented on PR #118:
URL: https://github.com/apache/jena-site/pull/118#issuecomment-1240665410

   See #119 for discussion on managing site releases.
   
   It will not affect this PR.


-- 
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.

To unsubscribe, e-mail: dev-unsubscr...@jena.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [jena-site] afs opened a new pull request, #119: Deploy website from branch 'publish'

[GitBox]

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

   We get changes for the website that are changes to go into the next release.
   
   There are also changes that should go out immediately.
   
   So there are two workflows. Currently, release-changes get held as approved 
PRs. This is workable but the approved PRs aren't checked against each other or 
for PRs-to-PRs.
   
   An alternative is to have a branch for accumulated changes for the next 
release. We should make it the default branch because tooling tends to end up 
with PRs to the default branch. Keep `main` for this.
   
   There is a `publish` is a new branch from which the currently deployed 
website.
   
   On a release, merge `main` into `publish`.
   
   The burden is than on website fixes. They need to go to `publish`. We can 
edit the target PRs through GH UI.
   
   So with this change, we have two branches. And probably so friction if a PR 
goes to `main` instead of `publish`. We can cherry-pick but it is a different 
commit. `merge` when publishing the next version may get this right, or it may 
not.
   
   This PR is the one-line `Jenkinsfile` change (untested).


-- 
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.

To unsubscribe, e-mail: dev-unsubscr...@jena.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [jena-site] afs commented on pull request #118: ServiceEnhancer: Revision initiated by JENA-1517

[GitBox]

afs commented on PR #118:
URL: https://github.com/apache/jena-site/pull/118#issuecomment-1240645129

   This should wait until the next release to get to the actual website. This 
need is becoming more common (a good thing).


-- 
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.

To unsubscribe, e-mail: dev-unsubscr...@jena.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [jena-site] Aklakan opened a new pull request, #118: ServiceEnhancer: Revision initiated by JENA-1517

[GitBox]

Aklakan opened a new pull request, #118:
URL: https://github.com/apache/jena-site/pull/118

   Added documentation of additional assembler options to configure bulk 
request aspects.
   Fixed a few grammar/formatting issues.


-- 
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.

To unsubscribe, e-mail: dev-unsubscr...@jena.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [jena-site] afs commented on a diff in pull request #117: Improved backup docs https://github.com/apache/jena/issues/1500

[GitBox]

afs commented on code in PR #117:
URL: https://github.com/apache/jena-site/pull/117#discussion_r965076213


##
source/documentation/tdb2/tdb2_admin.md:
##
@@ -67,3 +67,13 @@ continue to be serviced.
 
 There is also a command line tool `tdb2.tdbbackup` to run the
 backup process on a database not in use.
+

Review Comment:
   `tdb2.tdbbackup` has had this feature for a long time. `tdb2.tdbbackup` 
isn't really very important. Nowadays, tarsnaction handling applies to all 
databases so special casing it isn't necessary. TBH It should probably be 
removed.
   
   The recent PR put the same functionality into Fuseki - they don't share code.
   
   The Fuseki code isworks with any database type, integrates into the Fuseki 
lifecycle and Fuseki logging.
   
   Could you put this change in the Fuseki docs please?
   



-- 
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.

To unsubscribe, e-mail: dev-unsubscr...@jena.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [jena-site] ieugen opened a new pull request, #117: Improved backup docs https://github.com/apache/jena/issues/1500

[GitBox]

ieugen opened a new pull request, #117:
URL: https://github.com/apache/jena-site/pull/117

   Signed-off-by: Eugen Stan 


-- 
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.

To unsubscribe, e-mail: dev-unsubscr...@jena.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [jena-site] Aklakan commented on pull request #115: Documentation of AsyncParserBuilder

[GitBox]

Aklakan commented on PR #115:
URL: https://github.com/apache/jena-site/pull/115#issuecomment-1234581695

   No worries; I did some local tests loading a tdb2 with up to 10mio triples 
with the improved AsyncParser and it was fine, but I also wanted to do a 
performance comparison with jena 4.5.0 just to be safe - but then additional 
work dropped in this week; I am still on 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.

To unsubscribe, e-mail: dev-unsubscr...@jena.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [jena-site] afs commented on pull request #115: Documentation of AsyncParserBuilder

[GitBox]

afs commented on PR #115:
URL: https://github.com/apache/jena-site/pull/115#issuecomment-1234409698

   Sorry - the improved AsyncParser didn't make the 4.6.1 bugfix 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.

To unsubscribe, e-mail: dev-unsubscr...@jena.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [jena-site] afs merged pull request #116: Main 4.6.0 updates

[GitBox]

afs merged PR #116:
URL: https://github.com/apache/jena-site/pull/116


-- 
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.

To unsubscribe, e-mail: dev-unsubscr...@jena.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [jena-site] afs commented on pull request #114: Fix doc about querying remote service

[GitBox]

afs commented on PR #114:
URL: https://github.com/apache/jena-site/pull/114#issuecomment-1227002842

   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.

To unsubscribe, e-mail: dev-unsubscr...@jena.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [jena-site] afs merged pull request #114: Fix doc about querying remote service

[GitBox]

afs merged PR #114:
URL: https://github.com/apache/jena-site/pull/114


-- 
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.

To unsubscribe, e-mail: dev-unsubscr...@jena.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [jena-site] afs merged pull request #112: add geo-literal note and example

[GitBox]

afs merged PR #112:
URL: https://github.com/apache/jena-site/pull/112


-- 
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.

To unsubscribe, e-mail: dev-unsubscr...@jena.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [jena-site] afs merged pull request #107: Add ValidationListener documentation

[GitBox]

afs merged PR #107:
URL: https://github.com/apache/jena-site/pull/107


-- 
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.

To unsubscribe, e-mail: dev-unsubscr...@jena.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [jena-site] afs merged pull request #104: add note about geof:asGeoJSON

[GitBox]

afs merged PR #104:
URL: https://github.com/apache/jena-site/pull/104


-- 
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.

To unsubscribe, e-mail: dev-unsubscr...@jena.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [jena-site] Aklakan opened a new pull request, #115: Documentation of AsyncParserBuilder

[GitBox]

Aklakan opened a new pull request, #115:
URL: https://github.com/apache/jena-site/pull/115

   Documentation of the improvements of 
https://github.com/apache/jena/issues/1477


-- 
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.

To unsubscribe, e-mail: dev-unsubscr...@jena.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [jena-site] afs commented on pull request #113: Documentation for the service enhancer plugin

[GitBox]

afs commented on PR #113:
URL: https://github.com/apache/jena-site/pull/113#issuecomment-1221303317

   Linking into the website will occur when the 4.6.0 site is published.


-- 
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.

To unsubscribe, e-mail: dev-unsubscr...@jena.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [jena-site] afs merged pull request #113: Documentation for the service enhancer plugin

[GitBox]

afs merged PR #113:
URL: https://github.com/apache/jena-site/pull/113


-- 
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.

To unsubscribe, e-mail: dev-unsubscr...@jena.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [jena-site] Aklakan commented on pull request #113: Documentation for the service enhancer plugin

[GitBox]

Aklakan commented on PR #113:
URL: https://github.com/apache/jena-site/pull/113#issuecomment-1212327760

   The first version of the doc should be done and contain the relevant 
information for setting it up.


-- 
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.

To unsubscribe, e-mail: dev-unsubscr...@jena.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [jena-site] Aklakan opened a new pull request, #113: Serviceenhancer

[GitBox]

Aklakan opened a new pull request, #113:
URL: https://github.com/apache/jena-site/pull/113

   This is the documentation for https://github.com/apache/jena/issues/1314
   
   I think overall it includes the most important aspects and its ready for 
some feedback.
   
   There are a couple of things I still need to do to finalize it:
   [ ] Check namespaces (I think it makes sense to move all plugin related IRIs 
to `http://jena.apache.org/service-enhancer#`)
   [ ] Check spelling
   
   


-- 
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.

To unsubscribe, e-mail: dev-unsubscr...@jena.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org