[OASIS Issue Tracker] Commented: (CAMP-52) Use of Cardinality for JSON array attributes

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

    [ http://tools.oasis-open.org/issues/browse/CAMP-52?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=32587#action_32587 ] 

Tom Rutt commented on CAMP-52:
------------------------------

I propose the following resolution for this issue:

Change clause 5.2.1 from:
"
5.2.1 Cardinality
This constraint indicates the cardinality of the attribute.
"

to:

"
5.2.1 Required
If the required attribute constraint has value "false",  then
messages defined using that attribute are valid both with and without the attribute present.

If the value is "true" then the messages are valid only if the attribute is present. 
"

Throughout the spec change all specifications of the Cardinality attribute constraint in resource definitions to use the Required attribute constraint. 
 If the Cardinality constraint includes a 0 lower bound, the Required constraint should be "false".  
 If the Cardinality constraint has a 1 lower bound, the Required constraint should be "true"



> Use of Cardinality for JSON array attributes
> --------------------------------------------
>
>                 Key: CAMP-52
>                 URL: http://tools.oasis-open.org/issues/browse/CAMP-52
>             Project: OASIS Cloud Application Management for Platforms (CAMP) TC
>          Issue Type: Improvement
>          Components: Spec
>            Reporter: Tom Rutt
>
> There are several attributes defined with an array type (e.g, String[] . Link[])
> These attribute definitions have various cardinality values, including, 1, 0..1, or 0..*
>  It makes no sense for an array attribute to have cardinality 0..*, for this implies multiple arrays in the JSON serialization.
> In the case of 0..1 cardinality, Is there a difference in having an array present with 0 elements, versus not having the array present?
> In the case of 1 cardinality, is it allowed to have an array with 0 elements present for its serialization?
> There does not seem to be a way to specify that an array should not be present in the serialization with zero elements.  What is the difference between no attribute in the serialization, verses an array attribute with no elements?

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://tools.oasis-open.org/issues/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira