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

 


Help: OASIS Mailing Lists Help | MarkMail Help

sca-c-cpp message

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


Subject: NEW ISSUE: C++ componentType schema missing definitions in normativesection



Target:  C++ C&I Specification CD03

Description:  
1) Section 2.4.1 of the C++ C&I specification contains the normative definition of <interface.cpp/> but it does not describe the @requires and @policySets attributes that apply to this element as defined in the core SCA schema.
2) An @policySets attributes needs to be added to the definition of <function/> and <callbackFunction/> in Section 2.4.2 of the C++ C&I specification (as well as the interface.cpp schema).
3) Section 2.4.3 of the C++ C&I specification contains the normative definition of <implementation.cpp/> but it does not describe the @requires and @policySets attributes that apply to this element as defined in the core SCA schema.

4) An @policySets attributes needs to be added to the definition of <function/> in Section 2.4.4 of the C++ C&I specification (as well as the implementation.cpp schema).

Proposal:  
1) In section 2.4.1, add @requires and @policySets to the pseudo-schema for <interface.cpp/> and descriptions using language consistent with samples found in the assembly specification.  In particular, it should be noted that intents on an interface adds to or qualifies the intents of an individual member function of that interface.
2)  In section 2.4.2 add @policySets to the pseudo-schema shared by <function/> and <callbackFunction/>and a description using language consistent with samples found in the assembly specification. Also add this attribute to the CPPFunction in the interface.cpp schema.
3)  In section 2.4.3, add @requires and @policySets to the pseudo-schema for <implementation.cpp/> and descriptions using language consistent with samples found in the assembly specification.  In particular, it should be noted that intents on an implementation adds to or qualifies the intents of an individual member function of that implementation.
4) In section 2.4.4 add @policySets to the pseudo-schema for <function/> and a description using language consistent with samples found in the assembly specification. Also add this attribute to the CPPImplementationFunction in the implementation.cpp schema.


Bryan Aupperle, Ph.D.
STSM, WebSphere Enterprise Platform Software Solution Architect

Research Triangle Park,  NC
+1 919-254-7508 (T/L 444-7508)
Internet Address: aupperle@us.ibm.com


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