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

["Norman, Michael" <michael.norman@jpmchase.com>]

Both David Laurance and I were struggling yesterday.

Mike

Dr. Mike Norman | Vice President | Cloud Development | JPMorgan Chase 
45 Waterloo Street, Glasgow, G2 6HS | Phone: +44 (0)141 2280 0853 | michael.norman@jpmchase.com


-----Original Message-----
From: camp@lists.oasis-open.org [mailto:camp@lists.oasis-open.org] On Behalf Of Gilbert Pilz
Sent: 24 August 2015 20:17
To: camp@lists.oasis-open.org
Subject: Re: [camp] [OASIS Issue Tracker] (CAMP-190) Localization/Customization of Attribute Definition and Type Definition names

I wanted to respond to this, but I can't login to Jira. Is anyone else having problems?

~ gp

On Aug 20, 2015, at 3:57 AM, OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org> wrote:

>
>    [
> https://issues.oasis-open.org/browse/CAMP-190?page=com.atlassian.jira.
> plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=60571#c
> omment-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)
>
> ---------------------------------------------------------------------
> To unsubscribe from this mail list, you must leave the OASIS TC that
> generates this mail.  Follow this link to all your TCs in OASIS at:
> https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php
>


---------------------------------------------------------------------
To unsubscribe from this mail list, you must leave the OASIS TC that
generates this mail.  Follow this link to all your TCs in OASIS at:
https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php


This communication is for informational purposes only.  It is not intended as an offer or solicitation for the purchase or sale of any financial instrument or as an official confirmation of any transaction.  All market prices, data and other information are not warranted as to completeness or accuracy and are subject to change without notice.  Any comments or statements made herein do not necessarily reflect those of JPMorgan Chase & Co., its subsidiaries and affiliates (collectively, "JPMC").

This transmission may contain information that is proprietary, privileged, confidential and/or exempt from disclosure under applicable law.  If you are not the intended recipient, you are hereby notified that any disclosure, copying, distribution, or use of the information contained herein (including any reliance thereon) is STRICTLY PROHIBITED.  If you received this transmission in error, please immediately contact the sender and destroy the material in its entirety, whether in electronic or hard copy format.  Although this transmission and any attachments are believed to be free of any virus or other defect that might affect any computer system into which it is received and opened, it is the responsibility of the recipient to ensure that it is virus free and no responsibility is accepted by JPMC for any loss or damage arising in any way from its use.  Please note that any electronic communication that is conducted within or through JPMC's systems is subject to interception, monitoring, review, retention and external production in accordance with JPMC's policy and local laws, rules and regulations; may be stored or otherwise processed in countries other than the country in which you are located; and will be treated in accordance with JPMC policies and applicable laws and regulations.

Please refer to http://www.jpmorgan.com/pages/disclosures for disclosures relating to European legal entities.