Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

PROPOSAL: Separate the DID Method App Developer Spec from the DID Method Implementor Spec from the Business Message Flow Spec #28

Open
mwherman2000 opened this issue Dec 21, 2024 · 0 comments

Comments

@mwherman2000
Copy link

mwherman2000 commented Dec 21, 2024

For example, separate the specification of the blue boxes (DID Method App Developer Specifications) from the green boxes (DID Method Implementor Specifications) from the purple boxes (Business Message Flow Specifications):

  • The audience for the blue boxes are Application Architects and Developers leveraging DID Methods in their apps.
  • The audience for the green boxes are DID Method Implementors.
  • The audience for the purple boxes are Business Analysts.

Each of the 3 audiences has very different needs regarding a specification - indicating that each audience needs their own spec.

image

@mwherman2000 mwherman2000 changed the title PROPOSAL: Separate the specification of a DID Method from its underlying deployment/infrastructure architecture PROPOSAL: Separate the DID Method App Developer Spec from the DID Method Implementor Spec Dec 21, 2024
@mwherman2000 mwherman2000 changed the title PROPOSAL: Separate the DID Method App Developer Spec from the DID Method Implementor Spec PROPOSAL: Separate the DID Method App Developer Spec from the DID Method Implementor Spec from the Business Message Flow Spec Dec 22, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant