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-285) Import grammar is incorrect


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

Paul Lipton commented on TOSCA-285:
-----------------------------------

Presented by Chris to the TC on 2016-06-30. Not clear if changed in spec. Comments/updates invited. 

> Import grammar is incorrect
> ---------------------------
>
>                 Key: TOSCA-285
>                 URL: https://issues.oasis-open.org/browse/TOSCA-285
>             Project: OASIS Topology and Orchestration Specification for Cloud Applications (TOSCA) TC
>          Issue Type: Bug
>          Components: Profile-YAML, Spec - Simple Profile
>            Reporter: Chris Lauwers
>            Assignee: Matthew Rutkowski
>
> I finally got around to implementing the extended "imports" grammar and noticed issues with both the single-line and the multi-line grammar for imports. Imports grammar is as follows:
> 3.5.7.2.1 Single-line grammar:
> <import_name>: <file_URI>
> 3.5.7.2.2 Multi-line grammar
> <import_name>:
>   file: <file_URI>
>   repository: <repository_name>
>   namespace_uri: <definition_namespace_uri>
>   namespace_prefix: <definition_namespace_prefix>
> In both cases, the grammar specifies that imports have an "import_name". However, none of the YAML templates in the spec ever use such an import_name, and in any event, since there really isn't a use for such a name enforcing it would result in an unnecessary burden.



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