- From: Yves Raimond <Yves.Raimond@bbc.co.uk>
- Date: Thu, 20 Oct 2011 12:38:42 +0100
- To: Pierre-Antoine Champin <pierre-antoine@champin.net>
- Cc: Jeremy Carroll <jeremy@topquadrant.com>, RDF Working Group WG <public-rdf-wg@w3.org>
On Wed, Oct 19, 2011 at 08:10:36AM +0000, Pierre-Antoine Champin wrote:
> Is that just me, or does this use case relate to the one from the BBC
> [1] ? More precisely, aren't the notion of subdataset and the notion of
> slice somewhat aligned?
One is purely hierarchical, and the other allows for overlaps between datasets, I'd think?
In any case, yes, it's strongly related.
Best,
y
>
> pa
>
> [1]
> http://www.w3.org/2011/rdf-wg/wiki/TF-Graphs-UC#.28A_PRIORITY.29_Slicing_datasets_according_to_multiple_dimensions
>
> On 10/14/2011 04:06 AM, Jeremy Carroll wrote:
> >
> > TopQuadrant code routinely queries datasets that are provided by other
> > vendors; hence we have an interest in the dataset abstractions that are
> > provided in the standard.
> >
> > A particular area of interest for TopQuadrant is that we often want to
> > have a simple dataset algebra, where given a dataset with some set of
> > graph names N = { n1, n2, .... nk }, we may want to run a query against
> > a subdatset M of N, consisting of only some of the ni, e.g. M = { n3, n4 }.
> > Given such a capability then, at least over the powerset of N, we can
> > provide the usual set theoretic operators of union and intersection to
> > implement a change of application focus by considering a different
> > subdataset.
> >
> > I am wondering what is the best way to add this issue to the mix here. I
> > could write up a use case: would that be helpful?
> >
> > Jeremy
> >
> >
> >
>
>
Received on Thursday, 20 October 2011 11:39:13 UTC