attachment
<html>
<head>
<meta name="generator" content="Windows Mail 17.5.9600.20911">
<style type="text/css"><!--html { font-family: "Color Emoji", "Calibri", "Segoe UI", "Meiryo", "Microsoft YaHei UI", "Microsoft JhengHei UI", "Malgun Gothic", "sans-serif"; }--></style><style data-externalstyle="true"><!--
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph {
margin-top:0in;
margin-right:0in;
margin-bottom:0in;
margin-left:.5in;
margin-bottom:.0001pt;
}
p.MsoNormal, li.MsoNormal, div.MsoNormal {
margin:0in;
margin-bottom:.0001pt;
}
p.MsoListParagraphCxSpFirst, li.MsoListParagraphCxSpFirst, div.MsoListParagraphCxSpFirst,
p.MsoListParagraphCxSpMiddle, li.MsoListParagraphCxSpMiddle, div.MsoListParagraphCxSpMiddle,
p.MsoListParagraphCxSpLast, li.MsoListParagraphCxSpLast, div.MsoListParagraphCxSpLast {
margin-top:0in;
margin-right:0in;
margin-bottom:0in;
margin-left:.5in;
margin-bottom:.0001pt;
line-height:115%;
}
--></style></head>
<body dir="ltr">
<div data-externalstyle="false" dir="ltr" style="font-family: 'Calibri', 'Segoe UI', 'Meiryo', 'Microsoft YaHei UI', 'Microsoft JhengHei UI', 'Malgun Gothic', 'sans-serif';font-size:12pt;"><div><font face="Times New Roman">
</font><p style="margin: 0in 0in 10pt;"><font face="Arial"> </font><font face="Arial">The term " Conditionally Required" or "Conditionally
Mandatory" has been used extensively, usually without a special
definition. In many cases, it was not defined as a specific compliance term,
but used in a context that included specifying the condition. For example, in Candidate
Standard 5102.1-2003, XHTML™-Print</font></p><font face="Times New Roman">
</font><p style="margin: 0in 0in 10pt 0.5in;"><font face="Arial">"Support for Inline Image Data
is conditionally mandatory; i.e. any device supporting Inline Image Data shall
support this method."</font></p><font face="Times New Roman">
</font><p style="margin: 0in 0in 10pt;"><font face="Arial">It was defined under compliance terminology in Candidate
Standard 5100.6-2003 - Standard for The Internet Printing Protocol (IPP): Page
Overrides and in Candidate Standard 5100.5-2003, Standard for The Internet
Printing Protocol (IPP): Document Object</font></p><font face="Times New Roman">
</font><p style="margin: 0in 0in 10pt 0.5in;"><font face="Arial"><span style="mso-fareast-font-family: Calibri; mso-bidi-font-weight: bold; mso-bidi-font-style: italic;">"The term </span><b><span style="mso-fareast-font-family: Calibri;">CONDITIONALLY REQUIRED</span></b><span style="mso-fareast-font-family: Calibri;"> means that the Printer <b>MUST</b>
support the feature, if the specified condition is true."</span></font></p><font face="Times New Roman">
</font><p style="margin: 0in 0in 10pt;"><font face="Arial"><span style="line-height: 115%; mso-bidi-font-size: 14.0pt;">The
term was defined in a way similar to the current definition in </span><span style="line-height: 115%; mso-fareast-font-family: Calibri; mso-bidi-font-size: 14.0pt;">Candidate
Standard 5110.1-2014</span><span style="line-height: 115%; mso-bidi-font-size: 14.0pt;">, </span><span style="mso-fareast-font-family: Calibri;">PWG Hardcopy
Device Health Assessment Attributes</span>.</font></p><font face="Times New Roman">
</font><p style="margin: 0in 0in 10pt 0.5in;"><font face="Arial">"<span style="mso-fareast-font-family: Calibri;">The term CONDITIONALLY REQUIRED is additionally defined for a
conformance requirement that applies to a particular capability or feature</span>."</font></p><font face="Times New Roman">
</font><p style="margin: 0in 0in 10pt;"><font face="Arial">Although this definition was clarified in the section of the
text dealing with conditionally mandatory elements by:</font></p><font face="Times New Roman">
</font><p style="margin: 0in 0in 10pt 0.5in;"><font face="Arial">"<span style="mso-fareast-font-family: Calibri;">HCDs MUST support the attributes in this section if the particular
capability, as described before each attribute, is implemented on the HCD.</span>"</font></p><font face="Times New Roman">
</font><p style="margin: 0in 0in 10pt;"><font face="Arial">I am unhappy with "... <span style="mso-fareast-font-family: Calibri;">conformance requirement that applies to a particular capability or
feature</span>." as a general statement because:</font></p><font face="Times New Roman">
</font><p style="margin: 0in 0in 10pt 0.5in;"><font face="Arial"><span style="mso-tab-count: 1;"> </span>a.
Most conformance requirements apply to a particular capability or feature. I
assume that one is to infer that the requirement applies only if that
capability or feature exists in the subject implementation seeking to be
conformant.</font></p><font face="Times New Roman">
</font><p style="margin: 0in 0in 10pt 0.5in;"><font face="Arial"><span style="mso-tab-count: 1;"> </span>b.
A requirement is conditional to an implementation because the implementation includes
a <span style="mso-fareast-font-family: Calibri;">particular capability or
feature</span>, but is not necessarily a requirement of the <span style="mso-fareast-font-family: Calibri;">capability or feature</span> itself,
which is suggested by "applies to".</font></p><font face="Times New Roman">
</font><p style="margin: 0in 0in 10pt 0.5in;"><font face="Arial"><span style="mso-tab-count: 1;"> </span>c.
In a general sense, the condition may not be the inclusion of a feature or
capability. Conceivably, the condition may be how or where the implementation
is used or when it was created.</font></p><font face="Times New Roman">
</font><p style="margin: 0in 0in 10pt;"><font face="Arial">There is there is the additional question as to whether the
term should 'Conditionally Required" or "Conditionally
Mandatory". Since the basic compliance term is "Required", "Conditionally
Required" seems more appropriate.</font></p><font face="Times New Roman">
</font><p style="margin: 0in 0in 10pt;"><font face="Arial">A reasonable variation on the 2003 definition and the
RFC2119 definition of requirement levels is :</font></p><font face="Times New Roman">
</font><p style="margin: 0in 0in 10pt 0.5in;"><font face="Arial"><i style="mso-bidi-font-style: normal;">CONDITIONALLY
REQUIRED</i>: definition is a requirement of the specification if the specified
condition is true.</font></p><font face="Times New Roman">
</font><p style="margin: 0in 0in 10pt;"><font face="Arial">One might prefer a term other than "definition",
such as capability or feature, and consider a requirement of the implementation
rather than of the specification, but RFC 2119 wording <span style="mso-spacerun: yes;"> </span>is:" <span style="mso-spacerun: yes;">… </span>definition is an absolute requirement of the
specification."</font></p><font face="Times New Roman">
</font><p style="margin: 0in 0in 10pt;"><font face="Arial">Alternatively, we could modify the current definition to:</font></p><font face="Times New Roman">
</font><p style="margin: 0in 0in 10pt 0.5in;"><font face="Arial"><i style="mso-bidi-font-style: normal;">CONDITIONALLY
REQUIRED</i>: A conformance requirement that applies if the specified condition
is true.</font></p><p style="margin: 0in 0in 10pt 0.5in;"><br></p><p style="margin: 0in 0in 10pt 0.5in;"><font face="Arial">Bill Wagner</font></p><font face="Times New Roman">
</font><br></div></div>
</body>
</html>