[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [OASIS Issue Tracker] (TOSCA-153) CSD04 - Need ways to namespace Service Template (schema namespace)
[ https://issues.oasis-open.org/browse/TOSCA-153?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Matthew Rutkowski updated TOSCA-153:
-------------------------------------
Summary: CSD04 - Need ways to namespace Service Template (schema namespace) (was: Need ways to namespace Service Template (schema namespace) )
Fix Version/s: CSD04
(was: CSD2)
(was: CSD03)
> CSD04 - Need ways to namespace Service Template (schema namespace)
> -------------------------------------------------------------------
>
> Key: TOSCA-153
> URL: https://issues.oasis-open.org/browse/TOSCA-153
> Project: OASIS Topology and Orchestration Specification for Cloud Applications (TOSCA) TC
> Issue Type: New Feature
> Components: Profile-YAML
> Affects Versions: CSD2
> Reporter: Matthew Rutkowski
> Assignee: Matthew Rutkowski
> Fix For: CSD04
>
>
> TODO: Need a way to declare the "schema" namespace apart from the version of the TOSCA (grammar) that the service template is declared to be composed with.
> e.g. tosca_simple_1_0
> ----
> As TOSCA normative type are essential to simplified grammar, could this keyname be used to automatically import the normative types that aligned with/matched the same schema version?
> ----
> Can we use this key (implied) to also bring in the matchin TOSCA normative definitions (that was defined with the same schema version)?
> <or> <and> could override with explicit import in service template import section.
--
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]