W3C home > Mailing lists > Public > public-rdf-dawg@w3.org > October to December 2004

Re: URIs in constraints, isBound, casting in eq

From: Seaborne, Andy <andy.seaborne@hp.com>
Date: Mon, 22 Nov 2004 20:23:53 +0000
Message-ID: <41A24AD9.4050104@hp.com>
To: Dan Connolly <connolly@w3.org>
Cc: RDF Data Access Working Group <public-rdf-dawg@w3.org>



Dan Connolly wrote:
> On Mon, 2004-11-22 at 18:47 +0000, Seaborne, Andy wrote:
> 
>>Dan Connolly wrote:
> 
> [...]
> 
>>>We can introduce something ala log:uri if we want
>>>to do that sort of use/mention level-breaking:
>>>
>>>	WHERE dc:title log:uri ?TITLEURI
>>>	AND ?TITLEURI =~ /^http:/
>>
>>I'd prefer to reuse the function fn:string() from F&O that stringify's anything 
>>it's give
> 
> 
> anything including RDF Properties? (not the name of a property, but
> the property itself)
> 
> I don't think this works.

Not sure where properties themselves come into it.  It's the URI  - there 
aren't properties or resources in the query data model.  There are 
URIrefs, bNodes and RDF literals.

So fn:string() applied to a URIref is log:uri isn't it?  Just with a 
syntax that is more suited to the usage in expressions.

	Andy

> 
> 
>> as we already have a syntax for expressions.  I just had that implicit 
>>in the =~ operation.  On typed literals, it would be the lexical form.
>>
>>	string(dc:title) =~ /^http:/
>>
>>	Andy
Received on Monday, 22 November 2004 20:24:26 GMT

This archive was generated by hypermail 2.3.1 : Tuesday, 26 March 2013 16:15:21 GMT