Hi Donald, >> 2. Question: How did you check the 3rd processor requirement: >> "Implementations MUST NOT be implemented with an XML parser that >> converts relative URIs to absolute URIs." . How should a parser (like >> Xerces) convert a URI? Does a parser understands what a URI is? > Don't know about a parser but a schema verifier would, I think. > If it knows that some attribute value is a URI, who knows what > it might do to it... knowledge can be a dangerous thing. OK, this relates to Schema. My question is: Do we have some test vectors (like 3.1-3.7 examples in the c14n spec) that define the correct behaviour? I'm looking for test vectors (correct and bad ones) that allow me to ensure functionality of my implementation. For instance I want to ensure that an input like <absolute:correct xmlns:absolute='http://www.absolute.org/#likeVodka'> <relative:incorrect xmlns:relative='../cheating#away'> </relative:incorrect> </absolute:correct> throws an CanonicalizationException because of the use of relative URIs. Do we have something like this for the above topic? Question to IBM and IAIK: How did you test this behaviour? Regards, ChristianReceived on Monday, 30 July 2001 09:35:21 GMT
This archive was generated by hypermail 2.2.0 + w3c-0.29 : Thursday, 13 January 2005 12:10:13 GMT