Orderer endpoint format in orderer org definition

[tock-ibm]

In Fabric-x each endpoint is a string, in json, yaml, or comma separated format.
It must include the ID (= PartyID), and the API role = delivery | broadcast, as well as the address and port.
In the fabric-x-orderer, party IDs start from 1, ID=0 is illegal. The range is 1:(2^16)-1 as the party-ID is uint16.

The set of endpoint IDs should be consistent with the set if IDs declared in the ConsenterMapping. That is, the set of IDs from ConsenterMapping, (e.g. 1,2,3,4) defines the set of parties in the ordering service. Each party (ID) should have a delivery endpoint (assembler) and a broadcast endpoint (router).

[cendhu]

In Fabric-x each endpoint is a string, in json, yaml, or comma separated format. -- Do we need to support all possible formats? I have raised this question earlier too in some PR review.

[liran-funaro]

We must support string. YAML and JSON are for convenience. Yoav asked for JSON and Pasquale asked for YAML.