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-167) New JSON RFC

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

Alex Heneveld commented on CAMP-167:

Would be nice to have primitives (eg strings, ints) be allowed as valid JSON (which Anish points out is permitted in this spec) but I think given concerns about support in existing libraries and therefore interoperability I think it is safer not to update at this point.

Let's review the versions of specs we reference in the future and perhaps revisit this for JSON as well as YAML in CAMP v.Next.

> -------------
>                 Key: CAMP-167
>                 URL: https://tools.oasis-open.org/issues/browse/CAMP-167
>             Project: OASIS Cloud Application Management for Platforms (CAMP) TC
>          Issue Type: Bug
>          Components: Public Review
>            Reporter: Ashok Malhotra
>            Priority: Minor
> There is a revised JSON RFC.  See https://www.oasis-open.org/apps/org/workgroup/camp/email/archives/201403/msg00012.html
> We should discuss what, if any changes are needed in the CAMP Spec.  At a minimum we may want to
> change the normative reference.  Anish argues in https://www.oasis-open.org/apps/org/workgroup/camp/email/archives/201403/msg00013.html that no changes are needed in the spec.

This message was sent by Atlassian JIRA

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