NEW ISSUE: Title: Remove fault name from getFault HT API call

["Luc Clement" <luc.clement@activevos.com>]

Forwarding on Mark Ford's behalf (Active Endpoints changed domain name
recently)

-----Original Message-----
From: Mark Ford [mailto:mark.ford@activevos.com] 
Sent: Tuesday, April 01, 2008 7:27 PM
To: 'bpel4people@lists.oasis-open.org'
Subject: [bpel4people] NEW ISSUE: Title: Remove fault name from getFault HT
API call

TARGET: WS-HT API

DESCRIPTION: The element "getFault" used in the getFault operation defined
in the HT API has a required faultName child element. A task only supports
having a single fault set on it so it doesn't make sense to accept a fault
name here. This is likely left over from a previous version of this schema
where faultName was removed from the call but left behind in the Schema. The
description for getFault in the table of operations in Section 6 does not
have the fault name as an input parameter.

PROPOSAL: Remove the faultName child element from the getFault element in
ws-humantask-api.xsd as follows:

Existing definition - 

  <xsd:element name="getFault">
    <xsd:complexType>
      <xsd:sequence>
        <xsd:element name="identifier" type="xsd:anyURI" />
        <xsd:element name="faultName" type="xsd:NCName" />
      </xsd:sequence>
    </xsd:complexType>
  </xsd:element>

New definition - 

  <xsd:element name="getFault">
    <xsd:complexType>
      <xsd:sequence>
        <xsd:element name="identifier" type="xsd:anyURI" />
      </xsd:sequence>
    </xsd:complexType>
  </xsd:element>