1 / 8

Attribute Harmonisation: Bridging Language Gaps in Federation Systems

Explore the challenges and solutions in harmonizing attribute languages in federated systems, discussing common attributes, vocabulary consistency, and the impact of local variations. Learn how to define critical attributes, test definitions, and document issues for cross-language compatibility.

jada-floyd
Download Presentation

Attribute Harmonisation: Bridging Language Gaps in Federation Systems

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:Is it Possible? Andrew Cormack Chief Regulatory Adviser, JANET(UK) Andrew.Cormack@ja.net

  2. Tricks of Language • Languages have things in common • “Computer” (EN) == “Computer” (IT) • Things that look common but aren’t • “Cheque” (EN) != “Check” (US) • “Bill” (EN) != “Bill” (US) • “Pavement” (EN) != “Pavement” (US) • Things that are untranslatable • “Saudade”, “Hiraeth”, ...

  3. How about Attributes? • Federations develop • Common origin • Adapt to local needs • e.g. Course catalogues • May absorb local culture too • Can we communicate between these? • When I say “tomato” do you • Understand? Misunderstand? Look blank?

  4. Attribute Esperanto? • International attribute standards • eduPerson • SCHAC • Etc. • Should mean we use same words • But let’s look at a common attribute • eduPerson[Scoped]Affiliation • Specification has a controlled vocabulary

  5. Good News • Most values are used consistently • Member, faculty, student • Alum, affiliate, library-walk-in • At least as consistent as the real world • What is a student? Or a member? • When is an alumnus? • Where do I walk in? • ...

  6. Bad News • Staff • UK: anyone who works here • Everyone else: a worker who is not faculty • Employee • UK: a worker who is not faculty • Some others: anyone who works here • Some others: anyone with a contract • Some others: value not used • Some federations have local additions

  7. Does it Matter? • Maybe less than it appears • Many services only need member • E.g. Site licences • Some external services need enumerated lists • So broken values don’t matter • Use ePE (IdP enumerated) or ePPN (SP enumerated) • Some internal services need internal categories • So broken values don’t help • And don’t matter, because per-fed they are consistent • Anyway: individual may be staff & student & employee!

  8. What to Do? • Define the really important stuff • Test the definitions • With your country/language and others • Document problems for others’ benefit • Don’t expect too much • Remember that you aren’t in Kansas • Things may really be different over there

More Related