20160602 - Meeting minutes, Thursday 2nd June 2016 - OpenNCP Steering Committee
OpenNCP Steering Committee Meeting
Estimated - 16:00 to 17:00 CET
Performed -
AGENDA
- 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:
Support document
OpenNCP Governance
MEETING NOTES
- Steering Committee
- Last meeting we discussed the role of OpenNCP and to narrow its scope
- We're migrating the community site to CEF where we can describe the different topics
- Front page need to be prepared, clarify the OpenNCP role to the other parts
- We need to align amongst ourselves the following with regards to the OpenNCP Community
- Vision
- Mission - Open question to be addressed
- Provide up to date technical specifications/implementation? for eHealth: architecture, role of each component...
- AS IS we have technical implementation not in line with technical specifications
- markus.kalliola: We cannot go further than the role given to us by eHN - cf CEF work programme and governance model
- CP process: Change proposal process (work in progress)
- Develop and provide the best reference implementation possible of the epSOS specifications
- Support the ones that are using the OpenNCP reference implementation
- Provide up to date technical specifications/implementation? for eHealth: architecture, role of each component...
- Strategy
- Milestones
- Tasks
- Resources
- Separation of OpenNCP activity compared to the other activities (eHN, JASeHN...)?
- 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
- The OpenNCP should focus on technical implementation
- Specification's maintenance for design cross border services eP, PS specs?
- Example: Non-repudiation specifications
- Update of Gazelle, the testing tool having official specifications (pointing to epSOS specs)
- Not enough resources to implement
- 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
- Soeren has raised change proposals to EXPAND, not implemented in technical specifications
- Question? How will we achieve that?
- We need to have specs updated, then who is responsible to update specifications?
- EC did not receive the final specifications from Expand, this is therefore a bit tricky to refer to documents paragraphs...
=> Discussion ongoing.
- EC did not receive the final specifications from Expand, this is therefore a bit tricky to refer to documents paragraphs...