22nd October 2008 - Launch meeting minutes
Contents |
Participation
14 people has participated in the launch meeting of this Liberty HR-EDU SIG, representing the following organisations:
- Diginotar (NL)
- EIfEL (FR)
- Entr'Ouvert (BE)
- e-Works (AU)
- iProfile.org (UK)
- Stepstone (UK)
- Symlabs (PT)
- 3s Unternehmensberatung (AU)
- University Koblenz-Landau (DE)
- University of Kent (UK)
- University Karlsruhe (DE)
This meeting was hosted by TAS3 EU Project inside the ePortfolio and Digital Identity Conference organised by EIfEL in Maastricht.
Discussions
Some of the issues discussed during the meeting:
Support of HR-XML 2.5 or v3 specification for a proposal of the HR SIS ?
Decisions : Moving to HR-XML v3 specs and using the Candidate schema in standalone XML schema file. In addition this should support both iProfile HR-XML profile as well as Europass CV HR-XML profile. The CVT webervice could be use for cross interop.
EIfEL, iProfile and Stepstone has agreed to support these specs. An interop demonstration scenario will involve this three organisations showing iProfile CV data export to Stepstone as well as Europass HR-XML CV export to Stepstone.
It should be able to do distinction of the HR-XML profile used using a specific version attribue in the ID-WSF exchange.
Support of Liberty Discovery Service when several same ID-SIS data are availale for a user ?
'Example : the user as a CV in both iProfile Attribute Provider Service as well as in Universal CV Attribute Provider Service in a same circle of trust. Current implementation in Universal CV : in this project the DS send back to the requesting service the data available in the first available provider service. To avoid to much request to the CV Owner it should be possible to remember sharing settings already defined by the User.
Issue for iProfile is related to a second level of user attribute provider (aka when the educational data is hosted by different universities, like Europass diploma supplement, how to manage the request / selection of data by the CV owner ? This should imply the use of Interaction Service and cascading of user interactions with the system, see next point).
Recommendation from Sampo : it is easier to include the Disco Service with the IDP except if there is legal requirements.
Support of Liberty Interaction Service to request user ageement ?
Current implementation in Universal CV: to avoid the use of Interaction Service, the user previously select in is Attribute Provider Service if he accept or not to share is CV with all requestig services in the circle of trust.
To continue... (Sampo contribution welcome)
OpenID CV attribute support ?
Proposal: In order to be compliant with the OpenID attribute exchange specifications it is necessary to redefine the CV elements and attributes using the OpenID axschema definition which is not possible in this first step, a possibility is to bind HR-XML CV data as an XML "blob" string on top of the attribute exchange specs.
CV Infocard ?
Still to be discussed, it seems that it should be possible to use XML schema (so HR-XML v3 Candidate schemas), this as to be explored in the next coming months.
Paper board copies
Please find below copies of paper board (coming soon, a security issue avoids actually to upload them):
