[XML-DEV Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message]

Re: [good] Question about NS 1.1

• To: xml-dev@l...
• Subject: Re: [good] Question about NS 1.1
• From: james anderson <james.anderson@s...>
• Date: Tue, 09 Apr 2002 23:13:10 +0200
• Organization: nil
• References: <001f01c1dffa$539d7290$6501a8c0@pcukmka>
• Reply-to: james.anderson@s...

Michael Kay wrote:
> 
> > isn't any application better off processing the specialized values in
> > the parser's dynamic context than trying to resolve the conflicts
> > inherent in dragging that context around indefinitely? from the
> > descriptions which i have seen, the status of such values is known at
> > the point where they are parsed. are there cases where that
> > is not true?
> 
> yes, if the value has been blindly copied by an application that didn't know
> that the value had a dependency on the context. That's exactly what the
> whole XSLT-namespace problem is about.
> 

yes, but what value has been "blindly copied". where those attributes
values or element content which are declared to be in the QName domain
are processed in the parser's context, there are no lexical values -
which could exhibit a dependancy - to copy. where the application
introduces values it must introduce values in the correct domain.

it's as though one were to expect binary code to carry around the base
at which the aritmethic constants were read when the program was
compiled for the full life cycle of the program. or worse yet, the name
of the compiler setting to which the read base was bound together with
the setting at the point in time when the program was read. 

...

• Follow-Ups:
  • RE: [good] Question about NS 1.1
    • From: "Michael Kay" <michael.h.kay@n...>

• References:
  • RE: [good] Question about NS 1.1
    • From: "Michael Kay" <michael.h.kay@n...>

• Prev by Date: Re: WD for Namespaces 1.1
• Next by Date: Re: Entities
• Previous by thread: RE: [good] Question about NS 1.1
• Next by thread: RE: [good] Question about NS 1.1
• Index(es):
  • Date
  • Thread