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

[wg/did] change suggestion by @rxgrant #468

Merged
merged 5 commits into from
Dec 8, 2023
Merged

Conversation

pchampin
Copy link
Contributor

This PR reflects a change orinally proposed by @rxgrant at #448 (comment) .

It was discussed with some AC reviewers during today's meeting.

@rxgrant
Copy link

rxgrant commented Nov 30, 2023

I would change the "should not"s to "MUST NOT"s.

@pchampin pchampin changed the title change suggestion by @rxgrant [wg/did] change suggestion by @rxgrant Dec 1, 2023
2023/did-wg.html Outdated Show resolved Hide resolved
Co-authored-by: Ivan Herman <ivan@w3.org>
@pchampin
Copy link
Contributor Author

pchampin commented Dec 1, 2023

STRAWPOLL : please react to this post ("this PR" refers to changes up to e4ed7af)

  • 👍 I support this PR
  • 👀 I can live with this PR
  • 👎 I object to this PR

@cwilso
Copy link
Contributor

cwilso commented Dec 4, 2023

I don't understand the goal of obviating this.

@rxgrant
Copy link

rxgrant commented Dec 5, 2023

@cwilso it was explained in the thread that this came out of.

@brentzundel
Copy link
Member

I continue to maintain that this is an unnecessary change.
Also, this charter is not a specification, so adding normative language does not make sense to me. I can't approve with the normative language. I could hold my nose and not object if it were removed.

@cwilso
Copy link
Contributor

cwilso commented Dec 7, 2023

@rxgrant that's... not a response? Where was that discussion?

2023/did-wg.html Outdated Show resolved Hide resolved
@pchampin
Copy link
Contributor Author

pchampin commented Dec 8, 2023

Also, this charter is not a specification, so adding normative language does not make sense to me. I can't approve with the normative language.

@brentzundel see #467 (comment)

there are actually precedents of normative language in W3C charters :

* https://www.w3.org/2022/06/dx-wg-charter.html

* https://www.w3.org/2023/04/timed-text-wg-charter.html

In a sense, the charter specifies how the group will operate, so this is not entirely inappropriate...

That being said, as you +1'ed on Joe's proposal above, I'm accepting it.

Co-authored-by: Joe Andrieu <joe@andrieu.net>
@pchampin pchampin merged commit f421d75 into gh-pages Dec 8, 2023
@pchampin
Copy link
Contributor Author

@jandrieu

However, I do have a concern that even the language I propose would mean we could not maintain the Rubric as a NOTE. It is expected to shift to a registry, but we should clarify how this language affects that publication.

I believe that your latest proposal ("beyond those explicitly listed") is enough to "protect" the registry.

@plehegar plehegar deleted the did-wg-2023-notes branch June 25, 2024 21:25
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.

None yet

6 participants