Return-Path: Delivered-To: apmail-xml-xmlbeans-dev-archive@www.apache.org Received: (qmail 86717 invoked from network); 2 Jul 2004 21:31:15 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur-2.apache.org with SMTP; 2 Jul 2004 21:31:15 -0000 Received: (qmail 61410 invoked by uid 500); 2 Jul 2004 21:31:27 -0000 Delivered-To: apmail-xml-xmlbeans-dev-archive@xml.apache.org Received: (qmail 61299 invoked by uid 500); 2 Jul 2004 21:31:25 -0000 Mailing-List: contact xmlbeans-dev-help@xml.apache.org; run by ezmlm Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: Reply-To: xmlbeans-dev@xml.apache.org Delivered-To: mailing list xmlbeans-dev@xml.apache.org Received: (qmail 61258 invoked by uid 99); 2 Jul 2004 21:31:23 -0000 X-ASF-Spam-Status: No, hits=1.3 required=10.0 tests=RCVD_BY_IP,SB_NEW_BULK,SPF_HELO_PASS,SPF_PASS X-Spam-Check-By: apache.org Message-ID: Date: Fri, 2 Jul 2004 14:30:47 -0700 From: Noah Campbell To: xmlbeans-dev@xml.apache.org Subject: Re: xmlbeans xml security In-Reply-To: <83A0A695-CBBE-11D8-B6FD-000A95C89D86@akuma.org> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit References: <4B2B4C417991364996F035E1EE39E2E1DCE2F3@uskiex01.amer.bea.com> <1088699043.5276.33.camel@newlyn2.providerlink.com> <91D3E563-CBA4-11D8-B6FD-000A95C89D86@akuma.org> <5A2D8958-CBA8-11D8-B6FD-000A95C89D86@akuma.org> <83A0A695-CBBE-11D8-B6FD-000A95C89D86@akuma.org> X-Virus-Checked: Checked X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N I would be delighted to work together. Please let me know what I should work on so we're not overlapping. Noah On Thu, 1 Jul 2004 18:26:51 -0600, David Waite wrote: > > > On Jul 1, 2004, at 6:00 PM, Noah Campbell wrote: > > > I think we're on the same page in regards to this. I'm having to dig > > into the specs for c14n and at least how I interrept it the prefix of > > the QName from the localpart must be preserved in the original > > document. > > The full QName, prefix, namespace URI and local name must all be > preserved. > > > > > As I understand c14n (and I'm learning volumes as I prepare to > > implement a C14NSaver) the namespace is discarded in the > > cananocialized form. Sure the output is not xml valid, or namespace > > collisions cause a lossy form, but this is okay. The point is not to > > have a valid doc but a representation that will be unique on a byte > > level. > > The namespace definitions are always there if you canonicalize a full > document; redundant definitions are removed. Actually, only if you do > exclusive canonicalization on a partial document will namespaces be > removed, and only if no attributes or elements names included in the > canonicalized form are using them. The issue I stated below was that > the prefix was not preserved, so elements may switch prefixes on save > to whichever one happens to have precedence internally. This breaks > canonicalization, although it does not change the meaning of the > document. It also breaks infoset fidelity (xml-infoset , sections 2.2 > and 2.3 property 3). > > And I thought I was writing the C14NSaver. :) Would you like to work > together? > > > > -David Waite > > - --------------------------------------------------------------------- > To unsubscribe, e-mail: xmlbeans-dev-unsubscribe@xml.apache.org > For additional commands, e-mail: xmlbeans-dev-help@xml.apache.org > Apache XMLBeans Project -- URL: http://xml.apache.org/xmlbeans/ > > - --------------------------------------------------------------------- To unsubscribe, e-mail: xmlbeans-dev-unsubscribe@xml.apache.org For additional commands, e-mail: xmlbeans-dev-help@xml.apache.org Apache XMLBeans Project -- URL: http://xml.apache.org/xmlbeans/