OASIS ebXML Core (ebCore) TC

Hello TC, The work on the last outstanding bit of OASIS ebXML specifications, CPPA3, started many years ago. The latest restart was in 2016, with periodic updates for over two years. The last versions of specification, schema, schema documentation and samples were uploaded by the end of last year. Since then I've waited to see if any minor extensions are needed, but none have come up, at least not to me. Also, some users are going to start deploying CPPA3 as a download format for an AS4 community configuration platform, and for them it is important that the schema be stable and non-proprietary. Therefore I would like to ask if you agree that the time has come to move this work to completion. My proposal is to take a few weeks, until the end of this month, to allow anyone who wants to have a final look. Then, if there are no issues or concerns, we could start a ballot to approve the current work as Committee Specification Drafts and to open them up for Public review. Please let me know if this is OK with you. For review, below are the links to the latest documents. Specification: https://www.oasis-open.org/committees/download.php/64485/cppa-v3.0-wd12.odt Schema: https://www.oasis-open.org/committees/download.php/64482/cppa3.xsd (CPPA3) https://www.oasis-open.org/committees/download.php/64483/exception.xsd (Exception) Schema documentation: https://www.oasis-open.org/committees/download.php/64484/cppa3-exception-html-documentation.zip To get a quick overview of the latest work, the best starting point may be the following presentation: https://www.oasis-open.org/committees/download.php/64804/CPPA3%20Overview.pptx An open source library (Python2/3) implementing a wide range of CPPA3 related functionality is available from: https://pypi.org/project/cppa3/ A proof-of-concept showing use of CPPA3 for automated configuration of AS4 based on ENTSOG AS4 profile is available at: https://bitbucket.org/ebcore/as4_mgmt_poc/src Another proof-of-concept shows use of CPPA3 for generating P-Modes for the two AS4 products (Flame FMS and Domibus): https://secure.e-codex.eu/gitblit/summary/research%2Fas4config_poc.git Kind regards, Pim

Hi Pim Thanks for the update. As a vendor I have no particular feelings for/against CPPA3 but would need to consider the implications of supporting it as we have had no specific requirements from clients as yet on this. As a TC member I am ok that we put this out for discussion via the normal channels. I would also be open to a discussion with yourself and rest of the TC (telecon/f2f) around the benefits and use cases for this and where other existing approaches to exchanging connection and p-mode config detail may already exist. > On 04 Nov 2019, at 17:14 , Pim van der Eijk <pvde@sonnenglanz.net> wrote: > > > Hello TC, > > The work on the last outstanding bit of OASIS ebXML specifications, CPPA3, started many years ago. The latest restart was in 2016, with periodic updates for over two years. The last versions of specification, schema, schema documentation and samples were uploaded by the end of last year. Since then I've waited to see if any minor extensions are needed, but none have come up, at least not to me. > > Also, some users are going to start deploying CPPA3 as a download format for an AS4 community configuration platform, and for them it is important that the schema be stable and non-proprietary. Therefore I would like to ask if you agree that the time has come to move this work to completion. > > My proposal is to take a few weeks, until the end of this month, to allow anyone who wants to have a final look. Then, if there are no issues or concerns, we could start a ballot to approve the current work as Committee Specification Drafts and to open them up for Public review. > > Please let me know if this is OK with you. > > For review, below are the links to the latest documents. > > Specification: > https://www.oasis-open.org/committees/download.php/64485/cppa-v3.0-wd12.odt > > Schema: > > https://www.oasis-open.org/committees/download.php/64482/cppa3.xsd (CPPA3) > https://www.oasis-open.org/committees/download.php/64483/exception.xsd (Exception) > > Schema documentation: > https://www.oasis-open.org/committees/download.php/64484/cppa3-exception-html-documentation.zip > To get a quick overview of the latest work, the best starting point may be the following presentation: > > https://www.oasis-open.org/committees/download.php/64804/CPPA3%20Overview.pptx > An open source library (Python2/3) implementing a wide range of CPPA3 related functionality is available from: > > https://pypi.org/project/cppa3/ > A proof-of-concept showing use of CPPA3 for automated configuration of AS4 based on ENTSOG AS4 profile is available at: > > https://bitbucket.org/ebcore/as4_mgmt_poc/src > Another proof-of-concept shows use of CPPA3 for generating P-Modes for the two AS4 products (Flame FMS and Domibus): > > https://secure.e-codex.eu/gitblit/summary/research%2Fas4config_poc.git > Kind regards, > > Pim > > > > > > > -- Regards Theo Kramer

