[
https://issues.apache.org/jira/browse/JENA-2152?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andy Seaborne updated JENA-2152:
--------------------------------
Attachment: tdb2-union.ttl
> Persisting constituent named graphs config for default graph of custom
> dataset view.
> ------------------------------------------------------------------------------------
>
> Key: JENA-2152
> URL: https://issues.apache.org/jira/browse/JENA-2152
> Project: Apache Jena
> Issue Type: New Feature
> Components: Fuseki
> Reporter: damodara
> Priority: Major
> Labels: SPARQL, dataset, defaultGraph, fuseki
> Attachments: tdb2-union.ttl
>
>
> Namaste. Thanks for work on jena.
> Presently we can specify custom dataset for a sparql query with {{FROM}} and
> {{FROM NAMED}} declarations, whose default-graph is merge of graphs declared
> with {{FROM}}, and whose named graphs are individual named graphs declared
> with {{FROM NAMED}}.
> This pattern works fine until we have to search among merge of small number
> of named graphs, by enumerating all of them with {{FROM}}. But if we have to
> search across merge of thousands of small named graphs (like those,
> trusted-by-an-authority, extracted-from-specific-resources,
> have-certain-provanence), then it won’t scale to mention all of those
> constituent graphs of custom default graph in every sparql query.
>
> One obvious solution is giving this custom default graph an `IRI`, and
> describe it's component named graphs with minimal vocabulary. BlazeGraph
> follows this pattern, which they call as [Virtual
> Graphs|https://github.com/blazegraph/database/wiki/VirtualGraphs].
>
> And Virtuoso has [Graph
> Groups|http://docs.openlinksw.com/virtuoso/rdfgraphsecuritygroups/] feature
> to address this.
>
> It would be very useful if jena support such virtual default graphs easily
> Thanks again for great work.
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
