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

Gilbert Pilz commented on CAMP-190:

1.) Currently multiple type_definition resources can reference the same attribute_definition resource provided (a) they use the same name for the attribute and (b) the required, mutable, and consumer-mutable constraints agree. Do I understand your suggested language of "the attribute_definition resource provides metadata that defines represents exactly one supported attribute exactly one resource type supported by the Platform" to mean that you would like to explicitly forbid the reuse of attribute_definition resources across multiple type_definition resources?

2.) We shouldn't confuse the attribute_definition:type_definition attribute with the meta-mechanics of defining types and attributes. The 'type_definition' attribute of the attribute_definition resource functions no differently than the 'type_definition' attribute of any other resource. It is a reference to the type_definition resource that defines the type of this resource (an attribute_definition resource). The meta-ness of this attribute is one level less than most of the other attributes in the attribute_definition resource.

3.) I am confused by the following suggested wording for describing the 'defined_attribute' attribute:

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

None of the proposals so far have added a 'described_type' attribute to the attribute_definition resource. Your original proposal added 'described_type' to the type_definition resource and 'described_attribute' to the attribute_definition resource. In last weeks meeting we agreed to change these to 'defined_type' and 'defined_attribute', respectively. This sounds like you want to add two new attributes to the attribute_definition resource.

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