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] DSS Public comments


Dear DSS committee,

First of all, thanks to Konrad Lanz for the detailed formulation of the SOAP 
1.2 attachment feature support in DSS. 

I have two minor remarks, one of which being a copy+paste error in Konrad 
Lanz's text. The second remark is that in order to set the MIME type in  
<ds:Object> elements in the result, it would be advisable to add a MimeType 
attribute to the AttachmentReference type (just as in the Base64Data element)
[1].

Thus, I propose the following (minor) changes:

Am Sonntag, 24. Dezember 2006 12:36 schrieb Konrad Lanz:
> [...]
>
> ---------- That's all so far, the rest is to extend Section 6.2 --------
> ________________________________________________________________________
>
> * Create a new section 6.2.1 SOAP Attachment Feature and Element
> <AttachmentReference>
> ________________________________________________________________________
>
> [...]
>
> <xs:element name="AttachmentReference" type="dss:AttachmentReferenceType"/>
> <xs:complexType name="AttachmentReferenceType">
>     <xs:complexType name="AttachmentReferenceType">
>         <xs:sequence minOccurs="0">
>             <xs:element ref="ds:DigestMethod"/>
>             <xs:element ref="ds:DigestValue"/>
>         </xs:sequence>
>         <xs:attribute name="AttRefURI" type="xs:anyURI"/>
>     </xs:complexType>
>   <xs:attribute name="AttRefURI" type="xs:anyURI" />
> </xs:complexType>
>


<xs:element name="AttachmentReference" type="dss:AttachmentReferenceType"/>
<xs:complexType name="AttachmentReferenceType">
     <xs:sequence minOccurs="0">
        <xs:element ref="ds:DigestMethod"/>
        <xs:element ref="ds:DigestValue"/>
     </xs:sequence>
  <xs:attribute name="AttRefURI" type="xs:anyURI" />
  <xs:attribute name="MimeType" type="xs:string" use="optional"/>
</xs:complexType>



> * and add the element and type above to the schema.
> ________________________________________________________________________
>
> * Create a new section 6.2.1.1 Signing Protocol, Processing for XML
> Signatures, Process Variant for <AttachmentReference>
> ________________________________________________________________________
>

Replace the paragraph

> In the case of an input document which contains <AttachmentReference>
> the server retrieves the MIME headers from the attachment referred by
> AttRefURI and reads the content's MIME type.

with 

In the case of an input document which contains <AttachmentReference> the 
server retrieves the MIME type from the MimeType attribute (if present) 
otherwise from the content-type MIME header of the attachment referred by 
AttRefURI. 


Kind regards,

Clemens Orthacker


[1] If MIME is used as encapsulation mechanism, the MIME content-type is 
available via a MIME header. However, the SOAP 1.2 attachment feature is not 
restricted to MIME. Further the MIME header is not secured by the 
AttachmentReference's DigestValue, which is calculated over the binary 
attachment data (not including the MIME headers).

-- 
Clemens Orthacker  Secure Information Technology Center - Austria
Tel: +43 316 873 5512                   Web: http://www.a-sit.at/


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