Action Items #0139 #0140 Resolution

Acton Item # 0139

Verify the new XSDs at http://lists.oasis-open.org/archives/sca-bpel/201012/msg00000.html ( http://www.oasis-open.org/apps/org/workgroup/sca-bpel/members/action_item.php?action_item_id=3199 )

Resolution:

Updated the import statement that refers to sca-core-1.1-cd06.xsd schema in sca-bpel-extensions-1.1-cd02.xsd.

Changed

Acton Item # 0140

Look into whether the resolved issues are applied, if not apply them. Resolved issues are at http://osoa.org/jira/secure/IssueNavigator.jspa?reset=true&pid=10025&status=5 ( http://www.oasis-open.org/apps/org/workgroup/sca-bpel/members/action_item.php?action_item_id=3200 )

Resolution:

I looked into the resolved issues to check whether all of them have been applied to the cd02-rev9 version of the specification. I found that most of the issues have been applied, for the remaining ones I have applied the resolutions and created a new version of the spec (cd02-rev10). To summarize based on each resolved issue, we have:

BPEL-58 – Resolution already applied in previous version and modified subsequently.

BPEL-62 – Resolution already applied in CD02 version 9.

BPEL-63 – Resolution already applied in CD02 version 9.

BPEL-64 - Resolution already applied in CD02 version 9 with the exception of new normative statement:

[SBPELXXXX] A partnerLink MUST NOT have both the sca-bpel:service and sca-bpel:reference attributes present on it. It is now [SBPEL3020] (re-used number after applying

resolution for BPEL-66)

BPEL-65 - Changed normative statements [SBPEL2005,SBPEL2007 and SBPEL2025] to make “1” as the relevant value for sca-bpel:ignore attribute.

BPEL-66 - Applied changes by removing normative statement [SBPEL3020]

I am attaching changes as sca-bpel-1.1-spec-cd02-rev10.zip

Najeeb

sca-bpel message