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-221) CharacteristicSpecification schema is incorrect

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

Michael Norman commented on CAMP-221:

The spec here is trying to deal with the fact that the "payload" of the characteristic specification is polymorphic, and the type of the payload is defined in a type system outside of the CAMP API, to which we provide a reference in the type attribute.
There are 3 different solutions to this that we have tried/seen with varying degrees of success.
1) as per the spec, we "unroll" the object into a sequence of <name>,<value> string pairs (assumes the type can be serialized that way)
2) Actually make it a String and let the platform parse it as an Object 
3) make it a JSON Object (we need to extend the base CAMP types I think)
4) define the CharacteristicSpecification recursively and make it either a base CAMP type or a collection of CharacteristicSpecifications

Preference is currently 3)

> CharacteristicSpecification schema is incorrect
> -----------------------------------------------
>                 Key: CAMP-221
>                 URL: https://issues.oasis-open.org/browse/CAMP-221
>             Project: OASIS Cloud Application Management for Platforms (CAMP) TC
>          Issue Type: Bug
>          Components: Spec
>    Affects Versions: 1.2
>            Reporter: Anish Karmarkar
>            Assignee: Anish Karmarkar
>            Priority: Critical
> CharacteristicSpecfication (for both YAML and JSON) schema is incorrect.
> It says the following for YAML (4.3.7):
> -----
> type: String
> String: String *
> -----
> and the following for JSON (5.13):
> -----
> "characteristics": [
>     {
>       type: String,
>       String: String *
>     } +
>   ] ?,
> -----
> It is not clear why there is an attribute name called 'String'. A JSON attribute name must be unique therefore the cardinality of "*" is not possible. It is also not clear why the value must be a 'String' (and not something like Number)

This message was sent by Atlassian JIRA

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