RE: Namespaces, schemas, Simon's filters.

["Fuchs, Matthew" <matthew.fuchs@commerceone.com>]

Uh, yes.  I meant

> <a:baz xmlcont:a="foo">
>   <a:e1/>
>   <a:e2/>
> </a:baz>

It was obviously too late in the day for me to be writing to this group.

Thanks,

Matthew

> -----Original Message-----
> From: Peter Piatko [mailto:piatko@research.telcordia.com]
> Sent: Wednesday, August 29, 2001 7:19 PM
> To: Fuchs, Matthew; 'Tim Bray'; xml-dev@lists.xml.org
> Subject: Re: Namespaces, schemas, Simon's filters.
> 
> 
> 
> ----- Original Message -----
> From: "Fuchs, Matthew" <matthew.fuchs@commerceone.com>
> To: "'Tim Bray'" <tbray@textuality.com>; <xml-dev@lists.xml.org>
> Sent: Wednesday, August 29, 2001 4:11 PM
> Subject: RE: Namespaces, schemas, Simon's filters.
> 
> 
> > However, it has been argued that a serious lacuna in the 
> original NS rec
> is
> > the lack of an attribute to specify a namespace that 
> applies only to the
> > _content_ of the current element, not the element itself.  
> Let's call it
> > xmlcont for the moment.  Having such a thing would be very 
> convenient,
> both
> > for validating and non-validating applications.  For example, if I'm
> > inserting in one element content from another, with xmlcont 
> I don't need
> to
> > worry about prefix collisions, eg:
> >
> > Source:
> > <a:foo xmlns:a="foo">
> >   <a:e1/>
> >   <a:e2/>
> > </a:foo>
> >
> > Target:
> >
> > <a:baz/>
> > where a is defined somewhere above.
> >
> > Result:
> >
> > <a:foo xmlcont:a="foo">
> >   <a:e1/>
> >   <a:e2/>
> > </a:foo>
> >
> 
> Did you mean the following for the Result:
> 
> <a:baz xmlcont:a="foo">
>   <a:e1/>
>   <a:e2/>
> </a:baz>
> 
> Or is it just too late in the day for me to be reading this 
> mailing list?
> ;-)
> 
> Thanks,
> 
> Peter
> 
> 
>