6 messages in org.oasis-open.lists.dssRe: [dss] DSS Public comments| From | Sent On | Attachments |
|---|---|---|
| Pope, Nick | Dec 22, 2006 7:59 am | |
| Konrad Lanz | Dec 24, 2006 3:36 am | |
| Clemens Orthacker | Jan 12, 2007 6:52 am | |
| Konrad Lanz | Jan 12, 2007 7:26 am | |
| Juan Carlos Cruellas | Jan 12, 2007 9:12 am | |
| Konrad Lanz | Jan 12, 2007 10:56 am |
| Subject: | Re: [dss] DSS Public comments | |
|---|---|---|
| From: | Konrad Lanz (Konr...@labs.cio.gv.at) | |
| Date: | Jan 12, 2007 7:26:04 am | |
| List: | org.oasis-open.lists.dss | |
Hello Clemens,
Good Point, I agree.
Dear all,
Stefan, I propose to adopt the amendment suggested by Clemens as an editorial change together with the comments from JC and readding <VerifyResponse> to the xsd file.
Any thoughts anyone?
regards Konrad
Clemens Orthacker schrieb:
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).