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

Alex Heneveld commented on CAMP-190:

Like this proposal, it fixes the problem that `name` is abused on at least one of these resources, and that the meaning of `name` is unclear.

I think we should add language to 5.4.2

    "name" there for information purposes; it may be used directly in the GUI in some places, or it may be a key for an internationalization scheme (not currently in scope but possible through extensions).

And decide whether it is `described_xxx` or `defined_xxx` or `xxx_being_defined`.

Then LGTM.

> 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]