attachment-0001
<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:x="urn:schemas-microsoft-com:office:excel" xmlns:p="urn:schemas-microsoft-com:office:powerpoint" xmlns:a="urn:schemas-microsoft-com:office:access" xmlns:dt="uuid:C2F41010-65B3-11d1-A29F-00AA00C14882" xmlns:s="uuid:BDC6E3F0-6DA3-11d1-A2A3-00AA00C14882" xmlns:rs="urn:schemas-microsoft-com:rowset" xmlns:z="#RowsetSchema" xmlns:b="urn:schemas-microsoft-com:office:publisher" xmlns:ss="urn:schemas-microsoft-com:office:spreadsheet" xmlns:c="urn:schemas-microsoft-com:office:component:spreadsheet" xmlns:odc="urn:schemas-microsoft-com:office:odc" xmlns:oa="urn:schemas-microsoft-com:office:activation" xmlns:html="http://www.w3.org/TR/REC-html40" xmlns:q="http://schemas.xmlsoap.org/soap/envelope/" xmlns:rtc="http://microsoft.com/officenet/conferencing" xmlns:D="DAV:" xmlns:Repl="http://schemas.microsoft.com/repl/" xmlns:mt="http://schemas.microsoft.com/sharepoint/soap/meetings/" xmlns:x2="http://schemas.microsoft.com/office/excel/2003/xml" xmlns:ppda="http://www.passport.com/NameSpace.xsd" xmlns:ois="http://schemas.microsoft.com/sharepoint/soap/ois/" xmlns:dir="http://schemas.microsoft.com/sharepoint/soap/directory/" xmlns:ds="http://www.w3.org/2000/09/xmldsig#" xmlns:dsp="http://schemas.microsoft.com/sharepoint/dsp" xmlns:udc="http://schemas.microsoft.com/data/udc" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:sub="http://schemas.microsoft.com/sharepoint/soap/2002/1/alerts/" xmlns:ec="http://www.w3.org/2001/04/xmlenc#" xmlns:sp="http://schemas.microsoft.com/sharepoint/" xmlns:sps="http://schemas.microsoft.com/sharepoint/soap/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:udcs="http://schemas.microsoft.com/data/udc/soap" xmlns:udcxf="http://schemas.microsoft.com/data/udc/xmlfile" xmlns:udcp2p="http://schemas.microsoft.com/data/udc/parttopart" xmlns:wf="http://schemas.microsoft.com/sharepoint/soap/workflow/" xmlns:dsss="http://schemas.microsoft.com/office/2006/digsig-setup" xmlns:dssi="http://schemas.microsoft.com/office/2006/digsig" xmlns:mdssi="http://schemas.openxmlformats.org/package/2006/digital-signature" xmlns:mver="http://schemas.openxmlformats.org/markup-compatibility/2006" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns:mrels="http://schemas.openxmlformats.org/package/2006/relationships" xmlns:spwp="http://microsoft.com/sharepoint/webpartpages" xmlns:ex12t="http://schemas.microsoft.com/exchange/services/2006/types" xmlns:ex12m="http://schemas.microsoft.com/exchange/services/2006/messages" xmlns:pptsl="http://schemas.microsoft.com/sharepoint/soap/SlideLibrary/" xmlns:spsl="http://microsoft.com/webservices/SharePointPortalServer/PublishedLinksService" xmlns:Z="urn:schemas-microsoft-com:" xmlns:st="" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=Content-Type content="text/html; charset=us-ascii">
<meta name=Generator content="Microsoft Word 12 (filtered medium)">
<!--[if !mso]>
<style>
v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style>
<![endif]-->
<style>
<!--
/* Font Definitions */
@font-face
{font-family:Wingdings;
panose-1:5 0 0 0 0 0 0 0 0 0;}
@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;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
{font-family:Impact;
panose-1:2 11 8 6 3 9 2 5 2 4;}
@font-face
{font-family:Consolas;
panose-1:2 11 6 9 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-serif";}
h1
{mso-style-priority:9;
mso-style-link:"Heading 1 Char";
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:24.0pt;
font-family:"Times New Roman","serif";}
h2
{mso-style-priority:9;
mso-style-link:"Heading 2 Char";
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:18.0pt;
font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
pre
{mso-style-priority:99;
mso-style-link:"HTML Preformatted Char";
margin:0in;
margin-bottom:.0001pt;
font-size:10.0pt;
font-family:"Courier New";}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
{mso-style-priority:34;
margin-top:0in;
margin-right:0in;
margin-bottom:0in;
margin-left:.5in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-serif";}
span.Heading1Char
{mso-style-name:"Heading 1 Char";
mso-style-priority:9;
mso-style-link:"Heading 1";
font-family:"Cambria","serif";
color:#365F91;
font-weight:bold;}
span.Heading2Char
{mso-style-name:"Heading 2 Char";
mso-style-priority:9;
mso-style-link:"Heading 2";
font-family:"Cambria","serif";
color:#4F81BD;
font-weight:bold;}
span.HTMLPreformattedChar
{mso-style-name:"HTML Preformatted Char";
mso-style-priority:99;
mso-style-link:"HTML Preformatted";
font-family:Consolas;}
span.htmlpreformattedchar0
{mso-style-name:htmlpreformattedchar;
mso-style-priority:99;
font-family:"Courier New";}
span.EmailStyle23
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:windowtext;}
span.EmailStyle24
{mso-style-type:personal;
font-family:"Arial","sans-serif";
color:navy;
font-weight:normal;
font-style:normal;
text-decoration:none none;}
span.EmailStyle25
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@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:661157284;
mso-list-type:hybrid;
mso-list-template-ids:2030846620 67698703 67698713 67698715 67698703 67698713 67698715 67698703 67698713 67698715;}
@list l0:level1
{mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l1
{mso-list-id:1805267680;
mso-list-type:hybrid;
mso-list-template-ids:-1301748966 67698705 67698713 67698715 67698703 67698713 67698715 67698703 67698713 67698715;}
@list l1:level1
{mso-level-text:"%1\)";
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l1:level2
{mso-level-tab-stop:1.0in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l1:level3
{mso-level-tab-stop:1.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l1:level4
{mso-level-tab-stop:2.0in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l1:level5
{mso-level-tab-stop:2.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l1:level6
{mso-level-tab-stop:3.0in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l1:level7
{mso-level-tab-stop:3.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l1:level8
{mso-level-tab-stop:4.0in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l1:level9
{mso-level-tab-stop:4.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l2
{mso-list-id:2145810426;
mso-list-type:hybrid;
mso-list-template-ids:-1301748966 67698705 67698713 67698715 67698703 67698713 67698715 67698703 67698713 67698715;}
@list l2:level1
{mso-level-text:"%1\)";
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l2:level2
{mso-level-tab-stop:1.0in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l2:level3
{mso-level-tab-stop:1.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l2:level4
{mso-level-tab-stop:2.0in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l2:level5
{mso-level-tab-stop:2.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l2:level6
{mso-level-tab-stop:3.0in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l2:level7
{mso-level-tab-stop:3.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l2:level8
{mso-level-tab-stop:4.0in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l2:level9
{mso-level-tab-stop:4.5in;
mso-level-number-position:left;
text-indent:-.25in;}
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><span style='color:#1F497D'>My comments are inline
below<o:p></o:p></span></p>
<p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p>
<div>
<p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-family:"Impact","sans-serif";color:navy'>Peter
Zehler</span><span style='color:#1F497D'><br>
<br>
</span><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif";
color:navy'>Xerox Research Center Webster<br>
</span><span style='font-size:10.0pt;font-family:"Arial","sans-serif";
color:navy'>Email: <a href="mailto:Peter.Zehler@Xerox.com">Peter.Zehler@Xerox.com</a></span><span
style='color:#1F497D'><br>
</span><span style='font-size:10.0pt;font-family:"Arial","sans-serif";
color:navy'>Voice: (585) 265-8755</span><span style='color:#1F497D'><br>
</span><span style='font-size:10.0pt;font-family:"Arial","sans-serif";
color:navy'>FAX: (585) 265-7441</span><span style='color:#1F497D'><br>
</span><span style='font-size:10.0pt;font-family:"Arial","sans-serif";
color:navy'>US Mail: Peter Zehler</span><span style='color:#1F497D'><br>
</span><span style='font-size:10.0pt;font-family:"Arial","sans-serif";
color:navy'>Xerox Corp.</span><span style='color:#1F497D'><br>
</span><span style='font-size:10.0pt;font-family:"Arial","sans-serif";
color:navy'>800 Phillips Rd.</span><span style='color:#1F497D'><br>
</span><span style='font-size:10.0pt;font-family:"Arial","sans-serif";
color:navy'>M/S 128-25E</span><span style='color:#1F497D'><br>
</span><span style='font-size:10.0pt;font-family:"Arial","sans-serif";
color:navy'>Webster NY, 14580-9701</span><span style='color:#1F497D'> </span><span
style='font-size:12.0pt;font-family:"Times New Roman","serif";color:#1F497D'><o:p></o:p></span></p>
</div>
<p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p>
<div>
<div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in'>
<p class=MsoNormal><b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span></b><span
style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'> Tom Hastings
[mailto:tom.hastings@verizon.net] <br>
<b>Sent:</b> Monday, July 26, 2010 1:11 AM<br>
<b>To:</b> Zehler, Peter; ipp@pwg.org; mfd@pwg.org; cloud@pwg.org<br>
<b>Subject:</b> RE: [IPP] Attributes needed for Cloud Printing and definition
inconsistencies [4 questions about the representation of the values]<o:p></o:p></span></p>
</div>
</div>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif";
color:blue'>Pete,<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif";
color:blue'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif";
color:blue'>I have 4 questions about your proposed IPP attributes for Geo
Location for Cloud Printing:<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif";
color:blue'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif";
color:blue'>1.</span><span style='font-size:10.0pt;font-family:"Arial","sans-serif";
color:#1F497D'> </span><span style='font-size:10.0pt;font-family:"Arial","sans-serif";
color:blue'>The representation of the values of your proposed IPP “</span><span
style='color:blue'>size</span><span style='font-size:10.0pt;font-family:"Arial","sans-serif";
color:blue'>”, “</span><span style='color:blue'>horizontal-precision”,
and “vertical-precision” </span><span style='font-size:10.0pt;
font-family:"Arial","sans-serif";color:blue'>attributes are completely
different from the representation of the same attributes in RFC1876.<o:p></o:p></span></p>
<p class=MsoNormal><b><PZ>I made a mistake in my values. I used 8
bit unsigned integers instead of 4 bit. The values should be; Size= 18 (0x12),
HorizontalPrecision=34 (0x22), VerticalPrecision=34 (0x22). (This is why
I really don’t like this representation. That and the fact that for
the dimensions associated with MFDs it is not as precise a expressing it in simple
centimeters)</PZ><o:p></o:p></b></p>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif";
color:blue'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif";
color:blue'>If this difference is intentional, it would be good to explain the
difference and why and to indicate this intended difference in the spec?<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif";
color:blue'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif";
color:blue'>As I read RFC 1876, the representation of the SIZE, HORIZ PRE, and
VERT PRE attributes are all using this funny SIZE representation as a pair of
four-bit unsigned integers, where the most significant 4-bit unsigned integer
represents the base and the second 4-bit integer represents the power of 10 by
which to multiple the base, sort of a compressed floating point representation,
but using power of 10, not power of 2. The reason give in RFC 1876 is so
that the value is more easily human readable. HORIZ PRE and VERT PRE attributes
defined in RFC 1876, say:<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif";
color:navy'><o:p> </o:p></span></p>
<pre style='margin-left:.5in'>expressed using the same representation as SIZE<o:p></o:p></pre>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif";
color:blue'>i.e., using this same 8-bit “floating point”
representation.<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif";
color:navy'><o:p> </o:p></span></p>
<pre><span style='font-family:"Arial","sans-serif";color:blue'>BTW, the VERT PRE attribute has an ironic Freudian slip typo in RFC 1876, since I don’t find this representation very sane </span><span
style='font-family:Wingdings;color:blue'>L</span><span style='font-family:"Arial","sans-serif";
color:blue'>:<o:p></o:p></span></pre><pre style='margin-left:.5in'>expressed using the <span
style='background:yellow'>sane</span> representation as for SIZE<o:p></o:p></pre>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif";
color:navy'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif";
color:navy'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif";
color:blue'>2. The definitions on the </span><span style='color:blue'><<a
href="http://pwg-wiki.wikispaces.com/Geolocation">http://pwg-wiki.wikispaces.com/Geolocation</a>>
appear to be part of the PWG Semantic Model:<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:12.0pt;font-family:"Times New Roman","serif"'><o:p> </o:p></span></p>
<p class=MsoNormal style='margin-left:.5in'><span style='font-size:12.0pt;
font-family:"Times New Roman","serif"'>This page proposes an IPP collection
representing the DNS LOC data defined in <a
href="http://www.rfc-editor.org/rfc/rfc1876.txt">RFC 1876</a> .<br>
</span><a name="printer-geo-location_(collection)"></a><b><span
style='font-size:24.0pt;font-family:"Times New Roman","serif"'>printer-geo-location
(collection)</span></b><span style='font-size:12.0pt;font-family:"Times New Roman","serif"'><br>
The "printer-geo-location" attribute provides the physical location
of the printer. The collection has the following member attributes.<br>
</span><a name="printer-geo-location_(collection)-size_("></a><b><span
style='font-size:18.0pt;font-family:"Times New Roman","serif"'>size (integer
(0:MAX))</span></b><b><span style='font-size:24.0pt;font-family:"Times New Roman","serif"'><o:p></o:p></span></b></p>
<p class=MsoNormal style='margin-left:.5in'><span style='font-size:12.0pt;
font-family:"Times New Roman","serif"'>Diameter of enclosing sphere for printer
in centimeters. 0 represents any size less than one centimeter.<br>
</span><a name="printer-geo-location_(collection)-horizo"></a><b><span
style='font-size:18.0pt;font-family:"Times New Roman","serif"'>horizontal-precision
(integer (0:MAX))<o:p></o:p></span></b></p>
<p class=MsoNormal style='margin-left:.5in'><span style='font-size:12.0pt;
font-family:"Times New Roman","serif"'>The circle of error of the latitude and
longitude measurement in centimeters. 0 represents an error of less than one
centimeter.<br>
</span><a name="printer-geo-location_(collection)-vertic"></a><b><span
style='font-size:18.0pt;font-family:"Times New Roman","serif"'>vertical-precision
(integer(0:MAX))<o:p></o:p></span></b></p>
<p class=MsoNormal style='margin-left:.5in'><span style='font-size:12.0pt;
font-family:"Times New Roman","serif"'>The circle of error of the altitude
measurement in centimeters. 0 represents an error of less than one centimeter.<br>
</span><a name="printer-geo-location_(collection)-latitu"></a><b><span
style='font-size:18.0pt;font-family:"Times New Roman","serif"'>latitude
(integer(-324000000:324000000))<o:p></o:p></span></b></p>
<p class=MsoNormal style='margin-left:.5in'><span style='font-size:12.0pt;
font-family:"Times New Roman","serif"'>The latitude in thousandths of arc
seconds from the equator. 0 represents the equator, positive values represent
locations North of the equator, and negative values represent locations South
of the equator.<br>
</span><a name="printer-geo-location_(collection)-longit"></a><b><span
style='font-size:18.0pt;font-family:"Times New Roman","serif"'>longitude
(integer(-648000000:648000000))<o:p></o:p></span></b></p>
<p class=MsoNormal style='margin-left:.5in'><span style='font-size:12.0pt;
font-family:"Times New Roman","serif"'>The longitude in thousandths of arc
seconds from the prime meridian. 0 represents the prime meridian, positive
values represent locations East of the meridian, and negative values represent
locations West of the meridian.<br>
</span><a name="printer-geo-location_(collection)-altitu"></a><b><span
style='font-size:18.0pt;font-family:"Times New Roman","serif"'>altitude
(integer(-100000:MAX))<o:p></o:p></span></b></p>
<p class=MsoNormal style='margin-left:.5in'><span style='font-size:12.0pt;
font-family:"Times New Roman","serif"'>The distance in centimeters from the
WGS-84 ellipsoid to the center of the enclosing sphere defined by the
"side" member attribute. 0 represents the WGS-84 ellipsoid height,
positive values represent locations above the ellipsoid, and negative values represent
locations below the ellipsoid. <o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif";
color:navy'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif";
color:navy'>The PWG SM definitions appear to use signed 32-bit integer notation
and description which have the same bit representation as the unsigned 32-bit
integer notation and description in RFC 1876, right? Why change to use
the unsigned integer notation and descriptions, when the rest of the SM and IPP
use signed integer notations and descriptions?<o:p></o:p></span></p>
<p class=MsoNormal><b><PZ>To the best of my knowledge printer-geo-location
is not part of the PWG semantic model yet. I put out this mail note to
test my understanding of the proposal on the wiki site. I want to be sure
the semantics and syntax are well defined and the mapping to rfc1876 is
clear.</PZ><o:p></o:p></b></p>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif";
color:navy'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif";
color:navy'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif";
color:navy'>3. What is the relationship between Cloud Printing (which these
definitions are proposed for) and IPP Everywhere?<o:p></o:p></span></p>
<p class=MsoNormal><b><PZ>Cloud Printing can be implemented without IPP
Everywhere. The initial implementations will not be using IPP or IPP
Everywhere. It will be cobbled together with existing technologies used
in Web Services, messaging protocols, standard document formats and print
driver related technologies. IPP could play a role in this environment
but I believe it is most critical to obtain semantic alignment between IPP and
the emerging Cloud Printing technologies. IPP Everywhere addresses a
number of IPP shortcomings such as printer discovery, common document formats,
and interoperable security. IPP Everywhere could apply to Cloud Printing
but would require some extensions to accommodate intervening firewalls.</PZ><o:p></o:p></b></p>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif";
color:navy'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif";
color:navy'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif";
color:navy'>4. I like the idea used in IPP and the SM to have the data type
indicate the range of values in the definition of the attribute name and
attribute syntax, i.e., latitude (integer(-324000000:324000000)). Why
isn’t this technique of specifying the data type and the data type range
used in your proposal for attributes needed for Cloud Printing?<o:p></o:p></span></p>
<p class=MsoNormal><span style='color:#1F497D'><PZ>Added to definitions
below.</PZ><o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif";
color:navy'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif";
color:navy'>Tom<o:p></o:p></span></p>
<div>
<div class=MsoNormal align=center style='text-align:center'><span
style='font-size:12.0pt;font-family:"Times New Roman","serif"'>
<hr size=2 width="100%" align=center>
</span></div>
<p class=MsoNormal><b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span></b><span
style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'> ipp-bounces@pwg.org
[mailto:ipp-bounces@pwg.org] <b>On Behalf Of </b>Zehler, Peter<br>
<b>Sent:</b> Thursday, July 22, 2010 11:48<br>
<b>To:</b> ipp@pwg.org; mfd@pwg.org<br>
<b>Subject:</b> [IPP] Attributes needed for Cloud Printing and definition
inconsistencies</span><span style='font-size:12.0pt;font-family:"Times New Roman","serif"'><o:p></o:p></span></p>
</div>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal><b><span style='font-size:16.0pt'>Job Identifiers:<o:p></o:p></span></b></p>
<p class=MsoNormal>*<b>existing</b>*<o:p></o:p></p>
<p class=MsoNormal>job-id (SM: JobId): The identifier for a job with a local
scope. That is the ID is unique within the service. The ID may be
reused in other instance of a Printer (i.e. Print Service) or for jobs in
other types of services (e.g. Copy Service). Datatype: abstract:int32,
IPP:integer, SM:xs:int<o:p></o:p></p>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal>*<b>new</b>*<o:p></o:p></p>
<p class=MsoNormal>job-uuid (SM:JobUuid): The identifier for a job with a
global scope. The identifier is unique for a Job across all service
instances of any service type. The UUID URN namespace is
specified in rfc4122. The format used for “job-uuid” is the
string representation of a UUID as a URN. An example is “<span
style='color:#2E2C2C'>urn:uuid:a6b90f34-d0b1-1956 -7dec-009c4386fe3</span>”.
The version (aka subtype) used is implementation specific. Version 1
(i.e. time based) is recommended. Datatype: abstract:char[64],
IPP:uri MaxLength=64, SM:xs:anyURI maxLen=64<o:p></o:p></p>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal>Note: I do not believe the IPP attribute
“job-uri” is applicable as a globally unique identifier.<o:p></o:p></p>
<p class=MsoListParagraph style='text-indent:-.25in;mso-list:l2 level1 lfo2'><![if !supportLists]><span
style='mso-list:Ignore'>1)<span style='font:7.0pt "Times New Roman"'>
</span></span><![endif]>RFC2911 states “Since every URL is a specialized
form of a URI, even though the more generic term URI is used throughout the
rest of this document, its usage is intended to cover the more specific notion
of URL as well.”. All uses of the uri syntax is really a URL
syntax.<o:p></o:p></p>
<p class=MsoListParagraph style='text-indent:-.25in;mso-list:l2 level1 lfo2'><![if !supportLists]><span
style='mso-list:Ignore'>2)<span style='font:7.0pt "Times New Roman"'>
</span></span><![endif]>URL implies not only a specific protocol binding but
also a location.<o:p></o:p></p>
<p class=MsoListParagraph style='text-indent:-.25in;mso-list:l2 level1 lfo2'><![if !supportLists]><span
style='mso-list:Ignore'>3)<span style='font:7.0pt "Times New Roman"'>
</span></span><![endif]>Locations can be specified using an IP address that
need not be locally unique (e.g. 192.168.1.1, localhost) <o:p></o:p></p>
<p class=MsoListParagraph style='text-indent:-.25in;mso-list:l2 level1 lfo2'><![if !supportLists]><span
style='mso-list:Ignore'>4)<span style='font:7.0pt "Times New Roman"'>
</span></span><![endif]>Regarding the “job-uri” RFC2911 further
states that “This URI is then used by clients as the target for
subsequent Job operations.”. The globally unique identifier for a
job should not specify a transport endpoint for a specific
protocol. <o:p></o:p></p>
<p class=MsoListParagraph style='text-indent:-.25in;mso-list:l2 level1 lfo2'><![if !supportLists]><span
style='mso-list:Ignore'>5)<span style='font:7.0pt "Times New Roman"'>
</span></span><![endif]>The globally unique identifier for a Job, Printer or
Service should be a URN. It should be protocol independent so that a
product that supports multiple protocols should have the same identifiers
regardless of the protocol mapping.<o:p></o:p></p>
<p class=MsoListParagraph style='text-indent:-.25in;mso-list:l2 level1 lfo2'><![if !supportLists]><span
style='mso-list:Ignore'>6)<span style='font:7.0pt "Times New Roman"'>
</span></span><![endif]>The globally unique identifier for a Job, Printer
or Service should require no central authority to administrate them.
Generation of a unique identifier should be simple from an administrative point
of view and preferably automated.<o:p></o:p></p>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal>Note: Both the local and global identifiers should be
mandated. For legacy protocol mappings (e.g. IPP 1.1, WS-Print, LPR) the
local identifier MUST still be maintained. It is possible to use the
time_low portion of the Timestamp in the version 1 UUID as the local
identifier. The implementation may then keep only the 128 bit local
representation of the UUID and use it to create the appropriate protocol
values.<o:p></o:p></p>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal><b><span style='font-size:16.0pt'>Printer Identifiers:<o:p></o:p></span></b></p>
<p class=MsoNormal>*<b>existing (Service Monitoring MIB)*</b><o:p></o:p></p>
<p class=MsoNormal>applIndex (SM: <service>Id i.e. PrinterId): The
service identifier with a local scope. That is the ID is unique across
the service instances collocated on a host. Datatype: abstract:int32,
MIB:integer, SM:xs:int<o:p></o:p></p>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal>*<b>new</b>*<o:p></o:p></p>
<p class=MsoNormal>printer-uuid (SM:ServiceUuid): The identifier for a
Printer with a global scope. The identifier is unique across all service
instances of any service type. The UUID URN namespace is
specified in rfc4122. The format used for “job-uuid” is the
string representation of a UUID as a URN. An example is “<span
style='color:#2E2C2C'>urn:uuid:a6b90f34-d0b1-1956 -7dec-009c4386fe3</span>”.
The version (aka subtype) used is implementation specific. Version 1
(i.e. time based) is recommended. Datatype: abstract:char[64],
IPP:uri, SM:xs:anyURI maxLen=64<o:p></o:p></p>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal>Note: I do not believe the IPP attribute
“printer-uri” is applicable as a globally unique identifier. <o:p></o:p></p>
<p class=MsoListParagraph style='text-indent:-.25in;mso-list:l1 level1 lfo4'><![if !supportLists]><span
style='mso-list:Ignore'>1)<span style='font:7.0pt "Times New Roman"'>
</span></span><![endif]>RFC2911 states “Since every URL is a specialized
form of a URI, even though the more generic term URI is used throughout the
rest of this document, its usage is intended to cover the more specific notion
of URL as well.”. All uses of the uri syntax is really a URL
syntax.<o:p></o:p></p>
<p class=MsoListParagraph style='text-indent:-.25in;mso-list:l1 level1 lfo4'><![if !supportLists]><span
style='mso-list:Ignore'>2)<span style='font:7.0pt "Times New Roman"'>
</span></span><![endif]>URL implies not only a specific protocol binding but
also a location.<o:p></o:p></p>
<p class=MsoListParagraph style='text-indent:-.25in;mso-list:l1 level1 lfo4'><![if !supportLists]><span
style='mso-list:Ignore'>3)<span style='font:7.0pt "Times New Roman"'>
</span></span><![endif]>Locations can be specified using an IP address that
need not be locally unique (e.g. 192.168.1.1, localhost) <o:p></o:p></p>
<p class=MsoListParagraph style='text-indent:-.25in;mso-list:l1 level1 lfo4'><![if !supportLists]><span
style='mso-list:Ignore'>4)<span style='font:7.0pt "Times New Roman"'>
</span></span><![endif]>The printer may have multiple “printer-uri”
values as enumerated in the “printer-uris-supported”
attribute. There should be only a single identifier for a printer.<o:p></o:p></p>
<p class=MsoListParagraph style='text-indent:-.25in;mso-list:l1 level1 lfo4'><![if !supportLists]><span
style='mso-list:Ignore'>5)<span style='font:7.0pt "Times New Roman"'>
</span></span><![endif]>The globally unique identifier for a Job, Printer or
Service should be a URN. It should be protocol independent so that a
product that supports multiple protocols should have the same identifiers
regardless of the protocol mapping.<o:p></o:p></p>
<p class=MsoListParagraph style='text-indent:-.25in;mso-list:l1 level1 lfo4'><![if !supportLists]><span
style='mso-list:Ignore'>6)<span style='font:7.0pt "Times New Roman"'>
</span></span><![endif]>The globally unique identifier for a Job, Printer
or Service should require no central authority to administrate them.
Generation of a unique identifier should be simple from an administrative point
of view and preferably automated.<o:p></o:p></p>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal>Note: The local instance id in the MIB and SM are artifacts
of the model’s data binding and are insufficient for use as an
identifier. IPP’s printer-uri, the URL for Web Service bindings
(e.g. WS-Print) and the IP address for legacy protocols such as LPR and Port
9100 are also insufficient. They need not be globally unique.
Nonroutable IP addresses may be used. <o:p></o:p></p>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal><b><span style='font-size:16.0pt'>Printer Location:<o:p></o:p></span></b></p>
<p class=MsoNormal>*<b>existing*</b><o:p></o:p></p>
<p class=MsoNormal>printer-location (SM: ServiceLocation): Identifies the
location of the device that this Printer represents. (Example:
Pete’s Office) This is helpful for a human but is pretty much
useless for geolocation since the content is implementation specific.
Datatype: abstract:char[127], IPP:string MaxLength=127, SM:xs:int<o:p></o:p></p>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal>*<b>new</b>*<o:p></o:p></p>
<p class=MsoNormal>printer-geo-location (SM:ServiceGeoLocation): This
identifies the location of the associated device using the World Geodetic
System 1984(WGS84). The means for expressing the location information is
the same as used in DNS (rfc1876) Datatype: abstract:class,
IPP:collection, SM:sequence<o:p></o:p></p>
<p class=MsoNormal style='margin-left:.5in'><o:p> </o:p></p>
<p class=MsoNormal style='margin-left:.5in'>*<b>new</b>*<span style='color:
#1F497D'>(modified)</span><o:p></o:p></p>
<p class=MsoNormal style='margin-left:.5in'>size (SM:Size)<span
style='color:#1F497D'> (0x00 to 0x99)</span>: Diameter of the bounding
sphere containing the device expressed in centimeters.
Datatype: abstract: int32, IPP:integer, SM:xs:int<span
style='color:#1F497D'> (Note: representation is 2 encoded 4 bit integers(0-9).
Most significant represents the base and the least significant represents the
power of 10.) </span><o:p></o:p></p>
<p class=MsoNormal style='margin-left:.5in'><o:p> </o:p></p>
<p class=MsoNormal style='margin-left:.5in'>*<b>new</b>*<span style='color:
#1F497D'>(modified)</span><o:p></o:p></p>
<p class=MsoNormal style='margin-left:.5in'>horizontal-precision (SM:
HorizontalPrecision)<span style='color:#1F497D'> (0x00 to 0x99)</span>:
The horizontal precision expressed as the diameter of the “circle of
error” (i.e. twice the +- error value) The units are
centimeters. Datatype: abstract: int32, IPP:integer,
SM:xs:int<span style='color:#1F497D'>(Note: representation is 2 encoded 4 bit
integers(0-9). Most significant represents the base and the least
significant represents the power of 10.) </span><o:p></o:p></p>
<p class=MsoNormal style='margin-left:.5in'><o:p> </o:p></p>
<p class=MsoNormal style='margin-left:.5in'>*<b>new</b>*<span style='color:
#1F497D'>(modified)</span><o:p></o:p></p>
<p class=MsoNormal style='margin-left:.5in'>vertical-precision (SM:
VerticalPrecision)<span style='color:#1F497D'> (0x00 to 0x99)</span>: The
vertical precision expressed as the diameter of the “circle of
error” (i.e. twice the +- error value) The units are
centimeters. Datatype: abstract:integer, IPP: int32,
SM:xs:int<span style='color:#1F497D'>(Note: representation is 2 encoded 4 bit
integers(0-9). Most significant represents the base and the least
significant represents the power of 10.) </span><o:p></o:p></p>
<p class=MsoNormal style='margin-left:.5in'><o:p> </o:p></p>
<p class=MsoNormal style='margin-left:.5in'>*<b>new</b>*<span style='color:
#1F497D'> (modified)</span><o:p></o:p></p>
<p class=MsoNormal style='margin-left:.5in'>latitude (SM:Latitude<span
style='color:#1F497D'>(1823483648 to 4618967296)</span>: ): The
latitude of the center of the sphere described by the size attribute.
Expressed in thousandths of a second of arc. The value 2147483648
(2<sup>31</sup>) represents the equator. Values above that are
north and below are south. Datatype: abstract: int32, IPP:integer,
SM:xs:int<o:p></o:p></p>
<p class=MsoNormal style='margin-left:.5in'><o:p> </o:p></p>
<p class=MsoNormal style='margin-left:.5in'>*<b>new</b>*<span style='color:
#1F497D'> (corrected) (modified)</span><o:p></o:p></p>
<p class=MsoNormal style='margin-left:.5in'>longitude (SM:Latitude)<span
style='color:#1F497D'> (1499483648 to 4942967296) </span>The longitude of
the center of the sphere described by the size attribute. Expressed in
thousandths of a second of arc. The value 2147483648 (2<sup>31</sup>)
represents the prime meridian. Values above that are east and below are <span
style='color:#1F497D'>west</span>. The value is rounded away from the
prime meridian Datatype: abstract: int32, IPP:integer, SM:xs:int<o:p></o:p></p>
<p class=MsoNormal style='margin-left:.5in'><o:p> </o:p></p>
<p class=MsoNormal style='margin-left:.5in'>*<b>new</b>*<span style='color:
#1F497D'> (modified)</span><o:p></o:p></p>
<p class=MsoNormal style='margin-left:.5in'>altitude (SM:Altitude)<span
style='color:#1F497D'> (0 to MAX)</span>: The altitude of the center of
the sphere described by the size attribute. Expressed in centimeters from
a base of 100,000m below the reference spheroid used by GPS [WGS 84].
Altitude above (or below) sea level may be used as an approximation of altitude
relative to the [WGS 84] spheroid, though due to the Earth's surface not being
a perfect spheroid, there will be differences. Datatype:
abstract: int32, IPP:integer, SM:xs:int<o:p></o:p></p>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal>Note: There is disagreement on the semantics for all
the attributes between what is posted on <<a
href="http://pwg-wiki.wikispaces.com/Geolocation">http://pwg-wiki.wikispaces.com/Geolocation</a>>
and what I have in the definition above. I took the definition
directly from rfc1876 (I think). See included text from rfc1876 and the
location example 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><span style='color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-family:"Impact","sans-serif";color:navy'>Peter
Zehler</span><span style='color:#1F497D'><br>
<br>
</span><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif";
color:navy'>Xerox Research Center Webster<br>
</span><span style='font-size:10.0pt;font-family:"Arial","sans-serif";
color:navy'>Email: </span><a href="mailto:Peter.Zehler@Xerox.com"><span
style='font-size:10.0pt;font-family:"Arial","sans-serif"'>Peter.Zehler@Xerox.com</span></a><span
style='color:#1F497D'><br>
</span><span style='font-size:10.0pt;font-family:"Arial","sans-serif";
color:navy'>Voice: (585) 265-8755</span><span style='color:#1F497D'><br>
</span><span style='font-size:10.0pt;font-family:"Arial","sans-serif";
color:navy'>FAX: (585) 265-7441</span><span style='color:#1F497D'><br>
</span><span style='font-size:10.0pt;font-family:"Arial","sans-serif";
color:navy'>US Mail: Peter Zehler</span><span style='color:#1F497D'><br>
</span><span style='font-size:10.0pt;font-family:"Arial","sans-serif";
color:navy'>Xerox Corp.</span><span style='color:#1F497D'><br>
</span><span style='font-size:10.0pt;font-family:"Arial","sans-serif";
color:navy'>800 Phillips Rd.</span><span style='color:#1F497D'><br>
</span><span style='font-size:10.0pt;font-family:"Arial","sans-serif";
color:navy'>M/S 128-25E</span><span style='color:#1F497D'><br>
</span><span style='font-size:10.0pt;font-family:"Arial","sans-serif";
color:navy'>Webster NY, 14580-9701</span><span style='color:#1F497D'> <o:p></o:p></span></p>
<div style='border:none;border-bottom:solid windowtext 1.5pt;padding:0in 0in 1.0pt 0in'>
<p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p>
</div>
<p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='color:#1F497D'>From rfc1876 section 2 <<a
href="http://www.rfc-editor.org/rfc/rfc1876.txt">http://www.rfc-editor.org/rfc/rfc1876.txt</a></span>><span
style='color:#1F497D'> <o:p></o:p></span></p>
<p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Courier New"'>SIZE
The diameter of a sphere enclosing the described entity, in<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Courier New"'>
centimeters, expressed as a pair of four-bit unsigned<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Courier New"'>
integers, each ranging from zero to nine, with the most<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Courier New"'>
significant four bits representing the base and the second<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Courier New"'>
number representing the power of ten by which to multiply<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Courier New"'>
the base. This
allows sizes from 0e0 (<1cm) to 9e9<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Courier New"'>
(90,000km) to be expressed. This representation was chosen<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Courier New"'>
such that the hexadecimal representation can be read by<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Courier New"'>
eye; 0x15 = 1e5. Four-bit values greater than 9 are<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Courier New"'>
undefined, as are values with a base of zero and a non-zero<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Courier New"'>
exponent.<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Courier New"'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Courier New"'>
Since 20000000m (represented by the value 0x29) is greater<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Courier New"'>
than the equatorial diameter of the WGS 84 ellipsoid<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Courier New"'>
(12756274m), it is therefore suitable for use as
a<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Courier New"'>
"worldwide" size.<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Courier New"'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Courier New"'>HORIZ
PRE The horizontal precision of the data, in centimeters,<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Courier New"'>
expressed using the same representation as SIZE. This is<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Courier New"'>
the diameter of the horizontal "circle of error", rather<o:p></o:p></span></p>
<pre> than a "plus or minus" value. (This was chosen to match<o:p></o:p></pre><pre> the interpretation of SIZE; to get a "plus or minus" value,<o:p></o:p></pre><pre> divide by 2.)<o:p></o:p></pre><pre><o:p> </o:p></pre><pre>VERT PRE The vertical precision of the data, in centimeters,<o:p></o:p></pre><pre> expressed using the sane representation as for SIZE. This<o:p></o:p></pre><pre> is the total potential vertical error, rather than a "plus<o:p></o:p></pre><pre> or minus" value. (This was chosen to match the<o:p></o:p></pre><pre> interpretation of SIZE; to get a "plus or minus" value,<o:p></o:p></pre><pre> divide by 2.) Note that if altitude above or below sea<o:p></o:p></pre><pre> level is used as an approximation for altitude relative to<o:p></o:p></pre><pre> the [WGS 84] ellipsoid, the precision value should be<o:p></o:p></pre><pre> adjusted.<o:p></o:p></pre><pre><o:p> </o:p></pre><pre>LATITUDE The latitude of the center of the sphere described by the<o:p></o:p></pre><pre> SIZE field, expressed as a 32-bit integer, most significant<o:p></o:p></pre><pre> octet first (network standard byte order), in thousandths<o:p></o:p></pre><pre> of a second of arc. 2^31 represents the equator; numbers<o:p></o:p></pre><pre> above that are north latitude.<o:p></o:p></pre><pre><o:p> </o:p></pre><pre>LONGITUDE The longitude of the center of the sphere described by the<o:p></o:p></pre><pre> SIZE field, expressed as a 32-bit integer, most significant<o:p></o:p></pre><pre> octet first (network standard byte order), in thousandths<o:p></o:p></pre><pre> of a second of arc, rounded away from the prime meridian.<o:p></o:p></pre><pre> 2^31 represents the prime meridian; numbers above that are<o:p></o:p></pre><pre> east longitude.<o:p></o:p></pre><pre><o:p> </o:p></pre><pre>ALTITUDE The altitude of the center of the sphere described by the<o:p></o:p></pre><pre> SIZE field, expressed as a 32-bit integer, most significant<o:p></o:p></pre><pre> octet first (network standard byte order), in centimeters,<o:p></o:p></pre><pre> from a base of 100,000m below the [WGS 84] reference<o:p></o:p></pre><pre> spheroid used by GPS (semimajor axis a=6378137.0,<o:p></o:p></pre><pre> reciprocal flattening rf=298.257223563). Altitude above<o:p></o:p></pre><pre> (or below) sea level may be used as an approximation of<o:p></o:p></pre><pre> altitude relative to the the [WGS 84] spheroid, though due<o:p></o:p></pre><pre> to the Earth's surface not being a perfect spheroid, there<o:p></o:p></pre><pre> will be differences. (For example, the geoid (which sea<o:p></o:p></pre><pre> level approximates) for the continental US ranges from 10<o:p></o:p></pre><pre> meters to 50 meters below the [WGS 84] spheroid.<o:p></o:p></pre><pre> Adjustments to ALTITUDE and/or VERT PRE will be necessary<o:p></o:p></pre><pre> in most cases. The Defense Mapping Agency publishes geoid<o:p></o:p></pre><pre> height values relative to the [WGS 84] ellipsoid.<o:p></o:p></pre><pre><o:p> </o:p></pre>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Courier New"'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p>
<div style='border:none;border-bottom:solid windowtext 1.5pt;padding:0in 0in 1.0pt 0in'>
<p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p>
</div>
<p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoListParagraph style='margin-left:0in'><b><u><span style='font-size:
20.0pt'>2-Dimmensional Location of my office printer<o:p></o:p></span></u></b></p>
<p class=MsoListParagraph><b><span style='font-size:14.0pt'>Google Map URL:<o:p></o:p></span></b></p>
<p class=MsoListParagraph style='margin-left:1.0in'><a
href="http://maps.google.com/maps?f=q&source=s_q&hl=en&geocode=&q=800+phillips+rd+webster+ny+14580&sll=37.0625,-95.677068&sspn=62.226996,106.962891&ie=UTF8&hq=&hnear=800+Phillips+Rd,+Webster,+Monroe,+New+York+14580&ll=43.220973,-77.417162&spn=0.001781,0.003264&t=h&z=19">http://maps.google.com/maps?f=q&source=s_q&hl=en&geocode=&q=800+phillips+rd+webster+ny+14580&sll=37.0625,-95.677068&sspn=62.226996,106.962891&ie=UTF8&hq=&hnear=800+Phillips+Rd,+Webster,+Monroe,+New+York+14580&ll=43.220973,-77.417162&spn=0.001781,0.003264&t=h&z=19</a>
<o:p></o:p></p>
<p class=MsoListParagraph><b><span style='font-size:20.0pt'>Location
representations:<o:p></o:p></span></b></p>
<p class=MsoListParagraph><b><span style='font-size:14.0pt'>Decimal Degrees
(WGS84)<o:p></o:p></span></b></p>
<p class=MsoListParagraph style='margin-left:1.0in'>Latitude Longitude <br>
43.220973 -77.417162 <o:p></o:p></p>
<p class=MsoListParagraph><b><span style='font-size:14.0pt'>Degrees, Minutes
& Seconds<o:p></o:p></span></b></p>
<p class=MsoListParagraph style='margin-left:1.0in'>Latitude Longitude <br>
N43 13 15 W77 25 01 <o:p></o:p></p>
<p class=MsoListParagraph><b><span style='font-size:20.0pt'>GPS<o:p></o:p></span></b></p>
<p class=MsoListParagraph style='margin-left:1.0in'>Latitude Longitude <br>
N 43 13.258 W 77 25.030 <o:p></o:p></p>
<p class=MsoListParagraph><b><span style='font-size:20.0pt'>UTM<o:p></o:p></span></b></p>
<p class=MsoListParagraph style='margin-left:1.0in'> X Y <o:p></o:p></p>
<p class=MsoListParagraph style='margin-left:1.0in'>18N 303685 4788191 <o:p></o:p></p>
<p class=MsoListParagraph style='margin-left:1.0in'><o:p> </o:p></p>
<p class=MsoListParagraph style='margin-left:0in'><b><u><span style='font-size:
20.0pt'>My office elevation:<o:p></o:p></span></u></b></p>
<p class=MsoListParagraph style='margin-left:1.0in'>12800 centimeters (419
feet) above sea level<o:p></o:p></p>
<p class=MsoListParagraph style='margin-left:0in'><b><u><span style='font-size:
20.0pt'>Size of Printer:<o:p></o:p></span></u></b></p>
<p class=MsoListParagraph style='margin-left:1.0in'>91 centimeter (3 feet)<o:p></o:p></p>
<p class=MsoListParagraph style='margin-left:0in'><b><u><span style='font-size:
20.0pt'>Margin of error<o:p></o:p></span></u></b></p>
<p class=MsoListParagraph style='margin-left:1.0in'>183 centimeter (6 feet)<o:p></o:p></p>
<p class=MsoListParagraph style='margin-left:1.0in'><o:p> </o:p></p>
<p class=MsoListParagraph style='margin-left:0in'><b><u><span style='font-size:
36.0pt'>PrinterGeoLocation (RFC1876)<span style='color:#1F497D'> (Corrected)</span><o:p></o:p></span></u></b></p>
<p class=MsoListParagraph style='margin-left:1.0in'>Size = <span
style='color:#1F497D'>18</span> (0x12) (encoded centimeter)<span
style='color:#1F497D'> (corrected)</span><br>
HorizontalPrecision = <span style='color:#1F497D'>34</span> (0x22)
(encoded centimeter)<span style='color:#1F497D'> (corrected)</span><br>
VerticalPrecision = <span style='color:#1F497D'>34</span> (0x22) (encoded
centimeter)<span style='color:#1F497D'> (corrected)</span><o:p></o:p></p>
<p class=MsoListParagraph style='margin-left:1.0in'>Latitude = 2303079151
(thousandths of a second of arc, 2<sup>31</sup> represent equater) (
(DecimalDegreeLatitude*60*60*1000)+2147483648 )<o:p></o:p></p>
<p class=MsoListParagraph style='margin-left:1.0in'>Longitude = 1868781865
(thousandths of a second of arc, 2<sup>31</sup> represent prime meridian) <span
style='font-size:10.0pt'>( 2147483648-(DecimalDegreeLongitude*60*60*1000) )<br>
</span>Altitude = 10012800 (centimeter) (OfficeElevation+10000000)<o:p></o:p></p>
<p class=MsoNormal><span style='font-size:12.0pt;font-family:"Times New Roman","serif";
color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal><span style='font-size:12.0pt;font-family:"Times New Roman","serif"'><br>
-- <br>
This message has been scanned for viruses and <br>
dangerous content by <a href="http://www.mailscanner.info/"><b>MailScanner</b></a>,
and is <br>
believed to be clean. <o:p></o:p></span></p>
</div>
<br />--
<br />This message has been scanned for viruses and
<br />dangerous content by
<a href="http://www.mailscanner.info/"><b>MailScanner</b></a>, and is
<br />believed to be clean.
</body>
</html>