RE: namespace node implementation

> if saxon is using the name representation described in the earlier 
> message, the apparent namespaces at the time when the parent 
> was parsed 
> cannot affect the correctness of the model produced by this 
> operation. 
> neither the bindings apparent when the expressions were parsed nor 
> those when the expressions were compiled.

I'm sorry, I simply do not understand this sentence (or one-and-a-half
sentences).

Firstly, I don't see why the way I represent names internally should prevent
me from producing the correct output.

Secondly, I don't understand the distinction you are making between "when
the expressions were parsed" and "when the expressions were compiled".

And I'm not sure I understand what you mean by "apparent namespaces".

Michael Kay


> 
> > Right, and that's the problem I'm concerned about (assuming we're
> > talking about the same thing).  Given:
> >
> > let $a := <a xmlns:ns1="NS1"><b ns1:x="X"/></a>
> > let $c := <c xmlsns:ns2="NS2">{$a/b}</c>
> >
> > what is the result of get-in-scope-namespaces($c/b)?  It could be:
> 
> it does not matter what get-in-scope-naemspaces returns.
> 
> ? (defparameter $a (root (parse-document "<a xmlns:ns1='NS1'><b 
> ns1:x='X'/></a>")))
> $A
> ? (defParameter $c (root (parse-document "<c 
> xmlns:ns2='NS2'></c>"))) $C ? (setf (children $c) (children 
> $a)) (#<ELEM-NODE ||::\b 2 #x1693E16>) ? (write-node $c 
> *trace-output*) <c xmlns:ns2='NS2'><b ns1:x='X' 
> xmlns:ns1='NS1' /></c> #<ELEM-NODE ||::\c 1 #x169979E> ?
> 
> with the appropriate model for names, it is possible to produce a 
> correct result document without any "in-scope namespaces."
> 
> ...
>