[Bug 23441] Establish an MSE bytestream format registry

https://www.w3.org/Bugs/Public/show_bug.cgi?id=23441

--- Comment #3 from Aaron Colwell <acolwell@google.com> ---
(In reply to Pierre Lemieux from comment #2)
> The statement "the byte stream format registry is the authoritative source
> for byte stream format specifications that can be accepted by a
> SourceBuffer" implies that implementations cannot support a byte stream
> unless it is listed in the registry. Per the call earlier, this does not
> sound like it is the objective.
> 
> Suggest instead: "The byte stream format registry provides a mapping between
> return values of canPlayType() and byte stream format specifications."

I don't think the suggested text is quite right. I think the following might be
a little better at conveying what you want and perhaps address Adrian's
concerns on the call.

"The byte stream format registry provides mappings between a MIME type that may
be passed to addSourceBuffer() or isTypeSupported() and the byte stream format
expected by a SourceBuffer created with that MIME type. Implementations are
encouraged to register mappings for byte stream formats they support to
facilitate interoperability. The byte stream format registry is the
authoritative source for these mappings. If an implementation claims to support
a MIME type listed in the registry, its SourceBuffer implementation must
conform to the byte stream format specification listed in the registry entry."

I think this conveys that implementations can include mappings that are not in
the registry w/o encouraging such behavior. I want to avoid explicitly saying
"implementations may include stuff that is not in the registry" because I think
that sends the wrong message.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.

Received on Wednesday, 13 November 2013 08:41:00 UTC