New Issue: Need normative rules for property composition

["Murray, Bryan P." <bryan.murray@hp.com>]

The current WS-ResourceProperties spec does not give any rules for
composing 2 resource property documents into the single document to be
exposed from a portType beyond the recommendation to cut-and-paste
properties from both documents.

We need normative rules to address a situtation such as the following:

PortType Foo exposes a property "Name" that is required.

PortType Bar also wants to expose that same "Name" property AND be
composable with the Foo portType. However, if the Bar portType is not
composed with the Foo portType the "Name" property is to be optional.


The problem is what the rules are for composing these 2 portTypes. Both
contain a "Name" property (the Qname is foo:Name). They use the same
Qname because they want the property to be the same single property if
both portTypes are composed. However, one of the portTypes wants the
property to be optional and the other wants it to be required. What
should the composed portType do? There is a similar problem with
cardinality and perhaps other aspects of properties.

Bryan