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

Errors in 10-May-2000 draft

From: Gregor Karlinger <gregor.karlinger@iaik.at>
Date: Mon, 29 May 2000 11:10:56 +0200
To: "Joseph M. Reagle Jr." <reagle@w3.org>, "XML" <w3c-ietf-xmldsig@w3.org>
Message-ID: <NDBBIMACDKCOPBLEJCCDKELKCFAA.gregor.karlinger@iaik.at>
Hi Joseph,

as I read your reply to Don's error report today, I recognized that I did
send you the list of errors I have found in the draft (for whatever reason

So here are the errors I have found; I hope you find it useful despite the

Section 1.3, last paragraph (macro definition):

  I think the file extension in "xmldsig-core-schema.dtd" is misleading
  here. Please replace it with ".xsd", as done in section 9.

Section 2.0, example:

  Left parenthesis is missing before the Reference clause.

Section 2.1, example:

  Alg ids for CanonicalicationMethod (line s03) and Transform (line s07)
  are outdated.

Section 2.1, last paragraph:

  Keyword OPTIONAL is misused here. Should be written in small letters.

Section 2.2, first paragraph:

  Replace "use as foo:assuredby attribute" with "use a foo:assuredby

Section 3.2.2:

  Adapt section since there is a default c14n now.

Section 4.1, Schema definition:

  Attribute Id should be declared with optional use.

Section 4.2, last sentence:

  The Schema defintion for SignatureValue does not allow own encodings for
  specified algorithms.

Section 4.3.1, first paragraph:

   * Paragraph sould be adapted for default c14n.

   * Refers to section "6.1 Algorithm Identifiers", should be "6.1 Algorithm
     Identifiers and Implementation Requirements"

Section, third paragraph:

   The words MimeType, Charset should be set in normal font, since they are
no longer
   defined as attributes.

Section, Schema definition:

   Why use mixed content Ttransform?

Section, DTD:

   Reject MimeType and Charset attributes

Section, last sentence:

  Reference to section 6.1 should be adapted (see my remark on section

Section 4.4, Schema defintion:

  * KeyInfo: maxOccurs in clause choice should be unbounded instead of 1

  * KeyInfo <any> Element is missing in clause choice, otherwise it is not
    that applications place their own semantics within this element, as the
    textual description says.

  * KeyValue: Why mixed content model?

Section 4.4, DTD:

  * Replace Element content model for KeyInfo by an internal entity to allow
    application specific sematics.

  * Content model for KeyName, RetrievalMethod, MgmtData is wrong

Section 5.1, Schema definition:

  * Why use <sequence> in type definition?

  * Either minOccurs='1' is wrong or the content model of the corresponding
DTD Element
    declaration (Reference*)

Section 6.1, first paragraph, third sentence:

  Adapt sentence for default c14n.

Section 6.3, first paragraph:

  Adapt paragraph for default c14n.

Section 6.4, first paragraph:

  Adapt paragraph for default c14n.

Section 6.6, first paragraph:

  Adapt paragraph, since MimeType and Charset attributes no longer exist.

Section 6.6.2:

  Remove quoted printable.

Section 7.1

  I think your remark in the first ordered list, item 2 actually belongs to
the second
  ordered list, item 2.

Regards, Gregor
Gregor Karlinger
Phone +43 316 873 5541
Institute for Applied Information Processing and Communications
Received on Monday, 29 May 2000 05:11:37 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:21:33 UTC