OASIS ebXML Messaging Services TC

Please see attached fyi. Feel free to let me have your comments/input on this. OASIS AS4 Profile of ebMS 3.0 Version 1.0 Statement of Use ----------------------------------------------- Company: Flame Computing Enterprises Tel: +27 82 602 4026 Email: info at flame dot co dot za URL: http://flame.co.za Date: Mon May 14 08:00:00 SAST 2012 Products: FMS AS4 Server, FMS AS4 Light Client, FMS AS4 Minimal Client. Revision: @(#) $RCSfile: FMS-AS4-StatementOfUse-2012-05-14.txt,v $ $Revision: 1.2 $ $Date: 2012-05-21 09:28:59 $ Flame Message Server (FMS) ---------------------- The FMS AS4 Server conforms to the AS4 ebHandler Conformance Profile, and complies with all normative statements and requirements as per Section 2.1 of the AS4 Profile of ebMS 3.0 Version 1.0 Committee Specification Draft 05 / Public Review Draft 04 dated 21 March 2012. This includes the following i Compliance in full with the Feature Set table of section 2.1.1. ii Compliance with the WS-I requirements as per Section 2.1.2. iii Compliance with the P-Mode parameters as per Section 2.1.3. Additional supported features include the following i Compression as specified in section 3.1. ii Reception Awareness, Duplicate Detection and Message Retry as specified in section 3.2 iii Support for Semantics of Receipt as specified in section 3.4. iv Usage Rules as defined in section 5.1. v AS4 Usage Agreement support via flexible P-Mode configuration. Optional Features not currently supported include the following i Sub-channels for Message Pulling as defined in section 2 of ebMS V3 Part 2 ([ebMS3ADV]) for intermediaries in a multi-hop context as defined in section 3.5. ii Support for CPAs as defined in section 5.2.7. Non-Normative Features not currently supported include the following i Controlling Content and Sending of Receipts P-Mode parameter NonRepudiation as defined in section 5.2.1. ii Error Handling P-Mode parameter MissingReceiptNotifyProducer as defined in section 5.2.2. FMS AS4 Light Client -------------------- The FMS AS4 Light Client conforms to the AS4 ebHandler Profile, and complies with all normative statements and requirements as per Section 2.2 of the AS4 Light Client Conformance Profile of the ebMS 3.0 Version 1.0 Committee Specification Draft 05 / Public Review Draft 04 dated 21 March 2012. This includes the following i Compliance in full with the Feature Set table of section 2.2.1. ii Compliance with the WS-I requirements as per Section 2.2.2. iii Compliance with the P-Mode parameters as per Section 2.2.3. Additional supported features include the following i Compression as specified in section 3.1. ii Reception Awareness, Duplicate Detection and Message Retry as specified in section 3.2 iii Support for Semantics of Receipt as specified in section 3.4. iv Usage Rules as defined in section 5.1. v AS4 Usage Agreement support via flexible P-Mode configuration as defined in section 5.2. Optional Features not supported include the following i Sub-channels for Message Pulling as defined in section 2 of ebMS V3 Part 2 ([ebMS3ADV]) for intermediaries in a multi-hop context as defined in section 3.5. ii Support for CPAs as defined in section 5.2.7. Non-Normative Features not currently supported include the following i Controlling Content and Sending of Receipts P-Mode paramter NonRepudiation as defined in section 5.2.1. ii Error Handling P-Mode parameter MissingReceiptNotifyProducer as defined in section 5.2.2. FMS AS4 Minimal Client ---------------------- The FMS AS4 Minimal Client conforms to the AS4 ebHandler Profile, and complies with all normative statements and requirements as per Section 2.3 of the AS4 Light Client Conformance Profile of the ebMS 3.0 Version 1.0 Committee Specification Draft 05 / Public Review Draft 04 dated 21 March 2012. This includes the following i Compliance in full with the Feature Set table of section 2.3.1. ii Compliance with the WS-I requirements as per Section 2.3.2. iii Compliance with the P-Mode parameters as per Section 2.3.3. -- Regards Theo Kramer Flame Computing Enterprises cc +27 82 602 4026 http://flame.co.za

