RE: Call for Implementation: Canonical XML Becomes a W3C Candidate Recommendation

Hi Gregor,

Actually, I understood your question a little better shortly after the last
email, though I wouldn't change anything in it at this time.

You are asking about the difference between what an XML processor must do
versus what information it must export to the application.

I don't recall anything that permits an XML processor to report less
information than it derives from the input.  In particular, I don't recall
anything that binds this concept to validating vs. non-validating
processors.

The closest we come to it is in the Conformance section of [XML], where
there is a reiteration of the idea that non-validating processors may vary
in their information output "depending on whether the processor reads
parameter and external entities".  But this is an instance of the processor
reporting less information because it has derived less from the possible
input (because it didn't read the input).

That in mind, I haven't gone looking through the spec for evidence to
support what you're thinking either, so I'd be happy to think about any
passage of the spec you may have come across that would substantiate a
behavioral difference.

Thanks,
John Boyer
Development Team Leader,
Distributed Processing and XML
PureEdge Solutions Inc.
Creating Binding E-Commerce
v: 250-479-8334, ext. 143  f: 250-479-3772
1-888-517-2675   http://www.PureEdge.com <http://www.pureedge.com/>



-----Original Message-----
From: w3c-ietf-xmldsig-request@w3.org
[mailto:w3c-ietf-xmldsig-request@w3.org]On Behalf Of Gregor Karlinger
Sent: Sunday, November 05, 2000 11:20 PM
To: John Boyer; Joseph M. Reagle Jr.; IETF/W3C XML-DSig WG
Subject: AW: Call for Implementation: Canonical XML Becomes a W3C
Candidate Recommendation


Hi John,

> Yes, non-validating parsers are supposed to recognize the types of
> attributes, unless they have been unable to read the declaration (e.g. due
> to external declaration), but c14n covers this too by requiring
> that such a
> processor be augmented to read the attribute types so that it can
> normalize
> attributes as if it were a validating processor.

That a non validating parser is required to normalize the attribute
values is ok. This is explicitley mentioned in XML 1.0 (Second Edition).

What I am not so sure about is, if a non-validating parser must support
structures which enable the application to select elements by the values
of ID attributes.

Regards, Gregor
---------------------------------------------------------------
Gregor Karlinger
mailto:gregor.karlinger@iaik.at
http://www.iaik.at
Phone +43 316 873 5541
Institute for Applied Information Processing and Communications
Austria
---------------------------------------------------------------

Received on Monday, 6 November 2000 12:07:37 UTC