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

Extend the ability to publish Registries to IG/AB/TAG #972

Open
wants to merge 2 commits into
base: main
Choose a base branch
from

Conversation

frivoal
Copy link
Collaborator

@frivoal frivoal commented Jan 8, 2025

See #902


Preview | Diff

@frivoal frivoal added the Agenda+ Marks issues that are ready for discussion on the call label Jan 8, 2025
@frivoal frivoal requested a review from fantasai January 8, 2025 08:49
Copy link
Member

@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.

Tiny typo

index.bs Outdated Show resolved Hide resolved
Co-authored-by: Ted Thibodeau Jr <[email protected]>
@@ -4702,15 +4702,15 @@ Registry Definitions</h4>
and which is responsible for evaluating whether such requests
satisfy the criteria defined in the [=registry definition=].

The [=custodian=] may be the [=Working Group=], the [=Team=], or a delegated entity.
The [=custodian=] may be the initiating [=chartered group|chartered=] or [=elected group=], the [=Team=], or a delegated entity.
Copy link
Collaborator

Choose a reason for hiding this comment

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

I think we can simplify this to "[=group=]", no?

@@ -4721,9 +4721,9 @@ Registry Definitions</h4>
<h4 id=reg-pub>
Publishing Registries</h4>

[=Registries=] can be published either
[=Registries=] can be published by [=chartered group|chartered=] or [=elected groups=] either
Copy link
Collaborator

Choose a reason for hiding this comment

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

I think we can just delete the "by" phrase, it's not adding anything.

as a stand-alone [=technical report=] on the [=Registry Track=] called a <dfn>registry report</dfn>,
or incorporated as part of a [=Recommendation=] as an <dfn oldids="registry-section">embedded registry</dfn>.
or, in the case of [=Working Groups=], incorporated as part of a [=Recommendation=] as an <dfn oldids="registry-section">embedded registry</dfn>.
Copy link
Collaborator

Choose a reason for hiding this comment

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

Suggested change
or, in the case of [=Working Groups=], incorporated as part of a [=Recommendation=] as an <dfn oldids="registry-section">embedded registry</dfn>.
or, in the case of those owned by [=Working Groups=],
incorporated as part of a [=Recommendation=] as an <dfn oldids="registry-section">embedded registry</dfn>.

@@ -4814,22 +4814,22 @@ Updating Registry Tables</h4>
(i.e. [[#correction-classes|Class 5 changes]])
can be made by re-publishing the [=technical report=] that contains the affected table,
without needing to satisfy any other requirements for the publication
(not even Working Group consensus, unless this is required by the [=registry definition=]).
(not even consensus, unless this is required by the [=registry definition=]).
Copy link
Collaborator

Choose a reason for hiding this comment

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

Suggested change
(not even consensus, unless this is required by the [=registry definition=]).
(not even a [=group decision=], unless this is required by the [=registry definition=]).

Copy link
Collaborator

Choose a reason for hiding this comment

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

And so on throughout.

Such [=registry changes=] do not trigger new [=Advisory Committee Reviews=],
nor Exclusion Opportunities,
and do not require verification via an [=update request=],
even for [=technical reports=] at maturities where this would normally be expected.
Such publications can be made
even in the absence of a [=Working Group=] chartered to maintain the registry
even in the absence of a group chartered to maintain the registry
Copy link
Collaborator

Choose a reason for hiding this comment

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

Suggested change
even in the absence of a group chartered to maintain the registry
even in the absence of a [=group=] chartered to maintain the registry

when the [=custodian=] is another entity.

Note: The custodian is only empowered to make [=registry changes=].
If the Working Group establishing the registry wishes
If the [=chartered group|chartered=] or [=elected group=] establishing the registry wishes
Copy link
Collaborator

Choose a reason for hiding this comment

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

Suggested change
If the [=chartered group|chartered=] or [=elected group=] establishing the registry wishes
If the [=group=] establishing the registry wishes

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Agenda+ Marks issues that are ready for discussion on the call
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants