<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<p>Thanks Reese for sharing these suggestions. This works for me.</p>
<p>To fill people in on some of the pre-list history.</p>
<p>The original OSGeo Lexicon concept sprung from an idea (from
Felicity Brand) that we create a collective OSGeo Glossary. After
floating the idea publicly, Reese Plews and Ron Tse reached out
and let me know about how progressed they were with the ISO TC211
<a class="moz-txt-link-freetext" href="https://www.geolexica.org/">https://www.geolexica.org/</a> . In particular, they offered to
provide all the software and processes, ready to go, for use by
OSGeo.</p>
<p>Needless to say, I was super excited, and this spawned the
setting up this OSGeo Lexicon Committee, which would be needed to
manage the processes behind the terminology.</p>
<p>And so here we are, with Reese's plan below, and quite a sizable
community on list, with many names I recognise and respect. I
think we have plenty of challenges ahead, but I think we are off
to a good start.</p>
<p>Warm regards, Cameron<br>
</p>
<div class="moz-cite-prefix">On 30/11/19 1:02 pm, Reese Plews wrote:<br>
</div>
<blockquote type="cite"
cite="mid:ab1e3d5e4a540a954fe3812ef1cb296fca3b118e@webmail.tc211tmg.org">
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
<div>hello everyone,</div>
<div><br>
</div>
<div>there have not been any more subscription requests for the
past few days now, so i think the initial core group members
have registered. thank you again for your interest.<br>
</div>
<div><br>
</div>
<div>due to the end of year holidays, along with commitments to
meetings and projects, i propose we begin our main discussions
in late January or early February 2020. <br>
</div>
<div><br>
</div>
<div>before that time, i will work to prepare some drafts of the
initial work tasks/process flow documentation that was
originally discussed prior to the official start of this group.</div>
<div><br>
</div>
<div>roughly this work consists of:</div>
<br>
1) description of how the committee should draft terminology
entries; idea to base this on some simple and clear predefined
practices<br>
<br>
2) refine the flow of how the committee works with a terminology
entry; (from discovery, discussion, agreement, and publishing to
<a href="http://osgeo.geolexica.org" moz-do-not-send="true">osgeo.geolexica.org</a>)<br>
<br>
<div>
3) learn who our users are/will be and if we are meeting their
needs</div>
<div><br>
</div>
<div>to enable collaboration with the members of this group, the
plan is to work on these documents online, using google
docs/sheets. <br>
</div>
<div>once some finalized materials are ready these could be
shifted to our Lexicon wiki page or retained on google. <br>
</div>
<div><br>
</div>
<div>since the list is visible to non-members through the archive,
the shared links will be set for RO with the ability to
comment. <br>
</div>
<div>if anyone wants to do more than comment, you can contact me
off-list and i will give you access to the documents.</div>
<div><br>
</div>
<div>some of you have provided links in your introduction
messages. i will assume those links are public and can be shared
in any documents. <br>
</div>
<div><br>
</div>
<div>once the drafts are ready for comment, i will send around the
links. <br>
</div>
<div><br>
</div>
<div>thank you for your patience. talk with you again soon.<br>
</div>
<div><br>
</div>
<div>reese<br>
</div>
<div><br>
</div>
<div><br>
</div>
<div><br>
</div>
<div> <br>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<pre class="moz-quote-pre" wrap="">_______________________________________________
Lexicon mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Lexicon@lists.osgeo.org">Lexicon@lists.osgeo.org</a>
<a class="moz-txt-link-freetext" href="https://lists.osgeo.org/mailman/listinfo/lexicon">https://lists.osgeo.org/mailman/listinfo/lexicon</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>
</body>
</html>