[OASIS Issue Tracker] (CAMP-191) Need a generic mechanism for constraining values of attributes

[OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org>]

     [ https://issues.oasis-open.org/browse/CAMP-191?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Anish Karmarkar updated CAMP-191:
---------------------------------

    Priority: Trivial  (was: Major)

> Need a generic mechanism for constraining values of attributes
> --------------------------------------------------------------
>
>                 Key: CAMP-191
>                 URL: https://issues.oasis-open.org/browse/CAMP-191
>             Project: OASIS Cloud Application Management for Platforms (CAMP) TC
>          Issue Type: Bug
>            Reporter: Mike Norman
>            Priority: Trivial
>
> The general approach that I am taking is that the client reads the Type definition and the Attrinute Definitions and uses that to construct the UI components that allow the user to read, create and update the resources.
> The resources come back as json, which gets deserialized into the basic json types.  Over that there are then additional constraints provided by the Attribute Definitions , namely URIs and Timestamps which are effectively constraints on the String type, and Links which are special json objects.
> In extensions it's quite possible we need additional constraints such as field lengths for strings (text boxes vs. text areas) and integer/double and/or range constraints on numeric types.  There doesn't appear to be a way of doing this via the API except by extending the ATtribute Type, which is a bit unsatisfactory because it's a completely different mechanism from the way the timestamp constraint is being specifiied.
> We also need to be able to deal with constrained URIs.  Possibly the best example is when you are using the GUI to create an assembly from a Plan by reference.  6.11.1 You need to populate a gui control (e.g. a listbox) with the set of available plans (on the Platform, or possibly other Platforms).  There's no obvious way of retrieving this list via the API.  



--
This message was sent by Atlassian JIRA
(v6.2.2#6258)