xpath namespace (was Re: DTB status (on today's agenda))

> 2) In any case which FULL URIs should I take for RIF builtins which come 
> from XPAth/XQuery?

On this issue, I'll note that we've been promised that XQuery/XSL will
talk about it today and get back to us.

   http://lists.w3.org/Archives/Public/public-qt-comments/2008Apr/0132.html

My sense right now is that (c) is best, but I might be missing some
reasons for (a).

        -- Sandro

> The following options exist:
> 
> a) define own prefixes (separate for functions and predicates):
> 
>   http://www.w3.org/2007/rif-builtin-predicates#numeric-equal
> 
>   http://www.w3.org/2007/rif-builtin-functions#concat
> 
> 
> b) define own prefix (same for functions and predicates):
> 
>   http://www.w3.org/2007/rif-builtins#numeric-equal
> 
>   http://www.w3.org/2007/rif-builtins#concat
> 
> c) reuse XPath/Xquery fn: prefix (problem: not prefix defined for op: we 
> still would need to invent one):
> 
>   http://www.w3.org/2005/xpath-??????#numeric-equal
> 
>   http://www.w3.org/2005/xpath-functions#concat
> 
> 
> d) use the URIs in the XPath, XQuery document:
> 
>   http://www.w3.org/TR/xpath-functions/#func-numeric-equal
> 
>   http://www.w3.org/TR/xpath-functions/#func-concat
> 
> e) an older proposal was to use actually symbol spaces for 
> builtin-functions and -predicates
> 
>   "numeric-equal"^^http://www.w3.org/2007/rif-builtin-predicates
>   "numeric-add"^^http://www.w3.org/2007/rif-builtin-functions
> 
> 
> I personally prefer a) and suggest to
> 
> PROPOSE: We define own namespace prefixes
>    PREFIX("pred", "http://www.w3.org/2007/rif-builtin-predicates#").
>    PREFIX("func", "http://www.w3.org/2007/rif-builtin-functions#").
> for RIF builtin functions and predicates

> Dr. Axel Polleres, Digital Enterprise Research Institute (DERI)
> email: axel.polleres@deri.org  url: http://www.polleres.net/
> 
> rdfs:Resource owl:differentFrom xsd:anyURI .