20160602 - Meeting minutes, Thursday 2nd June 2016 - OpenNCP Steering Committee

Owned by michele.foucart
Last updated: Jun 03, 2016
2 min read

OpenNCP Steering Committee Meeting

 

Estimated - 16:00 to 17:00 CET

Performed -

AGENDA

  1. Steering Committee

 

LOCATION

  Adobe Connect

http://ec-wacs.adobeconnect.com/openncp/

Room Passcode:  markus.kalliola or Licinio Kustra Mano

----------------

If you have never attended an Adobe Connect meeting before:

Test your connection: http://ec-wacs.adobeconnect.com/common/help/en/support/meeting_test.htm

Get a quick overview: http://www.adobe.com/products/adobeconnect.html

Adobe, the Adobe logo, Acrobat and Adobe Connect are either registered trademarks or trademarks of Adobe Systems Incorporated in the United States and/or other countries.

PARTICIPANTS

Today's Meeting Participants:

Licinio Kustra Mano

Soeren Bittins

markus.kalliola

michele.foucart

Support document

OpenNCP Governance

Governance Model 

MEETING NOTES

  1. Steering Committee
    1. Last meeting we discussed the role of OpenNCP and to narrow its scope
    2. We're migrating the community site to CEF where we can describe the different topics
      1. Front page need to be prepared, clarify the OpenNCP role to the other parts
    3. We need to align amongst ourselves the following with regards to the OpenNCP Community
      1. Vision
      2. Mission - Open question to be addressed
        1. Provide up to date technical specifications/implementation? for eHealth: architecture, role of each component...
          1. AS IS we have technical implementation not in line with technical specifications
          2. markus.kalliola: We cannot go further than the role given to us by eHN - cf CEF work programme and governance model
          3. CP process: Change proposal process (work in progress)
        2. Develop and provide the best reference implementation possible of the epSOS specifications
        3. Support the ones that are using the OpenNCP reference implementation
      3. Strategy
      4. Milestones
      5. Tasks
      6. Resources
    4. Separation of OpenNCP activity compared to the other activities (eHN, JASeHN...)?
      1. Dependant of other projects, engagements...how could we influence when we do not have room to influence. Challenge on how OpenNCP need to develop, go forward
      2. The OpenNCP should focus on technical implementation
      3. Specification's maintenance for design cross border services eP, PS specs?
          1. Example: Non-repudiation specifications
          2. Update of Gazelle, the testing tool having official specifications (pointing to epSOS specs)
      5. Not enough resources to implement
      1. In 2012 Carecom provider made updates on the data model - we cannot change the service provider without significant developments on LTR and transformation manager. Then if we update, specifications won't been up to date any more
      2. Soeren has raised change proposals to EXPAND, not implemented in technical specifications
        1. Question? How will we achieve that?
      3. We need to have specs updated, then who is responsible to update specifications?
        1. EC did not receive the final specifications from Expand, this is therefore a bit tricky to refer to documents paragraphs...
          => Discussion ongoing.