Hi Theo, Thanks for your email. On 13-11-19 12:46, Theo Kramer wrote: Thanks for the update. As a vendor I have no particular feelings for/against CPPA3 but would need to consider the implications of supporting it as we have had no specific requirements from clients as yet on this. One reason I propose finalizing the work is that I have some users that are interested. The simplest approach for a vendor would be to provide an import mechanism from this format to whatever the vendor uses for messaging configuration. As long as a product has an API and/or structured import data format, past experience is that this is usually not that hard in practice. For AS4, as mentioned, I did a proof-of-concept for two AS4 products, one of which is Flame FMS, entry point is https://secure.e-codex.eu/gitblit/summary/research%2Fas4config_poc.git , some generated configurations for Flame FMS are available in that repository. As a TC member I am ok that we put this out for discussion via the normal channels. Great, formalizing the current draft as a Committee Specification Draft and opening it for review would be the way to get feedback. I would also be open to a discussion with yourself and rest of the TC (telecon/f2f) around the benefits and use cases for this and where other existing approaches to exchanging connection and p-mode config detail may already exist. OK I'll contact you offline on this, maybe we can set up a meeting with any interested members. Kind Regards, Pim

Hello, Based on feedback I've received so far from some of you, and the absence of comments from others, there seem to be no open comments from TC members on the CPPA3 spec that they want to be addressed. One user community intends to use it and wants the specification to be standardized. Therefore I plan to start a ballot next week, similar to the one https://www.oasis-open.org/apps/org/workgroup/ebcore/ballot.php?id=2934 , short-circuiting some unnecessary steps. Note that OASIS ballots require majorities, and voting members count for calculating quorum. Kind Regards, Pim van der Eijk -------- Forwarded Message -------- Subject: [ebcore] Finalizing CPPA3 Date: Mon, 4 Nov 2019 16:14:22 +0100 From: Pim van der Eijk <pvde@sonnenglanz.net> To: ebcore@lists.oasis-open.org Hello TC, The work on the last outstanding bit of OASIS ebXML specifications, CPPA3, started many years ago. The latest restart was in 2016, with periodic updates for over two years. The last versions of specification, schema, schema documentation and samples were uploaded by the end of last year. Since then I've waited to see if any minor extensions are needed, but none have come up, at least not to me. Also, some users are going to start deploying CPPA3 as a download format for an AS4 community configuration platform, and for them it is important that the schema be stable and non-proprietary. Therefore I would like to ask if you agree that the time has come to move this work to completion. My proposal is to take a few weeks, until the end of this month, to allow anyone who wants to have a final look. Then, if there are no issues or concerns, we could start a ballot to approve the current work as Committee Specification Drafts and to open them up for Public review. Please let me know if this is OK with you. For review, below are the links to the latest documents. Specification: https://www.oasis-open.org/committees/download.php/64485/cppa-v3.0-wd12.odt Schema: https://www.oasis-open.org/committees/download.php/64482/cppa3.xsd (CPPA3) https://www.oasis-open.org/committees/download.php/64483/exception.xsd (Exception) Schema documentation: https://www.oasis-open.org/committees/download.php/64484/cppa3-exception-html-documentation.zip To get a quick overview of the latest work, the best starting point may be the following presentation: https://www.oasis-open.org/committees/download.php/64804/CPPA3%20Overview.pptx An open source library (Python2/3) implementing a wide range of CPPA3 related functionality is available from: https://pypi.org/project/cppa3/ A proof-of-concept showing use of CPPA3 for automated configuration of AS4 based on ENTSOG AS4 profile is available at: https://bitbucket.org/ebcore/as4_mgmt_poc/src Another proof-of-concept shows use of CPPA3 for generating P-Modes for the two AS4 products (Flame FMS and Domibus): https://secure.e-codex.eu/gitblit/summary/research%2Fas4config_poc.git Kind regards, Pim