[Versa] Question about query

[Michael Olson]

On Sep 4, 2005, at 6:03 PM, Uche Ogbuji wrote:

> On Sun, 2005-09-04 at 13:24 -0400, Chimezie Ogbuji wrote:
>>> What does it mean for a Versa resource data type to be the actual
>>> resource itself, and not just its name?  It hurts my head to try to  
>>> make
>>> sense of that.  I think these are just names, and therefore I draw  
>>> the
>>> opposite conclusion.
>>
>> I think of it as a name of an actual resource that resides in the
>> underlying RDF graph.  The  last part - for me - is the more important
>> distinction.  I guess my question is what is an example use case of a
>> URI reference to a resource that does not exist in the RDF graph?
>
> As simple as
>
> all() -> dc:creator -> eq(<mailto:foo at yahoo.com>)
>
> It's possible when the query is formulated that <mailto:foo at yahoo.com>
> is not in the graph.  According to this magic implication we're talking
> about, this should instantly become the empty set.  Or are we saying
> that we would *mandate* lazy determination of the value of that item?
>


Not at all.  The problem is you are mixing queries with function  
arguments.  As I've said in other parts of this thread, resource  
literals are treated differently when they are function arguments for  
exactly the reasons that you mention.

What I originally asked was what does this query return

<mailto:foo at yahoo.com>

Just this as a query.  From your example, it is used in the predicate  
expression of your traverse.


In the case of the predicate of a traverse, it is logical to call it a  
"filter".

As a top level query, I don't think that it is a "filter" as there is  
nothing to filter.

> And what of the simple query
>
> <mailto:foo at yahoo.com> = <mailto:bar at yahoo.com>
>

Why does it matter what is on the left or right side of the equals?  If  
we decide that <uri> is a query, then you are comparing two queries in  
the model.  If you want to compare uris then compare them as strings.

Mike
------------------------------------------------------------------------ 
---------------
Mike Olson                                                Principal  
Consultant
mike.olson at fourthought.com                +1 720 253 4662
Fourthought, Inc.                                       
http://Fourthought.com
PO Box 270590,                                       http://4Suite.org
Louisville, CO 80027-5009, USA
XML strategy, XML tools, knowledge management