- From: Scott Cantor <cantor.2@osu.edu>
- Date: Tue, 29 Dec 2009 15:30:50 -0500
- To: "'Frederick Hirsch'" <frederick.hirsch@nokia.com>, "'XMLSec WG Public List'" <public-xmlsec@w3.org>
- Cc: "'Pratik Datta'" <PRATIK.DATTA@oracle.com>, "'Ed Simon'" <edsimon@xmlsec.com>
Frederick Hirsch wrote on 2009-12-29: > We should add the following explanation, with some editing, to the 2.0 > requirements on prefix rewriting , agreed? That material is an oversimplification though. > [[ > After all, having the namespace prefixes covered by the signature > actually is some kind of violation of the idea of prefixes. As far as > I understood that concept, the prefixes don't have to be unique, and > may even be substituted within any processing instant if two prefixes > happen to cause a collision. The only requiredly unique setting is the > namespace uri and local name. Thus, if the (unlikely, agreed) case > happens that two XML documents are to be merged that both have the > same namespace prefix for different namespace uris, whereas XML > Signatures protect the chosen prefixes in both documents, you either > have to invalidate one of the signatures (by changing its prefixes) or > risk a processing collision (by keeping the same namespace prefix for > different uris). > ]] This assumes that you don't just ensure each piece is well formed to begin with, with appropriate namespace declarations in each document. Having done that, c14n takes care of signature integrity (modulo all the usual issues with QName content that make that very hard to achieve in practice and are NOT fixed by prefix rewriting). -- Scott
Received on Tuesday, 29 December 2009 20:31:28 UTC