On Monday 21 January 2002 12:16, you wrote: > On Mon, Jan 21, 2002 at 05:16:03PM +0000, Matt Sergeant wrote: > > Actually I'd welcome some sort of AxIgnorePI Yes/No option (default No, I > > guess). Is that about right? > > yes! please! I want exactly the same thing, an XSLT or CSS PI which I can > use when editing the file locally (ie bang it into IE5 or Opera), > but for it to be ignored when AxKit comes into operation on the web server.
Isn't the answer then to NOT have the PI in the original data? I mean if you sometimes need it and sometimes don't then the stylesheet isn't really PART of the document, its really a part of the processing chain that uses that document, so the processing chain should provide that information... In other words your base document stored on disk should NOT contain the PI, instead the request for the document should somehow specify what stylesheet to use. This could be accomplished in a number of ways, but one of the easiest would be to have the request ask for a document that was nothing but a "switch" that had a couple of conditional XSLT stylesheets that would provide the actual content, along with whichever PI was appropriate for the circumstances. This could also be accomplished with XSP or whatever, but the point is that the PI really doesn't belong in the document. PI's in documents should only be present when they are ALWAYS relevant. In effect putting a stylesheet reference in a document is turning the document into the equivalent of an object, an amalgamation of code and data. Sometimes that just isn't appropriate. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
