| Meeting Jul 02 |
1 |
2014-07-02 |
| Re: [regrep] Notice of Decision regarding Submission of OASIS ebXML RegRep V4.0, ebXML Messaging Services V3.0: Core Features, AS4 Profile of ebMS 3.0 V1.0, and ebXML Business Process Specification Schema Technical Specification v2.0.4 to ISO/TC 154 |
2 |
2014-07-02 |
| =?UTF-8?Q?Special_Majority_Ballots_to_ratify_the_TC=E2=80=99s_decisi?= =?UTF-8?Q?on_to_submit_OASIS_ebXML_Messaging_Services_Version_3=2E0=3A_Cor?= =?UTF-8?Q?e_Features_OASIS_Standard_and_AS4_Profile_of_ebMS_3=2E0_Versio?= =?UTF-8?Q?n_1=2E0_OASIS_Standard_to_ISO_TC_154_have_been_set_up?= |
1 |
2014-07-02 |
| [OASIS Issue Tracker] (EBXMLMSG-45) PMode parameter for Key Transport algorithm |
2 |
2014-07-02 |
| [OASIS Issue Tracker] (EBXMLMSG-52) Content-Disposition header requirement |
1 |
2014-07-11 |
| [OASIS Issue Tracker] (EBXMLMSG-53) Preventing replay attack for PullRequest |
1 |
2014-07-11 |
| [OASIS Issue Tracker] (EBXMLMSG-54) Compressed SWA mimetype part property clarification |
1 |
2014-07-16 |
| [OASIS Issue Tracker] (EBXMLMSG-55) AS4 Constrained to oneWay MEP |
3 |
2014-07-16 |
| [OASIS Issue Tracker] (EBXMLMSG-56) Too narrow definition of PMode[1].Security.SendReceipt |
2 |
2014-07-16 |
| Call adjourned early today.. |
1 |
2014-07-16 |
| [OASIS Issue Tracker] (EBXMLMSG-57) Expected HTTP response codes |
7 |
2014-07-30 |
| [OASIS Issue Tracker] (EBXMLMSG-58) Use of WS-Security timestamp element |
2 |
2014-07-30 |
| =?UTF-8?B?Q2FuY2VsbGVkIGViTVMgYml3ZWVrbHkg?= =?UTF-8?B?VEMgbWVldGluZw==?= |
1 |
2014-07-31 |
