OASIS ebXML Core (ebCore) TC

 View Only
  • 1.  Groups - ebcore-au-v1.0 uploaded

    Posted 08-31-2015 10:25
    Submitter's message
    Hi,

    The comments we've received so far on this specification are generally positive, and there does not seem to be a need to discuss it. All comments are still welcome, but as some users need this functionality to be standardized soon, I would like to finish this version. Is it OK if we take one week for any comments and then proceed to CSD and to public review if there are none?

    Kind Regards,

    Pim

    The update below has only minor changes:
    - Changed RespondByDate to RespondBy for consistency.
    - Updated samples accordingly.
    - Added error code to sample exception.
    - Fixed URLs to generated documentation.
    -- Mr. Pim van der Eijk Document Name : ebcore-au-v1.0 Description The ebCore Agreement Update specification defines message exchanges and an XML schema to support the exchange of agreement update requests and positive or negative responses to such requests. The main initial application of the specification is the exchange of X.509 certificates for certificate rollover, but offers extensibility for other types of updates. The specification is based on the concept of communication agreements and the creating of new agreements as independently identified updated copies of existing agreements. The specification supports ebMS2, ebMS3 and AS4 but can also be used with other protocols that have a concept of communication agreement. Download Latest Revision Public Download Link Submitter : Mr. Pim van der Eijk Group : OASIS ebXML Core (ebCore) TC Folder : Contributions Date submitted : 2015-08-31 03:24:09 Revision : 4


  • 2.  Re: [ebcore] Groups - ebcore-au-v1.0 uploaded

    Posted 08-31-2015 18:11
    Hi Pim, I have not looked into this in detail until now. I will try to have a look into this week. You indicate some users need this functionality standardised soon. Having only a standard probably will not help them solve the issue they have, so I assume they expect support for this spec soon as well?  Regards, Sander On 31 Aug 2015, at 12:24, Pim van der Eijk < pvde@sonnenglanz.net > wrote: Submitter's message Hi, The comments we've received so far on this specification are generally positive, and there does not seem to be a need to discuss it. All comments are still welcome, but as some users need this functionality to be standardized soon, I would like to finish this version. Is it OK if we take one week for any comments and then proceed to CSD and to public review if there are none? Kind Regards, Pim The update below has only minor changes: - Changed RespondByDate to RespondBy for consistency. - Updated samples accordingly. - Added error code to sample exception. - Fixed URLs to generated documentation. -- Mr. Pim van der Eijk Document Name : ebcore-au-v1.0 Description The ebCore Agreement Update specification defines message exchanges and an XML schema to support the exchange of agreement update requests and positive or negative responses to such requests. The main initial application of the specification is the exchange of X.509 certificates for certificate rollover, but offers extensibility for other types of updates. The specification is based on the concept of communication agreements and the creating of new agreements as independently identified updated copies of existing agreements. The specification supports ebMS2, ebMS3 and AS4 but can also be used with other protocols that have a concept of communication agreement. Download Latest Revision Public Download Link Submitter : Mr. Pim van der Eijk Group : OASIS ebXML Core (ebCore) TC Folder : Contributions Date submitted : 2015-08-31 03:24:09 Revision : 4 Attachment: smime.p7s Description: S/MIME cryptographic signature


  • 3.  Re: [ebcore] Groups - ebcore-au-v1.0 uploaded

    Posted 09-01-2015 06:02
    OK great.   And yes,  once this specification hopefully gets to CS,  they intend to enhance their existing AS4 profile to mandate support this feature.  Note that support for Agreement Update does not necessarily require fully automated built-in feature of messaging product .   And yes, they're hoping to have this in place before their current set of certificates expires .. On 08/31/2015 08:11 PM, Sander Fieten wrote: Hi Pim, I have not looked into this in detail until now. I will try to have a look into this week. You indicate some users need this functionality standardised soon. Having only a standard probably will not help them solve the issue they have, so I assume they expect support for this spec soon as well?  Regards, Sander On 31 Aug 2015, at 12:24, Pim van der Eijk < pvde@sonnenglanz.net > wrote: Submitter's message Hi, The comments we've received so far on this specification are generally positive, and there does not seem to be a need to discuss it. All comments are still welcome, but as some users need this functionality to be standardized soon, I would like to finish this version. Is it OK if we take one week for any comments and then proceed to CSD and to public review if there are none? Kind Regards, Pim The update below has only minor changes: - Changed RespondByDate to RespondBy for consistency. - Updated samples accordingly. - Added error code to sample exception. - Fixed URLs to generated documentation. -- Mr. Pim van der Eijk Document Name : ebcore-au-v1.0 Description The ebCore Agreement Update specification defines message exchanges and an XML schema to support the exchange of agreement update requests and positive or negative responses to such requests. The main initial application of the specification is the exchange of X.509 certificates for certificate rollover, but offers extensibility for other types of updates. The specification is based on the concept of communication agreements and the creating of new agreements as independently identified updated copies of existing agreements. The specification supports ebMS2, ebMS3 and AS4 but can also be used with other protocols that have a concept of communication agreement. Download Latest Revision Public Download Link Submitter : Mr. Pim van der Eijk Group : OASIS ebXML Core (ebCore) TC Folder : Contributions Date submitted : 2015-08-31 03:24:09 Revision : 4


  • 4.  Re: [ebcore] Groups - ebcore-au-v1.0 uploaded

    Posted 09-01-2015 15:44
    And BTW if anyone else intends to review and needs more than a week,  let me know ... Kind Regards, Pim On 09/01/2015 08:01 AM, Pim van der Eijk wrote: OK great.   And yes,  once this specification hopefully gets to CS,  they intend to enhance their existing AS4 profile to mandate support this feature.  Note that support for Agreement Update does not necessarily require fully automated built-in feature of messaging product .   And yes, they're hoping to have this in place before their current set of certificates expires .. On 08/31/2015 08:11 PM, Sander Fieten wrote: Hi Pim, I have not looked into this in detail until now. I will try to have a look into this week. You indicate some users need this functionality standardised soon. Having only a standard probably will not help them solve the issue they have, so I assume they expect support for this spec soon as well?  Regards, Sander On 31 Aug 2015, at 12:24, Pim van der Eijk < pvde@sonnenglanz.net > wrote: Submitter's message Hi, The comments we've received so far on this specification are generally positive, and there does not seem to be a need to discuss it. All comments are still welcome, but as some users need this functionality to be standardized soon, I would like to finish this version. Is it OK if we take one week for any comments and then proceed to CSD and to public review if there are none? Kind Regards, Pim The update below has only minor changes: - Changed RespondByDate to RespondBy for consistency. - Updated samples accordingly. - Added error code to sample exception. - Fixed URLs to generated documentation. -- Mr. Pim van der Eijk Document Name : ebcore-au-v1.0 Description The ebCore Agreement Update specification defines message exchanges and an XML schema to support the exchange of agreement update requests and positive or negative responses to such requests. The main initial application of the specification is the exchange of X.509 certificates for certificate rollover, but offers extensibility for other types of updates. The specification is based on the concept of communication agreements and the creating of new agreements as independently identified updated copies of existing agreements. The specification supports ebMS2, ebMS3 and AS4 but can also be used with other protocols that have a concept of communication agreement. Download Latest Revision Public Download Link Submitter : Mr. Pim van der Eijk Group : OASIS ebXML Core (ebCore) TC Folder : Contributions Date submitted : 2015-08-31 03:24:09 Revision : 4