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 3 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?

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

[=group=] on its own links to a definition that also includes the AC. I don't think the AC should be in the business of publishing anything

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

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

To me, this seems like the place in the Process which establishes who can publish a Registry. The alternative is line 3018, but that feels more like a reference to something established elsewhere than the place that establishes it.

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

Copy link
Member

Choose a reason for hiding this comment

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

in the case of is usually more words than necessary. I try to eliminate it whenever I see it.

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, for [=Working Groups=], incorporated into a [=Recommendation=]
as an <dfn oldids="registry-section">embedded registry</dfn>.

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

Indirectly, I think which phrasing we pick here kind of depends on what we do on line 4727: depending on how we right the two parts of this contrast, we might suggest that doing a registry in a REC is the only way for WGs to do it, while we actually want to say that only WGs have the ability to do so, but that they can also do it standalone like everyone else.

index.bs Outdated Show resolved Hide resolved
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

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

[=groups=] also refers to the AB, TAG, and AC, which I don't think is appropriate in the context of this sentense

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

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

Ok with dropping to group, but I don't think the hyperlinking helps

Co-authored-by: fantasai <[email protected]>
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