<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:dt="uuid:C2F41010-65B3-11d1-A29F-00AA00C14882" 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:Wingdings;
panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
{font-family:"Angsana New";
panose-1:2 2 6 3 5 4 5 2 3 4;}
@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:blue;
text-decoration:underline;}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
{mso-style-priority:34;
margin-top:0in;
margin-right:0in;
margin-bottom:0in;
margin-left:.5in;
font-size:11.0pt;
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;}
/* List Definitions */
@list l0
{mso-list-id:1717385980;
mso-list-type:hybrid;
mso-list-template-ids:-1789341382 -157366444 67698691 67698693 67698689 67698691 67698693 67698689 67698691 67698693;}
@list l0:level1
{mso-level-start-at:3;
mso-level-number-format:bullet;
mso-level-text:-;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:"Calibri",sans-serif;
mso-fareast-font-family:Calibri;}
@list l0:level2
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:"Courier New";}
@list l0:level3
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Wingdings;}
@list l0:level4
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Symbol;}
@list l0:level5
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:"Courier New";}
@list l0:level6
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Wingdings;}
@list l0:level7
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Symbol;}
@list l0:level8
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:"Courier New";}
@list l0:level9
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Wingdings;}
ol
{margin-bottom:0in;}
ul
{margin-bottom:0in;}
--></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="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal">You can find lots of info regarding ISO policies here:<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><a href="https://www.iso.org/resources.html">https://www.iso.org/resources.html</a><o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">(Btw, as this list was created by an ISO technical body for purposes of its technical work, it’s my understanding that all applicable policies would apply to this list.)<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">For instance, wrt copyright, among other details:<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">“If you offer such content, you undertake to declare this to ISO or ISO/IEC, identify the name of the copyright holder and assist ISO or ISO/IEC in obtaining appropriate permission to i) share the content in the standards development process,
ii) to publish the content, or parts thereof, in original or modified form in ISO or ISO/IEC standards and iii) to exploit the content as part of an ISO or ISO/IEC standard according to ISO and IEC practice. If you or the organization you are representing
own/s the copyright in the content, such permission is implicitly granted to ISO or ISO/IEC, upon submission of the content to the standards development process.”<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Or regarding communication of committee work (which, in my understanding, would include this mail list*), among other details:<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">“[Externally shared] information shall not include details about the identity of the individuals or companies (including the names of the person, the company they work for, etc.)… shall not include information about how any NSB or committee
member voted… Committee and working group documents such as working documents, minutes, or working group recommendations shall not be shared externally… personal opinions… are clearly identified as personal opinions… do not convey the views or positions of
others… do not criticize the views or positions of others…”<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">*Based on stated ISO policies that I’m aware of, it’s a bit surprising that activity can happen on a publicly-archived email list unless<o:p></o:p></p>
<p class="MsoNormal">i) the (sub-)committee had sanctioned creation of a public list for committee work<o:p></o:p></p>
<p class="MsoNormal">ii) the subscription page explicitly calls out the general policy, calls out that the list is public, and implicit or explicit acknowledgement that one’s opinions will be made public (not true in this case)<o:p></o:p></p>
<p class="MsoNormal">iii) there is also a non-public forum in which experts that wish to can participate in discussion
<o:p></o:p></p>
<p class="MsoNormal">In this case, I assume (i) is true; (ii) is not true, though probably everyone here is aware that they are participating in a publicly archived list. And (iii) hasn’t really been necessary up to now because, up to now, nothing has been
brought _<i>into ISO processes</i>_ that has been of such a potentially-contentious nature as to require a non-public forum for open discussion among experts without needing to worry about unintended repercussions.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">And just to clarify: ISO principles are concerned about openness and transparency of _<i>outcomes</i>_, but chooses to protect views expressed by individuals during the process of arriving at those outcomes because that leads to more openness
among experts during the process. ISO is not the only standards-development organization that has such policies.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Note that the communication policy is relevant to patent discussions. I’ll get back to this below.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">As for ISO patent policies, there’s a link on that resources page, repeated here for convenience:<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><a href="https://www.iso.org/iso-standards-and-patents.html">https://www.iso.org/iso-standards-and-patents.html</a><o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Now, it appears that the details might only be available if have access to internal documents (e.g., if you were added because your NB nominated you as an expert to participate in a WG). Some of the high-level points are<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<ul style="margin-top:0in" type="disc">
<li class="MsoListParagraph" style="margin-left:0in;mso-list:l0 level1 lfo1">Participants should, as early as possible, “draw attention to” known patents that would be essential to implementation of a specification<o:p></o:p></li><li class="MsoListParagraph" style="margin-left:0in;mso-list:l0 level1 lfo1">Patent holders must submit a “Patent Statement and Licensing Declaration” form and agree to RAND licensing terms for any implementer in relation to essential patents; however, they
are not required to enumerate specific details regarding the patents.<o:p></o:p></li><li class="MsoListParagraph" style="margin-left:0in;mso-list:l0 level1 lfo1">In committee or WG discussions, “the Technical Bodies may not take position regarding the essentiality, scope, validity or specific licensing terms of any claimed Patents.” IOW (my
paraphrase), the tech nerds should not engage in legal discussions.<o:p></o:p></li><li class="MsoListParagraph" style="margin-left:0in;mso-list:l0 level1 lfo1">ISO maintains a database of declared patents but is not accountable for that being complete.<o:p></o:p></li></ul>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">For US participants in work of SC29, INCITS provides more public visibility into its patent policy, and other legal info:<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><a href="https://www.incits.org/standards-information/legal-info">https://www.incits.org/standards-information/legal-info</a><o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">It calls out things that are not to be discussed in meetings. Now, that doesn’t include discussion of specifics regarding patents. But here, I think there is an unwritten rule because anybody participating in an ISO technical body and who
works for a company with lawyers that are concerned with IP-related risks has (I would think) at some point been told by their employer, “Do not ever discuss patent claims—either ours or theirs—with anyone from another company.”<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Certainly early in my time at Microsoft (probably in the required “PM Bootcamp” training), I was told this, along with the elaboration that, if people from another company start discussing patents, ask them not to; and if they continue,
then _<i>immediately leave</i>_. The general issue here is, “We do not want you learning about any other company’s patents.”<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">And the reason for that has to do with penalties. In at least some jurisdictions—and certainly in the US—there are additional penalties if a company is found to be in violation of patent protections (i.e., implementing protected claims
without a license) _<i>and it is found that they were aware of the patents</i>_. In the US, prior knowledge of the patents results in automatic _<i>tripling</i>_ of financial penalties.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">For that reason, in an ISO (or INCITS or Unicode…) meeting, I would never say more than “I am aware of patents that may be essential for implementation of this specification,” since given any specifics may shut down discussion.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">On this list, if someone mentioned patent details in the course of some subject, I would anticipate that some would feel it necessary at a minimum to discontinue participating in or reading any messages in that thread (perhaps even immediately
deleting them from their mail). And if that happened repeatedly, I would anticipate people might unsubscribe from the list and, perhaps, insist on a more formal WG process in which details of discussions are not made public.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Consider the presence of a public archive in relation to a company’s concern about protection from patent suits: Suppose person A, even in a single message, mentions specifics about some patent. And suppose the public archive shows that
person B working for company X was a member of the list at that time. Even if person B had not read any message mentioning the patent details, the fact that they were receiving those messages from the list would likely be taken as material evidence that they
had prior knowledge of the patent, hence making company X liable for triple indemnity if found guilty in a legal suit.
<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Now, IANAL. But my understanding is that any discussion of any specific details regarding essential patents becomes a significant obstacle to technical discussion. It’s best to leave the patents to the lawyers.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Sorry this got long, but I hope it’s at least somewhat helpful.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Peter<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b>From:</b> Dave Crossland <dcrossland@google.com> <br>
<b>Sent:</b> Friday, August 21, 2020 9:21 PM<br>
<b>To:</b> Peter Constable <pgcon6@msn.com><br>
<b>Cc:</b> mpeg-otspec <mpeg-otspec@lists.aau.at><br>
<b>Subject:</b> Re: [MPEG-OTSPEC] MATH Encumbrance<o:p></o:p></p>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<p class="MsoNormal" style="margin-bottom:12.0pt"><o:p> </o:p></p>
<div>
<div>
<p class="MsoNormal">On Sat, Aug 22, 2020, 12:02 AM Peter Constable <<a href="mailto:pgcon6@msn.com">pgcon6@msn.com</a>> wrote:<o:p></o:p></p>
</div>
<blockquote style="border:none;border-left:solid #CCCCCC 1.0pt;padding:0in 0in 0in 6.0pt;margin-left:4.8pt;margin-right:0in">
<div>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">It’s best not to bring up specific patents in cross-company discussions since some companies have policies requiring employees to exit discussions if other parties mention any specifics
regarding patents. (Triple indemnity being a bit scary and all.)<o:p></o:p></p>
</div>
</div>
</blockquote>
</div>
</div>
<div>
<p class="MsoNormal">There are a lot of new people here, like myself, who have no idea about this kind of "unwritten rule," so I'm very grateful for your shedding light on this. <o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">Does "exit discussions" mean not posting on this thread, or this mailing list?<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<div>
<blockquote style="border:none;border-left:solid #CCCCCC 1.0pt;padding:0in 0in 0in 6.0pt;margin-left:4.8pt;margin-right:0in">
<div>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">I will say that I was a party in some patents in my time at MS that were filed solely for defensive purposes, never with any intent to charge licensing fees.<o:p></o:p></p>
</div>
</div>
</blockquote>
</div>
</div>
<div>
<p class="MsoNormal">Right, and my name is on some Google patents for font UI stuff, which I am fine with for the same reasons. <o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">But isn't the point of a formal standards body to get that intent turned into something in writing? And is that what OFF means? Or isn't it? <o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">Since the MATH table is in OFF, this seemed like a good case study for informing the future of 32 bit GIDs and so on that Li Renzhi just mentioned.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">But I'm happy to talk, without a specific existing case study, about hypotheticals. <o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<div>
<blockquote style="border:none;border-left:solid #CCCCCC 1.0pt;padding:0in 0in 0in 6.0pt;margin-left:4.8pt;margin-right:0in">
<div>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"> In the font space, I’d suggest that licensing fees could result in diverging formats and renewed font wars, which nobody wants. It’s not like video formats or something that takes
rocket science to eke out the next leap in performance. Nobody significantly benefits if fonts don’t just work everywhere.<o:p></o:p></p>
</div>
</div>
</blockquote>
</div>
</div>
<div>
<p class="MsoNormal">I certainly don't want renewed Font Wars, and that's why I'm raising this topic. <o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">In order to prevent it, I want to see a clear path forwards for fixing long-standing problems with OFF within the OFF development process... <o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">And I want to confirm that the OFF process does actually guarantee "just works everywhere," because it ensures patents don't require licensing as written policy. <o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"> <o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"> <o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"> <o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">Peter<o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"> <o:p></o:p></p>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><b>From:</b> Dave Crossland <<a href="mailto:dcrossland@google.com" target="_blank">dcrossland@google.com</a>>
<br>
<b>Sent:</b> Friday, August 21, 2020 8:09 PM<br>
<b>To:</b> Peter Constable <<a href="mailto:pgcon6@msn.com" target="_blank">pgcon6@msn.com</a>><br>
<b>Cc:</b> mpeg-otspec <<a href="mailto:mpeg-otspec@lists.aau.at" target="_blank">mpeg-otspec@lists.aau.at</a>><br>
<b>Subject:</b> Re: [MPEG-OTSPEC] MATH Encumbrance<o:p></o:p></p>
</div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"> <o:p></o:p></p>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">Is that because of a MPEG OFF patent policy applying to
<a href="https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fpatents.google.com%2Fpatent%2FUS7492366&data=02%7C01%7C%7C7c6b72474e5d4370297908d84652bf08%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637336668484634086&sdata=1HnKCddnRJw89dNzxZ2%2FehO%2FiqN6hDrvzpyx4poxVP0%3D&reserved=0" target="_blank">
https://patents.google.com/patent/US7492366</a> that means a license isn't required?<o:p></o:p></p>
</div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"> <o:p></o:p></p>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">On Fri, Aug 21, 2020, 9:29 PM Peter Constable <<a href="mailto:pgcon6@msn.com" target="_blank">pgcon6@msn.com</a>> wrote:<o:p></o:p></p>
</div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">I’m not aware of any such requirement.<o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"> <o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"> <o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">Peter<o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"> <o:p></o:p></p>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><b>From:</b> mpeg-otspec <<a href="mailto:mpeg-otspec-bounces@lists.aau.at" target="_blank">mpeg-otspec-bounces@lists.aau.at</a>>
<b>On Behalf Of </b>Dave Crossland<br>
<b>Sent:</b> Friday, August 21, 2020 5:51 PM<br>
<b>To:</b> mpeg-otspec <<a href="mailto:mpeg-otspec@lists.aau.at" target="_blank">mpeg-otspec@lists.aau.at</a>><br>
<b>Subject:</b> [MPEG-OTSPEC] MATH Encumbrance<o:p></o:p></p>
</div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"> <o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">Hi<o:p></o:p></p>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"> <o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">Does MATH table implementation require a license?<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"> <o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">Cheers<o:p></o:p></p>
</div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">Dave<o:p></o:p></p>
</div>
</body>
</html>