You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Section 8 mentions a "a register of profile objects which currently contains just the 4 instances above from Figure 2."
Readers may expect (especially because of the word "currently") to be able to register their own functional profile into that register, just like with IANA registries. Note that W3C now has a Registry Track.
Do we want to use the Registry Track to define formal registration process to augment the table in Table 2. If not, we should probably reword Section 8 to defuse this kind of expectation.
The text was updated successfully, but these errors were encountered:
Yes, we do want a registry of Functional Profiles. We've seen a couple more FPs be considered recently (file name endings, not QSA or HTTP to indicate Media Types; OGC API implementation etc.), so we will likely see more still, at a very slow growth rate.
Section 8 mentions a "a register of profile objects which currently contains just the 4 instances above from Figure 2."
Readers may expect (especially because of the word "currently") to be able to register their own functional profile into that register, just like with IANA registries. Note that W3C now has a Registry Track.
Do we want to use the Registry Track to define formal registration process to augment the table in Table 2. If not, we should probably reword Section 8 to defuse this kind of expectation.
The text was updated successfully, but these errors were encountered: