OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

tosca message

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


Subject: [OASIS Issue Tracker] (TOSCA-301) Wrong grammar definition pointing to non existent type


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

Matthew Rutkowski commented on TOSCA-301:
-----------------------------------------

These are interesting suggestions; however, the grammar is not incorrect. 

The <property_type> is a specific definition (just below) which says any valid TOSCA data type, which in turn has a specific definition.

For the 'required' value, the grammar again points consistently to the description below the schema which indicates it is a boolean value, which again, is a specific definition of boolean built on YAML's boolean (links to it), but allows us to simply call it 'boolean'.

I would personally, not change anything as this is how all the grammars are written throughout the document.  We could add more hyperlinks in the schema for this one case if it helps the reader click directly to the correct type/definition.

> Wrong grammar definition pointing to non existent type
> ------------------------------------------------------
>
>                 Key: TOSCA-301
>                 URL: https://issues.oasis-open.org/browse/TOSCA-301
>             Project: OASIS Topology and Orchestration Specification for Cloud Applications (TOSCA) TC
>          Issue Type: Bug
>          Components: Profile-YAML
>    Affects Versions: V1.1_CSD04
>            Reporter: Luca Gioppo
>
> At line 1369 we have the grammar definition of properties and we have:
> <property_name>:
>   type: <property_type> 
>   description: <property_description>
>   required: <property_required>
>   default: <default_value>
>   status: <status_value>
>   constraints: 
>     - <property_constraints>
> It should be more proper to write:
> <property_name>:
>   type: <YAML Type> 
>   description: <description definition>
>   required: <YAML_BOOLEAN>
>   default: <default_value>
>   status: <property_status_value>
> etc....
> We do not have ANY "property_type" but a "YAML type"



--
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]