SUBMITTED BY: Mark Ford
TARGET: HT, Section 6.1.4

DESCRIPTION: The setGenericHumanRole operation in ws-humantask-api.wsdl
accepts an htd:setGenericHumanRole element. This element is defined in
ws-humantask-api-wsdl.xsd as follows:

  <xsd:element name="setGenericHumanRole">
    <xsd:complexType>
      <xsd:sequence>
        <xsd:element name="identifier" type="xsd:anyURI" />
        <xsd:element name="genericHumanRole" type="xsd:string" />
        <xsd:element name="organizationalEntity"
          type="htd:tOrganizationalEntity" />
      </xsd:sequence>
    </xsd:complexType>
  </xsd:element>

The spec doesn't define the possible values for genericHumanRole. The
genericHumanRole should either be a schema type that contains an enumerated
list of values or the spec should list what the well known role names are.
Without a formal definition in place it's going to be an interop issue.

This needs to be an open list to allow a user to extend the list of possible values

PROPOSAL:

At the 29 Oct 2008, we accepted the proposal submitted by Dieter at http://www.oasis-open.org/apps/org/workgroup/bpel4people/email/archives/200809/msg00039.html.