[OASIS Issue Tracker] (TOSCA-198) CSD02 - simplify "schema" specification

[OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org>]

     [ https://issues.oasis-open.org/browse/TOSCA-198?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Matthew Rutkowski  updated TOSCA-198:
-------------------------------------

              Summary: CSD02 - simplify "schema" specification  (was: simplify "schema" specification)
             Assignee: Matthew Rutkowski 
        Fix Version/s: CSD2
    Affects Version/s: CSD2

> CSD02 - simplify "schema" specification
> ---------------------------------------
>
>                 Key: TOSCA-198
>                 URL: https://issues.oasis-open.org/browse/TOSCA-198
>             Project: OASIS Topology and Orchestration Specification for Cloud Applications (TOSCA) TC
>          Issue Type: Improvement
>          Components: Profile-YAML
>    Affects Versions: CSD2
>            Reporter: Chris Lauwers
>            Assignee: Matthew Rutkowski 
>            Priority: Minor
>             Fix For: CSD2
>
>
> Property definitions can include an "entry_schema" key that is used to declare the schema definition for entries of “container” types such as the TOSCA list or map. The schema specification is currently somewhat confusing, since it seems to allow for 3 different ways to specify "names" associated with the schema:
> 1. There is a "type" key in the specification that can refer to a named type (either a built-in type of a custom type created in the "datatype_definitions" section of a template).
> 2. There is a "name" key in the specification that allows an arbitrary name to be associated with the schema
> 3. The "datatypes_definitions" key of a template specifies a name for each newly created schema external to the schema specification itself.
> I believe there is room for simplification.



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