[OASIS Issue Tracker] (CAMP-190) Localization/Customization of Attribute Definition and Type Definition names

[OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org>]

    [ https://issues.oasis-open.org/browse/CAMP-190?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=62477#comment-62477 ] 

Gilbert Pilz commented on CAMP-190:
-----------------------------------

In my limited experience attribute names are rarely surfaced to the UI. The are used primarily as keys into the local JSON objects. My preference, as far as attribute values, is not (1) and not (3). You can't really tell a Consumer implementer that they can't do (2), so it is always an option.

I'd like to discuss what the spec should actually say about this. As far as attribute values go, should the requirement on the Provider to translate values according to "Accept-Language" be a MAY, SHOULD, or MUST? Should we say anything at all about attribute names, or just remain silent?

> Localization/Customization of Attribute Definition and Type Definition names
> ----------------------------------------------------------------------------
>
>                 Key: CAMP-190
>                 URL: https://issues.oasis-open.org/browse/CAMP-190
>             Project: OASIS Cloud Application Management for Platforms (CAMP) TC
>          Issue Type: Bug
>    Affects Versions: 1.2
>            Reporter: Michael Norman
>            Assignee: Michael Norman
>            Priority: Minor
>
> The Attribute Definitions and the Type Definitions seem to link their names to the name of the resource/attribute in the spec (although this is only clear to me for the attribute definition). However there may be a requirement for a different name to be used in the User Interface as a less formal word to describe the attribute or resource, and indeed to deal with localization. It would be useful for there to be two names in these resources, one which is linked to the resource/attribute and one which is both user-mutable and locale-specific (e.g. it may be possible for an implementation to issue different values based on http request header localization).



--
This message was sent by Atlassian JIRA
(v6.2.2#6258)