50 likes | 173 Views
Attribute Harmonisation. Andrew Cormack Chief Regulatory Adviser, JANET(UK) Andrew.Cormack@ja.net. Why?. So words mean the same thing No Humpty Dumptys Reduce misunderstandings “bill/check”, “citation/endorsement”, “pavement” NB don’t even need translation to create these
E N D
Attribute Harmonisation Andrew Cormack Chief Regulatory Adviser, JANET(UK) Andrew.Cormack@ja.net
Why? • So words mean the same thing • No Humpty Dumptys • Reduce misunderstandings • “bill/check”, “citation/endorsement”, “pavement” • NB don’t even need translation to create these • To minimise wheel re-invention • Avoid pairwise languages • unless the term only matters to a pair • Reduce effort/negotiation
How? • Proactive • Define everything we might ever need to say • Lots of effort up-front • Much of which may never be needed • Reactive • Document what we have said • Define how to say new things • Only invent as much as we need
Past UK AM Experience • Very small vocabulary required (ATHENS) • Known user • Unique label for this user • Covered by this Licence Agreement • Only two kinds of authorisation rule • Those organisations • Those individuals • Other stuff (e.g. VLE) pre-loaded in bulk • Use MIS integration protocols, not attributes
So UK recommends • Core attributes (wheels we made earlier) • ePSA, ePTID (privacy improvement), ePE, ePPN • Recommend (but don’t mandate) that • All IdPs be able to provide these if required • All SPs base services/licences on these • Subsidiary attributes (wheels a lot of you use) • None so far; will be documented as they arise • SPs/IdPs suggest candidates • Additional attributes (wheels other people use) • Recommend borrowing from eduPerson etc. • Custom attributes (wheels you make yourself)