Hi Venu, In order to make this work we have to somehow deliver these properties to the parser at the point where the input stream is opened. This is in XMLEntityManager.
Aside from the name and package suggested for this class, I like the general idea. XMLEntityManager is a general parser component, so I would prefer an extension which has more general semantics (RequestPropertyInputSource?) which could be reused perhaps in the future for other standards which allow request properties to be specified, instead of special casing XInclude (which is still experimental). Regarding Elliotte's note about changes to XInclude, some of which are directly related to these accept attributes [1][2], if a draft is coming in the near future we should probably wait. [1] http://lists.w3.org/Archives/Public/www-xml-xinclude-comments/2004Feb/0014.html [2] http://lists.w3.org/Archives/Public/www-xml-xinclude-comments/2004Mar/0001.html On Tue, 2 Mar 2004, Venu wrote: > Hi All, > > In order to support content negotiation for parse=xml [1], I suggest > that we create a new Class(say XIncludeInputSource [3]) by extending > XMLInputSource and have setter and getter methods to store and retrieve > Http parameters [2] .We will use this instead of XMLInputsource when a > document is being included. > > Any suggestions or comments ? --------------------------- Michael Glavassevich XML Parser Development IBM Toronto Lab E-mail: [EMAIL PROTECTED] E-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
