[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=62498#comment-62498 ] 

Anish Karmarkar commented on CAMP-190:
--------------------------------------

I'm also leaning towards (2) for attribute names.
For attribute values, the use of Accept-Language is well understood in the REST world. I don't think we really need any MAY/SHOULD/MUST for that. We can either merely point out the header and its use or just stay 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)