Skip to content

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

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

Define Audience for TRTF v2 #49

Closed
andorsk opened this issue Jan 12, 2023 · 1 comment
Closed

Define Audience for TRTF v2 #49

andorsk opened this issue Jan 12, 2023 · 1 comment
Labels
type: discussion discussion related issue. type: documentation Improvements or additions to documentation
Milestone

Comments

@andorsk
Copy link
Contributor

andorsk commented Jan 12, 2023

The goal of this issue is to define the audience for trtf v2 w.r.t. the #48 . My STRAWMAN suggestion here is the the following:

  • Specification: Should be technical in nature and very specific.
    • Developers and Architects
    • Standards Bodies
  • Companion Guide: Should focus on readability and clarity.
    • Developers and Architects
    • Governance bodies
    • People that want to learn more about trust registries at an ecosystem level

We can discuss more over the call.

Proposal to close this issue: A section in the README of the v2 section defining the intended audience of the deliverables, and possibly additional section within the deliverables themselves.

@andorsk andorsk added the type: documentation Improvements or additions to documentation label Jan 12, 2023
@andorsk
Copy link
Contributor Author

andorsk commented Jan 12, 2023

Jan 12 Meeting:

@tim: Interested in the what's not the hows. Needs to be simple.
@darrellodonnell : Companion guide(s) <- multiple guides for different personas.
@neil: Trust Registry is an example verifiable data. What does authentication mean in context of the TR. Authentic entities and authentic data.

  • who are the Persona's who a) use, b) update/create and c) are beneficiaries of TRs
    @a-fox: Pan Canadian Trust Framework: Assurance model. Bridges gap between policy makers and tech people.
    @mike: target the people who have to build ecosystems--companies (esp. large companies), organizations, and governments.
    @darrellodonnell: Personas - at minimum we have TWO - the Technical and Governance (includes Business). I think we can start there and refine over time. Answering the question: who's the authoritative issuers of the governance framework. Start with the STRAWMAN.
    @dan: two personas: (1) comments about what the code does, (2) actual code
    @tim: Government bodies. Needs to be crystal clear. Will eventually move to legislation so needs to consider policy makers.
    @Sandy: Audience should include the metaverse. Might have implications to the governance of the metaverse.
    @andorsk : need to care about unknown contexts.
    @jacques: DIACC PCF is well timed.

Action Items:

  • Tim to help build the personas for governance.
  • @andorsk technical personas.

@andorsk andorsk added the type: discussion discussion related issue. label Jan 12, 2023
@trustoverip trustoverip locked and limited conversation to collaborators Jan 17, 2023
@andorsk andorsk converted this issue into discussion #64 Jan 17, 2023

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

Labels
type: discussion discussion related issue. type: documentation Improvements or additions to documentation
Projects
None yet
Development

No branches or pull requests

1 participant