message reference component & syntax

In the current draft we have operation/(input|output)/@messageReference
being optional. That doesn't make any sense as we have no rules 
defined for how to compute its value if its not there. Life ain't
going to work without knowing what role a message plays in a 
message pattern.

This is part of a larger set of problems with the syntax we 
currently have. I will be sending a separate note out about that
but wanted to highlight this particular inconsistency first.


Received on Thursday, 18 September 2003 06:49:55 UTC