--Cheers,Alex.
-- --
You received this message because you are subscribed to the C&P "Stardog" group.
To post to this group, send email to sta...@clarkparsia.com
To unsubscribe from this group, send email to
stardog+u...@clarkparsia.com
For more options, visit this group at
http://groups.google.com/a/clarkparsia.com/group/stardog?hl=en
Determines how the Stardog parser handles bnode identifiers that may be present in RDF input. If this property is enabled (i.e.,TRUE
), parsing and data loading performance are improved; but the other effect is that if distinct input files use (randomly or intentionally) the same bnode identifier, that bnode will point to one and the same node in the database. If you have input files that use explicit bnode identifiers, and multiple files may use the same bnode identifiers, and you don’t want those bnodes to be smushed into a single node in the database, then this configuration option should be disabled (set toFALSE
).
---
You received this message because you are subscribed to the Google Groups "Stardog" group.
To unsubscribe from this group and stop receiving emails from it, send an email to stardog+u...@clarkparsia.com.
Thanks folks.Digging a little more, it looks as though Sesame/RIO 2.7.x is based on the old RDF spec where only alphanumeric is allowed, while 2.8.x uses the new spec, see:
I can't easily figure out what versions of what are used by Stardog.
I can work around the issue easily enough, but was just a bit surprised at Stardog not being compliant with the up-to-date RDF spec :)