- From: Steve Harris <steve.harris@garlik.com>
- Date: Fri, 7 Sep 2012 11:35:32 +0100
- To: "public-rdf-wg@w3.org WG" <public-rdf-wg@w3.org>
Taking a step back, and thinking about what we (Experian) actually use bNodes for, to inform our position on the various scope questions. Basically, it's just a replacement for auto_increment columns in SQL. There are two motivations for this 1) it saves the data generating process from minting a globally unique identifier for it 2) it's more efficient in the store, as there's no need to store a text symbol for it This has been helped by Skolem URIs, as now we have an easy way to refer to them between SPARQL queries. Any other features of bNodes are just a distraction or inconvenience really. I'm sure other people have different reasons for using them, anyone care to share? - Steve -- Steve Harris, CTO Garlik, a part of Experian +44 7854 417 874 http://www.garlik.com/ Registered in England and Wales 653331 VAT # 887 1335 93 80 Victoria Street, London, SW1E 5JL
Received on Friday, 7 September 2012 10:35:59 UTC