[wg/das] Move Web Serial from "Tentative Deliverable" to "Deliverable"

[hafta]

Can Web Serial be moved from “tentative deliverable” to “deliverable” given Mozilla has announced an intent to prototype which would make two implementations?

Here's Mozilla’s intent to prototype: https://groups.google.com/a/mozilla.org/g/dev-platform/c/EDLTASS4Zik/m/LXJRL6yFCQAJ

We prefer to keep the existing note in the listing of the deliverable: "Note: This work may turn into a joint deliverable with the Web Applications Working Group."

[anssiko]

@himorin to integrate.

[marcoscaceres]

Before integrating this, a few things worth noting while the charter is still in the refinement phase (In Charter Refinement) and horizontal reviews are ongoing — including an unresolved i18n issue (i18n-needs-resolution on w3c/strategy#530).

Mozilla's intent to prototype is noted, but an intent is not yet an implementation. Promoting Web Serial from tentative deliverable to full deliverable implies the WG expects this to proceed to Recommendation, which the W3C Process says requires the Team to consider whether "there are independent interoperable implementations of the current specification."

The request doesn't explain what use cases or platform-model changes make this appropriate to promote now that weren't present during the WICG incubation. What is different? WebKit's position on Web Serial is under evaluation (WebKit/standards-positions#199), and it's an open question whether Web Serial has the same device-independence profile as WebUSB and Web Bluetooth.

The venue question in #783 is also directly relevant and unresolved.