Given explainers have no formal standing in terms of W3C process, I'll merge this PR now to allow the interested parties read and comment on the document more easily.
I expect further refinements are needed. Feedback is welcome via the issue #9 and as PRs against this markdown file that is the source of the explainer. Given this is an explainer-stage work hashing out use cases and exploring various designs, contributors from outside the WG participants continue to be very much welcome. A lot of the feedback incorporated into this document in fact originates from the broader ecosystem or from participants of other W3C WGs.
With my co-chair hat on I'll note that merging this PR now does not mean the WG would start work on this feature. Technically, we're incubating this feature directly in a Working Group as allowed by the W3C process and our charter.
Given explainers have no formal standing in terms of W3C process, I'll merge this PR now to allow the interested parties read and comment on the document more easily.
I expect further refinements are needed. Feedback is welcome via the issue #9 and as PRs against this markdown file that is the source of the explainer. Given this is an explainer-stage work hashing out use cases and exploring various designs, contributors from outside the WG participants continue to be very much welcome. A lot of the feedback incorporated into this document in fact originates from the broader ecosystem or from participants of other W3C WGs.
With my co-chair hat on I'll note that merging this PR now does not mean the WG would start work on this feature. Technically, we're incubating this feature directly in a Working Group as allowed by the W3C process and our charter.