<div>Quick feedback:</div><div><br></div><div><b>Conceptual Model</b></div><div><br></div><div>So much better than last time I looked. GetCapabilities is now listed allowing client to perform version negotiation and figure out what it can support, indeed that is listed as a "Key Requirement" this time out.</div><div><br></div><div>A few of the sections later on could benefit from some Q&A for consistency … </div><div><br></div><div>GeoTIFF is marked as "<span style="font-family: TimesNewRomanPSMT; font-size: 12pt; ">This class describes the extension to the OWS Context Core which supports in-line or </span><font face="TimesNewRomanPSMT" size="4">referenced offerings. ; this can include referencing local files or into databases."</font></div><div><font face="TimesNewRomanPSMT" size="4"><br></font></div><div><font face="TimesNewRomanPSMT" size="4">However the details only provide "</font><span style="font-family: ArialMT; font-size: 12px; ">content" that is a "</span><font face="ArialMT"><span style="font-size: 12px;">Local reference to a File</span></font><span style="font-family: ArialMT; font-size: 12px; ">" </span><font face="TimesNewRomanPSMT" size="4">- this does not on the face of it indicate support for "in-line" GeoTIFF provided as part of the context document.</font></div><div><font face="TimesNewRomanPSMT" size="4"><br></font></div><div><font face="TimesNewRomanPSMT" size="4">I am also looking for a vendor extension section, so that the lowly shapefile can be supported (as this is still a primary use case for desktop apps).</font></div><div><br></div><div><b>ATOM Encoding</b></div><div><b><br></b></div><div>I eventually skipped to the examples, I like the smooth ramp up between simply listing operations (HTTP GET GetCapabilities, GetXXXX), through to allowing HTTP Post, through to caching the results at the time the context was created. This would allow an application to display what was intended (say what a decision was based on) and then "refresh" it to reflect the current operating picture.</div><div><br></div><div>-- </div><div><div>Jody Garnett<br></div><div><br></div></div>
<p style="color: #A0A0A8;">On Tuesday, 19 February 2013 at 10:41 AM, Jody Garnett wrote:</p>
<blockquote type="cite" style="border-left-style:solid;border-width:1px;margin-left:0px;padding-left:10px;">
<span><div><div>
<div>
Last time I looked at this one with Jim … I hated it (even though he was keen on how ATOM had been used).</div><div>For me It was not providing enough context for a client to make its own request.</div><div><br></div>
<div><div>I would really like to see a context document take shape, it would be very valuable between systems (which we tend to like on these osgeo lists).</div><div><br></div><div>Tracing through your links I arrive at some word docs, don't suppose you can format shift those to PDF or something more portable.</div><div><br></div><div>-- </div><div>Jody Garnett<br></div><div><br></div></div>
<p style="color: #A0A0A8;">On Tuesday, 19 February 2013 at 3:39 AM, Carl Reed wrote:</p><blockquote type="cite"><div>
<span><div><div>
<div dir="ltr">
<div style="FONT-FAMILY: 'Times New Roman'; COLOR: #000000; FONT-SIZE: 12pt">
<div style="FONT-FAMILY: 'Times New Roman'; COLOR: #000000; FONT-SIZE: 12pt">I
am not sure if this group saw this announcement. This is a preliminary comment
period. There will be another comment period later in the process.</div>
<div style="FONT-FAMILY: 'Times New Roman'; COLOR: #000000; FONT-SIZE: 12pt"> </div>
<div style="FONT-FAMILY: 'Times New Roman'; COLOR: #000000; FONT-SIZE: 12pt">The
announcement is here:</div>
<div style="FONT-FAMILY: 'Times New Roman'; COLOR: #000000; FONT-SIZE: 12pt"> </div>
<div style="FONT-FAMILY: 'Times New Roman'; COLOR: #000000; FONT-SIZE: 12pt"><a title="http://www.opengeospatial.org/node/1765" href="http://www.opengeospatial.org/node/1765">http://www.opengeospatial.org/node/1765</a></div>
<div style="FONT-FAMILY: 'Times New Roman'; COLOR: #000000; FONT-SIZE: 12pt"> </div>
<div style="FONT-FAMILY: 'Times New Roman'; COLOR: #000000; FONT-SIZE: 12pt">Please
ignore the Comment Due date. The OGC OWS Context Standards Working Group is
happy to receive comments on this candidate standard at any time.</div>
<div style="FONT-FAMILY: 'Times New Roman'; COLOR: #000000; FONT-SIZE: 12pt"> </div>
<div style="FONT-FAMILY: 'Times New Roman'; COLOR: #000000; FONT-SIZE: 12pt">Regards</div>
<div style="FONT-FAMILY: 'Times New Roman'; COLOR: #000000; FONT-SIZE: 12pt"> </div>
<div style="FONT-FAMILY: 'Times New Roman'; COLOR: #000000; FONT-SIZE: 12pt">Carl
Reed, PhD<br>CTO and Executive Director Standards Program<br>Open Geospatial
Consortium<br><a href="http://www.opengeospatial.org">www.opengeospatial.org</a><br><br>The OGC: Making Location
Count!<br><br>---------------------<br><br>This communication, including
attachments, is for the exclusive use of addressee and may contain proprietary,
confidential or privileged information. If you are not the intended recipient,
any use, copying, disclosure, dissemination or distribution is strictly
prohibited. If you are not the intended recipient, please notify the sender
immediately by return email and delete this communication and destroy all
copies.<br><br>"The important thing is not to stop questioning." -- Albert
Einstein <br>"Security is mostly a superstition. It does not exist in nature.
Life is either a daring adventure or nothing." -- Helen Keller
</div></div></div>
</div><div><div>_______________________________________________</div><div>Standards mailing list</div><div><a href="mailto:Standards@lists.osgeo.org">Standards@lists.osgeo.org</a></div><div><a href="http://lists.osgeo.org/mailman/listinfo/standards">http://lists.osgeo.org/mailman/listinfo/standards</a></div></div></div></span>
</div></blockquote><div>
<br>
</div>
</div></div></span>
</blockquote>
<div>
<br>
</div>