 SCA C and C++ Telecon (Conference Call) |
|
| Name | SCA C and C++ Telecon (Conference Call) |
| Time | Thursday, 10 January 2008, 11:00am to 12:00pm EST
(Thursday, 10 January 2008, 04:00pm to 05:00pm UTC) |
| Description | Chat Room http://webconf.soaphub.org/conf/room/sca-c-cpp-TC Web Conference http://oasis.acrobat.com/ccpptc/ |
| Minutes | 0. Role Bryan Aupperle Andrew Borley Pete Robbins 1. Agenda bashing Add introduction of Adobe Connect after item 2. 2. Accept minutes from SCA-C-C++ TC meeting of 3 January Note: accepting these minutes includes approving resolution of http://www.osoa.org/jira/browse/CCPP-31 Should C++ specification define annotations? Minutes approved 3. Action Items a. AI-2 (Pete): C++ header files No update 4. New Issues None 5. Issue Discussion a. http://www.osoa.org/jira/browse/CCPP-26 C++ componentType files Proposed resolution: http://lists.oasis-open.org/archives/sca-c-cpp/200801/msg00004.html Proposal accepted with addition that absolute paths are allowed for the library path. b. http://www.osoa.org/jira/browse/CCPP-24 Conformance Targets Liaison subcommittee direction is for two classes of targets: SCA artifacts (i.e. SCDL files) and SCA runtime and its subsets(such as a binding). TC’s may add others (such as an annotation processor or component implementations). Up to TC’s to define specific error handling. Assembly TC will define some common errors but not necessarily format for returning errors. Proposal: Close with no specific action. We are addressing this via our Conformance Statement review. Proposal accepted. c. Status of other open issues 6. Conformance Statements: - Are the current conformance statements appropriate? - Are the current conformance statements worded properly? - Are additional conformance statements needed? Start with Section 6.2.4 of the current C++ WD (http://www.oasis-open.org/committees/download.php/25974/sca-cppcni-1.1-spec-wd-02.doc) Questions about callback objects and remote service providers. We need some additional discussion on this after consulting with the other TCs. 7. AOB Schema section should be move to an appendix Header files will also be added as an appendix. |
| Agenda | 0. Role 1. Agenda bashing 2. Accept minutes from SCA-C-C++ TC meeting of 3 January Note: accepting these minutes includes approving resolution of http://www.osoa.org/jira/browse/CCPP-31 Should C++ specification define annotations? 3. Action Items a. AI-2 (Pete): C++ header files 4. New Issues None 5. Issue Discussion a. http://www.osoa.org/jira/browse/CCPP-26 C++ componentType files Proposed resolution: http://lists.oasis-open.org/archives/sca-c-cpp/200801/msg00004.html b. http://www.osoa.org/jira/browse/CCPP-24 Conformance Targets Liaison subcommittee direction is for two classes of targets: SCA artifacts (i.e. SCDL files) and SCA runtime and its subsets(such as a binding). TC’s may add others (such as an annotation processor or component implementations). Up to TC’s to define specific error handling. Assembly TC will define some common errors but not necessarily format for returning errors. Proposal: Close with no specific action. We are addressing this via our Conformance Statement review. c. Status of other open issues 6. Conformance Statements: - Are the current conformance statements appropriate? - Are the current conformance statements worded properly? - Are additional conformance statements needed? Start with Section 6.2.4 of the current C++ WD (http://www.oasis-open.org/committees/download.php/25974/sca-cppcni-1.1-spec-wd-02.doc) On the 3 January call we recognized we needed to review callback objects and services references before finishing the review of section 6.2.4 7. AOB |
| Submitter | Dr. Bryan Aupperle |
| Group | OASIS Service Component Architecture / C and C++ (SCA-C-C++) TC |
| Access | This event is visible to OASIS Service Component Architecture / C and C++ (SCA-C-C++) TC and shared with
|