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] Created: (CAMP-52) Use of Cardinality for JSON array attributes


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

        


[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]