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=63773#comment-63773 ] 

Chris Lauwers commented on TOSCA-285:

While going through Luc's test assertions, I noticed that this issue never got addressed. The main problem is that in v1.0 of the spec, the "imports" grammar uses a list of "named" imports, whereas all the examples use "unnamed" imports. This needs to get corrected. 

I would like to re-iterate my previous suggestion to make the grammar consistent with the examples (i.e. use unnamed imports) rather than the other way around since there is absolutely no use for the import name.

> 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:
> Single-line grammar:
> <import_name>: <file_URI>
> 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

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