Assigned: http://www.osoa.org/jira/browse/BP-50
From: Dieter Koenig1
[mailto:dieterkoenig@de.ibm.com]
Sent: Tuesday, December 02, 2008 12:17
To: bpel4people@lists.oasis-open.org
Subject: [bpel4people] New Issue: Refactor User, Group, and
OrganizationalEntity
Target: WS-HumanTask 1.1, BPEL4People 1.1, ws-humantask-types.xsd,
ws-humantask-context.xsd, ws-humantask-api.wsdl, and all examples
Description: Multiple WS-HT XML Schema artifacts
("ws-humantask-types.xsd", "ws-humantask-context.xsd",
"ws-humantask-api.wsdl") import the WS-HT language XML Schema
("ws-humantask.xsd") only to reference the data types
User/Group/OrganizationalEntity. However, none of them requires any other
element from the WS-HT language XML Schema (note that this would not even be
meaningful).
Proposal: Refactor the User/Group/OrganizationalEntity definitions in order to
reduce the complexity of import relationships (see diagram - note that the
diagram may have been transmitted as attachment).
>>> Note: This proposal implies a namespace
change for the User/Group/OrganizationalEntity data types which are used in
many places.
Summary of changes:
A. Move the User/Group/OrganizationalEntity-related definitions (listed below)
into the WS-HT data types XML Schema ("ws-humantask-types.xsd").
B. Remove the import of the WS-HT language XML Schema (in
"ws-humantask-types.xsd", "ws-humantask-context.xsd",
"ws-humantask-api.wsdl").
C. Change the namespace prefix for User/Group/OrganizationalEntity from
"htd:" to "htt:" in the BPEL4People and WS-HumanTask specs
as well as in all referencing XML artifacts (including examples).
XML Schema element and type definitions that will be moved into
ws-humantask-types.xsd:
<!-- data types for people assignment -->
<xsd:element name="user" type="tUser" />
<xsd:simpleType name="tUser">
<xsd:restriction base="xsd:string"
/>
</xsd:simpleType>
<xsd:element name="group" type="tGroup"
/>
<xsd:simpleType name="tGroup">
<xsd:restriction base="xsd:string"
/>
</xsd:simpleType>
<xsd:element name="organizationalEntity"
type="tOrganizationalEntity"
/>
<xsd:complexType name="tOrganizationalEntity">
<xsd:choice>
<xsd:element ref="users" />
<xsd:element ref="groups" />
</xsd:choice>
</xsd:complexType>
<!-- elements and types for organizational entities
-->
<xsd:element name="users" type="tUserlist"
/>
<xsd:complexType name="tUserlist">
<xsd:sequence>
<xsd:element ref="user" minOccurs="0"
maxOccurs="unbounded"
/>
</xsd:sequence>
</xsd:complexType>
<xsd:element name="groups"
type="tGrouplist"
/>
<xsd:complexType name="tGrouplist">
<xsd:sequence>
<xsd:element ref="group" minOccurs="0"
maxOccurs="unbounded"
/>
</xsd:sequence>
</xsd:complexType>
Kind Regards
Dieter König
Senior
Technical Staff Member, WebSphere Process Server Architect
IBM
Software Group, Application and Integration Middleware Software
WSS
Business Process Solutions
|
|
Phone:
|
+49-7031-16-3426
|
IBM Deutschland
|
|
E-Mail:
|
dieterkoenig@de.ibm.com
|
Schönaicher Str. 220
|
|
|
71032 Böblingen
|
|
|
Germany
|
|
|
IBM Deutschland Research & Development GmbH / Vorsitzender
des Aufsichtsrats: Martin Jetter
Geschäftsführung: Erich Baier
Sitz der Gesellschaft: Böblingen / Registergericht: Amtsgericht Stuttgart,
HRB 243294
|