|
Do members of the FFM TC approve FFM Integration Interface Specification V1.0 [1] with non-material changes [2] and designated cross reference changes [3] as a Committee Specification?
This ballot requires a Special Majority Vote [4]. The TC roster currently lists 6 voting members. In order to pass, at least 4 members have to vote Yes and no more than 2 members may vote No.
[1] URI for the specification
http://www.oasis-open.org/committees/download.php/46955/latest/FFMII-Specification-20120920-v1 0-wd06.zip
[2] The Working Draft for this Committee Specification contains changes made since its last public review. The changes made are documented in http://www.oasis-open.org/committees/download.php/46998/latest/ffmii-v1.0-wd06-change-list.txt . The TC judges these changes to be Non-Material Changes in accordance with the definition in the OASIS TC Process (http://www.oasis-open.org/policies-guidelines/tc-process#dNonmaterialChange).
[3] This Specification Approval Motion includes the following Designated Cross-Reference Changes requested in accordance with the requirements of Section 2.19 of the TC Process (http://www.oasis-open.org/policies-guidelines/tc-process#crossRefs):
Current reference to be updated:
[FFMII-REQ] Field Force Management Integration Interface Requirements, Version 1.0. 28 February 2012. OASIS Committee Note Draft 02 Public Review Draft 02. https://www.oasis-open.org/committees/download.php/45408/ffm-if-requirements-v1.0-cnprd02.zip
Expected approval status:
Committee Note, October 2012
The TC acknowledges that approval and publication of the specification may be delayed by the Designated Cross-Reference Changes.
[4] http://www.oasis-open.org/committees/process-2010-07-28.php#dSpecialMajority
|
