[OASIS Issue Tracker] (AMQP-131) Clarify Source default-outcome and outcomes field descriptions

[OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org>]

     [ https://issues.oasis-open.org/browse/AMQP-131?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Lorenz Quack updated AMQP-131:
------------------------------

    Description: 
Currently the description of the default-outcome field of the source type is confusing:

1) The specification says: "The value MUST be a valid outcome." This seems to contradict the fact that the field is not mandatory.

2) The specification says: "Indicates the outcome to be used for transfers that have not reached a terminal state at the receiver when the transfer is settled, including when the source is destroyed." My understanding of this was that this *instructs* the receiver to use the specified outcome in the given scenario. This does not make sense. Rob mentioned in a private conversation that the intention is that this *informs* the receiver of the sender's behaviour in the given scenario.

-3) My assumption is that the default-outcome should be listed in the "outcomes" field (if specified). This is not mentioned in the specification.-


  was:
Currently the description of the default-outcome field of the source type is confusing:

1) The specification says: "The value MUST be a valid outcome." This seems to contradict the fact that the field is not mandatory.

2) The specification says: "Indicates the outcome to be used for transfers that have not reached a terminal state at the receiver when the transfer is settled, including when the source is destroyed." My understanding of this was that this *instructs* the receiver to use the specified outcome in the given scenario. This does not make sense. Rob mentioned in a private conversation that the intention is that this *informs* the receiver of the sender's behaviour in the given scenario.

3) My assumption is that the default-outcome should be listed in the "outcomes" field (if specified). This is not mentioned in the specification.



> Clarify Source default-outcome and outcomes field descriptions
> --------------------------------------------------------------
>
>                 Key: AMQP-131
>                 URL: https://issues.oasis-open.org/browse/AMQP-131
>             Project: OASIS Advanced Message Queuing Protocol (AMQP) TC
>          Issue Type: Improvement
>          Components: Messaging
>            Reporter: Lorenz Quack
>              Labels: Clarification
>
> Currently the description of the default-outcome field of the source type is confusing:
> 1) The specification says: "The value MUST be a valid outcome." This seems to contradict the fact that the field is not mandatory.
> 2) The specification says: "Indicates the outcome to be used for transfers that have not reached a terminal state at the receiver when the transfer is settled, including when the source is destroyed." My understanding of this was that this *instructs* the receiver to use the specified outcome in the given scenario. This does not make sense. Rob mentioned in a private conversation that the intention is that this *informs* the receiver of the sender's behaviour in the given scenario.
> -3) My assumption is that the default-outcome should be listed in the "outcomes" field (if specified). This is not mentioned in the specification.-



--
This message was sent by Atlassian JIRA
(v6.2.2#6258)