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

Michael Norman commented on CAMP-190:
-------------------------------------

Hi Gil,

I now remember seeing this problem when I was drafting the proposal. I should probably have spent a little more time drafting the proposal tohelp the editor.  I think it is worth noting that this relationship wasn't ever previously specified in the proposal, so we are tightening something up rather than resolving a new problem.

Couple of things.  There is a one to many relationship between type_definitions and attribute_definitions, otherwise the type_definition attribute of the attribute_definition wouldn't make sense.  So we need "the attribute_definition resource provides metadata that defines represents exactly one supported attribute exactly one resource type supported by the Platform".
Once this is in place, the easiest way to define the requirement is by reference to the term "general representation" which we use in the specification. 	So we can say something like "The value of this attribute defines the name of the attribute as it appears in the general representation of the resource named in the described_type attribute of the attribute_definition"

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