New project name for BIS3 upgrade project.
Status | DECIDED |
|---|---|
Stakeholders | @serge Libert (Fedict) (Unlicensed) @Dirk Willekens (Unlicensed) @Martin Forsberg @Siw Midtgård Meckelborg (Unlicensed) @Erlend Klakegg Bergheim (Deactivated) @Elisa Bertocchi (Unlicensed) @Soren.Pedersen@esv.se (Unlicensed) @SARA FACCHINETTI (Unlicensed) @A P @Jerry Dimitriou @Jan Andre Mærøe @Helena Ask (Unlicensed) |
Outcome | Name unchanged as PEPPOL BIS3 upgrade |
Due date | Feb 14, 2018 |
Owner | @Georg Birgisson (Unlicensed) |
Background
The current team name is similar to the BIS3 invoice project name. It was agreed in team meeting 2 to collect proposals from the team for a new name.
Team are invited to discuss name proposals by commenting to this decision.
Action items
Comments
As far as I understand the upgrade is mainly due to an alignment to EN 16931. Starting from the invoice profile and in cascade to the other Peppol profiles. If this is the case the name might be PEPPOL EN 16931 alignment
Hi, my impression is that this issue is not a pressing one and with the invoice project delivering and closing this problem of confusion is limited. I propose an outcome that we stay with the current name, PEPPOL BIS3 Upgrade. If no comments received on this further before next meeting I will update this decision accordingly.
I propose to stick to PEPPOL BIS3 upgrade, and incorporate the PEPPOL BIS 3 INVOICE into the project, just by including the deliverables of the previous project, i.e. the PEPPOL BIS 3 INVOICE project, into our project deliverables:) this is more or less what happens between PC 434 (now TC434) and TC 440.