OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

dss message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: RE: [dss] Groups - Digital Signature Service Core Protocols, Elements, and Bindings (oasis-dss-1.0-core-spec-wd-33pre9.doc) uploaded


Stefan,

I think we have the basic ideas right but I think we need to tidy up the current text of 3.3.   Also, 3.5.5 and 3.5.8 needs to be re-specified to align with 3.3.  I suggest that this is done in terms of changes to the rules in 3.3, rather than respecifying the same rules again.


More specifically:

A) Description of handling Canonicalization in 3.3 is broken up into item 1c, Item 2 and 3.3.1 which I found very difficult to follow.

I suggest that there is one item that describes the rules for canonicalisation combining these three into 3 separate points:

 i) (from 1c) If carried in <InlineXML> the need to extract XML data without namespace or other dependencies.  This may be achieved using Exclusive Canonical XML (How does this fit in with next point)

ii) (from 3.3.1) If no other transform use canonical XML, As per XML-Sig rule
  
iii) (from 2) if applying other transforms which result in node-set then need to apply Canonical XML.  Also follow XML Sig rules

B) Item 1 / 3.  It should be made clear that steps 1 & 2 apply to each <Document> at the start before Item 1.

C) I found the mechanism of making direct reference to part of a document confusing.  I prefer the current approach of referencing [REFABC] section 1.2.3.

D) Item 1a. Not sure I understand the reason for the reference [XML-NT-Document].  Is this trying to say that the XML contained within <Document> MUST be a complete XML Document as defined in [XML-NT-Document].

E) Item 1c  This is confusing.
The requirement is to extract the data without any namespace or other dependencies or XML containing document.  One way of achieving this is to use exclusive Canonicalization.

What 9is mean by “transport Protocol”.  Assume not layer 4 protocol?  Does this mean DSS XML protocol elements down to <DOCUMENT>.


F) Item 2 I prefer existing approach of referencing document and section within document.  If wish can provide Hyperlink in section text, but I find this difficult to follow.

G) Item 3 The text “The server MUST perform steps 1 and 2 for each <Document> in <InputDocuments>” should be at start of 1 & 2.

H) There is no description of the processing for the case where the <InputDocument> is <DocumentHash>

I) Section 3.4 Item 1 needs to be aligned with the step 1 handling of the different  ways of encoding XML.  To simplify this I suggest that we rule out InLine for CMS.

Also in earlier sections:

J) 2.4.2 ignorePIsComments Attribute

Line 399 – 

Change It contains the ignorePIsComments attribute.  … MAY be ignored. 

To

It may contain the ignorePIsComments attribute.  ….  SHALL be ignored.  


K) 2.4.2 

Different content of Document is a “Choice” but text describes them all as optional.

Suggest replace with 

“The <Document> element contains a choice of one of the following …..”

Delete (Option) after each element description.

Nick

> -----Original Message-----
> From: stefan@drees.name [mailto:stefan@drees.name]
> Sent: 17 July 2005 11:50
> To: dss@lists.oasis-open.org
> Subject: [dss] Groups - Digital Signature Service Core Protocols,
> Elements, and Bindings (oasis-dss-1.0-core-spec-wd-33pre9.doc) uploaded
> 
> 
> Mainly the addidtional changes to accomplish a 
> stringent simplified basic processing with a schema, 
> enabling InlineXML, EscapedXML and Base64XML all 
> in the same part (<Document>).
> 
> This document tries to be consistent with regard to 2.4.2, 
> 3.3 and 3.3.1,.2,.3.
> 
> Please see the comments (Word-Comments-Feature)for solicited Feedback and
> discussion.
> 
> Excpect further discussion on the list.
> 
> Many thanks to Konrad Lanz for the daily conferences;)
> 
>  -- Stefan Drees
> 
> The document revision named Digital Signature Service Core Protocols,
> Elements, and Bindings (oasis-dss-1.0-core-spec-wd-33pre9.doc) has been
> submitted by Stefan Drees to the OASIS Digital Signature Services (DSS) TC
> document repository.  This document is revision #5 of
> oasis-dss-1.0-core-spec-wd-31.doc.
> 
> Document Description:
> This document defines XML request/response protocols for signing and
> verifying XML documents and other data.  It also defines an XML timestamp
> format, and an XML signature property for use with these protocols. 
> Finally, it defines transport and security bindings for the protocols.
> 
> View Document Details:
> http://www.oasis-open.org/apps/org/workgroup/dss/document.php?docu
ment_id=13646

Download Document:  
http://www.oasis-open.org/apps/org/workgroup/dss/download.php/13646/oasis-dss-1.0-core-spec-wd-33pre9.doc

Revision:
This document is revision #5 of oasis-dss-1.0-core-spec-wd-31.doc.  The
document details page referenced above will show the complete revision
history.


PLEASE NOTE:  If the above links do not work for you, your email application
may be breaking the link into two pieces.  You may be able to copy and paste
the entire link address into the address field of your web browser.

-OASIS Open Administration




[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]