You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@jena.apache.org by gi...@apache.org on 2021/09/24 13:01:25 UTC

[jena-site] branch asf-staging updated: Staged site from sparql-apis (ddff79dcaa14624f25a5837d30ea3df4605edb0f)

This is an automated email from the ASF dual-hosted git repository.

git-site-role pushed a commit to branch asf-staging
in repository https://gitbox.apache.org/repos/asf/jena-site.git


The following commit(s) were added to refs/heads/asf-staging by this push:
     new 1fa40c1  Staged site from sparql-apis (ddff79dcaa14624f25a5837d30ea3df4605edb0f)
1fa40c1 is described below

commit 1fa40c180747f8b551193b2b076e37b381f42bfa
Author: jenkins <bu...@apache.org>
AuthorDate: Fri Sep 24 13:01:22 2021 +0000

    Staged site from sparql-apis (ddff79dcaa14624f25a5837d30ea3df4605edb0f)
---
 content/documentation/sparql-apis/index.html | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/content/documentation/sparql-apis/index.html b/content/documentation/sparql-apis/index.html
index 78d38cf..1fdcf1d 100644
--- a/content/documentation/sparql-apis/index.html
+++ b/content/documentation/sparql-apis/index.html
@@ -265,7 +265,7 @@ and receiving datasets, rather than individual graphs.</p>
 <p>Both API and GPI provide builders for detailed setup, particularly for remote usage over HTTP and HTTPS where detailed control of the HTTP requests is sometimes necessary to work with other triple stores.</p>
 <p>HTTP authentication support is provided, supporting both basic and digest authentication in challenge-response scenarios.</p>
 <p>Factory style functions for many common usage patterns are retained in <code>QueryExecutionFactory</code>, <code>UpdateExecutionFactory</code>.</p>
-<h2 id="changes-from-jena-410-to-jena-420">Changes from Jena 4.1.0 to Jena 4.2.0</h2>
+<h2 id="changes-from-jena-420-to-jena-430">Changes from Jena 4.2.0 to Jena 4.3.0</h2>
 <ul>
 <li>
 <p>Execution objects have a companion builder. This is especially important of HTTP as there many configuration options that may be needed. Local use is still covered by the existing <code>QueryExecutionFactory</code> as well as the new <code>QueryExecutionBuilder</code>.</p>