- From: James Fuller <james.fuller.2007@gmail.com>
- Date: Wed, 27 Aug 2008 12:24:06 +0200
- To: mozer <xmlizer@gmail.com>
- Cc: "Florent Georges" <fgeorges@fgeorges.org>, "Norman Walsh" <ndw@nwalsh.com>, public-xml-processing-model-comments@w3.org
On Wed, Aug 27, 2008 at 12:20 PM, mozer <xmlizer@gmail.com> wrote: > James, > > Not really, since the *foreign element* have already the meaning of > calling and user defined step > > Suppose we allow foreign element and the mechanism we already have : > > then when the pipeline processor encounter > > <foreign:element> > ... > </foreign:element> > yes, but isnt that what declarations are for ? e.g. that foreign element *needs* a declaration before it is be used as as step, even if this is internally my impl refers to a std, optional and my own external declaration (as imports). > It won't know if : > * this was supposed to be a call to a user defined step, that has not > been declared > * or if it is just a foreign element, that could be user for anything > > So having this element, has also the big advantage of allowing tools > the detect quickly bugs once again, I dont see the problem allowing this. ta, Jim
Received on Wednesday, 27 August 2008 10:24:42 UTC