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

Re: XMLDSIG Interop in connection with 48th IETF

From: Joseph M. Reagle Jr. <reagle@w3.org>
Date: Tue, 18 Jul 2000 14:34:29 -0400
Message-Id: <3.0.5.32.20000718143429.00ace100@localhost>
To: "IETF/W3C XML-DSig WG" <w3c-ietf-xmldsig@w3.org>
[I'm forwarding this to this list because it's easier to track.]

Forwarded Text ----
 To: "Joseph M. Reagle Jr." <reagle@w3.org>
 From: Merlin Hughes <merlin@baltimore.ie>
 Subject: Re: XMLDSIG Interop in connection with 48th IETF 
 In-reply-to: <3.0.5.32.20000718130700.00a9fd20@localhost> 
 Date: Tue, 18 Jul 2000 19:30:42 +0100
 Status:   
 
 
 r/reagle@w3.org/2000.07.18/13:07:00
 >How do you mean broken? Kevin has pointed out one problem and alluded to
 >others, if you guys point them out, I'll be happy to fix them in the next
 >version.
 
 Some minor inconsistencies:
 
 4.4.3 RetrievalMethod
 
 Schema has Encoding attribute on both RetrievalMethod and Type
 elements but DTD has Encoding attribute just on Type element.
 DTD correct?
 
 Then in the DTD on file, there is no Type element defined.
 
 The Schema has mandatory content for the Type element. This
 seems wrong because it can't then be implemented interoperably
 without further specification.
 
 4.3.3.1 Transform
 
 In the schema, the "XPath" element is case-incorrect "Xpath".
 
 Merlin Hughes
 Baltimore Technologies, plc
 
End Forwarded Text ----

_________________________________________________________
Joseph Reagle Jr.   
W3C Policy Analyst                mailto:reagle@w3.org
IETF/W3C XML-Signature Co-Chair   http://www.w3.org/People/Reagle/
Received on Tuesday, 18 July 2000 14:34:38 GMT

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