On 10/10/13 07:34, Alexei Golovko wrote:
By the way, only --set "arq:outputGraphBNodeLabels=true" works;
after insert
... ja:context
       [ ja:cxtName "arq:outputGraphBNodeLabels" ;
         ja:cxtValue "true" ] ;
to config file and restarting fuseki (1.0.0) outputs blank nodes as _:b0,
not as <_: ...>

Strange - it works for me (JSON output, not text).

What happens for you if you remove the inference layer and use memory storage or TDB storage directly?

(and which version of teh code is this?)

I tried this config with the datbase have a bnode in it:

--------------------------------------

# Licensed under the terms of http://www.apache.org/licenses/LICENSE-2.0

## Example of a TDB dataset published using Fuseki: persistent storage.

@prefix :        <#> .
@prefix fuseki:  <http://jena.apache.org/fuseki#> .
@prefix rdf:     <http://www.w3.org/1999/02/22-rdf-syntax-ns#> .
@prefix rdfs:    <http://www.w3.org/2000/01/rdf-schema#> .
@prefix tdb:     <http://jena.hpl.hp.com/2008/tdb#> .
@prefix ja:      <http://jena.hpl.hp.com/2005/11/Assembler#> .

[] rdf:type fuseki:Server ;
ja:context [ ja:cxtName "arq:outputGraphBNodeLabels" ; ja:cxtValue "true" ] ;
   fuseki:services (
     <#service_tdb_all>
   ) .

# TDB
[] ja:loadClass "com.hp.hpl.jena.tdb.TDB" .
tdb:DatasetTDB  rdfs:subClassOf  ja:RDFDataset .
tdb:GraphTDB    rdfs:subClassOf  ja:Model .

## Updatable TDB dataset with all services enabled.

<#service_tdb_all> rdf:type fuseki:Service ;
    rdfs:label                      "TDB Service (RW)" ;
    fuseki:name                     "data" ;
    fuseki:serviceQuery             "query" ;
    fuseki:serviceQuery             "sparql" ;
    fuseki:serviceUpdate            "update" ;
    fuseki:serviceUpload            "upload" ;
    fuseki:serviceReadWriteGraphStore      "data" ;
    # A separate read-only graph store endpoint:
    fuseki:serviceReadGraphStore       "get" ;
    fuseki:dataset           <#tdb_dataset_readwrite> ;
    .

<#tdb_dataset_readwrite> rdf:type      tdb:DatasetTDB ;
    tdb:location "DB" ;
    .


Reply via email to