Just a heads up... I heard the other day that there may be a problem
with Xerces not performing attribute value normalization with validation
turned off. You will also certainly not get Schema related things like
attribute defaults without validation turned on (though there are other
issues there...)
The issue seems related to the XML processing model debates. There are
two possible ways of interpreting the validation feature. In the first
model, the processor always behaves as the XML spec says a validating
processor behaves, and it is using the feature to indicate whether or
not to report validation failures. After all, the spec says that failures
of validity constraints are reported "at user-option" and SAX documents
the feature as:
http://xml.org/sax/features/validation
true: Report all validation errors (implies external-general-entities
and external-parameter-entities).
false: Do not report validation errors.
In the second model, the processor treats the validation setting as a
control for when the processor is a "validating processor" and when it
is a "non-validating processor". The spec is pretty clear on what a
validating processor must do, and much more wishy-washy about what a
non-validating processor must do. Since, for example, the latter does
not need to read all of the entities referrenced in the document, this
processing model is not a very good one for use with an XSLT processor.
The problem is that Xerces tends to think of the validation feature
is terms of the second model, not the first. Therefore, the option
as implemented by Xerces does not mean "fully-conformant validating
processor that does not report validation errors" the way that SAX
specifies and the way that Xalan would want. This is a problem with
Xerces that should be fixed on their end.
Regards,
Glenn
Scott Boag/CAM/Lotus@Lotus on 06/20/2001 10:11:08 AM
Please respond to [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
cc: [EMAIL PROTECTED]
Subject: Re: Antwort: Re: Antwort: [Bug 2124] - Status of SAXSource is
changed in Xalan 2.1.0
ID processing seems to work OK these days without dynamic validation being
turned on, so I simply commented out the setting of dynamic validation for
the source tree (I should do it for the stylesheet also, but, one thing at
a time). Please give it another try.
-scott
Scott Boag
To: [EMAIL PROTECTED]
06/20/2001 cc: [EMAIL PROTECTED]
09:17 AM Subject: Re: Antwort: Re:
Antwort: [Bug 2124] - Status of SAXSource
is changed in Xalan 2.1.0(Document
link: Scott Boag)
Thomas, I am getting more and more confused by this.
Dynamic validation has, in fact, been turned on for a long time, correct?
The only thing that is different in the recent code is that errors are
being properly reported, correct?
-scott
Scott Boag
To: [EMAIL PROTECTED]
06/20/2001 cc:
08:42 AM Subject: Re: Antwort: Re:
Antwort: [Bug 2124] - Status of SAXSource
is changed in Xalan 2.1.0(Document
link: Scott Boag)
> If XSLT 2.0 becomes W3C Recommendation (or working draft) then it
> contingently makes sens to use dynamic validation as default because you
> need it to use the XMLSchema.
The id(...) function won't work correctly with validation turned off now,
correct?
-scott
Thomas2.Maesing
@bgs-ag.de To: [EMAIL PROTECTED]
cc: (bcc: Scott
Boag/CAM/Lotus)
06/20/2001 Subject: Antwort: Re:
Antwort: [Bug 2124] - Status of SAXSource is
04:00 AM changed in Xalan 2.1.0
Please respond
to xalan-dev
Yes,
I think so because it is the default behavior from xalan-j 1(in a later
version it was switched on, but as specified in the documentation of itself
it
should not. But this was no problem because errors did not stop the
transformation) up to xalan-j_2_1_0. It is also the default
behavior of Saxon.
I have found nothing in the XSLT Spec that a XSLT Processor should be a
validating XMLProcessor for the Source Document.
I also have found nothing in JAXP 1.1 Spec regarding to the transform
package.
So in my opinion at the time it should not be used as default.
If XSLT 2.0 becomes W3C Recommendation (or working draft) then it
contingently makes sens to use dynamic validation as default because you
need it to use the XMLSchema.
Regards
Thomas
[EMAIL PROTECTED] am 19.06.2001 19:18:36
Bitte antworten an [EMAIL PROTECTED]
An: [EMAIL PROTECTED]
Kopie:
Thema: Re: Antwort: [Bug 2124] - Status of SAXSource is changed in Xalan
2.1.0
Hi Thomas. I just want to be clear. You are proposing to turn off dynamic
validation altogether?
> Another possible way is to provide the direct validation/dynamic feature
> to the user
> as Attribute (via setAttribute(java.lang.String name, java.lang.Object
> value)) .
No. I don't want to get into the business of setting properties on the
XMLReader... that's what SAXSource is there for.
I think dynamic validation is the right default, but I understand your
problem. I really think this is a sort of Parser bug, but that's only my
opinion, and doesn't help much right now. I'll look into it a bit further.
-scott
