[Rats] Use case -> architecture document

[Kathleen Moriarty <[e-mail]>]

Hello!

I read through the latest version of the ‘use case’ document yesterday and
found it very easy to read and understand, meaning I think it is written
well and could be easily understood by many without having to climb up a
learning curve.

First, this could be a very useful document to register claims for the use
cases.

Second, if the workflow for the passport and background check were added
and put in terms of the open trust protocol v2 from TEEP, we have a fairly
nice architecture document that’s easy to read and may gain adoption.  The
workflows cover the various interactions between roles and TEEP has
actively broken up OTrP in v2 to accommodate using EAT tokens, this
would help create that link and make it very clear.

The other thing I like about the use case document and think we should
expand on is the references to other work items.  This makes it an
architecture document that maps out the full plan of the WG.  One like that
was extremely well received by all the ADs that don’t like
informational/helpful documents.

I’m a bit nervous with the terminology being defined and would love to see
something like this that’s simplified and more easily adoptable.

I appreciate the work done to improve the architecture document, but I do
think the structure changes to the use case document as suggested could
result in an easier to understand (and therefore easier to adopt) document.

While the architecture document is more readable, I think we can do
better.  Adoption is important and our timeliness matters a lot for this
work.  EATs can be used for may use cases with OTrPv2, so let's keep it as
simple as we can.

Thoughts are appreciated.

Best regards,
Kathleen--

Best regards,
Kathleen