This page tries to collect the technology relevant things happening in PEPPOL.
Note: this is not an official "News" page. This is just what I'm collecting...
Todays PEPPOL practical update is mainly for improved Simplerinvoicing validation. The version 1.1 was restored and 1.2 validation was fixed.
As announced today the CIPA SMP 3.0 which will be released soon will only comply to the OASIS SMP specification but NOT to the PEPPOL SMP specification. So from a PEPPOL perspective there's currently no need to plan an update. But that may of course trigger a quicker transition of PEPPOL from the PEPPOL SMP specification to the OASIS SMP specification... another TICC todo.
The participant information tool now has an "Auto-detect SML" feature and also tries to print a few information even if a request fails.
A new PEPPOL TICC team was founded to take care of the "PEPPOL Policy for the use of identifiers" as well the basic codelists for transmission (identifier issuing agencies, document type, processes and transport protocols). The new team is lead by me and if you want to actively participate, please drop me a note. The initial telephone conference is planned for June 8th or 9th.
Because some changes from RC1 to final were missing, the artefacts were re-released. PEPPOL Practical was using the correct artefacts from the beginning!
As the new validation rules take effect today, I added them right away. Additionally the PEPPOL Dictionary was updated.
The BIS2 document validation with OpenPEPPOL validation artefacts 3.4.0 was released.
We had a lovely two day F2F meeting hosted by BRZ. Approx. 70 people were attending. The first day started with an introduction section for newcomers and continued with a lot of presentation on what's going on. The second day had more of a workshop character with interactive sessions and that was highly appreciated by the attendees.
Finally the new PEPPOL website is live. It's definitively a great improvement. Check it out at http://www.peppol.eu.
phoss SMP 5.0.2 was released. This is a maintenance release with PEPPOL Directory API support.
A documentation on the PEPPOL PKI was started. Click here to read the details.
Additionally a new page called
The first parts of the European Norm for e-Invoicing have been finally approved.
Now PEPPOL can move forward on adopting the EN in their BIS.
Finally the new Document Validation Webservice is provided. Click here for Webservice details. This Webservice allows you to use all validations also available on the manual validation page.
Additionally the CEN/TC 434 / EN 16931 validation artefact drafts (!) as of today are available for usage in validation!
Finally the BIS2 document validation with OpenPEPPOL validation artefacts 3.3.0 is available. Additionally support for Simplerinvoicing 1.1 was added. Click here to validate your business document.
The slides of the presentations from the London face to face meeting are now available:
I added a new page that explains the document exchange. It shows how the PEPPOL participant ID, the DNS and the SMP work together.participant information page was changed so that arbitrary participant identifier schemes can be tested.
Finally the CEF conformance testing was finished successfully so I'm proud to present to you phoss SMP. This is now the official project name of the previous "ph-peppol-smp-server". Compared to RC2 no functional changes were performed - just UI beautifications. To see version 5.0 in action have a look at http://smp.helger.com. If you want to learn more about phoss SMP features, just request a demo user (via email or the contact form).
OpenPEPPOL PoACC fall release published. They get mandatory by 2016-11-15 (12:00 CET).
Update to my PEPPOL SMP Server.
Includes some functional improvements. Read more at
Update to my PEPPOL SMP Server.
Once the conformance test with CEF is finished, version 5.0.0 will be released!
OpenPEPPOL PoACC fall release published for review.
They get manadatory by 2016-11-15 (12:00 CET).
In this version OpenPEPPOL decided to no longer maintain the ODS files, and instead directly work on the Schematron files - what a pitty.
OASIS is pleased to announce the approval and publication of a new Committee Specification
by the members of the OASIS Business Document Exchange (BDXR) TC:
Service Metadata Publishing (SMP) Version 1.0, Committee Specification 03
Note: this SMP specification is not yet used in OpenPEPPOL, but there are plans to do so in the future.
Note: my SMP Server 5.0.0-Beta1 already supports this specification version!
In a Letter of Understanding (LoU) signed between the Commission and OpenPEPPOL, the parties agree a plan for the transition from AS2 to AS4 in the PEPPOL profile of CEF eDelivery. As part of this, support for SMP/SML lookup and PKI specifications as used in the PEPPOL eDelivery network will continue in the CEF eDelivery architecture.
Finally the production SML was updated to version 3.
It improves integration with PEPPOL Directory as well as customizability in general. Look on GitHub Wiki for further details.
PEPPOL SMP Server v5 is approaching. It improves integration with PEPPOL Directory as well as customizability in general. Compared to previous versions, this version needs a JDK 8 to run. Look on GitHub for further details.
PEPPOL Validation Artefacts 3.2.0 were released. The latest version can be found at https://joinup.ec.europa.eu/svn/peppol/Validation Resources/BIS v2/
SMP Server release 4.0.3 is out. It fixes the problem that service group deletions were not propagated to the SML when using the SQL backend and adds an overview page with all tasks and action items.
The SMK release was updated to version 3.0.1 which fixes most of the mentioned problems.
My SMP Server 4.0.2 was released. It fixes the compatibility problems introduced by the SMK 3.0.0 release. If you are only using the SML client library, please make sure to use at least version 4.3.1.
Here is a list of issues I've identified with the new SMK 3.0.0:
Finally a first version of the BIS2 document validation is available on this page. Click here to validate your business document.
A new version (3.0.0) of the SMK (not SML) was deployed by DIGIT. It contains the following new features:
If you are still using PEPPOL LIME there is good news for you. I grabbed the deprecated CIPA component and am providing a LIME server and client based on AS2. Have a look at it at https://github.com/phax/peppol-lime.
Added information about my new SMP release 4.0.0. It includes a management GUI for easily creating service groups, endpoints and redirects. Read all the details or quick start at https://github.com/phax/peppol-smp-server.
Added information about the SML support since these information are hard to find if you can't find the original email anymore. Read all the details.
New versions of my SMP server will be released soon. Version 4 of peppol-smp-server ships with a brand new administration interface that gives you the possibility to manage your endpoints with nice forms directly in the browser.
The development of the PEPPOL Yellow Pages progresses. Follow the development on GitHub at peppol-yellow-pages. Helping hands are always welcome.
New PEPPOL validation artefacts are out for review.
The ZIP file
with the Schematron and XSLT files can be downloaded.
are also available.
Deadline for submitting comments to email@example.com is October 1st 2015.
On June 9th the SML migration from BRZ to the EC took place. Read this page for all the details!
Based on the CIPA SMP server 2.2.3 I decided to fork my own clone of a PEPPOL SMP. It is available in 2 different versions:
Based on my previous projects as2-lib, as2-peppol-servlet and ph-ubl and peppol-sbdh I created a minimal PEPPOL AS2 server for receiving PEPPOL AS2 messages. The project as2-peppol-server is located on GitHub and available as OSS under the Apache 2.0 license.
CIPA 2.2.3 is a minor update that basically extends the SMP client and the SML
client library functionality. Additionally the class
got deprecated because I assume it is of no further need as the original author (BRZ)
no longer needs it (for quite some time now).
Because of the SSL 3.0 vulnerability called POODLE (see http://en.wikipedia.org/wiki/POODLE) certain PEPPOL APs may disable SSL 3.0 on their systems.
For the Oracle Java Runtime the code of the
AccessPointClient is fine.
So when you are using the Oracle JDK no further actions need to be taken.
But when using the IBM Java Runtime please make sure that you
set the constant
SSL_PROTOCOL in class
A new release of the
cipa-start-client was build, which fixes this problem for IBM JDKs.
The version number of the fix release is 2.2.2-1 and it can be found in the
Joinup Nexus (binary format -
and in the CIPA SVN (sources -