|
[XML-DEV Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message] RE: Namespaces, schemas, Simon's filters.
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@r...] > Sent: Wednesday, August 29, 2001 7:19 PM > To: Fuchs, Matthew; 'Tim Bray'; xml-dev@l... > Subject: Re: Namespaces, schemas, Simon's filters. > > > > ----- Original Message ----- > From: "Fuchs, Matthew" <matthew.fuchs@c...> > To: "'Tim Bray'" <tbray@t...>; <xml-dev@l...> > 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 > > >
|
PURCHASE STYLUS STUDIO ONLINE TODAY!Purchasing Stylus Studio from our online shop is Easy, Secure and Value Priced! Download The World's Best XML IDE!Accelerate XML development with our award-winning XML IDE - Download a free trial today! Subscribe in XML format
|
|||||||||

Cart








