OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

bpel4people message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: BP-125: OrganizationalEntity Cannot Contain Users AND Groups


Assigned: http://www.osoa.org/jira/browse/BP-125


________________________________________
From: Dieter Koenig1 [dieterkoenig@de.ibm.com]
Sent: Monday, August 10, 2009 04:21
To: bpel4people@lists.oasis-open.org
Subject: [bpel4people] New Issue: OrganizationalEntity Cannot Contain Users AND Groups

Target:

WS-HumanTask 1.1 CD 05 revision 03, Section 3.4.4 Data Type for
Organizational Entities and "ws-humantask-types.xsd". Also affected are
BPEL4People 1.1 CD 05 and example XML artifacts.


Description:

Section 3.4.4 defines the tOrganizationalEntity data type. It is used in
literal people assignments and API operations like forward or nominate.

Queries used to resolve logical people groups may return users or groups.
Moreover, they may also return mixed sets of users and groups. Likewise,
other occurrences of tOrganizationalEntity may also require support for
such mixed sets.

The choice allows an element of this type to contain EITHER a list of zero
or more users OR a list of zero or more groups, but not users AND groups.

<xsd:element name="organizationalEntity" type="tOrganizationalEntity"/>
<>xsd:complexType name="tOrganizationalEntity">
  <xsd:choice
    <xsd:element ref:="users"/>
    <xsd:element ref:="groups"/>
  </xsd:choice>
</xsd:complexType>

<xsd:element name="user" type="tUser"/>
<>xsd:simpleType name="tUser">
  <xsd:restriction base="xsd:string"/>
</xsd:simpleType>

<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="group" type="tGroup"/>
<>xsd:simpleType name="tGroup">
  <xsd:restriction base="xsd:string"/>
</xsd:simpleType>

<xsd:element name="groups" type="tGrouplist"/>
<>xsd:complexType name="tGrouplist">
  <xsd:sequence>
    <xsd:element ref:="group" minOccurs="0" maxOccurs="unbounded"/>
  </xsd:sequence>
</xsd:complexType>


Proposal:

Also allow the presence of users AND groups in an element of type
tOrganizationalEntity.

(A) Change the first paragraph in 3.4.4 from:
"The following XML schema definition describes the format of the data that
is returned at runtime when evaluating a logical people group. The result
can contain either a list of users or a list of groups. The latter is used
to defer the resolution of one or more groups of people to a later point,
such as when the user accesses a task list."

to:
"The following XML schema definition describes the format of the data that
is returned at runtime when evaluating a logical people group. The result
can contain a list of users or groups. A group is used to defer the
resolution of a group of people to a later point, such as when the user
accesses a task list."

(B) Change the XML Schema type definitions as follows (also in
"ws-humantask-types.xsd"):

<xsd:element name="organizationalEntity" type="tOrganizationalEntity"/>
<>xsd:complexType name="tOrganizationalEntity">
  <xsd:choice minOccurs="0" maxOccurs="unbounded">
    <xsd:element name="user" type="tUser"/>
    <xsd:element name="group" type="tGroup"/>
  </xsd:choice>
</xsd:complexType>

<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>

(C) Make all operation signatures referencing the existing list types
tUsers and tGroups consistent with the above definition.

(D) Make all examples using elements of type tOrganizationalEntity, tUsers
and tGroups in WS-HT, B4P and example XML artifacts consistent with the
above definition.


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                      (Embedded
                                                                                  image moved
                                                                                     to file:
                                                                                pic05855.gif)

  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



[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]