edugain-discuss AT lists.geant.org
Subject: An open discussion list for topics related to the eduGAIN interfederation service.
List archive
- From: Peter Schober <peter.schober AT univie.ac.at>
- To: edugain-discuss AT geant.net, edugain-tsg AT geant.net
- Subject: Re: [eduGAIN-discuss] [eduGAIN-SG] issue on metadata flow
- Date: Mon, 7 Jul 2014 14:44:00 +0200
- Authentication-results: prod-mail.geant.net (amavisd-new); dkim=pass header.i= AT univie.ac.at
- List-archive: <https://mail.geant.net/mailman/private/edugain-discuss/>
- List-id: eduGAIN discussion list <edugain-discuss.geant.net>
- Organization: ACOnet
* Nicole Harris <harris AT terena.org> [2014-07-07 14:05]:
> I think that the correct action here is to remind the SP
> http://scitation.aip.org/ that it should not consume the metadata
> tagged as "eduGAIN" at this point in time.
But how does that fit in with REFEDS' (and others') attempts to make
it /easier/ for SPs to federate (or interfederate)?
"Here's some metadata /and/ here are the rules you'll have to
implement to process it (otherwise the UX will suck and other
federations will complain" does not seem like something we want
publishers having to go through, let alone with /different/ rules from
each federation they need to peer with.
But then it's unlikely smaller federations who had -- or still have --
to wait for several years in order to federate with an SP in the first
place probably won't ever be in a position to get the SP to implement
their custom rules. So it's probably a non-issue after all... sigh.
-peter
PS: http://scitation.aip.org/ does not list /all/ IDPs within eduGAIN,
some of our participating institutions are missing, for some reason.
Not that being available in that list would give them access, even if
they did license content and had contracts in place.
- Re: [eduGAIN-discuss] [eduGAIN-SG] issue on metadata flow, (continued)
- Re: [eduGAIN-discuss] [eduGAIN-SG] issue on metadata flow, Ian Young, 07-Jul-2014
- Re: [eduGAIN-discuss] [eduGAIN-SG] issue on metadata flow, Glenn Wearen, 07-Jul-2014
- Re: [eduGAIN-discuss] [eduGAIN-SG] issue on metadata flow, Tomasz Wolniewicz, 07-Jul-2014
- Re: [eduGAIN-discuss] [eduGAIN-SG] issue on metadata flow, Glenn Wearen, 07-Jul-2014
- Re: [eduGAIN-discuss] [eduGAIN-SG] issue on metadata flow, Ian Young, 07-Jul-2014
- Re: [eduGAIN-discuss] [eduGAIN-SG] issue on metadata flow, Peter Schober, 07-Jul-2014
- Re: [eduGAIN-discuss] [eduGAIN-SG] issue on metadata flow, Ian Young, 07-Jul-2014
- Re: [eduGAIN-discuss] [eduGAIN-SG] issue on metadata flow, Ian Young, 07-Jul-2014
- Re: [eduGAIN-discuss] [eduGAIN-SG] issue on metadata flow, Nicole Harris, 07-Jul-2014
- Re: [eduGAIN-discuss] [eduGAIN-SG] issue on metadata flow, Peter Schober, 07/07/2014
- Re: [eduGAIN-discuss] [eduGAIN-SG] issue on metadata flow, Ian Young, 07-Jul-2014
- Re: [eduGAIN-discuss] [eduGAIN-SG] issue on metadata flow, Andy Bennett, 07-Jul-2014
- Re: [eduGAIN-discuss] [eduGAIN-SG] issue on metadata flow, Ian Young, 07-Jul-2014
- Re: [eduGAIN-discuss] issue on metadata flow, Ian Young, 07-Jul-2014
- Re: [eduGAIN-discuss] issue on metadata flow, Lalla Maria Laura Mantovani, 07-Jul-2014
Archive powered by MHonArc 2.6.19.