<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">
Hi Cameron,
<div class=""><br class="">
</div>
<div class="">Not to speak for Gobe and Scott — from my understanding, OGC operates the OGC Naming Authority which is way more powerful. Its role not only covers glossaries but also naming assignments and code lists (similar to what IANA does). It also provides
semantic web output like RDF and TTL. There is a defined process on updates managed by Gobe's group.</div>
<div class=""><br class="">
</div>
<div class="">Geolexica handles simple glossaries to serve terms and definitions under the terminology schema used in ISO (term, definition, notes, examples), without needing a server it keeps costs and maintenance minimal.</div>
<div class=""><br class="">
</div>
<div class="">We have been discussing with Gobe on how we could add Geolexica terms inside OGC NA in an automated way, but haven’t had the time to make it happen yet. Maybe we should do that soon...</div>
<div class=""><br class="">
</div>
<div class="">Kind regards,</div>
<div class="">Ron</div>
<div class=""><br class="">
</div>
<div 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><br class="">
<blockquote type="cite" class="">
<div class="">On Oct 1, 2019, at 4:04 AM, Cameron Shorter <<a href="mailto:cameron.shorter@gmail.com" class="">cameron.shorter@gmail.com</a>> wrote:</div>
<br class="Apple-interchange-newline">
<div class="">
<div text="#000000" bgcolor="#FFFFFF" class="">
<p class="">Gobe, Carl, Scott,</p>
<p class="">I'm keen to hear the OGC weigh in on the geolexia approach being proposed. (Ideally before weighing in on the good questions below). In particular, I'd like to hear discussion about whether the OGC might adopt a similar approach, or set of processes,
or adopt the same technology stack. I feel we wouldn't have done our due diligence if we were to propose advice to the OSGeo community without first getting endorsement from the OGC.<br class="">
</p>
<p class="">I think ISO TC211, the OGC, and OSGeo are key players here, and it would be good to have us all singing from the same songbook.</p>
<p class="">I'm also listening for lessons that we can take from the geospatial domain into general documentation guidance for all open source (and other) domains, through TheGoodDocsProject I'm helping set up.</p>
<p class="">Cheers, Cameron</p>
<div class="moz-cite-prefix">On 30/9/19 9:23 pm, Ronald Tse wrote:<br class="">
</div>
<blockquote type="cite" cite="mid:76E5B3BF-0593-43EA-BF05-207CD560E69F@ribose.com" class="">
<div style="word-wrap: break-word; -webkit-nbsp-mode: space;
line-break: after-white-space;" class="">
Hi Felicity, Bruce,
<div class=""><br class="">
</div>
<div class="">Thanks for the great questions! As a noob to OSGeo, replies inline…</div>
<div class=""><br class="">
</div>
<div class="">
<blockquote type="cite" class="">
<div class="">• Before we can do any sort of bulk upload we'll need to add columns for the fields we're missing to comply with the required format. (For example, entry_status, authoritative_source, etc)<br class="">
</div>
</blockquote>
<div class=""><br class="">
</div>
<div class="">If it is decided that the Google Sheet will serve as the authoritative data store for the glossary, we have the ability to pull from that to generate the site.</div>
<br class="">
<blockquote type="cite" class="">
<div class="">• Is this an authoritative OSGeo taxonomy?<br class="">
</div>
</blockquote>
<div class=""><br class="">
</div>
<div class="">It should be?</div>
<br class="">
<blockquote type="cite" class="">
<div class="">• What terms do we want included?<br class="">
</div>
</blockquote>
<div class=""><br class="">
</div>
<div class="">Probably all technical terms across OSGeo projects, I imagine that OSGeoLive documentation would provide a host of them?</div>
<br class="">
<blockquote type="cite" class="">
<div class="">• How do we define the ‘official’, authoritative definition of the term(s)?<br class="">
</div>
</blockquote>
<div class=""><br class="">
</div>
<div class="">Maybe there should be some terminology group / list setup to vet these terms and their sources?</div>
<br class="">
<blockquote type="cite" class="">
<div class="">• How do we approve new terms? What process is required to do the approval?<br class="">
</div>
</blockquote>
<div class="">
<blockquote type="cite" class="">• Similarly, what process do we need to modify, retire or remove an existing ‘authoritative’ term?<br class="">
</blockquote>
</div>
<div class=""><br class="">
</div>
<div class="">These actions relating to term lifecycle ought to be done by people (and probably consensus), especially since stability is arguably important. Some process should be required. Maybe a terms of reference for this terminology management list/group
will be needed.</div>
<div class=""><br class="">
</div>
<div class="">Ron</div>
<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; 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 Sep 30, 2019, at 10:01 AM, Bruce Bannerman <<a href="mailto:bruce.bannerman.osgeo@gmail.com" class="" moz-do-not-send="true">bruce.bannerman.osgeo@gmail.com</a>> wrote:</div>
<br class="Apple-interchange-newline">
<div class="">
<div style="word-wrap: break-word; -webkit-nbsp-mode:
space; line-break: after-white-space;" class="">
Hi everyone.
<div class=""><br class="">
</div>
<div class="">If we are to set up a taxonomy, I suggest that we also think about a process behind the inclusion of ‘authoritative’ terms. </div>
<div class=""><br class="">
</div>
<div class="">This will become important for the future use and re-use of this taxonomy.</div>
<div class=""><br class="">
</div>
<div class="">Some items to think about:</div>
<div class=""><br class="">
</div>
<div class="">
<ul class="MailOutline">
<li class="">Is this an authoritative OSGeo taxonomy?</li><li class="">What terms do we want included?</li><li class="">How do we define the ‘official’, authoritative definition of the term(s)?</li><li class="">How do we approve new terms? What process is required to do the approval?</li><li class="">Similarly, what process do we need to modify, retire or remove an existing ‘authoritative’ term?</li></ul>
<div class=""><br class="">
</div>
<div class="">Thjis will become important as people come to rely on an OSGeo taxonomy.</div>
<div class=""><br class="">
</div>
<div class="">Also, I fully endorse Ron’s comments about not reinventing the wheel and re-using existing taxonomies where possible.</div>
<div class=""><br class="">
</div>
<div class="">Kind regards,</div>
<div class=""><br class="">
</div>
<div class="">Bruce</div>
<div class=""><br class="">
</div>
<div class=""><br class="">
<blockquote type="cite" class="">
<div class="">On 30 Sep 2019, at 09:42, Felicity Brand <<a href="mailto:felicitybrand@gmail.com" class="" moz-do-not-send="true">felicitybrand@gmail.com</a>> wrote:</div>
<br class="Apple-interchange-newline">
<div class="">
<div dir="ltr" class="">
<div class="">I spent a few hours yesterday collating content from sources people had sent us into a spreadsheet. There's nearly 500 terms in there: <a href="https://docs.google.com/spreadsheets/d/19tulyAEDN5Q5n-u_jlmXIKQjPI2Lwv6fh5Orad1mz1I/edit#gid=0" target="_blank" class="" moz-do-not-send="true">https://docs.google.com/spreadsheets/d/19tulyAEDN5Q5n-u_jlmXIKQjPI2Lwv6fh5Orad1mz1I/edit#gid=0</a></div>
<div class=""><br class="">
</div>
<div class="">As I understand it:</div>
<div class="">
<ul class="">
<li style="margin-left:15px" class="">Before we can do any sort of bulk upload we'll need to add columns for the fields we're missing to comply with the required format. (For example, entry_status, authoritative_source, etc)</li><li style="margin-left:15px" class="">We'll need to review and cull terms that are generic or extraneous - that aren't quite OSGeo specific.</li></ul>
</div>
<div class=""><br class="">
</div>
<div class="">Thanks</div>
<div class="">Felicity</div>
</div>
<br class="">
<div class="gmail_quote">
<div dir="ltr" class="gmail_attr">On Mon, Sep 30, 2019 at 9:27 AM Cameron Shorter <<a href="mailto:cameron.shorter@gmail.com" class="" moz-do-not-send="true">cameron.shorter@gmail.com</a>> wrote:<br class="">
</div>
<blockquote class="gmail_quote" style="margin:0px 0px 0px
0.8ex;border-left:1px solid
rgb(204,204,204);padding-left:1ex">
<div dir="ltr" class="">
<div dir="ltr" class="">Folks,
<div class="">As per links below, Ron has set up an OSGeo Glossary system that we can play around with.</div>
<div class="">Feedback welcomed ...</div>
</div>
<br class="">
<div class="gmail_quote">
<div dir="ltr" class="gmail_attr">On Mon, 30 Sep 2019 at 07:51, Reese W. Plews <<a href="mailto:rplews@gmail.com" target="_blank" class="" moz-do-not-send="true">rplews@gmail.com</a>> wrote:<br class="">
</div>
<blockquote class="gmail_quote" style="margin:0px 0px 0px
0.8ex;border-left:1px solid
rgb(204,204,204);padding-left:1ex">
hello Cameron, good morning. no problem moving back to the mail list.<br class="">
we just were not sure if you were ready that it be shown to your group<br class="">
or not at this time.<br class="">
<br class="">
the loading process for geolexica was built around the requirements of<br class="">
the ISO MLTG excel file. moving entries into an excel file with the<br class="">
same format would be the easiest way to load content. bringing them in<br class="">
from another source would require code additions/modifications. Ron<br class="">
can tell you where those modifications would be needed and i am sure<br class="">
there are members in your group who could work up something that meets<br class="">
your requirements. but if you have entries already in a list-like<br class="">
form, putting them into excel is an easy way.<br class="">
<br class="">
i was not aware of the other projects, but Ron may have heard of them<br class="">
before. thank you for mentioning our work to them. if they are able to<br class="">
make use of geolexica or some of the terminology management concepts<br class="">
that we use within TC211 i think we are very happy.<br class="">
<br class="">
will be in touch,<br class="">
<br class="">
reese<br class="">
<br class="">
On Mon, Sep 30, 2019 at 5:30 AM Cameron Shorter<br class="">
<<a href="mailto:cameron.shorter@gmail.com" target="_blank" class="" moz-do-not-send="true">cameron.shorter@gmail.com</a>> wrote:<br class="">
><br class="">
> Wow!!!<br class="">
> I feel like it is Christmas. Thankyou.<br class="">
> Do you mind if we take this email thread back on list?<br class="">
> Assuming it is okay with you, I'd like to show it to the rest of the<br class="">
> OSGeo community, and start talking about next steps with them.<br class="">
><br class="">
> Questions will cover:<br class="">
> 1. Do you have any suggestions for bulk uploading hundreds for existing<br class="">
> terms? I suggest a tool be written to support that.<br class="">
><br class="">
> 2. A few months ago, I've helped kick off TheGoodDocsProject [1], where<br class="">
> a bunch of senior tech writers are building best practice templates and<br class="">
> writing instructions for documenting open source projects. I think that<br class="">
> you might have part of the answer to what goes into a "Glossary"<br class="">
> template. So I'd like to introduce you to that email list too. [2]<br class="">
><br class="">
> [1] <a href="https://thegooddocsproject.dev/" rel="noreferrer" target="_blank" class="" moz-do-not-send="true">
https://thegooddocsproject.dev/</a><br class="">
> [2] <a href="https://groups.io/g/thegooddocsproject/" rel="noreferrer" target="_blank" class="" moz-do-not-send="true">
https://groups.io/g/thegooddocsproject/</a><br class="">
><br class="">
> On 30/9/19 12:25 am, Ronald Tse wrote:<br class="">
> > And the site branding has been somewhat updated with OSGeo branding.<br class="">
> > We’ll refine the design in the days to come.<br class="">
> ><br class="">
> > Ron<br class="">
</blockquote>
</div>
<br class="" clear="all">
<div class=""><br class="">
</div>
<div dir="ltr" class="gmail_attr">From: <strong class="gmail_sendername" dir="auto">
Ronald Tse</strong> <span dir="auto" class=""><<a href="mailto:tse@ribose.com" target="_blank" class="" moz-do-not-send="true">tse@ribose.com</a>></span><br class="">
Date: Sun, 29 Sep 2019 at 23:08<br class="">
Subject: Re: glossary discussion on osgeo-standards ....<br class="">
To: Cameron Shorter <<a href="mailto:cameron.shorter@gmail.com" target="_blank" class="" moz-do-not-send="true">cameron.shorter@gmail.com</a>><br class="">
Cc: Reese Plews <<a href="mailto:rplews@gmail.com" target="_blank" class="" moz-do-not-send="true">rplews@gmail.com</a>><br class="">
</div>
<br class="">
<br class="">
<div class="">Hi Cameron,
<div class=""><br class="">
</div>
<div class="">I’m happy to let you know the site is somewhat live (the design, not yet):</div>
<div class=""><a href="https://osgeodev.geolexica.org/" target="_blank" class="" moz-do-not-send="true">https://osgeodev.geolexica.org</a></div>
<div class=""><br class="">
</div>
<div class="">The first term there is your do-ocracy:</div>
<div class=""><a href="https://osgeodev.geolexica.org/concepts/10/" target="_blank" class="" moz-do-not-send="true">https://osgeodev.geolexica.org/concepts/10/</a></div>
<div class=""><br class="">
</div>
<div class="">The repo is located at:</div>
<div class=""><a href="https://github.com/geolexica/osgeo.geolexica.org" target="_blank" class="" moz-do-not-send="true">https://github.com/geolexica/osgeo.geolexica.org</a></div>
<div class=""><br class="">
</div>
<div class="">I’ve added some contribution instructions here, certainly they can be improved:</div>
<div class=""><a href="https://github.com/geolexica/osgeo.geolexica.org#contributing" target="_blank" class="" moz-do-not-send="true">https://github.com/geolexica/osgeo.geolexica.org#contributing</a></div>
<div class=""><br class="">
</div>
<div class="">The deployment is automated. If you can provide your (and/or your team's) GitHub handle(s) I can add you to the group for direct access, especially for the addition of terms. </div>
<div class=""><br class="">
</div>
<div class="">Hope this helps!</div>
<div class=""><br class="">
</div>
<div class="">Ron</div>
<div class=""><br class="">
<div class="">
<div style="" class="">_____________________________________<br class="">
<br class="">
Ronald Tse<br class="">
Ribose Inc.</div>
</div>
</div>
</div>
<div dir="ltr" class="">
<div dir="ltr" class="">
<div class="">
<div dir="ltr" class="">
<div dir="ltr" class="">
<div dir="ltr" class="">
<div dir="ltr" class="">
<div dir="ltr" class="">
<div class="">
<div class=""><br class="">
</div>
</div>
<div class=""><br class="">
<br class="">
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</blockquote>
</div>
_______________________________________________<br class="">
Standards mailing list<br class="">
<a href="mailto:Standards@lists.osgeo.org" class="" moz-do-not-send="true">Standards@lists.osgeo.org</a><br class="">
<a href="https://lists.osgeo.org/mailman/listinfo/standards" class="" moz-do-not-send="true">https://lists.osgeo.org/mailman/listinfo/standards</a></div>
</blockquote>
</div>
<br class="">
</div>
</div>
</div>
</blockquote>
</div>
<br class="">
</div>
</div>
<br class="">
<fieldset class="mimeAttachmentHeader"></fieldset>
<pre class="moz-quote-pre" wrap="">_______________________________________________
Standards mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Standards@lists.osgeo.org">Standards@lists.osgeo.org</a>
<a class="moz-txt-link-freetext" href="https://lists.osgeo.org/mailman/listinfo/standards">https://lists.osgeo.org/mailman/listinfo/standards</a></pre>
</blockquote>
<pre class="moz-signature" cols="72">--
Cameron Shorter
Technology Demystifier
Open Technologies and Geospatial Consultant
M +61 (0) 419 142 254</pre>
</div>
_______________________________________________<br class="">
Standards mailing list<br class="">
<a href="mailto:Standards@lists.osgeo.org" class="">Standards@lists.osgeo.org</a><br class="">
https://lists.osgeo.org/mailman/listinfo/standards</div>
</blockquote>
</div>
<br class="">
</div>
</body>
</html>