[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [OASIS Issue Tracker] Updated: (CAMP-121) 4.3.3.3 requirements - array?
[ http://tools.oasis-open.org/issues/browse/CAMP-121?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Martin Chapman updated CAMP-121: --------------------------------- Proposal: Close no action but ensure that we use our pseudo-schema consitently We have added a pseudo-schema to 1.7 that addresses our use of the term array > 4.3.3.3 requirements - array? > ----------------------------- > > Key: CAMP-121 > URL: http://tools.oasis-open.org/issues/browse/CAMP-121 > Project: OASIS Cloud Application Management for Platforms (CAMP) TC > Issue Type: Bug > Components: Public Review > Reporter: Gilbert Pilz > > From the comment list: https://lists.oasis-open.org/archives/camp-comment/201309/msg00078.html > TAB issue: https://tools.oasis-open.org/issues/browse/TAB-96 > 4.3.3.3 requirements currently reads in part: > ***** > This array specifies the ways in which the artifact described by this Artifact Specification engages with the services provided by the platform. > ***** > What type of array is intended by "This array...?" > Is it a YAML sequence (which is ordered)? or it is closer to a mapping (unordered key/value pairs)? > Reasoning that even unordered pairs do have an order of appearance in a data stream, the prohibition against treating order of the array as significant doesn't exclude either of those possibilities. -- 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]