<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">Hi Cameron,<div class=""><br class=""></div><div class="">The documentation will be “living” and subject to intermittent update, so you can consider the work in the URL provided to be ready for production, even though it will evolve. We are implementing such documentation as a permanent and maintained program and will extend this documentation to other standards (including new standards as they are published). We do not yet have a timeline for “catch-up” of existing standards.</div><div class=""><br class=""></div><div class="">Best Regards,</div><div class="">Scott</div><div class=""><br class=""><div><blockquote type="cite" class=""><div class="">On Apr 25, 2017, at 3:10 PM, Cameron Shorter <<a href="mailto:cameron.shorter@gmail.com" class="">cameron.shorter@gmail.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class="">
  
    <meta content="text/html; charset=utf-8" http-equiv="Content-Type" class="">
  
  <div bgcolor="#FFFFFF" text="#000000" class=""><p class="">Hi Scott,</p><p class="">Thanks for your response and URL. Could you please update us on
      current status and schedule for OGC documentation.</p><p class="">* Is the documentation at <a moz-do-not-send="true" href="http://cite.opengeospatial.org/pub/cite/files/edu/index.html" class="">http://cite.opengeospatial.org/pub/cite/files/edu/index.html</a>
      considered draft, ready for production, other?</p><p class="">* Is there a maintenance program in place to ensure that this
      documentation is continuously kept up to date? Eg: to update
      existing documentation whenever a new standard is published.<br class="">
    </p><p class="">* It appears that the URL provided only mentions WMS KML, SLD,
      SE, CSW standards. Is there any commitment to generate
      documentation for other standards?<br class="">
    </p>
    Warm regards, Cameron<br class="">
    <br class="">
    <div class="moz-cite-prefix">On 26/4/17 2:12 am, Scott Simmons
      wrote:<br class="">
    </div>
    <blockquote cite="mid:3C21AC2E-13A9-40CC-8776-CAF54D725B01@opengeospatial.org" type="cite" class="">
      <meta http-equiv="Content-Type" content="text/html; charset=utf-8" class="">
      Hi Cameron,
      <div class=""><br class="">
      </div>
      <div class="">OGC would very much like to be the source of
        documentation where possible to keep you from duplicating
        effort! Perhaps you could link to our material where it is
        current and useful (as you referenced in your mail) and I will
        be sure to keep you informed as we accelerate our
        “implementer-friendly” standards documentation. Examples of such
        documentation can be found here:</div>
      <div class=""><a moz-do-not-send="true" href="http://cite.opengeospatial.org/pub/cite/files/edu/index.html" class="">http://cite.opengeospatial.org/pub/cite/files/edu/index.html</a></div>
      <div class=""><br class="">
      </div>
      <div class="">Where the OSGeo community has developed superior
        documentation, you may want to stick with that material until we
        get our material ready.</div>
      <div class=""><br class="">
      </div>
      <div class="">Best Regards,</div>
      <div class="">Scott</div>
      <div class=""><br class="">
        <div class="">
          <div style="letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">
            <div class="">Scott Simmons</div>
            <div class="">Executive Director, Standards Program</div>
            <div class="">Open Geospatial Consortium (OGC)</div>
            <div class="">
              <div class="">tel +1 970 682 1922</div>
              <div class="">mob +1 970 214 9467</div>
            </div>
            <div class=""><a moz-do-not-send="true" href="mailto:ssimmons@opengeospatial.org" class="">ssimmons@opengeospatial.org</a></div>
            <div class=""><br class="">
            </div>
            <div class="">The OGC: Making Location Count…</div>
            <div class=""><a moz-do-not-send="true" href="http://www.opengeospatial.org/" class="">www.opengeospatial.org</a></div>
            <div class=""><br class="">
            </div>
          </div>
          <br class="Apple-interchange-newline">
          <br class="Apple-interchange-newline">
        </div>
        <br class="">
        <div class="">
          <blockquote type="cite" class="">
            <div class="">On Apr 24, 2017, at 6:00 PM, Cameron Shorter
              <<a moz-do-not-send="true" href="mailto:cameron.shorter@gmail.com" class="">cameron.shorter@gmail.com</a>>
              wrote:</div>
            <br class="Apple-interchange-newline">
            <div class="">
              <div class="">To date, OSGeo-Live documentation has
                included write ups of a number of OGC Standards
                (including both English master text and translations).
                [1]<br class="">
                <br class="">
                However, this documentation hasn't been maintained for a
                number of years.<br class="">
                <br class="">
                As we go through rationalising what we continue to
                include on OSGeo-Live, we are wondering what should be
                done about OGC standards text on OSGeo-Live.<br class="">
                <br class="">
                I'm aware of the OGC has created some material [2],
                which on first glance looks to be more complete and more
                current than the OSGeo-Live material.<br class="">
                <br class="">
                I'm interested to hear thoughts (especially from the
                OGC) on what we should do in moving forward.<br class="">
                <br class="">
                * Should we drop OSGeo-Live write up of OGC Standards
                all together, as it is not core business of OSGeo? (This
                would free up some space on OSGeo-Live)<br class="">
                <br class="">
                * Should we provide a reference to a OGC Standards URL?
                If so, where would that be?<br class="">
                <br class="">
                * Should we make a copy OGC standards into OSGeo-Live
                docs? If so, who will take responsibility for writing
                and maintaining the build scripts.<br class="">
                <br class="">
                * Would the OGC want to investigate using OSGeo-Live's
                existing translation community to translate OGC docs? If
                so, how should this be approached and who would like to
                coordinate it?<br class="">
                <br class="">
                Thoughts will be welcomed.<br class="">
                <br class="">
                [1] <a moz-do-not-send="true" href="https://live.osgeo.org/en/standards/standards.html" class="">https://live.osgeo.org/en/standards/standards.html</a><br class="">
                <br class="">
                [2] <a moz-do-not-send="true" href="https://github.com/opengeospatial/ogc_school" class="">https://github.com/opengeospatial/ogc_school</a><br class="">
                <br class="">
                <br class="">
                -- <br class="">
                Cameron Shorter<br class="">
                M +61 419 142 254<br class="">
                <br class="">
                _______________________________________________<br class="">
                Standards mailing list<br class="">
                <a moz-do-not-send="true" href="mailto:Standards@lists.osgeo.org" class="">Standards@lists.osgeo.org</a><br class="">
                <a class="moz-txt-link-freetext" href="https://lists.osgeo.org/mailman/listinfo/standards">https://lists.osgeo.org/mailman/listinfo/standards</a></div>
            </div>
          </blockquote>
        </div>
        <br class="">
      </div>
    </blockquote>
    <br class="">
    <pre class="moz-signature" cols="72">-- 
Cameron Shorter
M +61 419 142 254</pre>
  </div>

</div></blockquote></div><br class=""></div></body></html>