<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<p>Hi Ron,</p>
<p>I really like your proposal. It looks very practical, should
address quality requirements, and should be relatively light
weight to manage. Some comments/suggestions:</p>
<p>* You might want to mention the approach to your first load of
terms, which probably should involve a bulk load from a derivative
of the terms that Felicity has compiled.</p>
<p>* I suggest we set up an email list to discuss terms. OSGeo can
provide that for us, and I can coordinate that, once we have
agreed on our approach.<br>
</p>
<p>* I suggest that an updating the glossary be tied to a periodic
event, at least annually. I think we should tie in with the
OSGeoLive annual build cycle for this.</p>
<p>* You haven't mentioned <a href="https://osgeo.geolexica.org/">https://osgeo.geolexica.org/</a>
in your description. I assume that would be part of the solution?
If so, I suggest mentioning it.</p>
<p>* Another project I'm helping start up is <a
href="https://thegooddocsproject.dev/">https://thegooddocsproject.dev/</a>
(Writing templates to make good docs for open source projects). I
expect that the solution you are proposing would be valuable for a
wide variety of domains, and should be captured as best practices
in TheGoodDocsProject. At some point in the future, I'm hoping
that you might provide a generic version of your suggestions for
others to follow too.</p>
<p>Feel free to add your ideas below into the wiki at: <a
href="https://trac.osgeo.org/osgeolive/wiki/Glossary%20terms">https://trac.osgeo.org/osgeolive/wiki/Glossary%20terms</a></p>
<p>(Maybe add "DRAFT" at the top, until we have the process set up.)</p>
<p>* Ron and Reese, I'm hoping that you both will continue to
provide the leadership and stewardship of the community as it
grows? Your advice has been great to date.</p>
<p>Warm regards, Cameron<br>
</p>
<div class="moz-cite-prefix">On 10/10/19 2:40 pm, Ronald Tse wrote:<br>
</div>
<blockquote type="cite"
cite="mid:ADE0A1E3-ACAC-4283-8205-0BB4EB3AD6B7@ribose.com">
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<div style="word-wrap: break-word; -webkit-nbsp-mode: space;
line-break: after-white-space;" class="">
Hi Cameron,
<div class=""><br class="">
</div>
<div class="">OGC and ISO have established structures and their
processes may not perfectly fit the overtly-open model used by
OSGeo.</div>
<div class=""><br class="">
</div>
<div class="">As an open-source developer, my ideal workflow
with OSGeo terminology management would follow an open
proposal and feedback model, suited for an issue tracker like
GitHub offers.</div>
<div class=""><br class="">
</div>
<div class="">The vision is to allow crowd-sourcing of terms
while tracking those from ISO, OGC or whatever authoritative
source to prevent duplication.</div>
<div class=""><br class="">
</div>
<div class="">This is what I’d propose:</div>
<div class=""><br class="">
</div>
<div class="">1. Establish a terminology management group in
OSGeo.</div>
<div class=""><br class="">
</div>
<div class="">Other than ISO, OGC, the Electropedia also has
one, and it is especially important since quality checks will
be crucial to the success of the OSGeo terminology database.
It could be as simple as having two members “approve” new
terms or updates; similar to how OpenSSL accepts
contributions.</div>
<div class=""><br class="">
</div>
<div class="">
<div class="">For the terminology management group, a terms of
reference should be produced so that the steps for approval
and data quality requirements are clear. This can also be
openly shared with contributors so they know what to do.</div>
</div>
<div class=""><br class="">
</div>
<div class="">
<div class="">In the terminology management group, it would be
very helpful to involve representation from ISO/TC 211 and
OGC members so they can tell you whether any newly proposed
terms are problematic (e.g. duplication).</div>
</div>
<div class=""><br class="">
</div>
<div class="">2. Use an issue tracker like GitHub (or similar)
as an open communication platform.</div>
<div class=""><br class="">
</div>
<div class="">This is used to perform two-way communication
between OSGeo members and the contributors. This requires
every contributor to at least have an account, this helps
minimize spam. There will be two types of contributors, those
that purely suggest changes, and those who suggest changes but
can also format the desired content in the data format used by
the terminology database. People can easily help out with the
former. This allows whoever of the management group that
approves the term to directly “merge” in the changes to the
database with a click.</div>
<div class=""><br class="">
</div>
<div class="">3. Offer buttons to kickstart the feedback
process.</div>
<div class=""><br class="">
</div>
<div class="">To minimize friction in the feedback process, for
every term offered in the OSGeo terminology pages we can offer
a “propose new term” and “propose changes to this term"
buttons. This allows user to directly go to the issue platform
(e.g. GitHub) to make the suggested changes. A “contributors
guide” document will greatly help these people make the proper
suggestions and have them formatted correctly.</div>
<div class=""><br class="">
</div>
<div class="">4. The linkage between the OSGeo terminology
database back to ISO and OGC can be established for any terms
that originated from those parties.</div>
<div class=""><br class="">
</div>
<div class="">Does this help?</div>
<div class=""><br class="">
</div>
<div class="">Kind regards,</div>
<div class="">Ron</div>
<div class=""><br class="">
</div>
<div class=""><br class="">
<div class="">
<div style="color: rgb(0, 0, 0); letter-spacing: normal;
orphans: auto; text-align: start; text-indent: 0px;
text-transform: none; white-space: normal; widows: auto;
word-spacing: 0px; -webkit-text-stroke-width: 0px;
word-wrap: break-word; -webkit-nbsp-mode: space;
-webkit-line-break: after-white-space;" class="">
_____________________________________<br class="">
<br class="">
Ronald Tse<br class="">
Ribose Inc.<br class="">
<br class="">
+=========================================================+<br class="">
This message may contain confidential and/or privileged<br
class="">
information. If you are not the addressee or authorized
to<br class="">
receive this for the addressee, you must not use, copy,<br
class="">
disclose or take any action based on this message or any<br
class="">
information herein. If you have received this message in<br
class="">
error, please advise the sender immediately by reply
e-mail<br class="">
and delete this message. Thank you for your cooperation.<br
class="">
+=========================================================+</div>
</div>
<div class=""><br class="">
<blockquote type="cite" class="">
<div class="">On Oct 2, 2019, at 7:24 PM, Cameron Shorter
<<a href="mailto:cameron.shorter@gmail.com" class=""
moz-do-not-send="true">cameron.shorter@gmail.com</a>>
wrote:</div>
<br class="Apple-interchange-newline">
<div class="">
<div dir="ltr" style="caret-color: rgb(0, 0, 0);
font-family: Helvetica; font-size: 12px; font-style:
normal; font-variant-caps: normal; font-weight:
normal; letter-spacing: normal; text-align: start;
text-indent: 0px; text-transform: none; white-space:
normal; word-spacing: 0px; -webkit-text-stroke-width:
0px; text-decoration: none;" class="">
<div dir="ltr" class="">Hi Gobe,
<div class="">I can see that you have documented the
OGC process, and HOW external people can engage
with this process.</div>
<div class="">However, I'm really looking for a<span
class="Apple-converted-space"> </span><b
class="">Vision<span
class="Apple-converted-space"> </span></b>and<span
class="Apple-converted-space"> </span><b
class="">Technical Roadmap</b><span
class="Apple-converted-space"> </span>which
OSGeo can follow (re Terminology definitions). I
feel you haven't addressed our OSGeo use case. And
in particular, I'm not seeing an integration
strategy between OGC and OSGeo.</div>
<div class=""><br class="">
</div>
<div class="">On behalf of the OSGeo community, I'm
offering to help source extra terminology, but I
don't want to start a new incompatible system. I'm
hoping we can set up something which
seamlessly integrates with ISO 211 and OGC. And
for that I'm asking for help. Think about the
reality of sourcing terms from thousands of
individuals. These people are not interested in
managing a glossary, but would be fine with
suggesting a missing term, or refining a
definition - if we make the process easy.</div>
<div class=""><br class="">
</div>
<div class=""><b class="">So if you were to advise
on setting up an OSGeo Terminology system from
scratch what would you suggest?</b><span
class="Apple-converted-space"> </span>I'm
thinking advice should cover crowdsourcing
information, include a review process, and
particularly pertinent to the OGC, should describe
seamlessly integrate into OGC and ISO 211 systems
(because we have agreed on the same field names
and complementary processes).</div>
<div class=""><br class="">
</div>
<div class="">
<div class="">Note: In my first 30 sec look I can
see there are gaps in OGC definitions. I can't
find an edge case word "GeoJSON", but can find a
similar transport format "XML".</div>
<div class="">I can't find package names such as
"QGIS". I'm sure there are more. I feel the
OSGeo community could complement OGC hugely in
supporting the spatial community around
terminology - and we would be so much better
with OGC's help.</div>
</div>
<div class=""><br class="">
</div>
<div class="">After collating your thoughts, I
suggest we should follow up with a video
conference call.</div>
<div class=""><br class="">
</div>
<div class="">Sound good?</div>
<div class="">Cameron</div>
<div class=""><br class="">
</div>
</div>
</div>
</div>
</blockquote>
</div>
<br class="">
</div>
</div>
</blockquote>
<pre class="moz-signature" cols="72">--
Cameron Shorter
Technology Demystifier
Open Technologies and Geospatial Consultant
M +61 (0) 419 142 254</pre>
</body>
</html>