Proposal for Resolution of LC99.: Message Reference Component is Underspecified

LC99 [1] : The Message Reference Component description doesn't define the 
semantics of the message when the optional {message content model} 
property is absent.

I propose to make the property REQUIRED and to set it to #any if the 
element attribute is missing. I think this makes sense since the element 
attribute constrains the message, so if the element attribute is missing, 
then there is no constraint. The other reasonable alternative is to set 
the property to #none when the element attribute is missing, but I think 
this is less intuitive.

The spec should be changed as follows:

1. Change 2.5.1 The Message Reference Component

Current text: {message content model} OPTIONAL 

Proposed text: {message content model} REQUIRED

2. Change Table 2-6. Mapping between Message Reference Component 
Properties and XML Representation , {message content model} Row

Current text: If the element attribute information item is present and its 
value is a QName, then #element. Otherwise the actual value of the element 
attribute information item, if any, otherwise empty. 

Proposed text: If the element attribute information item is present and 
its value is a QName, then #element. Otherwise the actual value of the 
element attribute information item, if any, otherwise #any. 


[1] http://www.w3.org/2002/ws/desc/4/lc-issues/issues.html#LC99

Arthur Ryman,
Rational Desktop Tools Development

phone: +1-905-413-3077, TL 969-3077
assistant: +1-905-413-2411, TL 969-2411
fax: +1-905-413-4920, TL 969-4920
mobile: +1-416-939-5063, text: 4169395063@fido.ca
intranet: http://labweb.torolab.ibm.com/DRY6/