Project Progress

Evolutive Maintenance

Technical Office Milestones

Change Requests

• Unable to render Jira issues macro, execution error.

• • AF presented the RfC that allows search function and will list participants (previously named "yellow pages");
  • JA clarified that when a company's name is searched, it gives an ID (this is the basic functionality);
  • PH confirmed, it is a reverse lookup function;
  • PH pointed out that on top of the two solutions provided in the comments of the RfC, there is a third one: option C where the business card is offered as a service by the participant;
  • SP suggested a one or two-day workshop in Brussels to agree on the way forward;
  • SRR stated that the directory is a much requested feature and would be a strong tool for e-Procurement;
  • AF pointed out that the discussion that happened in previous calls were summarised in the comments of the RfC; AF stated that the involvement of e-SENS and OASIS is needed. Change needs to happen on the specification level;
  • PH agreed and suggested an informal review of the user communities to gather requirements for specifications which could then be handed to OASIS;
  • PH asked if PEPPOL could wait or if the solution A should be selected;
  • SRR stated that more elements are needed on the SMP;
  • AF asked if the service to list participants in the SML would be ok for solution A or C.
  • PH stated that the service couldn't yet be called but should be sufficient;
  • AF stated that the less changes in the specifications, the better and the faster the solution will be; therefore, solution B where the EC hosts a central service containing the business cards is not the preferred option for the EC
  • GC summed up by stating that solution A or C is preferred;
  • PH stated that the differences between solution A and C can be discussed in a workshop;
  • AF informed that a date will be suggested by the CEF SMO to organise a workshop between OASIS, eSens, PEPPOL and the EC in November.

•   Unable to render Jira issues macro, execution error.
  • AF informed that the RfC came from BRIS project to be able to use PostgreSQL database, for now only MySQL is supported. AF informed that for the BRIS community, this would be a risk and a problem as it would open the gate for the support of other DB and application servers.
  • FR stated that it is important to have low cost alternatives to MySQL to have a higher number of participants;
  • AF informed that a technical assessment was performed and that thanks to the ORM, it wouldn't be costly. There is however an issue with documentation and knowledge for PostgreSQL, it would also multiply the number of combination for testing. AF stated that the tool "docker" could help with the testing;
  • AF stated that a possible solution would be to unofficially include PostgreSQL, AF asked if NRW could then provide support and answer questions in the beginning;
  • NN answered positively but added that a disclaimer should probably be added;
  • JFR stated that if we accept one new database, we could not refuse others;
  • NN stated that it is understandable and that only two databases might create a massive delay for implementation;
  • JFR stated that Domibus is a sample implementation and is not meant to support all the available databases and application servers.
  • AF summed up by stating that configuration files and support should be provided by the user of the database community;
  • JFR added that the solution would not be tested, supported or documented by CEF;
  • FR stated that if would be good to allow MSs to use and support their own databases;
  • JFR stated that NRW has to define support and documentation for what they are going to do and this will be shared in the eDelivery community space with the above-mentioned disclaimer;
  • KL informed that a new meeting will be setup when the community space is ready to define what exactly to put in the space;
  • SN agreed to organise a meeting about this the week of the 17th of October;
  • NN asked if this will be supported in Domibus 3.2 officially;
  • AF answered that if will not be officially supported but there will be a redirection to the open source community.

Operations 

Communication