RE: ISSUE: cardinality of LPG parameter argument elements isincorrect

Apologies: Robin pointed me to http://docs.oasis-open.org/bpel4people/ws-humantask.xsd, and I realized that I had been looking at an older version of the schema. The (final) version of the schema does *actually* specify a maxOccurs for the tArgument definition of tFrom.

<xsd:element name="argument" type="tArgument" minOccurs="0" maxOccurs="unbounded"/>

As you might expect I’m retracting this issue.

Luc Clément

Active Endpoints

From: Luc Clément [mailto:luc.clement@activevos.com]
Sent: Sunday, March 13, 2011 10:12
To: bpel4people@lists.oasis-open.org
Cc: Dave Ings (ings@ca.ibm.com)
Subject: [bpel4people] ISSUE: cardinality of LPG parameter argument elements is incorrect

Dave / TC Members,

Find below a description of an issue we’ve uncovered with the cardinality of LPG argument parameters. The cardinality specified for the tFrom element is incorrect (defined in ws-humantask.xsd)

For consideration and discussion. Specifically, how do we track these types of issues and raise errata?

Luc Clément

Active Endpoints

Use case: A user would like to perform an LPG query taking as a filter two or more parameters (e.g. where ( (?orgUnits="${orgUnit}") && (?memberOf="${roleGroup}")) )

Issue Description:

tGenericHumanRole (ws-humantask.xsd) is defined as follows.

<xsd:complexType name="tGenericHumanRole">

<xsd:complexContent>

<xsd:extension base="tExtensibleElements">

<xsd:sequence>

<xsd:element name="from" type="tFrom"/>

</xsd:sequence>

</xsd:extension>

</xsd:complexContent>

</xsd:complexType>

Note though that tFrom currently does not allow for more than one argument given that the default value for both the minOccurs and the maxOccurs attributes is 1. Thus only a single argument can be specified not allowing for the use case to be satisfied.

<xsd:complexType name="tFrom" mixed="true">

<xsd:complexContent>

<xsd:extension base="tExtensibleMixedContentElements">

<xsd:sequence>

<xsd:choice>

<xsd:element name="argument" type="tArgument" minOccurs="0"/>

<xsd:element name="literal" type="tLiteral" minOccurs="0"/>

</xsd:choice>

</xsd:sequence>

<xsd:attribute name="expressionLanguage" type="xsd:anyURI"/>

<xsd:attribute name="logicalPeopleGroup" type="xsd:QName"/>

</xsd:extension>

</xsd:complexContent>

</xsd:complexType>

Proposal:

Update the argument element by adding a maxOccurs="unbounded" attribute.

<xsd:complexType name="tFrom" mixed="true">

<xsd:complexContent>

<xsd:extension base="tExtensibleMixedContentElements">

<xsd:sequence>

<xsd:choice>

<xsd:element name="argument" type="tArgument" minOccurs="0" maxOccurs="unbounded"/>

<xsd:element name="literal" type="tLiteral" minOccurs="0"/>

</xsd:choice>

</xsd:sequence>

<xsd:attribute name="expressionLanguage" type="xsd:anyURI"/>

<xsd:attribute name="logicalPeopleGroup" type="xsd:QName"/>

</xsd:extension>

</xsd:complexContent>

</xsd:complexType>

bpel4people message