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


##########
source/documentation/fuseki2/fuseki-server.md:
##########
@@ -1,15 +1,17 @@
 ---
-title: Running Fuseki with UI
+title: Running Fuseki
 ---
 
-Fuseki/UI can be run in a number of ways:
+Fuseki can be run as:
 
-* [As a standalone server](#fuseki-standalone-server)
-* [As a service](#fuseki-service) run by the operation system, for example, 
started when the machine boots
+* [As a standalone server with UI](#fuseki-standalone-server)
+* [As a service](#fuseki-service) run by the operation system, 
+   for example, started when the machine boots
+* Embbeded in an application, with or without a UI
 * [As a Web Application](#fuseki-web-application) inside a container such as 
Apache Tomcat or Jetty.
 
-Fuseki is also packaged as a plain server ["Fuseki Main"](fuseki-main.html)
-with no UI for use as a configurable SPARQL server, for [building as a Docker
+Fuseki is also packaged as a plain server ["Fuseki Plain"](fuseki-plain.html)
+with no UI for use as a configurable SPARQL server for [building as a Docker
 container](fuseki-docker.html), and as a deployment and development standalone
 server. It supports the arguments used by the standalone server. 

Review Comment:
   Yes, this could be better. 
   
   As of 5.3.0, I've used "Fuseki plain" for "no UI, no admin, no run/" (what 
was "Fuseki/main") and "Fuseki server" for the whole thing (what was 
Fuseki/webapp and now isn't a webapp).
   
   `jena-fuseki-main` == code, now including module'd admin, shiro and UI 
config.
   
   `jena-fuseki-server` == shared jar. It has two entry points, one for 
"server" and one for "plain". It does include the UI.
   
   `jena-fuseki-webapp` == (as of 5.3.0) the legacy code for the WAR file.
   



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

Reply via email to