[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:all-tabpanel ]

Gilbert Pilz updated CAMP-190:
------------------------------

    Proposal: https://www.oasis-open.org/apps/org/workgroup/camp/download.php/56312/camp-spec-v1.2-wd06-issue-190-v2.doc

throw new EditorsException("unable to process agreed upon resolution");

I know we agreed to resolve this, but I was unable to process that resolution due to a conflict with the new attribute_definit:defined_attribute. Mike's proposal called for the creation of a new requirement with the following wording:

The value of the defined_attribute in an attribute_definition resource SHALL match the name of the attribute that it describes.

The problem with this is that there is no matching taking place here. Unlike type_definition:defined_type (whose values matches the value of camp_resource:type for every resource with the type defined by this type_definition), the only record of the name of the attribute in a type_definition resource is the attribute_definit:defined_attribute itself. I took a stab at describing this in version 2 of the proposal which I have uploaded.

As an editor I have some leeway with regards to minor tweaks etc. to the agreed upon resolution but, in this case (omission of an entire requirement), I felt that the difference between what the TC had agreed to and what I felt was reasonable was too great to gloss over.

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