[OASIS Issue Tracker] Commented: (SRAMP-36) Batch Processing: Content-Type Multipart/HTML no longer valid

[OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org>]

    [ http://tools.oasis-open.org/issues/browse/SRAMP-36?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=30229#action_30229 ] 

Radek Pospisil  commented on SRAMP-36:
--------------------------------------

working draft document with approved changes
http://www.oasis-open.org/apps/org/workgroup/s-ramp/download.php/45814/s-ramp-atom-binding-v1.0-wd01-SRAMP-8-36-37.doc

> Batch Processing: Content-Type Multipart/HTML no longer valid
> -------------------------------------------------------------
>
>                 Key: SRAMP-36
>                 URL: http://tools.oasis-open.org/issues/browse/SRAMP-36
>             Project: OASIS SOA Repository Artifact Model and Protocol (S-RAMP) TC
>          Issue Type: Bug
>          Components: Atom Binding
>    Affects Versions: 1.0
>            Reporter: Vincent Brunssen
>            Assignee: Radek Pospisil 
>             Fix For: 1.0
>
>
> During the discussion of issue SRAMP-8 it was discovered that  Batch Processing has some issues regarding the use of content type.  The Content Type is shown to be multipart/html.  However, Martin Smithson commented to the group that multipart/html was only proposed and this proposal has since expired.  The TC needs to work to figure out which multipart/???? is the correct one to use and make appropriate changes.  The multipart/???? options can be found at http://www.w3.org/Protocols/rfc1341/7_2_Multipart.html.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://tools.oasis-open.org/issues/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira