Re-define the relayer categories

[lukerQuant]

About you

Name: Luke Riley Organization/Company: Quant

About your review

Document: EEA DLT Interoperability Specification

Note: this is a really good piece of work, congratulations to the authors and to the EEA working group.

Section: https://entethalliance.github.io/crosschain-interoperability/draft_dlt-interop_techspec.html#crosschain-message-relays

Comments/Suggestions/Feedback

I disagree with Oracle being a particular relay sub-type. According to the ISO/TC 307 definitions (found here), all the relays types listed are oracles. Copying the oracle definitions from the linked document:

• DLT oracle (distributed ledger technology oracle): service that updates a distributed ledger using data from outside of a DLT system

Hence why the Oracle category was used as one of the two main interoperability solution types in section 3.3.3 here.

So my general proposal for this section is to rename the Oracle Relay to something else, and introduce a higher level introduction, potentially about the different interoperability modes and interoperability solutions discussed in here (as ISO/TC 307's Interoperability Framework is set to use a similar structure as this paper).

[anaisofranc]

We have discussed this issue. We agreed to update as per below:

1. 'Oracle Relay' to be changed to 'Type 1 Relay' and to add context including ISO definition.
2. Add "Interoperation Modes" as per section 3.3.1 Interoperation Modes in this paper and align with ISO Interoperability Framework as a sub-section in section '7. Considerations' .

[lukerQuant]

Dear @anaisofranc,

That sounds like a good plan.

Thank you for your feedback on this, and thank you to the EEA cross-chain interoperability working group for their help regarding aligning standards across different Standards Developing Organisations.

Best wishes