> On Feb 4, 2022, at 4:03 PM, Andy Seaborne wrote:
>
> Ryan,
>
> Please, could you show example code that illustrates what you are seeing?
> Presumably it isn't a mix in one parser run because it looks like "Annn" come
> from a different place than UUIDs Ids.
Ryan,
Please, could you show example code that illustrates what you are
seeing? Presumably it isn't a mix in one parser run because it looks
like "Annn" come from a different place than UUIDs Ids.
Which version of Jena are you running?
Andy
On 04/02/2022 19:09, Shaw, Ryan wrote:
Hi Ryan,
Isn't it easier to skolemize the bnodes into URIs that you control?
If you only have URIs, then you could even hash the graph with SPARQL:
https://stackoverflow.com/questions/65798817/how-to-generate-a-hash-of-an-rdf-graph-using-sparql
It works but probably doesn't scale that well.
Hello,
I am trying to experiment with generating diffable N-Triples or flat Turtle
files.
I was hoping that I could do this by setting
JenaParameters.disableBNodeUIDGeneration to true, so that blank nodes would be
assigned IDs in increasing order as the parser created them. But it seems that
Update feedback:
Derby home setting is not necessary when setting the SIS_DATA variable.
Hence this is the cleaned up startup sequence in the docker entrypoint.sh:
# SiS_DATA set in docker-compose.yaml
export SIS_HOME=${SIS_DATA}/..
export START=`echo ${JAVA_HOME}/bin/java $JAVA_OPTIONS
We successfully loaded two demo sets with CRS wgs84 and CRS 27700.
So the geodetic EPSG dataset is used well.
The problem must be in our srs uri's then and we will investigate our
datasets and etl/minting on the schema's used.
Attaching to fuseki
fuseki|