Please see attached update to the original statement of use. This update replaces reference to the Draft Spec to the Committee Spec 03 Dated 30 April 2012. OASIS AS4 Profile of ebMS 3.0 Version 1.0 Statement of Use ----------------------------------------------- Company: Flame Computing Enterprises Tel: +27 82 602 4026 Email: info at flame dot co dot za URL: http://flame.co.za Date: Mon May 14 08:00:00 SAST 2012 Products: FMS AS4 Server, FMS AS4 Light Client, FMS AS4 Minimal Client. Revision: @(#) $RCSfile: FMS-AS4-StatementOfUse.txt,v $ $Revision: 1.3 $ $Date: 2012-05-25 12:34:25 $ Flame Message Server (FMS) ---------------------- The FMS AS4 Server conforms to the AS4 ebHandler Conformance Profile, and complies with all normative statements and requirements as per Section 2.1 of the AS4 Profile of ebMS 3.0 Version 1.0 Committee Specification 03 dated 30 April 2012. This includes the following i Compliance in full with the Feature Set table of section 2.1.1. ii Compliance with the WS-I requirements as per Section 2.1.2. iii Compliance with the P-Mode parameters as per Section 2.1.3. Additional supported features include the following i Compression as specified in section 3.1. ii Reception Awareness, Duplicate Detection and Message Retry as specified in section 3.2 iii Support for Semantics of Receipt as specified in section 3.4. iv Usage Rules as defined in section 5.1. v AS4 Usage Agreement support via flexible P-Mode configuration. Optional Features not currently supported include the following i Sub-channels for Message Pulling as defined in section 2 of ebMS V3 Part 2 ([ebMS3ADV]) for intermediaries in a multi-hop context as defined in section 3.5. ii Support for CPAs as defined in section 5.2.7. Non-Normative Features not currently supported include the following i Controlling Content and Sending of Receipts P-Mode parameter NonRepudiation as defined in section 5.2.1. ii Error Handling P-Mode parameter MissingReceiptNotifyProducer as defined in section 5.2.2. FMS AS4 Light Client -------------------- The FMS AS4 Light Client conforms to the AS4 ebHandler Profile, and complies with all normative statements and requirements as per Section 2.2 of the AS4 Profile of ebMS 3.0 Version 1.0 Committee Specification 03 dated 30 April 2012. This includes the following i Compliance in full with the Feature Set table of section 2.2.1. ii Compliance with the WS-I requirements as per Section 2.2.2. iii Compliance with the P-Mode parameters as per Section 2.2.3. Additional supported features include the following i Compression as specified in section 3.1. ii Reception Awareness, Duplicate Detection and Message Retry as specified in section 3.2 iii Support for Semantics of Receipt as specified in section 3.4. iv Usage Rules as defined in section 5.1. v AS4 Usage Agreement support via flexible P-Mode configuration as defined in section 5.2. Optional Features not supported include the following i Sub-channels for Message Pulling as defined in section 2 of ebMS V3 Part 2 ([ebMS3ADV]) for intermediaries in a multi-hop context as defined in section 3.5. ii Support for CPAs as defined in section 5.2.7. Non-Normative Features not currently supported include the following i Controlling Content and Sending of Receipts P-Mode paramter NonRepudiation as defined in section 5.2.1. ii Error Handling P-Mode parameter MissingReceiptNotifyProducer as defined in section 5.2.2. FMS AS4 Minimal Client ---------------------- The FMS AS4 Minimal Client conforms to the AS4 ebHandler Profile, and complies with all normative statements and requirements as per Section 2.3 of the AS4 Light Client Conformance Profile of the AS4 Profile of ebMS 3.0 Version 1.0 Committee Specification 03 dated 30 April 2012. This includes the following i Compliance in full with the Feature Set table of section 2.3.1. ii Compliance with the WS-I requirements as per Section 2.3.2. iii Compliance with the P-Mode parameters as per Section 2.3.3. On 21 May 2012, at 11:29 AM, Theo Kramer wrote: > Please see attached fyi. Feel free to let me have your comments/input on this. > > <FMS-AS4-StatementOfUse-2012-05-14.txt> > > -- > Regards > Theo Kramer > Flame Computing Enterprises cc > +27 82 602 4026 > http://flame.co.za > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: ebxml-msg-unsubscribe@lists.oasis-open.org > For additional commands, e-mail: ebxml-msg-help@lists.oasis-open.org -- Regards Theo

