fuseki status [get status after ./fuseki-server or java -jar]

Hello, I use Fuseki via command-line tools in a PHP project, so I made a small 'wrapper' to call ruby & sh scripts via php : it enables to send queries and process the results without using a RDF library such as EasyRDF. I'm currently writing a code for a "sandbox environment" based on the

Re: fuseki status [get status after ./fuseki-server or java -jar]

Hi Vincent, The script "./fuseki" runs Fuseki as an OS service, and it is a wrapper around "java -jar fuseki-server.jar". It is the script that records the process id and makes OS tools concerned with OS services know about Fuseki. If you run the server directly then there isn't a record of

Re: fuseki status [get status after ./fuseki-server or java -jar]

Hi Andy, Thanks a lot for the explanation! I'm going to have a look at the script. Anyway, since I'm not able to know how the user started the server, it seems that I have to combine ps and netstat (if netstat provides useful information about the server, it may be interesting to inform the

Re: Fwd: ✅ Literals as subjects Re: Toward easier RDF: a proposal

Internally, that means Graph/Node/Triple and the ARQ engine, Jena really works on what is called "Generalized RDF" in RDF 1.1 - so literals as subjects, literals as predicates blank nodes as predicates - work just fine. Whether they are a good idea is a different question. RDF* works as

Security and Fuseki

Greetings, Fuseki is getting access control security built into Fuseki itself. It will have: HTTPS support User authentication at the server HTTP access controls on the server, dataset and service endpoints Graph-level access control within an individual dataset If this is of interest

Is JENA_HOME the same as JENAROOT?

Hi, the current documentation is unclear IMO: https://jena.apache.org/documentation/tools/index.html#common-issues-with-running-the-tools It says $JENAROOT needs to be set, but then proceeds to show how to check $JENA_HOME. Which one is it? Or both? Martynas

Re: Parsing from stdin breaks in 3.9.0

>> What is happening here? Can't use 3.9.0 as all our CLI scripts would break. You can use "riot --syntax ttl" Andy On 22/11/2018 20:22, Martynas Jusevičius wrote: Sorry, this is the correct Turtle file: @prefix def: . @prefix dct: . @prefix dh:

Parsing from stdin breaks in 3.9.0

Hi, I have such a simple Turtle file called kaunas.ttl: ./create-container.sh \ -b https://linkeddatahub.com:4443/demo/city-graph/ \ -f "cert.pem" \ -p "test1234" \ --title "Kaunas" \ --slug "kaunas" \ https://linkeddatahub.com:4443/demo/city-graph/ It parses from command line using 3.6.0:

Re: Parsing from stdin breaks in 3.9.0

Sorry, this is the correct Turtle file: @prefix def: . @prefix dct: . @prefix dh: . _:container a def:Container . _:container dct:title "Kaunas" . _:container dh:slug "kaunas" . On Thu, Nov 22, 2018 at

Re: Parsing from stdin breaks in 3.9.0

cat kaunas.ttl | riot --syntax ttl --base="https://linkeddatahub.com:4443/demo/city-graph/; That worked. trig etc. scripts are broken re. stdin input though. On Thu, Nov 22, 2018 at 10:55 PM Andy Seaborne wrote: > > >> What is happening here? Can't use 3.9.0 as all our CLI scripts would >

Re: Is JENA_HOME the same as JENAROOT?

Already fixed in staging: http://jena.staging.apache.org/documentation/tools/index.html#common-issues-with-running-the-tools JENA_HOME On 22/11/2018 17:08, Martynas Jusevičius wrote: Hi, the current documentation is unclear IMO:

Re: Parsing from stdin breaks in 3.9.0

Sure - same issue. "riot --syntax trix". The issue is in "riot", the superclass of turtle, trix etc. But why not riot kaunas.ttl ? Andy On 22/11/2018 21:58, Martynas Jusevičius wrote: cat kaunas.ttl | riot --syntax ttl --base="https://linkeddatahub.com:4443/demo/city-graph/; That

Re: Parsing from stdin breaks in 3.9.0

I can change our CLI scripts, not a problem. But my question is, if the per-syntax scripts still exist in 3.9.0, why are they not parsing from stdin (anymore)? Makes no sense like this. I would say it's a bug :) On Thu, Nov 22, 2018 at 11:05 PM Andy Seaborne wrote: > > Sure - same issue. "riot

Re: Parsing from stdin breaks in 3.9.0

On 22/11/2018 22:08, Martynas Jusevičius wrote: I can change our CLI scripts, not a problem. But my question is, if the per-syntax scripts still exist in 3.9.0, why are they not parsing from stdin (anymore)? Makes no sense like this. I would say it's a bug :) Sure. Send a PR. Andy

Re: fuseki status [get status after ./fuseki-server or java -jar]

while you are at the fuseki status here when accessing /$/status I am not getting no results on a Fuseki - version 3.8.0 instance with an enabled admin console curl -u admin:*** http://localhost:3030/$/status get's me a 404 while I can see the results and stats in the web admin. On

Re: Security and Fuseki

Hello Andy, This is excellent news! Thank you and Mulesoft for supporting this! I will try out the graph-level access control and will let you know of our use case if it fits well. -- /Andrew On 2018-11-22 , at 15:59, Andy Seaborne mailto:a...@apache.org>> wrote: Greetings, Fuseki is

Re: fuseki status [get status after ./fuseki-server or java -jar]

Do you happen to know in which version it last did work? Andy On 22/11/2018 23:23, Marco Neumann wrote: while you are at the fuseki status here when accessing /$/status I am not getting no results on a Fuseki - version 3.8.0 instance with an enabled admin console curl -u admin:***