Skip to content

Consider removing Use Cases summary from core DM #1169

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

Closed
brentzundel opened this issue Jun 26, 2023 · 6 comments · Fixed by #1429
Closed

Consider removing Use Cases summary from core DM #1169

brentzundel opened this issue Jun 26, 2023 · 6 comments · Fixed by #1429
Assignees
Labels
ready for PR This issue is ready for a Pull Request to be created to resolve it

Comments

@brentzundel
Copy link
Member

When the VC Data Model was first published, the Use Cases document wasn't in the state it currently is. So a section of use cases was added to the core data model.

Now that we have a published and (soon to be new and improved) Use Cases document, I propose we rely on that document and remove the use cases summary from the core data model.

Concretely, I think we should remove section 1.3 and instead point to Use Cases and Requirements

@OR13
Copy link
Contributor

OR13 commented Jun 29, 2023

I agree.

@msporny
Copy link
Member

msporny commented Jun 30, 2023

Concretely, I think we should remove section 1.3 and instead point to Use Cases and Requirements

I'd be ok with doing that if someone cross-references all of the items in this list and ensures they are captured in the use cases document (I'm not sure that they are).

The reason we had this section initially was to ensure that the WG wrote down exactly what sort of ecosystem they wanted to create; that is, the three-party ecosystem (since we had organizations claiming that the three-party ecosystem was unnecessary at the time, or were confused about what such an ecosystem actually looked like).

I'd feel more comfortable if this section was moved to the Use Cases document in its entirety, and then whittled away over time as the statements were incorporated into that document.

@OR13
Copy link
Contributor

OR13 commented Jun 30, 2023

I'd be fine moving the section to use cases as a first step.

@brentzundel
Copy link
Member Author

@jandrieu and @KDean-GS1 there is a suggestion to either entirely remove, or move the VC Data Model Uses Cases section into VC Use Cases. I would appreciate your thoughts here.

@iherman
Copy link
Member

iherman commented Jul 20, 2023

The issue was discussed in a meeting on 2023-07-19

  • no resolutions were taken
View the transcript

2.1. Consider removing Use Cases summary from core DM (issue vc-data-model#1169)

See github issue vc-data-model#1169.

Brent Zundel: 1169 - since the Use Cases say what we want to say, I suggest removing the Use Case summary from the data model.

Manu Sporny: I fully support removing it as long as we make sure we have accounted for everything.
… The list is important as we spent a lot of time making sure that it was complete.

Manu Sporny: +1 this is post CR.

Brent Zundel: This is purely editorial, so I will label it post-CR.

Joe Andrieu: if someone wants the granularity expressed in the list, they can go to the separate document. However, a few concrete use-case examples would be beneficial.

@brentzundel brentzundel added the ready for PR This issue is ready for a Pull Request to be created to resolve it label Jan 24, 2024
@iherman
Copy link
Member

iherman commented Jan 24, 2024

The issue was discussed in a meeting on 2024-01-24

  • no resolutions were taken
View the transcript

2.1. Consider removing Use Cases summary from core DM (issue vc-data-model#1169)

See github issue vc-data-model#1169.

Brent Zundel: Consider removing use cases summary from core data model. I raised this issue to suggest that ... now that the data model is on a version 2.0 we may not need all the use cases stuff in the core data model spec in addition to the use cases document which also is being refurbished this round.
… The question to the group is: Do folks agree?

Manu Sporny: +1 I think this is ready for PR and we should remove it. One of the strongest arguments for removing it -- is we published 1.0 and 1.1 and it was in there.
… We can point back to those. It might be worth putting a link in there to those and another link to the use cases document in the PR you raise, Brent.
… So people can follow their nose to the content.

Brent Zundel: Originally, the question was -- do we just get rid of it, do we move it wholesale to the use cases/requirements doc, no takers there -- so the plan for the PR is to remove the section and add links and clean up the language.
… If anyone feels the plan should be different, please speak now.
… And I will have to remember I have something on my plate.
… Ok, not hearing any objections.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
ready for PR This issue is ready for a Pull Request to be created to resolve it
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants