- From: Steve Harris <steve.harris@garlik.com>
- Date: Fri, 1 Mar 2013 11:51:47 +0000
- To: Kingsley Idehen <kidehen@openlinksw.com>
- Cc: Manu Sporny <msporny@digitalbazaar.com>, RDF WG <public-rdf-wg@w3.org>, Linked JSON <public-linked-json@w3.org>
On 2013-02-27, at 16:36, Kingsley Idehen <kidehen@openlinksw.com> wrote: > On 2/27/13 10:37 AM, Steve Harris wrote: >> I don't want to throw numbers about, but for us the cost of anything that significantly decreases the efficiency of our RDF storage carries a huge monetary cost - we couldn't justify it without a significant upside. > This is a very important point, and from the DBMS engineering perspective it's true. There are costs to existing RDF stores and DBMS engines. > > A suggestion: > > Manu: JSON-LD should make a note about the use of bnodes to denote graphs. That note could then hone into its special use case scenarios e.g., where there's high velocity data with little mass. > > Steve: > As already acknowledged above, you are correct about the optimization cost to existing RDF stores and DBMS engines (it will hit Virtuoso too) . Thus, when our engines encounter such data, we could simply just remap the IRIs as part of our data ingestion (insert | import) routines. That's what we'll end up doing. > > Naturally, this means tweaking existing code re. data import, ingestion, and creation etc.. Personally, I believe we have the ability to close out this matter without holding up the various workgroups i.e., RDF 1.1 stays as is. JSON-LD has a fleshed out version of the note I suggested to Manu etc.. > > Manu/Steve: > > What do you think? I believe that would be equivalent to defining the syntactic construct to generate Skolem URIs at parse time - but I've not through about it too deeply. - Steve -- Steve Harris Experian +44 20 3042 4132 Registered in England and Wales 653331 VAT # 887 1335 93 80 Victoria Street, London, SW1E 5JL
Received on Friday, 1 March 2013 11:52:17 UTC