RE: [bt-spec] BTP Issue 60 : address-as-role or role address

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

 

BTP Issue 60 : address-as-role or role address

Category: minor technical
Submitter: Peter Furniss, Choreology
Description:
The abstract message descriptions call the address parameters "address-as-superior", "address-as-inferior", "address-as-decider", intending to be clear that these are addresses the actor in question offers for that role (i.e. as the target of particular future messages), given that the actor may also offer other addresses for that role (or indeed the same address, but for a different role)

The xml constructs call these "superior address" etc., which is shorter, and perhaps more message-oriented. (a PREPARE for example travels from the Superior (for this relationship) to the address-as-inferior of the Inferior of the relationship.

The names should be aligned or the difference justified in the text.

---

The "address-as" form is clearer for description.

 

Suggestion:

Align them as address-as-whatever, changing the XML appropriately.