<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:"Cordia New";
panose-1:2 11 3 4 2 2 2 2 2 4;}
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#0563C1;
text-decoration:underline;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
{mso-style-priority:99;
mso-style-link:"Plain Text Char";
margin:0in;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
span.PlainTextChar
{mso-style-name:"Plain Text Char";
mso-style-priority:99;
mso-style-link:"Plain Text";
font-family:"Calibri",sans-serif;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri",sans-serif;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang="EN-US" link="#0563C1" vlink="#954F72">
<div class="WordSection1">
<p class="MsoPlainText">If by "the request" you mean the original request to register these features (let me know if you mean something else), that was submitted to this list by Ken Lunde in December 2018. The following link will take you to the relevant message
in the list archive:<o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoNormal"><a href="https://lists.aau.at/pipermail/mpeg-otspec/2018-December/000060.html">https://lists.aau.at/pipermail/mpeg-otspec/2018-December/000060.html</a>
<o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText">AFAIK, a request for registration of these feature tags in OT was not submitted to Microsoft (or elsewhere) separately.<o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText">Peter<o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText">-----Original Message-----<br>
From: David Singer <singer@apple.com> <br>
Sent: Wednesday, August 19, 2020 1:46 PM<br>
To: Peter Constable <pgcon6@msn.com><br>
Cc: MPEG OT Spec list (mpeg-otspec@lists.aau.at) <mpeg-otspec@lists.aau.at><br>
Subject: Re: [MPEG-OTSPEC] lookup processing and 'chws', 'vchw'</p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText">> On Aug 19, 2020, at 13:43 , Peter Constable <<a href="mailto:pgcon6@msn.com"><span style="color:windowtext;text-decoration:none">pgcon6@msn.com</span></a>> wrote:<o:p></o:p></p>
<p class="MsoPlainText">> <o:p></o:p></p>
<p class="MsoPlainText">> I’d like to clarify something regarding my questions below. As the OTL feature tag registry was set up _as a registry_, I have taken that to mean that new feature tag requests may be subject to technical review for refinement but,
unless a requested tag is really not well formed or very obviously flawed, that it’s not subject to any kind of veto: a registered tag might be implemented only by the party that registered it, and the registry serves the intended purpose of allowing others
to create products that interop with that the registering party’s products that (presumably) support it.<o:p></o:p></p>
<p class="MsoPlainText">> <o:p></o:p></p>
<p class="MsoPlainText">> In other words, there’s no question in my mind that the ‘chws’ and ‘vchw’ tags should get added to the OT feature tag registry.<o:p></o:p></p>
<p class="MsoPlainText">> <o:p></o:p></p>
<p class="MsoPlainText">> But, as background information for general awareness, I would like to understand the status of implementations of these features. And if it does come to light that there are refinements that can or should be made in the feature descriptions,
then I’d like to see that discussed so that improvements in OT and OFF can get made.<o:p></o:p></p>
<p class="MsoPlainText">> <o:p></o:p></p>
<p class="MsoPlainText">> There’s also an additional question I’d like to ask: These features were registered jointly by Adobe and by W3C. I’d like to understand what, if anything, might be implied by W3C requesting this tag? Are there W3C specs that depend
on implementation of these features as described? Have browsers already implemented or are in process of implementing support for these features?<o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText">can you point me at the request, so I can try to help get an answer to the w3c question?<o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText">David Singer<o:p></o:p></p>
<p class="MsoPlainText">Manager, Software Standards, Apple Inc.<o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
</div>
</body>
</html>