Reminder: MathML meeting on Thursday

 We meet on Thursday at 10am Pacific, 1pm Eastern, *6pm Central European
Time.*

Note: North America and Europe still differ by one hour more than normal,
so the meeting will be an hour earlier in Europe.

The regulars for this group should have the meeting details in their
calendars. For everyone else, the details can be found on the members-only
W3C Math WG calendar
<https://www.w3.org/events/meetings/d6f2b73d-34fc-4276-b164-bdc62a675dcc/20230713T130000/>
.

Agenda
1. Announcements/Updates/Progress reports
2. Review updated draft charter
<https://w3c.github.io/mathml-docs/charter-2026.html>. Issues on it are here
<https://github.com/w3c/mathml/issues/568>.
3. Discuss the appropriateness of registries
<https://www.w3.org/policies/process/#registries>for intent concepts

Please try to read the documentation at the registries link above. I don't
have any experience with them and I need others to be informed about them
if we are to have a discussion.

Note: I asked AI for pros and cons:
Why Registries Are a Good Fit

   -

   *Lightweight Updates:* Unlike the Recommendation Track, changes to *registry
   entries <https://www.w3.org/policies/process/#registry-entry>* do not
   require a new *Advisory Committee Review
   <https://www.w3.org/policies/process/#advisory-committee-review>* or
   patent exclusion opportunities, provided the changes follow the
established *registry
   definition <https://www.w3.org/policies/process/#registry-definition>*.
   -

   *Separation of Concerns:* The *Registry Track
   <https://www.w3.org/policies/process/#registries>* allows the Working
   Group to define the *structure* and *policy* of the list once (the
   definition), while the actual *data* (the list of concepts) can evolve
   as the community identifies new needs.
   -

   *External Submissions:* The process facilitates *submission
   <https://www.w3.org/policies/process/#reg-def>* and ease of adding new
   terms, including by stakeholders who may be external to the core Working
   Group.
   -

   *Formal Status:* A *W3C Registry
   <https://www.w3.org/policies/process/#w3c-registry>* still carries the
   endorsement of W3C, providing the "core concepts" with more weight and
   stability than a simple *Group Note
   <https://www.w3.org/policies/process/#Note>*.


Cons of Using a Registry (vs. a Group Note)

   -

   *Significant Initial "Definition" Burden:* Unlike a Group Note
   <https://www.w3.org/policies/process/#WGNote>, which can be relatively
   free-form, a registry requires a formal registry definition
   <https://www.w3.org/policies/process/#reg-def>. The Working Group must
   achieve consensus on and document:
   -

      The exact *fields and constraints* of the data.
      -

      The *criteria for approval* (e.g., who can submit, what background
      info is required).
      -

      A *change policy* for how entries are deleted, deprecated, or
      modified.
      -

   *Maintenance Infrastructure Requirements:* A registry is a "living"
   document that necessitates ongoing administrative support:
   -

      *Designated Custodian:* You must identify a custodian
      <https://www.w3.org/policies/process/#custodian> responsible for
      evaluating requests. If that custodian becomes unresponsive, it
requires a W3C
      Decision <https://www.w3.org/policies/process/#def-w3c-decision>
and Advisory
      Committee Review
      <https://www.w3.org/policies/process/#advisory-committee-review> to
      replace them.
      -

      *Notification Systems:* The W3C Team
      <https://www.w3.org/policies/process/#team> is required to provide a
      means for interested parties to be notified of updates, adding technical
      overhead to the publication process.
      -

   *Strict Structural Limitations:* Registries
   <https://www.w3.org/policies/process/#registry> are designed strictly to
   document values and data. They are subject to specific restrictions that
   don't apply to Notes <https://www.w3.org/policies/process/#WGNote>:
   -

      *No Normative Requirements:* A registry report
      <https://www.w3.org/policies/process/#registry-report> or embedded
      registry <https://www.w3.org/policies/process/#embedded-registry> *must
      not* define any architectural or interoperability requirements.
      -

      *Patent Policy Exclusion:* Registries
      <https://www.w3.org/policies/process/#registry> are not subject to
      the W3C Patent Policy <https://www.w3.org/policies/patent-policy/>.
      If the "core concepts" imply specific implementation requirements or IPR
      commitments, they would need to be in a Recommendation Track
      <https://www.w3.org/policies/process/#w3c-recommendation-track>
      document instead.
      -

   *Complexity in Referencing:* As a registry
   <https://www.w3.org/policies/process/#registry> is essentially a lookup
   table, any specification that references it
   <https://www.w3.org/policies/process/#reg-ref-specifications> must be
   carefully written to ensure that a change in the registry doesn't
   accidentally change the conformance of the specification.


Finally, here are all the existing registries. They are all in a draft
state:

   -

   *WebCodecs Codec Registry
   <https://www.w3.org/TR/webcodecs-codec-registry/>*
   -

   *WebCodecs VideoFrame Metadata Registry
   <https://www.w3.org/TR/webcodecs-video-frame-metadata-registry/>*
   -

   *Encrypted Media Extensions Stream Format Registry
   <https://www.w3.org/TR/eme-stream-registry/>*
   -

   *Encrypted Media Extensions HDCP Version Registry
   <https://www.w3.org/TR/eme-hdcp-version-registry/>*
   -

   *Encrypted Media Extensions Initialization Data Format Registry
   <https://www.w3.org/TR/eme-initdata-registry/>*
   -

   *Web of Things (WoT) Binding Registry
   <https://www.w3.org/TR/wot-binding-registry/>*
   -

   *Media Source Extensions Byte Stream Format Registry
   <https://www.w3.org/TR/mse-byte-stream-format-registry/>*
   -

   *W3C Alternative and Augmented Communication (AAC) Symbol Registry
   <https://www.w3.org/TR/aac-registry/>*

All of the lists are quite short except the last one. For that, they have a
JSON list link and a table for visual display. The data is very simple. It
is draft dated 2022.

There is also "DID Methods <https://www.w3.org/TR/did-extensions-methods/>"
(which Gemini halunciated as being on the registry track). The
Decentralized Identifier Working Group <https://www.w3.org/groups/wg/did/> used
a series of W3C Notes to publish their list. They have a list of over 100
entries.