<html>
<head>
<meta content="text/html; charset=utf-8" http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<p>Cameron,</p>
<p>I am in favor of providing a reference to a OGC standards URL.</p>
<p>I think this URL should point to a landing page of OGC where the
partnership relation between OGC and OSGeo becomes clear, and the
relation of OGC to the OSGeo-Live software stack.</p>
<p>I cc'ed this mail to Athina, who probably can find out who can
help on behalf of OGC, if this is the option that the OSGeo
community preferes.</p>
<p><br>
</p>
<p>Dirk<br>
</p>
<br>
<div class="moz-cite-prefix">On 25-04-17 02:00, Cameron Shorter
wrote:<br>
</div>
<blockquote
cite="mid:bd086ebf-de11-4a06-e964-229cb9897db6@gmail.com"
type="cite">To date, OSGeo-Live documentation has included write
ups of a number of OGC Standards (including both English master
text and translations). [1]
<br>
<br>
However, this documentation hasn't been maintained for a number of
years.
<br>
<br>
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>
<br>
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>
<br>
I'm interested to hear thoughts (especially from the OGC) on what
we should do in moving forward.
<br>
<br>
* 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>
<br>
* Should we provide a reference to a OGC Standards URL? If so,
where would that be?
<br>
<br>
* 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>
<br>
* 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>
<br>
Thoughts will be welcomed.
<br>
<br>
[1] <a class="moz-txt-link-freetext" href="https://live.osgeo.org/en/standards/standards.html">https://live.osgeo.org/en/standards/standards.html</a>
<br>
<br>
[2] <a class="moz-txt-link-freetext" href="https://github.com/opengeospatial/ogc_school">https://github.com/opengeospatial/ogc_school</a>
<br>
<br>
<br>
</blockquote>
<br>
<div class="moz-signature">-- <br>
<meta http-equiv="CONTENT-TYPE" content="text/html; charset=utf-8">
<title></title>
<meta name="GENERATOR" content="LibreOffice 3.4 (Linux)">
<meta name="CREATED" content="0;0">
<meta name="CHANGEDBY" content="Dirk Frigne">
<meta name="CHANGED" content="20120229;15002500">
<style type="text/css">
<!--
@page { margin: 2cm }
P { margin-bottom: 0.21cm }
PRE { font-family: "Arial", sans-serif }
A:link { so-language: zxx }
-->
</style>
<pre>Met vriendelijke groeten
Dirk
ir Dirk Frigne
founder DFC Software Engineering
<a href="http://www.dfc.be/"><img src="cid:part1.4834B84C.028A88E7@dfc.be" name="DFC Software Engineering" border="0" align="LEFT" height="133" width="537"></a>
Brugsesteenweg 587
B-9030 Gent
Belgium
T: +32 9 236 61 96
E: <a class="moz-txt-link-abbreviated" href="mailto:dirk.frigne@dfc.be">dirk.frigne@dfc.be</a>
<a class="moz-txt-link-abbreviated" href="http://www.dfc.be">www.dfc.be</a>
Strongly involved into <a class="moz-txt-link-abbreviated" href="http://www.geomajas.org">www.geomajas.org</a>
BnP Fortis Paribas
290 0239807-44
IBAN BE55 2900 2398 0744
BIC: GEBABEBB
</pre>
</div></body></html>