OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

camp message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]

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

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

David Laurance commented on CAMP-190:

Reviewing the specification with localization / customization in mind, I am coming to the view that there should be no language customization in any of the protocols between CAMP Provider and CAMP Consumer.
> Supporting multiple human languages in a machine protocol is confusing at best and can lead to ambiguities or incompatibilities at worst.
> I found no text intended solely for humans in the protocols between Provider and Consumer.  My conclusion is that the Consumer is already responsible for communicating with humans.
> I did not find requirements for how the Consumer should communicate with human users.
> Users are free to add annotations to CAMP Plans, for example, in languages other than English.

Is it worthwhile summarizing this point in the specification?  If so, it should perhaps be in 1.4 (Non-Goals).  Perhaps something like this:

Management interfaces defined in the CAMP specification are intended to communicate between CAMP Provider and CAMP Consumer.  Names for interfaces and their associated attributes are defined in this specification using English terminology.  This specification does not provide for translation of English terms into other human languages.  Translation or other localization concerns may, of course, be supported by a CAMP Consumer in user interfaces, but localization  / customization is otherwise out of scope for this specification.

> 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

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]