[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [OASIS Issue Tracker] Updated: (TOSCA-153) WD02 - Define grammar and usage of Service Template keyname (schema namespace) "tosca_default_namespace"
[ http://tools.oasis-open.org/issues/browse/TOSCA-153?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthew Rutkowski updated TOSCA-153: ------------------------------------- Fix Version/s: CSD2 (was: CSD1) Affects Version/s: CSD2 (was: CSD1) > WD02 - Define grammar and usage of Service Template keyname (schema namespace) "tosca_default_namespace" > -------------------------------------------------------------------------------------------------------- > > Key: TOSCA-153 > URL: http://tools.oasis-open.org/issues/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: CSD2 > > > 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 is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://tools.oasis-open.org/issues/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]