OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

tosca-comment message

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

Subject: RE: [tosca-comment] Consistency of name and id attributes

Dear Oliver,

Thank you for your comments. I acknowledge receipt of the below as TOSCA TC Co-Chair. Please be assured that the TC will carefully consider your comments.

Paul Lipton

-----Original Message-----
From: tosca-comment@lists.oasis-open.org [mailto:tosca-comment@lists.oasis-open.org] On Behalf Of Oliver Kopp
Sent: Thursday, January 10, 2013 6:03 AM
To: tosca-comment@lists.oasis-open.org
Subject: [tosca-comment] Consistency of name and id attributes

Dear TOSCA team,

This mail is about names (type: xs:NCame or xs:string, dependend on context) and IDs (type: xs:ID) of things.

In the specification, EntityTypes and EntityTypeImplementations carry a name
(xs:NCame) and no ID. A ServiceTemplate carries an ID. A ServiceTemplate may also optionally carry a name (xs:string). Why is this method (mandatory id and an optional name) not used at EntityTypes and EntityTypeImplementations, too? My argument would be consistency reasons. As a side node, IMHO a name attribute should always be of the same type to avoid confusion. IMHO, a thing should always be referenced the same way throughout a document.

In the context of EntitytTemplates an id is always required, but a name (xs:
string) is optional at NodeTemplates, RelationshipTemplates, ArtifactTemplates, Policies, but required at Requirements, Capabilities. The specification on line 821 lists the name of a Requirement as optional, but required on line 591,642. Similar issue for Capabilities: optional on line 821, but required on lines 595,656. IMHO, the name should always be optional.
Possibly, a supplementary document should explain the taken design decisions.



This publicly archived list offers a means to provide input to the OASIS Topology and Orchestration Specification for Cloud Applications (TOSCA) TC.

In order to verify user consent to the Feedback License terms and to minimize spam in the list archive, subscription is required before posting.

Subscribe: tosca-comment-subscribe@lists.oasis-open.org
Unsubscribe: tosca-comment-unsubscribe@lists.oasis-open.org
List help: tosca-comment-help@lists.oasis-open.org
List archive: http://lists.oasis-open.org/archives/tosca-comment/
Feedback License: http://www.oasis-open.org/who/ipr/feedback_license.pdf
List Guidelines: http://www.oasis-open.org/maillists/guidelines.php
Committee: http://www.oasis-open.org/committees/tosca
Join OASIS: http://www.oasis-open.org/join/

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