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-238) 4.3.1.3 tags - Says array but defines string.


    [ https://issues.oasis-open.org/browse/CAMP-238?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=67107#comment-67107 ] 

Anish Karmarkar commented on CAMP-238:
--------------------------------------

Not an issue.
Notational convention (1.7) explains this.
The pseudo-schema says that it is a string array. The serialization would specific how string arrays are serialized. For example in JSON it will be ["sting 1", "string 2, "string 3"]


> 4.3.1.3 tags - Says array but defines string.
> ---------------------------------------------
>
>                 Key: CAMP-238
>                 URL: https://issues.oasis-open.org/browse/CAMP-238
>             Project: OASIS Cloud Application Management for Platforms (CAMP) TC
>          Issue Type: Bug
>         Environment: Technical
>            Reporter: Chet Ensign
>
> 4.3.1.3 tags reads in part:
> *****
> This node expresses an array of human-readable tags for the Plan or Specification.
> *****
> However, its data type is listed as string[ ]. Moreover, none of the other 51 instances of "tags" defines the representation of this "array."
> Actually that's not entirely true because Example 7 (non-normative Example 7) does show:
> *****
> tags: [ PHP, Drupal6, mikez ]
> *****
> But, an example showing an array, created with comma + whitespace is hardly a normative definition of an array. 



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


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