On Friday, 12/13/2002 at 10:57 EST, [EMAIL PROTECTED] wrote: > But in PSVI (the result of schema validation), nothing was made special for > whitespaces within elements with element-only content. So it *seems* that > schema doesn't want to make such distinction. This is why the parser > doesn't (and I don't think it should) have a feature for that.
I agree that this is a good justification for why the parser's existing suppress-ignorable-whitespace feature shouldn't use the schema information. But given that that feature is already a departure from basic XML processing (according to the XML REC, a processor should indicate which text is "whitespace in element content", not remove it), I don't see that there'd be anything wrong with adding a second feature which applies the same kind of filtering based on PSVI information. As long as the default is not to do so, it's harmless at worst and potentially useful. > So IMO, if people really think that > "schema-element-only-content-whitespace" is a significant concept and > should be marked special by a processor, then such requirement should be > raised to the schema WG I believe we should prototype it, establish that it is or isn't useful, then submit the idea and that evidence to the schema WG. But I currently don't have the cycles to submit a proposed patch, and I wouldn't be the one making the decision on whether to accept that patch into the Xerces code base, so feel free to take my opinion with the appropriate-sized block of salt. ______________________________________ Joe Kesselman / IBM Research --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
