[JENA-2152] Persisting constituent named graphs config for default graph of custom dataset view.

• Type: New Feature
• Status: Closed
• Priority: Major
• Resolution: Information Provided
• Component/s: Fuseki
• Labels: SPARQL dataset defaultGraph fuseki
• Assignee: Unassigned
• Reporter: damodara
• Created: 20/Aug/21 04:46
• Updated: 19/Dec/21 10:36
• Resolved: 02/Sep/21 11:42

Description

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.

 

And Virtuoso has  Graph Groups feature to address this.

 

It would be very useful if jena support such virtual default graphs easily

Thanks again for great work.