RE: MESSAGING STRAWMAN [3 of 5] VOTE

[Peter Furniss <peter.furniss@choreology.com>]

VOTE

- target address
	address
- atom identifier
	identifier
- participant address
	address
- participant identifier
	identifier
- vote
	'cancel' or 'ready'
- qualifiers
	list of qualifiers

<btp:vote value="ready|cancel">
  <btp:target-address>
    ...address...
  </btp:target-address>
  <btp:atom-identifier>...URI...</btp:atom-identifier>
  <btp:participant-address>
    ...address...
  </btp:participant-address>
  <btp:participant-identifier>...URI...</btp:participant-identifier>
  <btp:qualifiers>
    <foo:some-qualifier ...>...</foo:some-qualifier>
    <bar:another-qualifier ...>...</bar:another-qualifier>
  </btp:qualifiers>
</btp:vote>

Issue[MSG_004]: name of type attribute?
	value  (abstract msg realigned with this)

Issue[MSG_005]: do addresses need to say the carrier protocol to use? eg how
does it know to use SOAP?
	- see address subdocument

Issue[MSG_006]: should identifiers be URIs?
	- no : The same value must be matched by the receiver when received twice
from the
	 the originator, but is otherwise opaque
	- choices - base64, or hexstring
	--> hexstring.  comparison is case-insensitive.


Issue [MSG_XX]: Does <target-address> includes all the elements of the
particular some-address chosen in this case.  It MUST include the
additional-information. Carrier and the carrier-address (even the last part
of it) COULD be assumed to be available to the receiver.
 --> yes it does include all parts.
 --> there is only one target-address. Other addresses (i.e. "our"
addresses) may be repeated, and are to be treated as alternates.
 --> multiple x-address must be adjacent