Steven Noels wrote: > > Carsten Ziegeler wrote: > > > Ok, this could solve many problems, but what about: > > > > <cinclude src="http://post_to_my_xml_database";> > > <content> > > <document> > > <bla/> > > .. > > </document> > > </content> > > </cinclude> > > > > (I leftout some parts, but I think it's clear what I want to say) > > With the above you can send a complete XML document to somewhere > > and get a response which is then included. It's not possible > > to convert a complete XML document to an attribute value. > > Never thought of such a use case (seems hackish to me, and a case for a > SWT-like thing, but anyway). > :) - the example above might lead to this. Ok, believe me, it's not hackish. There are 3rd party data providers that require a post of an XML document in order to get data. So, if you want to include them, you need the above. Sad but true.
> Getting back to the schema, any extra attribute _and_ child element on > the xi:include are supported, so you could have something like this IIUC: > > <xi:include href="http://post-to-my-xml-thing";> > <content> > <document> > <bla/> > </document> > </content> > </xi:include> > > It would of course be up to the XInclude transformer to implement the > correct (and non-standard) behaviour then, but the standard syntax > supports it apparently. I don't find any specification on the processing > that should occur on the child-elements of xi:include, but we can ask > the authors. > Ah, ok, if that is possible, we could add the extra behaviour as child elements and still conform to the standard. That's ok for me. Carsten --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
