W3C home > Mailing lists > Public > public-html-bugzilla@w3.org > October 2012

[Bug 19615] New: editorial change to 1.2.2 key system part

From: <bugzilla@jessica.w3.org>
Date: Fri, 19 Oct 2012 02:56:03 +0000
To: public-html-bugzilla@w3.org
Message-ID: <bug-19615-2486@http.www.w3.org/Bugs/Public/>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=19615

          Priority: P2
            Bug ID: 19615
                CC: mike@w3.org, public-html-media@w3.org
          Assignee: adrianba@microsoft.com
           Summary: editorial change to 1.2.2 key system part
        QA Contact: public-html-bugzilla@w3.org
          Severity: normal
    Classification: Unclassified
                OS: Windows NT
          Reporter: eric.sun@huawei.com
          Hardware: PC
            Status: NEW
           Version: unspecified
         Component: Encrypted Media Extensions
           Product: HTML WG

There are some typos in 1.2.2 Key System section, I use ////???->"proposed
text" //// to show the modification.


///////////////////////////change begin/////////////////////////////////////
1.2.2. Key System

A Key System is a generic term for a decryption mechanism and/or content
protection provider. Key System strings provide unique identification of a Key
System. They ////"are"////  used by the user agent to select the Content
Decryption Modules and identify the source of a key-related event. Simple
Decryption Key Systems are supported by all user agents. User agents may also
provide additional CDMs with corresponding Key System strings.

Key System ////strings -> "string"//// ////are->"is"//// always a reverse
domain name. For example, "com.example.somesystem". Within a given system
("somesystem" in the example), ////subsystems->"sub Key System" /////may be
defined as determined by the key system provider. For example,
"com.example.somesystem.1" and "com.example.somesystem.1_5". Key system
providers should keep in mind that these will be used for comparison and
discovery, so they should be easy to compare and the structure should remain
reasonably simple.

If a user agent returns "maybe" or "probably" for any ////subsystem->"sub key
System"//// string, it must return "maybe" when a ////parent system->"parent
Key System" ////string is passed to canPlayType(). For example, if a user agent
returns "maybe" or "probably" for "com.example.somesystem.1_5", it must return
"maybe" for "com.example.somesystem".

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
Received on Friday, 19 October 2012 02:56:06 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Friday, 19 October 2012 02:56:08 GMT