Skip to content

Add note about mandatory/optional #22

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

Merged
merged 1 commit into from
Jun 12, 2025

Conversation

David-Chadwick
Copy link
Collaborator

@David-Chadwick David-Chadwick commented Jun 4, 2025

Copy link
Collaborator

@hendersonweb hendersonweb left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

ya that's a good idea to mention it explicitly. Agreed.

@David-Chadwick David-Chadwick merged commit b6aef62 into w3c-ccg:main Jun 12, 2025
Copy link
Contributor

@TallTed TallTed left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

To help ensure these discussions happen...

@@ -732,6 +732,9 @@ <h1>Overview of List Operator</h1>
<p>The List Operator provides a framework for managing a trusted list, which includes essential information about the entity responsible for the list's maintenance and its associated attributes.</p>

<h2>Attributes of List Operator</h2>
<p>
NOTE. It still needs to be decided which attributes should be mandatory and which should be optional. This needs further discussion.
Copy link
Contributor

@TallTed TallTed Jun 17, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Wording change, and perhaps this should be an issue, with link in the document?

Suggested change
NOTE. It still needs to be decided which attributes should be mandatory and which should be optional. This needs further discussion.
NOTE. It is yet to be decided which attributes should be mandatory and which
should be optional. This needs further discussion.

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Given that this draft has not yet been adopted by the WG, we cannot say it needs further discussion by the WG. The current wording implies that whoever works on the document next, will need to discuss this. So it implies the WG if the WG adopts it.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

OK, revised suggestion.

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

revised wording accepted but cannot be committed as the PR has already been merged. So can you raise a new PR please.

@@ -768,6 +772,9 @@ <h1>Overview of Trust Service Provider</h1>
<li>A set of URIs from which information about the TSP can be obtained</li>
</ul>
<h2>Attributes of Trust Service Provider</h2>
<p>
NOTE. It still needs to be decided which attributes should be mandatory and which should be optional. This needs further discussion.
Copy link
Contributor

@TallTed TallTed Jun 17, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Wording change, and perhaps this should be an issue, with link in the document?

Suggested change
NOTE. It still needs to be decided which attributes should be mandatory and which should be optional. This needs further discussion.
NOTE. It is yet to be decided which attributes should be mandatory and which
should be optional. This needs further discussion.

hendersonweb added a commit to hendersonweb/verifiable-issuers-verifiers that referenced this pull request Jul 7, 2025
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

Successfully merging this pull request may close these issues.

3 participants