Minutes of OASIS SDO TC Conference Call Call date: October 19, 2010 Call time: 12:00 PM to 01:00 PM Eastern Standard Time Minutes taken in the web conference tool and then copied here with slight edits and brief summary: References: - SDO 3.0 Charter: http://www.oasis-open.org/committees/sdo/charter.php - JIRA ISSUES AT http://www.osoa.org/jira/browse/SDO - Chat room: http://webconf.soaphub.org/conf/room/sdo-TC - WebConference: http://my.adobe.acrobat.com/sdotc Agenda: I - Intro a. Roll Call b. Assignment/Confirmation of Scribe c. Approval of last weeks minutes: http://www.oasis-open.org/apps/org/workgroup/sdo/download.php/39901/SDO%20TC%20Meeting%20minutes%20-%20October%2012%2C%202010.txt d. Agenda Bashing II - REVIEW ACTION ITEMS http://www.oasis-open.org/apps/org/workgroup/sdo/members/action_items.php No new AIs III - NEW ISSUES ISSUE-181: Nested normative statements in 7.4.2 JIRA: http://www.osoa.org/jira/browse/SDO-181 ISSUE-182: Missing normative statement in Section 8 JIRA: http://www.osoa.org/jira/browse/SDO-182 ISSUE-183: COR07110006 and COR07110007 need to be refactored. JIRA: http://www.osoa.org/jira/browse/SDO-183 IV - Continue Review of Core Spec Chapter 4 Baseline here: http://www.oasis-open.org/apps/org/workgroup/sdo/email/archives/201010/msg00010.html http://www.oasis-open.org/apps/org/workgroup/sdo/email/archives/201010/msg00012.html http://www.oasis-open.org/apps/org/workgroup/sdo/email/archives/201010/msg00011.html V - Review Brian's Comments to Core Spec Chapters 5-8 Baseline here: http://www.oasis-open.org/apps/org/workgroup/sdo/email/archives/201010/msg00006.html ============================================================================== I. Intro a. Roll Call Meeting Attendees: Bryan Aupperle IBM Group Member Fuhwei Lwo IBM Group Member Shawn Moe IBM Group Member Blaise Doughan Oracle Corporation Group Member Ron Barack SAP AG* Group Member b. Assignment/ Confirmation of Scribe Fuhwei Lwo c. Approval of last weeks minutes Ron: No objections; last meeting minutes approved II - REVIEW ACTION ITEMS http://www.oasis-open.org/apps/org/workgroup/sdo/members/action_items.php Bryan: Change Frank from co-chair to voting member III - NEW ISSUES ISSUE-181: Nested normative statements in 7.4.2 JIRA: http://www.osoa.org/jira/browse/SDO-181 Bryan: There are nested normative statements Bryan: Motion to open SDO-181 Fuhwei: Second it Ron: No objeciton; SDO-181 is opened ISSUE-182: Missing normative statement in Section 8 JIRA: http://www.osoa.org/jira/browse/SDO-182 Bryan: Move to resolve SDO-182 according to the proposal in the link above Fuhwei: Second it Ron: No objection; SDO-182 resolved ISSUE-183: COR07110006 and COR07110007 need to be refactored. JIRA: http://www.osoa.org/jira/browse/SDO-183 Bryan: Move to open SDO-183 Fuhwei: Second it Ron: No objection; SDO-183 opened Bryan: Move to resolve SDO-183 according to the proposal in the link above Fuhwei: Second it Ron: No objection; SDO-183 resolved IV - Continue Review of Core Spec Chapter 4 Baseline here: http://www.oasis-open.org/apps/org/workgroup/sdo/email/archives/201010/msg00010.html http://www.oasis-open.org/apps/org/workgroup/sdo/email/archives/201010/msg00012.html http://www.oasis-open.org/apps/org/workgroup/sdo/email/archives/201010/msg00011.html Ron: http://www.osoa.org/jira/browse/SDO-184 Ron: Calling getList(property) on a many-valued property retrieves the contents of the property as the appropriate language specific list construct. . In addition, the single valued get() methods can also be invoked on a many-valued property, When a get method is called on a property whose value is a List of length 1, then the item in the list MUST be returned (possibly after conversion); if the list is emtpy, null MUST returned. Conversely, when a set method is invoked on a many-value property, then the value is wrapped into a List of length 1 and then this List is set. If property.many is true then set(property, value) and setList(property, value) requre that "value" be a list as defined for the implementation languageFor many-valued Properties, get() and getList() return a List containing the actual values, the list is not a static copy of the current values. An SDO implementation MUST make all modifications to a returned List visible in the DataObject, so that all operations reflect the updated list contents. [COR04010402] An SDO implementation MUST make updates to the DataObject visible though a returned List object. [COR04010403] Bryan: Move to open SDO-184 Fuhwei: Second it Ron: No objection; SDO-184 opened Ron: Will remove 4.1.10 sample code and 4.1.11 Bryan Aupperle: In 4.2.1 add after the first sentence: If change logging is already active a call to ChangeSummary.beginLogging() has no effect. Ron: Will open an issue to remove reference about throwing an exception when trying to set a value on the read-only property