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

frivoal · 2025-01-08T08:49:45Z

See #902

Preview | Diff

See w3c#902

TallTed

Tiny typo

index.bs

Co-authored-by: Ted Thibodeau Jr <[email protected]>

fantasai · 2025-01-09T04:09:15Z

index.bs

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


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

[=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

fantasai · 2025-01-09T04:10:05Z

index.bs

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


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

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.

fantasai · 2025-01-09T04:10:37Z

index.bs

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


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

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

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.

I've suggested alternative wording that happens to address @frivoal 's comment above regarding WG options as well as removing "in the case of".

index.bs

fantasai · 2025-01-09T04:12:32Z

index.bs

 	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


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

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

fantasai · 2025-01-09T04:12:46Z

index.bs

 	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


Suggested change

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

If the [=group=] establishing the registry wishes

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

I was going to make the same comment as @fantasai - not only is it unnecessary wording, but it's also a future potential maintenance gotcha.

Co-authored-by: fantasai <[email protected]>

tantek

Seems like a reasonable improvement, and I agree with the replies from @frivoal to suggested changes.

nigelmegitt

Looks good to me, have made suggestions to remove probably unnecessary wording.

nigelmegitt · 2025-01-16T14:27:16Z

index.bs

+	[=Registries=] can be published by [=chartered group|chartered=] or [=elected groups=] either
 	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>.


This wording could be misunderstood to mean that chartered groups that are not Working Groups can publish registry reports, but that Working Groups can only incorporate them into Recommendations.

Suggested change

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

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

[=Registries=] can be published by [=chartered group|chartered=] or [=elected groups=]

as a stand-alone [=technical report=] on the [=Registry Track=] called a <dfn>registry report</dfn>.

[=Working Groups=] have an additional option to incorporate them as part of a [=Recommendation=], as an <dfn oldids="registry-section">embedded registry</dfn>.

nigelmegitt · 2025-01-16T14:28:37Z

index.bs

 	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


I was going to make the same comment as @fantasai - not only is it unnecessary wording, but it's also a future potential maintenance gotcha.

nigelmegitt · 2025-01-16T14:29:32Z

index.bs

 	to empower the custodian to add commentary on individual entries,
 	this needs to be part of the registry table’s definition.
 	If other changes are desired,
-	they need to be requested of the responsible Working Group--
-	or in the absence of a Working Group, of the Team.
+	they need to be requested of the [=chartered group|chartered=] or [=elected group=] responsible for maintaining the [=registry definition=]--


Suggested change

they need to be requested of the [=chartered group|chartered=] or [=elected group=] responsible for maintaining the [=registry definition=]--

they need to be requested of the group responsible for maintaining the [=registry definition=]--

nigelmegitt · 2025-01-16T14:29:56Z

index.bs

@@ -4859,12 +4859,13 @@ Registry Data Reports</h4>
 	is that of the [=technical report=] holding the [=registry definition=].

 	Anytime a change is made to a [=registry definition=],
-	the Working Group <em class=rfc2119>must</em> update and republish
+	the [=chartered group|chartered=] or [=elected group=] maintaining the [=registry definition=]


Suggested change

the [=chartered group|chartered=] or [=elected group=] maintaining the [=registry definition=]

the group maintaining the [=registry definition=]

nigelmegitt · 2025-01-16T14:30:14Z

index.bs

 	any document holding the corresponding [=registry tables=]
 	to make it consistent with these changes.

 	Given a recorded [=group decision=] to do so,
-	the [=Working Group=]
+	the [=chartered group|chartered=] or [=elected group=] maintaining the [=registry definition=]


Suggested change

the [=chartered group|chartered=] or [=elected group=] maintaining the [=registry definition=]

the group maintaining the [=registry definition=]

nigelmegitt · 2025-01-16T14:34:19Z

index.bs

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


I've suggested alternative wording that happens to address @frivoal 's comment above regarding WG options as well as removing "in the case of".

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

0828866

See w3c#902

frivoal added the Agenda+ Marks issues that are ready for discussion on the call label Jan 8, 2025

frivoal requested a review from fantasai January 8, 2025 08:49

TallTed suggested changes Jan 8, 2025

View reviewed changes

index.bs Outdated Show resolved Hide resolved

Fix capitalization

089f26d

Co-authored-by: Ted Thibodeau Jr <[email protected]>

fantasai reviewed Jan 9, 2025

View reviewed changes

index.bs Outdated Show resolved Hide resolved

fantasai reviewed Jan 9, 2025

View reviewed changes

improve phrasing

7329d5c

Co-authored-by: fantasai <[email protected]>

tantek approved these changes Jan 16, 2025

View reviewed changes

nigelmegitt reviewed Jan 16, 2025

View reviewed changes

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

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

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

frivoal commented Jan 8, 2025 •

edited by pr-preview bot

Loading

TallTed left a comment

fantasai Jan 9, 2025

frivoal Jan 10, 2025

fantasai Jan 9, 2025

frivoal Jan 10, 2025

fantasai Jan 9, 2025

TallTed Jan 9, 2025

frivoal Jan 10, 2025

nigelmegitt Jan 16, 2025 •

edited

Loading

fantasai Jan 9, 2025

frivoal Jan 10, 2025

fantasai Jan 9, 2025

frivoal Jan 10, 2025

nigelmegitt Jan 16, 2025

tantek left a comment

nigelmegitt left a comment

nigelmegitt Jan 16, 2025

nigelmegitt Jan 16, 2025

nigelmegitt Jan 16, 2025

nigelmegitt Jan 16, 2025

nigelmegitt Jan 16, 2025

nigelmegitt Jan 16, 2025 •

edited

Loading

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

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

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

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

	they need to be requested of the [=chartered group\|chartered=] or [=elected group=] responsible for maintaining the [=registry definition=]--
	they need to be requested of the group responsible for maintaining the [=registry definition=]--

	the [=chartered group\|chartered=] or [=elected group=] maintaining the [=registry definition=]
	the group maintaining the [=registry definition=]

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

Are you sure you want to change the base?

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

Conversation

frivoal commented Jan 8, 2025 • edited by pr-preview bot Loading

TallTed left a comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

nigelmegitt Jan 16, 2025 • edited Loading

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

tantek left a comment

Choose a reason for hiding this comment

nigelmegitt left a comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

nigelmegitt Jan 16, 2025 • edited Loading

Choose a reason for hiding this comment

frivoal commented Jan 8, 2025 •

edited by pr-preview bot

Loading

nigelmegitt Jan 16, 2025 •

edited

Loading

nigelmegitt Jan 16, 2025 •

edited

Loading