1 / 5

Attribute Harmonisation

In this discussion, Andrew Cormack, Chief Regulatory Adviser at JANET(UK), emphasizes the importance of harmonising terminology to ensure shared understanding across various stakeholders. Clarity in language reduces misunderstandings, such as variations in terms like "bill/check" or "citation/endorsement." By proactively defining essential terms and reacting to emerging needs, we can minimise needless negotiation and avoid redundant language development. The presentation draws on UK academic experience, advocating for core attributes and integration protocols to facilitate effective communication and service licensing in educational networks.

minor
Télécharger la présentation

Attribute Harmonisation

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Attribute Harmonisation Andrew Cormack Chief Regulatory Adviser, JANET(UK) Andrew.Cormack@ja.net

  2. 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

  3. 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

  4. 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

  5. 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)

More Related