Messages 2.5.2 - Clarify responsibilities when claims employ languages and scripts

Issue #802 resolved
Michael Jones created an issue

Mark Wahl asked "What is the requirement on the consumer? If a producer is allowed to use language codes, then SHOULD a consumer support it?"

That's a very good question. If I ask for “family_name” am I expected to handle the case where I get back “family_name#ja-Kana-JP” and “family_name#ja-Hani-JP” but not “family_name” and recognize that my request for "family_name" has been satisfied? Or am I expected to always get back “family_name” in addition to the claims with the language/script names?

We should probably clarify these questions in the specifications.

Comments (7)

  1. Michael Jones reporter

    Mark also asked this related question:

    Are there any semantics associated with the language tags? For example, would it be expected a consumer would ever see:

    "website":"http://markwahl.blogs.example.de", -- most of my readers are in Europe

    "website#en": "http://markwahl.blogs.example.com", -- my blog that's written in English

    "website#de": "http://markwahl.blogs.example.de", -- my blog that's written in German

    "website#x-klingon" : "http://trekstuff",

  2. Michael Jones reporter

    We will recommend that OPs return claims without script tags when returning them in the user's requested script when there is only one requested script. But we will also recommend that Clients be prepared to handle claims returned with script tags.

  3. Michael Jones reporter

    We will clarify that in a multi-script environment, it is fine to only return human-readable claims with language tags (and not without language tags). We will also clarify that if an OP receives a request for claims in a script that it doesn't have, any claims returned that don't use the requested script must have a script tag attached.

  4. Log in to comment