Re: justify or remove aliases: base-uri, resolve-uri

Dan Connolly <connolly@w3.org> writes:

> The xproc spec makes aliases of fn:base-uri and fn:resolve-uri:
[...]
> Please add rationale for the aliases or take them out.

Indeed, as this thread reveals, they are not strictly-speaking
aliases, but the prose is not clear on this point. I propose to make
the following editorial changes:

  2.7.5 Base URI

  Returns the base URI of the specified node, if it has one. This
  function provides an interoperable way for XPath 1.0 based
  processors to access the base URI of a node. It is conceptually the
  same as the XPath 2.0 fn:base-uri() function.

  If no argument is specified, the context item is taken to be the
  argument.

  This function returns the [base-uri] property of its argument, or
  the empty string if no base URI is defined for that argument or
  argument type.

  Note:

    This function is defined in our namespace because it would be
    inappropriate to require XPath 1.0 based processors to support the
    fn:base-uri function; it's semantics are deeply rooted in the
    XPath 2.0 data model which differs from the XPath 1.0 data model.

With similar changes to p:resolve-uri.

Does this justification satisfy you?

                                        Be seeing you,
                                          norm

-- 
Norman Walsh <ndw@nwalsh.com> | When we are tired, we are attacked by
http://nwalsh.com/            | ideas we conquered long ago.-- Nietzsche