W3C home > Mailing lists > Public > www-rdf-interest@w3.org > January 2004

Query across multiple models

From: Bob MacGregor <macgregor@ISI.EDU>
Date: Fri, 09 Jan 2004 09:45:28 -0800
Message-Id: <6.0.1.1.0.20040109090425.01c77ec0@tnt.isi.edu>
To: jena-dev@yahoogroups.com, www-rdf-interest@w3.org
<offshoot of a tiny Jena thread>

The fact that we can't query against a set of models reflects a problem
with RDF that can be expected to grow much more serious over time.
Basically, anyone who is doing serious RDF work is going to have
a lot of models, and most queries will run against multiple models.

What's needed to begin with is a formal means for defining the equivalent of
(dynamic) "union"
models.  The current Jena union is static (I think).  If   U represents the 
union
of A and B, and updates are made to A or B, those updates are not reflected
in U.  This is not acceptable in the long run.

There are, of course, many ways to define union.  The "import ontology" 
construct
in OWL is a somewhat badly-conceived means for doing so.  So adding this
is something that would probably take a committee quite a while to hash out.

Right now, there is a lot of bookkeeping that has been thrust on users because
the boundaries of the RDF spec cut off prematurely.  RDF has nothing today
resembling union, and it should have.  Until it does, RDF-based 
applications will not scale
gracefully to multiple model situations.

Cheers, Bob

At 01:54 PM 1/8/2004, Seaborne, Andy wrote:
>Andreas,
>
>You can create a union model and ask a query of that model: this will ask
>the query over both of the submodels.
>
>There is no optimization done by the union model: because it does not know
>in which model properties might be, it ask each model for each part of the
>query pattern.  If both the models are in the same database, then,
>currently, this would not be optimized to pass a single query down that will
>work against both models.  It could be but as there are different
>possibilities for database layout, the number of possible optimizations
>schemes grows.
>
>Such optimizations are possible with the architecture, they just aren't
>implemented.  You could write a specialization of the union model that
>optimized queries base on application-specific knowledge of where
>information is to be found.
>
>       Andy
>
> > ----Original Message----
> > From: andreasharth <mailto:andreasharth@yahoo.com>
> > Date: 8 January 2004 19:17
> >
> > Hi,
> >
> > I want to have a (RDQL) query that spans two or more models.  For
> > example, get dc:title for 
> <<http://example.org/sample>http://example.org/sample> from modelA and
> > get dc:description for the same URI from modelB.  The query I have in
> > mind is more complicated, but that's basically the functionality I am
> > looking for.
> >
> > What would be the best way to query across multiple models in Jena2?
> >
> > Thanks,
> > Andreas.
> >
> >
> >
> >
> > Yahoo! Groups Links
> >
> > To visit your group on the web, go to:
> > 
> <http://groups.yahoo.com/group/jena-dev/>http://groups.yahoo.com/group/jena-dev/ 
>
> >
> > To unsubscribe from this group, send an email to:
> > jena-dev-unsubscribe@yahoogroups.com
> >
> > Your use of Yahoo! Groups is subject to:
> > <http://docs.yahoo.com/info/terms/>http://docs.yahoo.com/info/terms/
>
>
>----------
>Yahoo! Groups Links
>    * To visit your group on the web, go to:
>    * 
> <http://groups.yahoo.com/group/jena-dev/>http://groups.yahoo.com/group/jena-dev/ 
>
>    *
>    * To unsubscribe from this group, send an email to:
>    * 
> <mailto:jena-dev-unsubscribe@yahoogroups.com?subject=Unsubscribe>jena-dev-unsubscribe@yahoogroups.com 
>
>    *
>    * Your use of Yahoo! Groups is subject to the 
> <http://docs.yahoo.com/info/terms/>Yahoo! Terms of Service.

=====================================
Robert MacGregor
Senior Project Leader
macgregor@isi.edu
Phone: 310/448-8423, Fax:  310/822-6592
Mobile: 310/251-8488

USC Information Sciences Institute
4676 Admiralty Way, Marina del Rey, CA 90292
=====================================
Received on Friday, 9 January 2004 12:45:43 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 7 December 2009 10:52:04 GMT