Please see attached update revision 1.4 to revision 1.4 of the Flame Computing statement of use. This update includes the following interoperability statement Interoperability The use of the specification includes interoperation with other similar independent implementations. OASIS AS4 Profile of ebMS 3.0 Version 1.0 Statement of Use ----------------------------------------------- Company: Flame Computing Enterprises Tel: +27 82 602 4026 Email: info at flame dot co dot za URL: http://flame.co.za Date: Mon May 14 08:00:00 SAST 2012 Products: FMS AS4 Server, FMS AS4 Light Client, FMS AS4 Minimal Client. Revision: @(#) $RCSfile: FMS-AS4-StatementOfUse.txt,v $ $Revision: 1.4 $ $Date: 2012-07-20 08:44:07 $ Flame Message Server (FMS) -------------------------- The FMS AS4 Server conforms to the AS4 ebHandler Conformance Profile, and complies with all normative statements and requirements as per Section 2.1 of the AS4 Profile of ebMS 3.0 Version 1.0 Committee Specification 03 dated 30 April 2012. This includes the following i Compliance in full with the Feature Set table of section 2.1.1. ii Compliance with the WS-I requirements as per Section 2.1.2. iii Compliance with the P-Mode parameters as per Section 2.1.3. Additional supported features include the following i Compression as specified in section 3.1. ii Reception Awareness, Duplicate Detection and Message Retry as specified in section 3.2 iii Support for Semantics of Receipt as specified in section 3.4. iv Usage Rules as defined in section 5.1. v AS4 Usage Agreement support via flexible P-Mode configuration. Optional Features not currently supported include the following i Sub-channels for Message Pulling as defined in section 2 of ebMS V3 Part 2 ([ebMS3ADV]) for intermediaries in a multi-hop context as defined in section 3.5. ii Support for CPAs as defined in section 5.2.7. Non-Normative Features not currently supported include the following i Controlling Content and Sending of Receipts P-Mode parameter NonRepudiation as defined in section 5.2.1. ii Error Handling P-Mode parameter MissingReceiptNotifyProducer as defined in section 5.2.2. Interoperability The use of the specification includes interoperation with other similar independent implementations. FMS AS4 Light Client -------------------- The FMS AS4 Light Client conforms to the AS4 ebHandler Profile, and complies with all normative statements and requirements as per Section 2.2 of the AS4 Profile of ebMS 3.0 Version 1.0 Committee Specification 03 dated 30 April 2012. This includes the following i Compliance in full with the Feature Set table of section 2.2.1. ii Compliance with the WS-I requirements as per Section 2.2.2. iii Compliance with the P-Mode parameters as per Section 2.2.3. Additional supported features include the following i Compression as specified in section 3.1. ii Reception Awareness, Duplicate Detection and Message Retry as specified in section 3.2 iii Support for Semantics of Receipt as specified in section 3.4. iv Usage Rules as defined in section 5.1. v AS4 Usage Agreement support via flexible P-Mode configuration as defined in section 5.2. Optional Features not supported include the following i Sub-channels for Message Pulling as defined in section 2 of ebMS V3 Part 2 ([ebMS3ADV]) for intermediaries in a multi-hop context as defined in section 3.5. ii Support for CPAs as defined in section 5.2.7. Non-Normative Features not currently supported include the following i Controlling Content and Sending of Receipts P-Mode paramter NonRepudiation as defined in section 5.2.1. ii Error Handling P-Mode parameter MissingReceiptNotifyProducer as defined in section 5.2.2. Interoperability The use of the specification includes interoperation with other similar independent implementations. FMS AS4 Minimal Client ---------------------- The FMS AS4 Minimal Client conforms to the AS4 ebHandler Profile, and complies with all normative statements and requirements as per Section 2.3 of the AS4 Light Client Conformance Profile of the AS4 Profile of ebMS 3.0 Version 1.0 Committee Specification 03 dated 30 April 2012. This includes the following i Compliance in full with the Feature Set table of section 2.3.1. ii Compliance with the WS-I requirements as per Section 2.3.2. iii Compliance with the P-Mode parameters as per Section 2.3.3. Interoperability The use of the specification includes interoperation with other similar independent implementations. On 25 May 2012, at 2:49 PM, Theo Kramer wrote: > Please see attached update to the original statement of use. > > This update replaces reference to the Draft Spec to the Committee Spec 03 Dated 30 April 2012. > > <FMS-AS4-StatementOfUse.txt> > > On 21 May 2012, at 11:29 AM, Theo Kramer wrote: > >> Please see attached fyi. Feel free to let me have your comments/input on this. >> >> <FMS-AS4-StatementOfUse-2012-05-14.txt> >> -- Regards Theo Kramer Flame Computing Enterprises cc +27 82 602 4026 http://flame.co.za