RE: Bug in IOTP's DTD

"Smith, Chris " <CHRIS.SMITH@royalbank.com> Fri, 15 October 1999 15:14 UTC

Received: from one.eListX.com (one.elistx.com [209.116.252.130]) by ietf.org (8.9.1a/8.9.1a) with SMTP id LAA14181 for <trade-archive@lists.ietf.org>; Fri, 15 Oct 1999 11:14:15 -0400 (EDT)
Received: from one.elistx.com by one.eListX.com id aa04422; 15 Oct 99 10:51 EDT
Received: from rbmail.royalbank.com by one.eListX.com id aa04410; 15 Oct 99 10:50 EDT
Received: id KAA12932; Fri, 15 Oct 1999 10:28:08 -0400
Received: by gateway ???
X-Server-Uuid: d237928a-6c98-11d3-985c-00a0c9ea509d
Received: by gateway id <48DV7KGC>; Fri, 15 Oct 1999 10:31:55 -0400
Message-ID: <2B30A9965635D311A29F002035297FFB1B2A1B@se001010.rbc1.royalbank.com>
From: "Smith, Chris " <CHRIS.SMITH@royalbank.com>
To: 'David Burdett' <david.burdett@commerceone.com>, "'hiroya@sdl.hitachi.co.jp'" <hiroya@sdl.hitachi.co.jp>
cc: "IETF Trade (E-mail)" <ietf-trade@lists.eListX.com>, "'kawatura@bisd.hitachi.co.jp'" <kawatura@bisd.hitachi.co.jp>, "'kent@differential.com'" <kent@differential.com>
Subject: RE: Bug in IOTP's DTD
Date: Fri, 15 Oct 1999 10:32:05 -0400
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2448.0)
X-WSS-ID: 1419E563236961-01-01
Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01BF171A.071BC634"
Sender: ietf-trade-owner@lists.eListX.com
Precedence: bulk
X-elistx: ietf-trade
Source-Info: From (or Sender) name not authenticated.

Interesting. The following is a rather subtle point, easily missed
when viewing the DTD (and NOT actually an error), but...

IOTP PackagedContent has

 <!ELEMENT PackagedContent (#PCDATA) >
 <!ATTLIST PackagedContent
  Name        CDATA            #IMPLIED
  Content     NMTOKEN          "PCDATA"
  Transform   (NONE|BASE64)    "NONE" >

while IOTP,DSIG has (corrected with removing the #IMPLIED)

 <!ELEMENT Value (#PCDATA) >
 <!ATTLIST Value
  ID          ID               #IMPLIED
  encoding    (base64|none)    'base64' >

Is there a specific reason that the attributes 
"encoding" and "Transform" don't agree on parameter
content and the default value of the parameter,
even though they are almost exactly the same
thing? Also, I can live with 'encoding' but this
is risking confusion with 'encoding' as it refers
to character sets like ISO-8859-1 (and as used on
the <?xml ...> XML declaration).

I realize that IOTP and DSIG are being worked on
independently, but could we have them be a little
less independent?

------------------------------------------------------------
 Chris Smith                                +1.416.348.6090
 Royal Bank                       chris.smith@royalbank.com


> -----Original Message-----
> From: David Burdett [mailto:david.burdett@commerceone.com]
> Sent: October 14, 1999 08:55 PM
> To: 'hiroya@sdl.hitachi.co.jp'
> Cc: IETF Trade (E-mail); 'kawatura@bisd.hitachi.co.jp';
> 'kent@differential.com'
> Subject: RE: Bug in IOTP's DTD
> 
> 
> Masaaki
> 
> I accept that there is a mistake in the IOTP DTD, however 
> this part of the IOTP DTD was copied **directly** from the 
> the IOTP dsig spec at
> 
> 	
> http://www.ietf.org/internet-drafts/draft-ietf-trade-iotp-v1.0
> -dsig-03.txt
> 
> which contains the same error. The only changes made when 
> copying were the removal of some blank lines and page headers 
> and footers.
> 
> The reason for copying in the IOTP dsig DTD is to avoid 
> having to use namespaces in IOTP.
> 
> So really what I think we should do is:
> 1. Fix the DTD in the IOTP dsig spec (Yoshiaki ?) and then
> 2. Fix the DTD in the IOTP spec.
> 
> Regards
> 
> David
> 
> -----Original Message-----
> From: Masaaki Hiroya [mailto:hiroya@sdl.hitachi.co.jp]
> Sent: Thursday, October 14, 1999 3:33 AM
> To: David Burdett
> Cc: hiroya@sdl.hitachi.co.jp
> Subject: Bug in IOTP's DTD
> 
> 
> 
> David
> 
> There is a bug in ietf.org/draft-ietf-trade-iotp-v1.0-protocol-06.
> 
> >  <!ELEMENT Value ( #PCDATA ) >
> >  <!ATTLIST Value
> >          ID               ID           #IMPLIED
> >          encoding    (base64|none)    #IMPLIED      'base64'
> 
> 
> I think #IMPLIED in the "encoding" attribute should be removed.
> 
> Draft-ietf-trade-iotp-v1.0-dsig-03.txt defines the Value 
> element as follows:
> 
> >    <!ELEMENT Value ( #PCDATA ) >
> >    <!ATTLIST Value
> >            ID                 ID            #IMPLIED
> >            encoding      (base64|none)     'base64'
> 
> Please correct the DTD in iotp-v1.0-protocol-06.
> 
> Masaaki
> 
> -----
> Masaaki Hiroya
> Systems Development Laboratory
> Hitachi, Ltd.
> tel: +81-44-549-1531
> fax: +81-44-549-1640
> email: hiroya@sdl.hitachi.co.jp
>