Details on IT development in Poland (not part of EMREX field trial)

Recent activities

• 2015-12-07: Our NCP is now compatible with 1.0.0 schema, and it is basically ready to be tested. Unfortunately, it turned out that I'll need to wait for an appropriate test-server in order to make it available externally (ourside of our VPN). It might take some time.
• 2015-12-02: Resumed work on Polish NCP based on the new schema.
• 2015-11-24: Version 1.0.0 of the schema was released. Waiting for some final comments and vetoes.
• 2015-11-18: First comments have appeared (as of today, by Miika only). Started work on the next revision of the proposal (while still waiting for more comments).
• 2015-11-10: Published a proposal of a new well-documented XSD. Ceased further work while waiting for comments.
• 2015-11-07: Returned from Norway and resumed work. Cloned the EMREX schemas respository and started updating and annotating it, according to what I've recently learned.
• 2015-11-05: I have visited Norway and learnt a lot about the actual state of affairs.
• 2015-10-12: NCP implementation mostly complete, but I'm having serious trouble with ELMO docs and examples.
• 2015-10-01: I have joined the project, started reading EMREX docs and implementing NCP.

Retrieving the list of our NCPs

In Poland, every HEI has a separate authentication system. Having multiple NCPs seems to be the most appropriate option.

• Option 1: We can provide a HTTPS URL with the dynamic list of all our NCPs. EMREG would fetch such list daily or hourly.
• Option 2: Alternatively, we could set up a cronjob and push the list to EMREG every time it changes, but this would probably require additional singing of such requests (e.g. with HMAC), hence, option 1 sounds easier.
• Option 3: Manually update the EMREG team via email messages, but we hope to avoid this.
• Option 4: We could set up an additional "man in the middle" NCP which would present the viewer with the list of "real" NCPs and provide redirection. This however seems ugly from UX perspective and, as far as I understand, that's exactly why EMREG has the singleFetch attribute (to avoid such "man in the middle" NCPs).

The format of this dynamically generated list is yet to be agreed upon, but the easiest option would be to follow the JSON format of the emreg/list service.

Implementation of NCP

Mostly complete, but the produced ELMO file is missing many crucial elements (because I couldn't find the proper documentation for them). The work on NCP will be resumed after the XSD is finalized.

Implementation of SMP

By SMP I mean the Java component only. Since - at this point - SMP seems to be fairly easy to implement - we are considering implementing it on our own, internally (to avoid the need of serving a separate Java application for our EMREX Client).

Implementation of the EMREX Client

Will start only after the NCP is finished.