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

Which document would (formally) define the terms for vocabularies #18

Closed
iherman opened this issue May 21, 2024 · 3 comments
Closed

Which document would (formally) define the terms for vocabularies #18

iherman opened this issue May 21, 2024 · 3 comments
Assignees

Comments

@iherman
Copy link
Member

iherman commented May 21, 2024

(This is just a bookmark for ourselves to act upon when the time comes...)

At the moment, the formal vocabulary terms in the Security Vocabulary are defined in the DI spec. This includes terms like "authentication". I would think that, eventually, the formal definition of the term will be exclusively in the controller document; when that happens, the Security Vocabulary must be updated, too.

@iherman
Copy link
Member Author

iherman commented May 21, 2024

Ref to #10, too.

@iherman
Copy link
Member Author

iherman commented Jun 19, 2024

The issue was discussed in a meeting on 2024-06-19

  • no resolutions were taken
View the transcript

3.7. Which document would (formally) define the terms for vocabularies (issue controller-document#18)

See github issue controller-document#18.

Brent Zundel: Formal vocabulary terms for security terms in data integrity, move to controller document.

Manu Sporny: Security vocabulary formally points to data integrity spec. Can update references to controller document. Would be the right thing to do. Can work with Ivan on that.

Brent Zundel: Calling it a day. Still a number of issues that are open.
… Core data model in a good place, now focusing on controller document.


@iherman
Copy link
Member Author

iherman commented Jul 18, 2024

This has been taken care of in w3c/vc-data-integrity#280. The current issue should have been closed at the merge of that issue; closing now.

@iherman iherman closed this as completed Jul 18, 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

2 participants