W3C home > Mailing lists > Public > w3c-ietf-xmldsig@w3.org > July to September 2000

Re: Errors in Section SignatureProperties

From: Joseph M. Reagle Jr. <reagle@w3.org>
Date: Mon, 28 Aug 2000 15:04:12 -0400
Message-Id: <3.0.5.32.20000828150412.01abc6d8@localhost>
To: "Gregor Karlinger" <gregor.karlinger@iaik.at>
Cc: "XML" <w3c-ietf-xmldsig@w3.org>
At 11:37 8/28/2000 +0200, Gregor Karlinger wrote:
 >1. Since the content model is mixed, also a SignatureProperty  Element
 >   with no subelements, but only textual content should be allowed.
 >Therefore
 >   the minOccurs attribute should have a correct value of '0'
 
Ok. Fixed.

 >>   <!ELEMENT SignatureProperty %Object.ANY; >
 >>   <!ATTLIST SignatureProperty
 >>             Target CDATA    #REQUIRED
 >>             Id ID  #IMPLIED  >
 >
 >
 >>   <!ENTITY % Object.ANY
 >'(#PCDATA|Signature|SignatureProperties|Manifest)*'>
 >
 >2. The content model for SignatureProperty according to the DTD definition
 >allows
 >   also things like Signature and SignatureProperties, which are in the
 >namespace
 >   of XML-Signature. This is in contradiction with the declartion of
 >   namespace='##other' in the schema above.

Right. This isn't really a mistake as much as a best effort since the DTD is
limited (and I didn't want to create too many entities) and the schema
permits specificity and I know it wouldn't make sense just to throw a naked
signature in SignatureProperties... I could create a SignatureProperties.ANY
that was #PCDATA only, I could make the schema definition ##any, or leave it
as is. What's your preference?


_________________________________________________________
Joseph Reagle Jr.   
W3C Policy Analyst                mailto:reagle@w3.org
IETF/W3C XML-Signature Co-Chair   http://www.w3.org/People/Reagle/
Received on Monday, 28 August 2000 15:04:17 GMT

This archive was generated by hypermail 2.2.0 + w3c-0.29 : Thursday, 13 January 2005 12:10:11 GMT