RE: [tosca] [OASIS Issue Tracker] (TOSCA-285) Import grammar is incorrect

[Chris Lauwers <lauwers@ubicity.com>]

Using the import name as the namespace prefix would preclude cases where files are imported without assigning a namespace name or where multiple files are imported in the same namespace (e.g. the default namespace)

Chris

-----Original Message-----
From: tosca@lists.oasis-open.org [mailto:tosca@lists.oasis-open.org] On Behalf Of OASIS Issues Tracker
Sent: Wednesday, October 12, 2016 10:16 PM
To: tosca@lists.oasis-open.org
Subject: [tosca] [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=63780#comment-63780 ] 

Luc Boutier commented on TOSCA-285:
-----------------------------------

Hi Chris,

I guess the import 'name' could be the namespace prefix. We don't have namespace example and I even don't use them right now but as there definition for them I guess we should be able to define a prefix..

What do you think ?

Luc

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

---------------------------------------------------------------------
To unsubscribe from this mail list, you must leave the OASIS TC that generates this mail.  Follow this link to all your TCs in OASIS at:
https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php