Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 2 Next »

 

Estimated: 13:00 to 14:00 CET.

Performed:  CET

Agenda

  1. Connectathon
    1. Feedback tests
    2. agreement on a let-it-fail configuration manager: singletons (O(nsec)) without notifications, allowing bursts
  2. Business analysis update
    1. see document "Comments_SMP_ICD_v0 10"
  3. Deployment environments: different environments for PPT and Prod or differenciation?
  4. Update from Oasis
    1. Source code license of the new OASIS-SMP
    2. Doubt on the usage of extensions for the additional signature
  5. Update cache?
  6. Updated roadmap?
    1. Projectathon for testing SMP/SML final developments?
    2. e-SENS eHealth pilot timing
      1. NCP autoconfigurationin June
      2. Pilot in October
  7. Next steps

Location

  • AdobeConnect:

http://ec-wacs.adobeconnect.com/openncp/
Room Passcode:  markus.kalliola or michele.foucart
------------------------------------------------------------------------------------------------
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.
------------------------------------------------------------------------------------------------

 

Meeting Notes

  1. Connectathon
    1. Feedback tests
    2. agreement on a let-it-fail configuration manager: singletons (O(nsec)) without notifications, allowing bursts
  2. Business analysis update
     "Comments_SMP_ICD_v0 10"
    1. § 3.5.2.2

      "The SignedServiceMetadata structure holds both a ServiceMetadata structure and the corresponding signature by the receiver to allow the user (or any other user) verifying the authenticity of the information provided by the SMP by using the public key of the receiver before sending him any document" –

       => does this still apply after the analysis of CR from OASIS TC (can we disclose it?)?

    2. §4.1.2

      To be updated according to feedback from OASIS TC: use "lax" –

       => Can we already disclose it in this doc?

    3. §4.4.2

      "eHealth will host its SMP instance" –

       => What does this mean? Will it be an authority different from DIGIT?

    4. §4.4.2
      Regarding this note from the previous comments: "This document is a generic one. This choice is left open to the various future implementations and therefore not specified in here."

      =>  maybe include it in the document?

  3. Deployment environments: different environments for PPT and Prod or differenciation?
  4. Update from Oasis
    1. Source code license of the new OASIS-SMP
    2. Doubt on the usage of extensions for the additional signature
  5. Update cache?
  6. Updated roadmap?
    1. Projectathon for testing SMP/SML final developments?
    2. e-SENS eHealth pilot timing
      1. NCP autoconfigurationin June
      2. Pilot in October
  7. Next steps


 


  • No labels