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


Help: OASIS Mailing Lists Help | MarkMail Help

wss message

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

Subject: Issue 376: Input format to Transform - proposed resolution

-----Original Message-----
From: ext [mailto:Frederick.Hirsch@nokia.com] 
Sent: Monday, March 21, 2005 12:47 PM
To: Manveen.Kaur@Sun.COM; wss-comment@lists.oasis-open.org
Subject: [wss-comment] Input format to Transform - proposed resolution

Proposed resolution to the issue below

In addition to the change at line 273 (referring to draft 17 pdf,
swa-profile-1.0-draft-17-diff.pdf ), stating the that input of the
transforms is octet stream, we can also add the following text to
section 4.3.2 after line 301 

The octet stream input to this transform is the entire content of the
MIME attachment associated with the CID, including the MIME headers and
attachment content, as represented in the MIME part containing the

The output of the transform is an octet stream consisting of
concatenation of the MIME canonicalized MIME headers selected by the
transform followed by the concatenation of the MIME canonicalization of
the attachment content. The MIME canonicalization of headers and content
are described subsequently in this specification.

If there is an improved way of wording this, a proposal would be

If acceptable, we could also add similar wording for section 4.3.1,
referring only to the attachment content.

regards, Frederick

Frederick Hirsch

-----Original Message-----
From: ext Manveen Kaur [mailto:Manveen.Kaur@Sun.COM]
Sent: Thursday, March 17, 2005 2:42 PM
To: wss-comment@lists.oasis-open.org
Subject: [wss-comment] Input format to Transform

Comments on SwA CD [1]

The Attachment-Complete Transform needs to operate on attachment content
and MIME Headers. Currently, the SwA draft [1] does not identify how the
such dereferenced information (both content and MIME header information)
needs to be provided to the transform as input.

The xml-dsig spec [2] says that input to a transform should be a nodeset
or octet-stream and all other information needs to be provided as
transformation parameters.

Quoting the relevant piece from xml-dsig core [2] (section

'Some Transforms may require explicit MIME type, charset (IANA
registered "character set"), or other such information concerning the
data they are receiving from an earlier Transform or the source data,
although no Transform algorithm specified in this document needs such
explicit information. Such data characteristics are provided as
parameters to the Transform algorithm and should be described in the
specification for the algorithm.'

There should be a  standard input format to the Attachment-Complete



[2] http://www.w3.org/TR/xmldsig-core/

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