<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<p>Thanks for the research Helena,</p>
<p>It sounds like an OSGeo Special Interest Group will address our
Lexicon Committee requirements. Unless there are any objections, I
propose to push forward with our agenda of setting up an email
list, building a committee, selecting a chair, and getting some
work done.</p>
<p>If you have any objections, please respond ASAP, ideally within
the next 48 hours. <br>
</p>
<p>--</p>
<p>Further to Helena's research:</p>
<p>* Yes, I'd suggest special interest groups should be listed on
the website.</p>
<p>* I found this page: <a
href="https://wiki.osgeo.org/wiki/Interest_Groups">https://wiki.osgeo.org/wiki/Interest_Groups</a>
which I'd suggest should be made official by the board. It
currently states: "This page documents the current dicsussion and
has not yet been approved as official OSGeo policy!"</p>
<p>* The OSGeo Standards Committee should get a page somewhere. I'm
pretty sure it had one before, but I can't find it now.<br>
<br>
</p>
<div class="moz-cite-prefix">On 2/11/19 1:22 pm, Helena Mitasova
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:25031747-C0F8-4F2D-B9BA-0CDAB15263A1@ncsu.edu">
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
I looked into this a little bit and I did not find any Standards
committee here
<div class=""><a href="https://www.osgeo.org/about/committees/"
class="" moz-do-not-send="true">https://www.osgeo.org/about/committees/</a> </div>
<div class=""><a href="https://wiki.osgeo.org/wiki/Main_Page"
class="" moz-do-not-send="true">https://wiki.osgeo.org/wiki/Main_Page</a><br
class="">
<div class=""><a href="https://www.osgeo.org/about/board/"
class="" moz-do-not-send="true">https://www.osgeo.org/about/board/</a></div>
<div class=""><br class="">
</div>
<div class="">But I found OSGeo Standards special interest group
and associated mailing list:</div>
<div class=""><a
href="http://osgeo-org.1560.x6.nabble.com/Special-Interest-Groups-f5179645.html"
class="" moz-do-not-send="true">http://osgeo-org.1560.x6.nabble.com/Special-Interest-Groups-f5179645.html</a></div>
<div class=""><a
href="http://osgeo-org.1560.x6.nabble.com/OSGeo-Standards-f5012448.html"
class="" moz-do-not-send="true">http://osgeo-org.1560.x6.nabble.com/OSGeo-Standards-f5012448.html</a></div>
<div class="">Interestingly enough, I could not find the special
interest groups on the new website - is it something that
should be added there?</div>
<div class=""><br class="">
</div>
<div class="">I don’t think that board vote is needed to
establish a special interest group and mailing list,</div>
<div class="">But the board can voice support and endorsement -
I would like to voice my support here if the special interest
group is the way to go.</div>
<div class=""><br class="">
</div>
<div class="">Cameron, if you think that it would be better to
have Lexicon as an official OSGeo committee (with everything
that comes with it, see</div>
<div class=""><a
href="https://wiki.osgeo.org/wiki/Committee_Guidelines"
class="" moz-do-not-send="true">https://wiki.osgeo.org/wiki/Committee_Guidelines</a>),
then apparently, the board needs to vote to approve the
committee chair </div>
<div class="">according to the guidelines (which I believe are
partially based on the bylaws).</div>
<div class=""><br class="">
</div>
<div class="">I hope this clarifies the process somewhat and
cameron please let us know which way you would like to go,</div>
<div class=""><br class="">
</div>
<div class="">Thanks a lot for the initiative, Helena</div>
<div class=""><br class="">
</div>
<div class="">
<div class="">
<div>
<blockquote type="cite" class="">
<div class="">On Nov 1, 2019, at 9:13 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="">
<meta http-equiv="Content-Type" content="text/html;
charset=UTF-8" class="">
<div text="#000000" bgcolor="#FFFFFF" class="">
<p class="">Astroidex, Kalxas, Delawen, Helena,
OSGeo Board,</p>
<p class="">Do my answers below address your
questions re setting up an OSGeo Lexicon
committee?</p>
<p class="">Within the next few weeks I'm hoping to
reach out to those from the OSGeo community who
have provided glossaries and are likely to be
interested in joining a Lexicon committee. From
that committee we can elect a chair.</p>
<p class="">I'm prefer to have the OSGeo Board's
blessing before progressing further. Is that
something you'd be prepared to provide?<br
class="">
</p>
<p class="">Cheers, Cameron<br class="">
</p>
<div class="moz-cite-prefix">On 30/10/19 10:17 am,
Cameron Shorter wrote:<br class="">
</div>
<blockquote type="cite"
cite="mid:CABqeU+hq+LHamidWfijEw5VFJMkcZCbgWcHbR6dCqnnNrbw9HQ@mail.gmail.com"
class="">
<meta http-equiv="content-type"
content="text/html; charset=UTF-8" class="">
<div dir="ltr" class="">Hi Angelos, board,<br
class="">
<div class="">That is a good question. Working
the lexicon community within the standards
committee is something we should consider.
While I wouldn't want to rule it out as an
option, I'd vote -0 for it.</div>
<div class="">My reasoning:</div>
<div class="">* The lexicon committee is only
focusing on one very narrow use case within
the greater OSGeo/Standards space.</div>
<div class="">* The standards committee has a
very board focus across all standards related
use cases. In particular, it has focused on
managing the relationship between OSGeo and
OGC.</div>
<div class="">* The lexicon committee will be
very noisy within this very specific lexicon
use case. People interested in general
standards will be swapped with emails and I
predict we will very quickly kill off any
other standards related conversations due to
the noise.</div>
<div class="">* The standards committee is
relatively quiet, and it could be argued that
we could consider retiring the standards
committee and restart it as a lexicon
committee. I don't think this is the case. I
think the standards committee still has
meaning and purpose.</div>
<div class=""><br class="">
</div>
<div class="">For these reasons, I believe the
Lexicon and Standards committees should be
kept separate. </div>
<div class=""><br class="">
</div>
<div class="">For my next steps, I'm hoping to
follow this process:</div>
<div class="">1. Get endorsement from the board.</div>
<div class="">2. Create a new <a
href="mailto:lexicon@lists.osgeo.org"
moz-do-not-send="true" class="">lexicon@lists.osgeo.org</a>
email list</div>
<div class="">3. Reach out to OSGeo projects and
invite them to join the list and participate
in a committee</div>
<div class="">4. Boostrap a lexicon committee</div>
<div class="">5. Committee members to vote for a
committee chair</div>
<div class="">6. Start getting serious about the
work we are doing.</div>
<div class=""><br class="">
</div>
<div class="">I'm hoping that the board can
discuss via email, ask questions which I'll
answer, then we can set up a motion and help
us move through the steps above.</div>
<div class=""><br class="">
</div>
<div class="">Warm regards, Cameron</div>
<div class=""><br class="">
</div>
<div class="">For reference, I've copied
comments from the board meeting:</div>
<div class=""><a
href="http://irclogs.geoapt.com/osgeo/%23osgeo.2019-10-28.log"
moz-do-not-send="true" class="">http://irclogs.geoapt.com/osgeo/%23osgeo.2019-10-28.log</a> <br
class="">
</div>
<div class=""><br class="">
</div>
<div class="">
<table style="" class="">
<tbody class="">
<tr class="">
<td class="" valign="top">16:22:49</td>
<td class="gmail-nick"
style="color:rgb(128,0,0)"
valign="top">helena_:</td>
<td class="gmail-post"
style="font-family:monospace,"Courier
New",Courier;font-size:0.9em">#7
Lexicon committee</td>
</tr>
<tr class="">
<td class="" valign="top">16:23:13</td>
<td class="gmail-nick"
style="color:rgb(128,0,0)"
valign="top">helena_:</td>
<td class="gmail-post"
style="font-family:monospace,"Courier
New",Courier;font-size:0.9em">they
keep changing the name but it is an
important initiative</td>
</tr>
<tr class="">
<td class="" valign="top">16:23:37</td>
<td class="gmail-nick"
style="color:rgb(128,0,0)"
valign="top">astroidex:</td>
<td class="gmail-post"
style="font-family:monospace,"Courier
New",Courier;font-size:0.9em">just
a question. Could it be part of one
existing committee?</td>
</tr>
<tr class="">
<td class="" valign="top">16:23:47</td>
<td class="gmail-nick"
style="color:rgb(128,0,0)"
valign="top">delawen:</td>
<td class="gmail-post"
style="font-family:monospace,"Courier
New",Courier;font-size:0.9em">(I'm
back did I miss any voting?)</td>
</tr>
<tr class="">
<td class="" valign="top">16:23:50</td>
<td class="gmail-nick"
style="color:rgb(128,0,0)"
valign="top">kalxas:</td>
<td class="gmail-post"
style="font-family:monospace,"Courier
New",Courier;font-size:0.9em">I
am wondering why this has to be a
separate committee from standards</td>
</tr>
<tr class="">
<td class="" valign="top">16:24:03</td>
<td class="gmail-nick"
style="color:rgb(128,0,0)"
valign="top">astroidex:</td>
<td class="gmail-post"
style="font-family:monospace,"Courier
New",Courier;font-size:0.9em">same
for me</td>
</tr>
<tr class="">
<td class="" valign="top">16:24:06</td>
<td class="gmail-nick"
style="color:rgb(128,0,0)"
valign="top">kalxas:</td>
<td class="gmail-post"
style="font-family:monospace,"Courier
New",Courier;font-size:0.9em">delawen,
no :)</td>
</tr>
<tr class="">
<td class="" valign="top">16:24:19</td>
<td class="gmail-nick"
style="color:rgb(128,0,0)"
valign="top">astroidex:</td>
<td class="gmail-post"
style="font-family:monospace,"Courier
New",Courier;font-size:0.9em">it
could be part of education</td>
</tr>
<tr class="">
<td class="" valign="top">16:24:38</td>
<td class="gmail-nick"
style="color:rgb(128,0,0)"
valign="top">delawen:</td>
<td class="gmail-post"
style="font-family:monospace,"Courier
New",Courier;font-size:0.9em">if
they feel they have enough work to be
isolated... see no reason why not</td>
</tr>
<tr class="">
<td class="" valign="top">16:24:43</td>
<td class="gmail-nick"
style="color:rgb(128,0,0)"
valign="top">astroidex:</td>
<td class="gmail-post"
style="font-family:monospace,"Courier
New",Courier;font-size:0.9em"><a
href="https://www.osgeo.org/about/committees/" moz-do-not-send="true"
class="">https://www.osgeo.org/about/committees/</a></td>
</tr>
<tr class="">
<td class="" valign="top">16:24:44</td>
<td class="gmail-nick"
style="color:rgb(128,0,0)"
valign="top">sigq:</td>
<td class="gmail-post"
style="font-family:monospace,"Courier
New",Courier;font-size:0.9em">Title:
Committees - OSGeo (at <a
href="http://www.osgeo.org/"
moz-do-not-send="true" class="">www.osgeo.org</a>)</td>
</tr>
<tr class="">
<td class="" valign="top">16:24:44</td>
<td class="gmail-nick"
style="color:rgb(128,0,0)"
valign="top">kalxas:</td>
<td class="gmail-post"
style="font-family:monospace,"Courier
New",Courier;font-size:0.9em">given
that OGC and ISO are involved, I think
it should be standards</td>
</tr>
<tr class="">
<td class="" valign="top">16:24:53</td>
<td class="gmail-nick"
style="color:rgb(128,0,0)"
valign="top">delawen:</td>
<td class="gmail-post"
style="font-family:monospace,"Courier
New",Courier;font-size:0.9em">but
I would give them some time to do
stuff before making them official</td>
</tr>
<tr class="">
<td class="" valign="top">16:25:41</td>
<td class="gmail-nick"
style="color:rgb(128,0,0)"
valign="top">delawen:</td>
<td class="gmail-post"
style="font-family:monospace,"Courier
New",Courier;font-size:0.9em">If
you think it should be standards, we
can answer them that</td>
</tr>
<tr class="">
<td class="" valign="top">16:25:41</td>
<td class="gmail-nick"
style="color:rgb(128,0,0)"
valign="top">kalxas:</td>
<td class="gmail-post"
style="font-family:monospace,"Courier
New",Courier;font-size:0.9em">also,
we do need a chair to approve them,
right?</td>
</tr>
<tr class="">
<td class="" valign="top">16:26:00</td>
<td class="gmail-nick"
style="color:rgb(128,0,0)"
valign="top">helena_:</td>
<td class="gmail-post"
style="font-family:monospace,"Courier
New",Courier;font-size:0.9em">Angelos
- can you please get bcak to Cameron
with suggestion from the board to make
it part of standards?</td>
</tr>
<tr class="">
<td class="" valign="top">16:26:25</td>
<td class="gmail-nick"
style="color:rgb(128,0,0)"
valign="top">astroidex:</td>
<td class="gmail-post"
style="font-family:monospace,"Courier
New",Courier;font-size:0.9em">good
idea</td>
</tr>
<tr class="">
<td class="" valign="top">16:26:44</td>
<td class="gmail-nick"
style="color:rgb(128,0,0)"
valign="top">kalxas:</td>
<td class="gmail-post"
style="font-family:monospace,"Courier
New",Courier;font-size:0.9em">yes,
I can follow up</td>
</tr>
</tbody>
</table>
</div>
</div>
<br class="">
<div class="gmail_quote">
<div dir="ltr" class="gmail_attr">On Wed, 30 Oct
2019 at 02:30, Angelos Tzotsos <<a
href="mailto:gcpp.kalxas@gmail.com"
moz-do-not-send="true" class="">gcpp.kalxas@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">Hi Cameron,<br
class="">
<br class="">
The formation of the lexicon committee was
discussed during the board <br class="">
meeting yesterday.<br class="">
One question that came up is: what is the
reason this work cannot be <br class="">
done under the standards committee, since this
involves members from <br class="">
OSGeo, OGC and ISO?<br class="">
<br class="">
Regards,<br class="">
Angelos<br class="">
<br class="">
On 10/24/19 12:16 AM, Cameron Shorter wrote:<br
class="">
> Angelos,<br class="">
><br class="">
> We haven't discussed selecting a chair of
the committee yet, but I <br class="">
> will be suggesting Reese and/or Ron as we
bootstrap this committee. <br class="">
> They both have been been very active in
setting up this initiative and <br class="">
> come with lots of experience.<br class="">
><br class="">
> On 22/10/19 10:47 pm, Victoria Rautenbach
wrote:<br class="">
>> Dear All<br class="">
>><br class="">
>> This is a great initiative, thank you
Cameron and Reese. I fully<br class="">
>> support this initiative and working
with the ISO/TC 211 TMG on their<br class="">
>> mature terminology database.<br
class="">
>><br class="">
>> Reese, will be great to work with you
again!<br class="">
>><br class="">
>> Regards<br class="">
>> Victoria<br class="">
>><br class="">
>> On Tue, Oct 22, 2019 at 9:52 AM
Angelos Tzotsos <br class="">
>> <<a
href="mailto:gcpp.kalxas@gmail.com"
target="_blank" moz-do-not-send="true"
class="">gcpp.kalxas@gmail.com</a>>
wrote:<br class="">
>>> Hi Cameron,<br class="">
>>><br class="">
>>> Have you decided on a committee
chair?<br class="">
>>> Who will be the point of contact
for the board?<br class="">
>>><br class="">
>>> Cheers,<br class="">
>>> Angelos<br class="">
>>><br class="">
>>> On 10/21/19 8:32 PM, Cameron
Shorter wrote:<br class="">
>>><br class="">
>>> OSGeo Board,<br class="">
>>><br class="">
>>> On behalf of Ron, Reese and
myself, I've added an item to the board <br
class="">
>>> agenda requested the board's
approval for the setting up of an OSGeo <br
class="">
>>> Lexicon Committee. Unfortunately
none of us will be awake during <br class="">
>>> this meeting so will not be in a
position to discuss the proposal in <br
class="">
>>> person. Hopefully if you have any
questions you can raise them <br class="">
>>> before hand in this email thread.<br
class="">
>>><br class="">
>>> We have started a wiki page for
the committee here: <br class="">
>>> <a
href="https://wiki.osgeo.org/wiki/Lexicon_Committee"
rel="noreferrer" target="_blank"
moz-do-not-send="true" class="">https://wiki.osgeo.org/wiki/Lexicon_Committee</a><br
class="">
>>><br class="">
>>> Thanks in advance, Cameron<br
class="">
>>><br class="">
>>> On 19/10/19 4:15 am, Cameron
Shorter wrote:<br class="">
>>><br class="">
>>><br class="">
>>> Angelos, the other end of the day
would probably be easier. I think <br
class="">
>>> this link shows board locations
along with Ron (Hong Kong) and Reese <br
class="">
>>> (Tokyo).<br class="">
>>><br class="">
>>> <a
href="https://www.timeanddate.com/worldclock/meetingtime.html?year=2019&month=10&day=20&p1=240&p2=248&p3=102&p4=269&p5=250&p6=26&p7=37&p8=286&p9=734"
rel="noreferrer" target="_blank"
moz-do-not-send="true" class="">https://www.timeanddate.com/worldclock/meetingtime.html?year=2019&month=10&day=20&p1=240&p2=248&p3=102&p4=269&p5=250&p6=26&p7=37&p8=286&p9=734</a>
<br class="">
>>> <<a
href="https://www.timeanddate.com/worldclock/meetingtime.html?year=2019&month=10&day=19&p1=240&p2=248&p3=102&p4=269&p5=250&p6=26&p7=37&p8=286&p9=734"
rel="noreferrer" target="_blank"
moz-do-not-send="true" class="">https://www.timeanddate.com/worldclock/meetingtime.html?year=2019&month=10&day=19&p1=240&p2=248&p3=102&p4=269&p5=250&p6=26&p7=37&p8=286&p9=734</a>>
<br class="">
>>><br class="">
>>><br class="">
>>> Does anyone else from the OSGeo
board have an opinion on this <br class="">
>>> proposal and wish to share it? We
could make the meeting <br class="">
>>> coordination easier if we narrow
participation to only those with an <br
class="">
>>> interest and an opinion.<br
class="">
>>><br class="">
>>> On 18/10/19 8:16 pm, Angelos
Tzotsos wrote:<br class="">
>>><br class="">
>>> Hi,<br class="">
>>><br class="">
>>> In that case we should probably
arrange a specific call for this topic.<br
class="">
>>> I think the only working timeslot
would be around 20:00-22:00 UTC<br class="">
>>><br class="">
>>> On 10/17/19 9:24 PM, Cameron
Shorter wrote:<br class="">
>>><br class="">
>>> Angelos, the board meeting is 3am
for me. The 3 of us involved are <br class="">
>>> in this Asian/Australia timezone.<br
class="">
>>><br class="">
>>> Reese, we can get you set up with
IRC (Internet Chat Relay) quite <br class="">
>>> easily. It is text based only.
Quickest way to get started is with <br
class="">
>>> the web client: <a
href="https://webchat.freenode.net/"
rel="noreferrer" target="_blank"
moz-do-not-send="true" class="">https://webchat.freenode.net/</a><br
class="">
>>><br class="">
>>> On 17/10/19 10:19 pm, <a
href="mailto:rplews@tc211tmg.org"
target="_blank" moz-do-not-send="true"
class="">rplews@tc211tmg.org</a> wrote:<br
class="">
>>><br class="">
>>> hello Angelos, thank you for the
invitation, two issues for me, <br class="">
>>> local time is 1am and i have
never done Internet Relay Chat. i can <br
class="">
>>> do skype or zoom. if you have
another time/date let me know. sorry <br
class="">
>>> about this time.<br class="">
>>> reese<br class="">
>>><br class="">
>>><br class="">
>>> ----- Original Message -----<br
class="">
>>> From:<br class="">
>>> "Angelos Tzotsos" <<a
href="mailto:gcpp.kalxas@gmail.com"
target="_blank" moz-do-not-send="true"
class="">gcpp.kalxas@gmail.com</a>><br
class="">
>>><br class="">
>>> To:<br class="">
>>> "Cameron Shorter" <<a
href="mailto:cameron.shorter@gmail.com"
target="_blank" moz-do-not-send="true"
class="">cameron.shorter@gmail.com</a>>,<br
class="">
>>> <<a
href="mailto:standards@lists.osgeo.org"
target="_blank" moz-do-not-send="true"
class="">standards@lists.osgeo.org</a>>,
"<a href="mailto:board@lists.osgeo.org"
target="_blank" moz-do-not-send="true"
class="">board@lists.osgeo.org</a>"<br
class="">
>>> <<a
href="mailto:board@lists.osgeo.org"
target="_blank" moz-do-not-send="true"
class="">board@lists.osgeo.org</a>>,
"OSGeo Discussions" <<a
href="mailto:discuss@lists.osgeo.org"
target="_blank" moz-do-not-send="true"
class="">discuss@lists.osgeo.org</a>><br
class="">
>>> Cc:<br class="">
>>> "Reese Plews" <<a
href="mailto:rplews@gmail.com"
target="_blank" moz-do-not-send="true"
class="">rplews@gmail.com</a>><br
class="">
>>> Sent:<br class="">
>>> Thu, 17 Oct 2019 12:14:37
+0300<br class="">
>>> Subject:<br class="">
>>> Re: [OSGeo-Standards]
[Board] glossary discussion on<br class="">
>>> osgeo-standards ....<br
class="">
>>><br class="">
>>><br class="">
>>> Hi all,<br class="">
>>><br class="">
>>> Would someone be available
to join our next board meeting to<br class="">
>>> discuss this issue?<br
class="">
>>> <a
href="https://wiki.osgeo.org/wiki/Board_Meeting_2019-10-28"
rel="noreferrer" target="_blank"
moz-do-not-send="true" class="">https://wiki.osgeo.org/wiki/Board_Meeting_2019-10-28</a><br
class="">
>>><br class="">
>>> Regards,<br class="">
>>> Angelos<br class="">
>>><br class="">
>>> On 10/15/19 9:52 PM, Cameron
Shorter wrote:<br class="">
>>><br class="">
>>> OSGeo Board, OSGeo
Discuss,<br class="">
>>><br class="">
>>> I'd like to introduce
you to this proposal that Ron and Reese<br
class="">
>>> have been developing on
the OSGeo Standards email list, which<br
class="">
>>> I think should fit under
the legal structure of an OSGeo<br class="">
>>> Committee.<br class="">
>>><br class="">
>>> I have vague
recollections that setting up a committee<br
class="">
>>> requires board approval?
I've found some old tips on running a<br
class="">
>>> committee here: <br
class="">
>>> <a
href="https://wiki.osgeo.org/wiki/Committee_Guidelines"
rel="noreferrer" target="_blank"
moz-do-not-send="true" class="">https://wiki.osgeo.org/wiki/Committee_Guidelines</a><br
class="">
>>><br class="">
>>> Comments welcomed.<br
class="">
>>><br class="">
>>> On 15/10/19 4:47 pm,
Ronald Tse wrote:<br class="">
>>><br class="">
>>> Hi Cameron,<br
class="">
>>><br class="">
>>> Thank you for the
suggestions! I have updated the proposal<br
class="">
>>> to reflect your
comments below.<br class="">
>>><br class="">
>>> I would be honored
to help with terminology management at<br
class="">
>>> OSGeo. Can’t speak
for Reese but with his leadership in<br
class="">
>>> already doing
terminology cleanup on Felicity’s sheet, he<br
class="">
>>> seems pretty
committed already :-)<br class="">
>>><br class="">
>>> Ron<br class="">
>>><br class="">
>>> ———<br class="">
>>><br class="">
>>> Recommendations for
OSGeo terminology management<br class="">
>>><br class="">
>>> 1. Establish a
terminology management group in OSGeo.<br
class="">
>>><br class="">
>>> ISO/TC 211, IEC
Electropedia and OGC all have one for<br
class="">
>>> terminology
management. The existence of this group is<br
class="">
>>> crucial to the
success of the OSGeo terminology database.<br
class="">
>>> It will play two
essential roles:<br class="">
>>><br class="">
>>> a) As the gatekeeper
of terms to ensure quality checks of<br
class="">
>>> contributions<br
class="">
>>> b) As the seat of
central terminology knowledge for<br class="">
>>> alignment of terms
and concepts. To facilitate the flow of<br
class="">
>>> terminology
knowledge to terminology authors and users.<br
class="">
>>><br class="">
>>> It would be helpful
to involve representation from ISO/TC<br
class="">
>>> 211 and OGC in this
group, in order to leverage their<br class="">
>>> experience in
terminology. Such experience will be useful<br
class="">
>>> in situations such
as alerting on cross-organization<br class="">
>>> alignment of
concepts or term duplication.<br class="">
>>><br class="">
>>> An email list shall
be setup for this group for internal<br
class="">
>>> communication.<br
class="">
>>><br class="">
>>><br class="">
>>> 2. Establish a terms
of reference for terminology <br class="">
>>> management.<br class="">
>>><br class="">
>>> For the terminology
management group, a terms of reference<br
class="">
>>> should be produced
so that the steps for approval and data<br
class="">
>>> quality requirements
are clear. This should be openly<br class="">
>>> shared with
contributors so they are clear on acceptance<br
class="">
>>> criteria.<br
class="">
>>><br class="">
>>> Contributors may
propose changes to the terminology<br class="">
>>> database at any
time. The terminology management group<br
class="">
>>> shall discuss and
approve or disapprove of the proposal<br
class="">
>>> within a reasonable
timeframe. This practice is in-line<br
class="">
>>> with the open
source, change-based, rapid iteration<br
class="">
>>> mantra, similar to
OpenSSL.<br class="">
>>><br class="">
>>> For releases, the
group shall convene periodically, such<br
class="">
>>> as every 4-6 months,
to discuss previously decided<br class="">
>>> proposals,
governance or technical issues related to<br
class="">
>>> terminology
management.<br class="">
>>><br class="">
>>> The method of
submitting change requests shall also be<br
class="">
>>> determined and
announced so that contributors understand<br
class="">
>>> the necessary
processes and timeline.<br class="">
>>><br class="">
>>><br class="">
>>> 3. Establish an
online terminology database presence.<br
class="">
>>><br class="">
>>> Terminology isn’t
useful until people use them, which<br
class="">
>>> means people need to
first know they exist and what they<br
class="">
>>> mean. Geolexica is
an initiative that currently serves<br
class="">
>>> ISO/TC 211’s
terminology management group in making its<br
class="">
>>> multi-lingual
geographic information terminology available<br
class="">
>>> on the internet (<a
href="https://www.geolexica.org/"
rel="noreferrer" target="_blank"
moz-do-not-send="true" class="">https://www.geolexica.org</a>).
We propose to<br class="">
>>> use <a
href="https://osgeo.geolexica.org/"
rel="noreferrer" target="_blank"
moz-do-not-send="true" class="">https://osgeo.geolexica.org/</a>
to serve OSGeo in<br class="">
>>> managing its
terminology database. Geolexica not only<br
class="">
>>> serves
human-readable concepts and terms, but also
serves<br class="">
>>> in machine-readable
JSON, allowing APIs to directly<br class="">
>>> consume the content.<br
class="">
>>><br class="">
>>> The structure of
Geolexica is designed for efficiency with<br
class="">
>>> streamlined
management and operations. Terms are stored in<br
class="">
>>> structured data
(YAML) files, and are directly deployable<br
class="">
>>> to the website. The
website operates according to best<br class="">
>>> practices, and is
served as a static website with dynamic<br
class="">
>>> search
functionality. Security and performance have
always<br class="">
>>> been key
considerations.<br class="">
>>><br class="">
>>> For terms that
originate from other authoritative<br class="">
>>> terminology
databases, such as those from ISO or OGC, a<br
class="">
>>> linkage shall be
established from the OSGeo terminology<br
class="">
>>> database back to the
source.<br class="">
>>><br class="">
>>><br class="">
>>> 4. Use an issue
tracker with source code management<br
class="">
>>> functionality as an
open communication platform (e.g.<br class="">
>>> GitHub).<br class="">
>>><br class="">
>>> The issue tracker is
used to perform two-way communication<br
class="">
>>> between OSGeo
members and the contributors. This requires<br
class="">
>>> every contributor to
at least have an account, which helps<br
class="">
>>> minimize spam. The
source code management functionality is<br
class="">
>>> used to manage
terminology data in a machine-useable way.<br
class="">
>>><br class="">
>>> There are generally
two types of contributors:<br class="">
>>><br class="">
>>> a) those who suggest
changes via textual description, and<br
class="">
>>> b) those who suggest
changes but can also format the<br class="">
>>> desired content in
the data format used by the terminology<br
class="">
>>> database.<br
class="">
>>><br class="">
>>> People can easily
help out with the former in formatting<br
class="">
>>> the changes into a
proper data structure change. This<br class="">
>>> allows the
terminology management group to directly<br
class="">
>>> approve, merge and
deploy the proposed term modifications<br
class="">
>>> (and creations,
deletions), all made effective with a<br
class="">
>>> single click.<br
class="">
>>><br class="">
>>><br class="">
>>> 5. Allow easy
feedback from terminology users.<br class="">
>>><br class="">
>>> To minimize friction
in the feedback process, for every<br class="">
>>> term offered in the
OSGeo terminology pages we can offer a<br
class="">
>>> “propose new term”
and “propose changes to this term"<br class="">
>>> buttons. This allows
user to directly go to the issue<br class="">
>>> platform (e.g.
GitHub) to make the suggested changes.<br
class="">
>>><br class="">
>>> A “contributors
guide” document will greatly help these<br
class="">
>>> people make the
proper suggestions and have them formatted<br
class="">
>>> correctly.<br
class="">
>>><br class="">
>>><br class="">
>>> 6. Initial load and
data cleanup.<br class="">
>>><br class="">
>>> The initial load of
the terms will involve a bulk load<br class="">
>>> from the cleaned
terms and definitions that Felicity has<br
class="">
>>> compiled. Geolexica
could easily handle the initial<br class="">
>>> conversion from
table format into the desired structured<br
class="">
>>> data format.<br
class="">
>>><br class="">
>>> The cleanup process
has already been started by Reese<br class="">
>>> Plews, convenor of
the TMG at ISO/TC 211.<br class="">
>>><br class="">
>>><br class="">
>>>
_____________________________________<br
class="">
>>><br class="">
>>> Ronald Tse<br
class="">
>>> Ribose Inc.<br
class="">
>>><br class="">
>>> On Oct 10, 2019,
at 3:34 PM, Cameron Shorter<br class="">
>>> <<a
href="mailto:cameron.shorter@gmail.com"
target="_blank" moz-do-not-send="true"
class="">cameron.shorter@gmail.com</a>>
wrote:<br class="">
>>><br class="">
>>> Hi Ron,<br
class="">
>>><br class="">
>>> I really like
your proposal. It looks very practical,<br
class="">
>>> should address
quality requirements, and should be<br
class="">
>>> relatively light
weight to manage. Some<br class="">
>>>
comments/suggestions:<br class="">
>>><br class="">
>>> * You might want
to mention the approach to your first<br
class="">
>>> load of terms,
which probably should involve a bulk<br
class="">
>>> load from a
derivative of the terms that Felicity has<br
class="">
>>> compiled.<br
class="">
>>><br class="">
>>> * I suggest we
set up an email list to discuss terms.<br
class="">
>>> OSGeo can
provide that for us, and I can coordinate<br
class="">
>>> that, once we
have agreed on our approach.<br class="">
>>><br class="">
>>> * I suggest that
an updating the glossary be tied to a<br
class="">
>>> periodic event,
at least annually. I think we should<br
class="">
>>> tie in with the
OSGeoLive annual build cycle for this.<br
class="">
>>><br class="">
>>> * You haven't
mentioned <a
href="https://osgeo.geolexica.org/"
rel="noreferrer" target="_blank"
moz-do-not-send="true" class="">https://osgeo.geolexica.org/</a><br
class="">
>>> <<a
href="https://osgeo.geolexica.org/"
rel="noreferrer" target="_blank"
moz-do-not-send="true" class="">https://osgeo.geolexica.org/</a>>
in your description. I<br class="">
>>> assume that
would be part of the solution? If so, I<br
class="">
>>> suggest
mentioning it.<br class="">
>>><br class="">
>>> * Another
project I'm helping start up is<br class="">
>>> <a
href="https://thegooddocsproject.dev/"
rel="noreferrer" target="_blank"
moz-do-not-send="true" class="">https://thegooddocsproject.dev/</a><br
class="">
>>> <<a
href="https://thegooddocsproject.dev/"
rel="noreferrer" target="_blank"
moz-do-not-send="true" class="">https://thegooddocsproject.dev/</a>>
(Writing templates<br class="">
>>> to make good
docs for open source projects). I expect<br
class="">
>>> that the
solution you are proposing would be valuable<br
class="">
>>> for a wide
variety of domains, and should be captured<br
class="">
>>> as best
practices in TheGoodDocsProject. At some point<br
class="">
>>> in the future,
I'm hoping that you might provide a<br
class="">
>>> generic version
of your suggestions for others to<br class="">
>>> follow too.<br
class="">
>>><br class="">
>>> Feel free to add
your ideas below into the wiki at:<br class="">
>>> <a
href="https://trac.osgeo.org/osgeolive/wiki/Glossary%20terms"
rel="noreferrer" target="_blank"
moz-do-not-send="true" class="">https://trac.osgeo.org/osgeolive/wiki/Glossary%20terms</a><br
class="">
>>><br class="">
>>> (Maybe add
"DRAFT" at the top, until we have the<br
class="">
>>> process set up.)<br
class="">
>>><br class="">
>>> * Ron and Reese,
I'm hoping that you both will<br class="">
>>> continue to
provide the leadership and stewardship of<br
class="">
>>> the community as
it grows? Your advice has been great<br
class="">
>>> to date.<br
class="">
>>><br class="">
>>> Warm regards,
Cameron<br class="">
>>><br class="">
>>><br class="">
>>><br class="">
>>>
_______________________________________________<br
class="">
>>> Standards mailing
list<br class="">
>>> <a
href="mailto:Standards@lists.osgeo.org"
target="_blank" moz-do-not-send="true"
class="">Standards@lists.osgeo.org</a><br
class="">
>>> <a
href="https://lists.osgeo.org/mailman/listinfo/standards"
rel="noreferrer" target="_blank"
moz-do-not-send="true" class="">https://lists.osgeo.org/mailman/listinfo/standards</a><br
class="">
>>><br class="">
>>><br class="">
>>><br class="">
>>>
_______________________________________________<br
class="">
>>><br class="">
>>><br class="">
>>><br class="">
>>> Board mailing list<br
class="">
>>> <a
href="mailto:Board@lists.osgeo.org"
target="_blank" moz-do-not-send="true"
class="">Board@lists.osgeo.org</a><br
class="">
>>> <a
href="https://lists.osgeo.org/mailman/listinfo/board"
rel="noreferrer" target="_blank"
moz-do-not-send="true" class="">https://lists.osgeo.org/mailman/listinfo/board</a><br
class="">
>>><br class="">
>>><br class="">
>>><br class="">
>>> --<br class="">
>>><br class="">
>>><br class="">
>>> Angelos Tzotsos, PhD<br
class="">
>>><br class="">
>>><br class="">
>>><br class="">
>>> Charter Member<br class="">
>>><br class="">
>>><br class="">
>>><br class="">
>>> Open Source Geospatial
Foundation<br class="">
>>> <a
href="http://users.ntua.gr/tzotsos"
rel="noreferrer" target="_blank"
moz-do-not-send="true" class="">http://users.ntua.gr/tzotsos</a><br
class="">
>>><br class="">
>>><br class="">
>>><br class="">
>>> -- <br class="">
>>> Cameron Shorter<br class="">
>>> Technology Demystifier<br
class="">
>>> Open Technologies and Geospatial
Consultant<br class="">
>>><br class="">
>>> M +61 (0) 419 142 254<br class="">
>>><br class="">
>>><br class="">
>>><br class="">
>>>
_______________________________________________<br
class="">
>>> Board mailing list<br class="">
>>> <a
href="mailto:Board@lists.osgeo.org"
target="_blank" moz-do-not-send="true"
class="">Board@lists.osgeo.org</a><br
class="">
>>> <a
href="https://lists.osgeo.org/mailman/listinfo/board"
rel="noreferrer" target="_blank"
moz-do-not-send="true" class="">https://lists.osgeo.org/mailman/listinfo/board</a><br
class="">
>>><br class="">
>>><br class="">
>>><br class="">
>>> -- <br class="">
>>> Angelos Tzotsos, PhD<br class="">
>>> Charter Member<br class="">
>>> Open Source Geospatial Foundation<br
class="">
>>> <a
href="http://users.ntua.gr/tzotsos"
rel="noreferrer" target="_blank"
moz-do-not-send="true" class="">http://users.ntua.gr/tzotsos</a><br
class="">
>>><br class="">
>>>
_______________________________________________<br
class="">
>>> Board mailing list<br class="">
>>> <a
href="mailto:Board@lists.osgeo.org"
target="_blank" moz-do-not-send="true"
class="">Board@lists.osgeo.org</a><br
class="">
>>> <a
href="https://lists.osgeo.org/mailman/listinfo/board"
rel="noreferrer" target="_blank"
moz-do-not-send="true" class="">https://lists.osgeo.org/mailman/listinfo/board</a><br
class="">
><br class="">
<br class="">
<br class="">
-- <br class="">
Angelos Tzotsos, PhD<br class="">
Charter Member<br class="">
Open Source Geospatial Foundation<br class="">
<a href="http://users.ntua.gr/tzotsos"
rel="noreferrer" target="_blank"
moz-do-not-send="true" class="">http://users.ntua.gr/tzotsos</a><br
class="">
<br class="">
</blockquote>
</div>
<br class="" clear="all">
<div class=""><br class="">
</div>
-- <br class="">
<div dir="ltr" class="gmail_signature">
<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=""><span
style="font-size:12.8px"
class="">Cameron Shorter</span><br
class="">
</div>
<div class="">Technology
Demystifier</div>
<div class="">Open Technologies
and Geospatial Consultant</div>
<div class=""><br class="">
</div>
<div class="">M +61 (0) 419 142
254</div>
<div class=""><br class="">
</div>
</div>
<div class=""><br class="">
<br class="">
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</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>
</div>
_______________________________________________<br
class="">
Board mailing list<br class="">
<a href="mailto:Board@lists.osgeo.org" class=""
moz-do-not-send="true">Board@lists.osgeo.org</a><br
class="">
<a class="moz-txt-link-freetext" href="https://lists.osgeo.org/mailman/listinfo/board">https://lists.osgeo.org/mailman/listinfo/board</a></div>
</blockquote>
</div>
<br class="">
<div class="">
<div style="color: rgb(0, 0, 0); font-family: Helvetica;
font-size: 12px; font-style: normal; font-variant-caps:
normal; font-weight: normal; letter-spacing: normal;
orphans: auto; text-align: start; text-indent: 0px;
text-transform: none; white-space: normal; widows: auto;
word-spacing: 0px; -webkit-text-size-adjust: auto;
-webkit-text-stroke-width: 0px;">Helena Mitasova</div>
<div style="color: rgb(0, 0, 0); font-family: Helvetica;
font-size: 12px; font-style: normal; font-variant-caps:
normal; font-weight: normal; letter-spacing: normal;
orphans: auto; text-align: start; text-indent: 0px;
text-transform: none; white-space: normal; widows: auto;
word-spacing: 0px; -webkit-text-size-adjust: auto;
-webkit-text-stroke-width: 0px;">Professor, Department
of Marine, Earth and Atmospheric Sciences<br class="">
Faculty Fellow,<br class="">
Center for Geospatial Analytics<br class="">
North Carolina State University<br class="">
Raleigh, NC 27695-8208</div>
<div style="color: rgb(0, 0, 0); font-family: Helvetica;
font-size: 12px; font-style: normal; font-variant-caps:
normal; font-weight: normal; letter-spacing: normal;
orphans: auto; text-align: start; text-indent: 0px;
text-transform: none; white-space: normal; widows: auto;
word-spacing: 0px; -webkit-text-size-adjust: auto;
-webkit-text-stroke-width: 0px;"><a
href="mailto:hmitaso@ncsu.edu" class=""
moz-do-not-send="true">hmitaso@ncsu.edu</a></div>
<div style="color: rgb(0, 0, 0); font-family: Helvetica;
font-size: 12px; font-style: normal; font-variant-caps:
normal; font-weight: normal; letter-spacing: normal;
orphans: auto; text-align: start; text-indent: 0px;
text-transform: none; white-space: normal; widows: auto;
word-spacing: 0px; -webkit-text-size-adjust: auto;
-webkit-text-stroke-width: 0px;" class=""><br class="">
</div>
<br class="Apple-interchange-newline">
</div>
<br class="">
</div>
</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>