[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [OASIS Issue Tracker] (TOSCA-150) CLOSE - WD02 - Work towards a common syntax for Requirement definitions (currently 3 variant grammars/forms)
[ https://issues.oasis-open.org/browse/TOSCA-150?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthew Rutkowski updated TOSCA-150: ------------------------------------- Summary: CLOSE - WD02 - Work towards a common syntax for Requirement definitions (currently 3 variant grammars/forms) (was: WD02 - Work towards a common syntax for Requirement definitions (currently 3 variant grammars/forms)) > CLOSE - WD02 - Work towards a common syntax for Requirement definitions (currently 3 variant grammars/forms) > ------------------------------------------------------------------------------------------------------------ > > Key: TOSCA-150 > URL: https://issues.oasis-open.org/browse/TOSCA-150 > Project: OASIS Topology and Orchestration Specification for Cloud Applications (TOSCA) TC > Issue Type: Improvement > Components: Profile-YAML > Affects Versions: CSD2 > Reporter: Matthew Rutkowski > Assignee: Matthew Rutkowski > Fix For: CSD2 > > > Here is what we have now: > # Requirement for a specific named entity (e.g., a Node Type or Node Template) > - <requirement_name>: <entity_name> > # Requirement clause for a specific named Capability Type > - <requirement_name>: <capability_type_name> > # Requirement for a node type with an optional, explicit Relationship type > - <requirement_name>: <node_type_name> > relationship_type: <relationship_name> > Thomas, Derek and Matt believe we can collapse into single grammar. > Also, we need to expand the definitions to show constraints. -- 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]