RE: [tosca-comment] Bugs in TOSCA csprd01

["Lipton, Paul C" <Paul.Lipton@ca.com>]

Hi Rene,

Thank you for your detailed comments. I acknowledge receipt of the below as TOSCA TC Co-Chair. Please be assured that the TC will carefully consider your comments. Given the holidays and the duration of the 30 day review period, there may be some delay, but we will be sure to respond to each of the items below. 

Have a happy holiday season and New Year. 

Thanks again,
Paul 


-----Original Message-----
From: tosca-comment@lists.oasis-open.org [mailto:tosca-comment@lists.oasis-open.org] On Behalf Of Rene T.
Sent: Thursday, December 20, 2012 6:37 AM
To: OASIS TOSCA mailing list
Subject: [tosca-comment] Bugs in TOSCA csprd01

Hello,

we have found the following bugs in TOSCA csprd01:

1. In spec p. 23, l. 579, listing l. 16 the attribute "targetPropertyRef" has the type "xs:IDREF". But in the XSD, l. 162, the attribute is defined as "xs:string".
"targetPropertyRef" contains a XPath expression, so "xs:string" should be correct.

2. According to spec p. 27, l. 785 the name of the attribute is "targetObjectPropertyRef". In XSD, l. 162 the same attribute has the name "targetPropertyRef".

3.  In spec p. 85, l. 3181 - 3183, listing l. 24 - 26 and the XSD "Tags" 
is defined as a child element of "ServiceTemplate". But on p. 109, l. 
4539 - 4541, listing l. 3 - 5 the element "Tags" is a child element of "Definitions".

4. According to spec p. 88, l. 3331, listing l. 174 the element "PreCondition" contains the condition as plain text. But in XSD, l. 743
- 748 (complexType "tCondition") no plain text is allowed.

5. In spec p. 88. l. 3330, listing l. 173 the element has the name "PreCondition". But in XSD, l. 577 the same element has the name "Precondition".

6. Spec, p. 89, l. 3424, listing l. 267 says that the element "ImplementationArtifact" has a attribute "name". But in XSD, l. 557 -
566 (complexType "tImplementationArtifact") no attribute "name" is specified.

7. In spec, p. 85, l. 3191, listing l. 34 the character "+" indicates that in a "PropertyMappings" element must be one or more "PropertyMapping" elements. But in XSD, l. 115 exactly one "PropertyMapping" element is allowed in "PropertyMappings", because no "maxOccurs=unlimited" is specified.

Is it possible to fix these issues?

Best regards,
Rene

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