[Dev] Fwd: [refeds] Public consultation on the Data protection Code of Conduct

[Wim Kok]

Hi,

Will the code be signed by the CLARIN SPF  (via MPI or CLARIN-ERIC) or by the individual SP's?

Regards,

Wim

-----Oorspronkelijk bericht-----
Van: dev-bounces at lists.clarin.eu [mailto:dev-bounces at lists.clarin.eu] Namens Daan Broeder
Verzonden: dinsdag 26 juni 2012 10:28
Aan: CLARIN EU developers
Onderwerp: Re: [Dev] Fwd: [refeds] Public consultation on the Data protection Code of Conduct

Hi all,

So, yesterday was the kick-off of a pilot project concerned with investigating the acceptability of this Code of Conduct especially to the CLARIN community.
So let me add to Dieter's message that it is especially of interest to have administrators of SPs and IdPs look at the Code of Conduct and give feedback if this CoC would make them more inclined to sign or release their user's attributes. But any feedback is very welcome!

Best,
Daan

--
Daan Broeder
The Language Archive ­ MPI for Psycholinguistics
+31 24 3521103
daan.broeder at mpi.nl

P.O. Box 310
6500 AH Nijmegen, The Netherlands






On 6/26/12 10:19 , "Dieter van Uytvanck" <dieter.vanuytvanck at mpi.nl> wrote:

>Hi all,
>
>as you probably know we plan to join an eduGAIN pilot with the CLARIN
>SPs. Below you find the consultation on the corresponding Code of
>Conduct (which was circulated on the list in an earlier version too).
>
>best regards,
>Dieter
>
>-------- Original Message --------
>Subject:       [refeds] Public consultation on the Data protection Code of
>Conduct
>Date:  Tue, 26 Jun 2012 09:53:05 +0200
>From:  Mikael Linden <Mikael.Linden at csc.fi>
>To:    refeds at terena.org <refeds at terena.org>
>
>
>Dear REFEDS,
>
>
>
>REFEDS attribute release workgroup and eduGAIN task have been preparing
>a Data Protection Code of Conduct which aims at reducing the Home
>Organisations¹ risks (and hesitation) to release attributes to Service
>Providers in EU/EEA. The primary motivation has been interfederation
>(e.g. eduGAIN), but the Code of Conduct could be used also locally in
>federations.
>
>
>
>As mentioned in my presentation in Reykjavik, the Code of Conduct is
>now exposed to a public consultation and is available in:
>https://refeds.terena.org/index.php/Code_of_Conduct_for_Service_Provide
>rs
>
>- Cover letter: a short introduction (1 page)
>
>- GEANT Data Protection Code of Conduct: the document exposed to a
>public consultation (4 pages)
>
>- Comment form: Template for submitting your comments
>
>
>
>The consultation starts now and ends on the 12^th August, 2012. Please
>provide your comments to edugain-policy-comments at geant.net
><mailto:edugain-policy-comments at geant.net> using the template. To
>ensure transparency of the process, the comments and resolutions by the
>REFEDS wg and eduGAIN will be published.
>
>
>
>In particular, we would like to know
>
>- if you, as a Service Provider, feel comfortable to sign the Code of
>Conduct document
>
>- if you, as a Home Organisation, feel confident to release attributes
>to a Service Provider which has committed to the Code of Conduct
>
>
>
>As agreed in the REFEDS Reykjavik meeting, after this public
>consultation, a separate call for comments will be organized on the
>technical implementation of the Code of Conduct.
>
>
>
>On behalf of the eduGAIN task and the REFEDS attribute release
>workgroup,
>
>Mikael Linden
>
>_______________________________________________
>Dev mailing list
>Dev at lists.clarin.eu
>https://lists.clarin.eu/cgi-bin/mailman/listinfo/dev

_______________________________________________
Dev mailing list
Dev at lists.clarin.eu
https://lists.clarin.eu/cgi-bin/mailman/listinfo/dev

________________________________

----------------------------------------------------------
Aan dit bericht kunnen geen rechten worden ontleend.
Het bericht is alleen bestemd voor de geadresseerde.
Indien het bericht niet voor u is bestemd, verzoeken wij
u dit aan ons te melden en het bericht te verwijderen.

This message shall not constitute any obligations.
This message is intended solely for the addressee.
If you have received this message in error, please
inform us and delete the message.
----------------------------------------------------------