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: [bpel4people] NEW ISSUE: Title: Value of genericHumanRole in setGenericHumanRole operation call should be defined


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.

PROPOSAL: 



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