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


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