<div dir="ltr">Hi Angelos, board,<br><div>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>My reasoning:</div><div>* The lexicon committee is only focusing on one very narrow use case within the greater OSGeo/Standards space.</div><div>* 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>* 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>* 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><br></div><div>For these reasons, I believe the Lexicon and Standards committees should be kept separate. </div><div><br></div><div>For my next steps, I'm hoping to follow this process:</div><div>1. Get endorsement from the board.</div><div>2. Create a new <a href="mailto:lexicon@lists.osgeo.org">lexicon@lists.osgeo.org</a> email list</div><div>3. Reach out to OSGeo projects and invite them to join the list and participate in a committee</div><div>4. Boostrap a lexicon committee</div><div>5. Committee members to vote for a committee chair</div><div>6. Start getting serious about the work we are doing.</div><div><br></div><div>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><br></div><div>Warm regards, Cameron</div><div><br></div><div>For reference, I've copied comments from the board meeting:</div><div><a href="http://irclogs.geoapt.com/osgeo/%23osgeo.2019-10-28.log">http://irclogs.geoapt.com/osgeo/%23osgeo.2019-10-28.log</a> <br></div><div><br></div><div><table style="color:rgb(0,0,0);font-family:"Times New Roman";font-size:16px"><tbody><tr><td valign="top">16:22:49</td><td class="gmail-nick" valign="top" style="color:rgb(128,0,0)">helena_:</td><td class="gmail-post" style="font-family:monospace,"Courier New",Courier;font-size:0.9em">#7 Lexicon committee</td></tr><tr><td valign="top">16:23:13</td><td class="gmail-nick" valign="top" style="color:rgb(128,0,0)">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><td valign="top">16:23:37</td><td class="gmail-nick" valign="top" style="color:rgb(128,0,0)">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><td valign="top">16:23:47</td><td class="gmail-nick" valign="top" style="color:rgb(128,0,0)">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><td valign="top">16:23:50</td><td class="gmail-nick" valign="top" style="color:rgb(128,0,0)">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><td valign="top">16:24:03</td><td class="gmail-nick" valign="top" style="color:rgb(128,0,0)">astroidex:</td><td class="gmail-post" style="font-family:monospace,"Courier New",Courier;font-size:0.9em">same for me</td></tr><tr><td valign="top">16:24:06</td><td class="gmail-nick" valign="top" style="color:rgb(128,0,0)">kalxas:</td><td class="gmail-post" style="font-family:monospace,"Courier New",Courier;font-size:0.9em">delawen, no :)</td></tr><tr><td valign="top">16:24:19</td><td class="gmail-nick" valign="top" style="color:rgb(128,0,0)">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><td valign="top">16:24:38</td><td class="gmail-nick" valign="top" style="color:rgb(128,0,0)">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><td valign="top">16:24:43</td><td class="gmail-nick" valign="top" style="color:rgb(128,0,0)">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/">https://www.osgeo.org/about/committees/</a></td></tr><tr><td valign="top">16:24:44</td><td class="gmail-nick" valign="top" style="color:rgb(128,0,0)">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">www.osgeo.org</a>)</td></tr><tr><td valign="top">16:24:44</td><td class="gmail-nick" valign="top" style="color:rgb(128,0,0)">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><td valign="top">16:24:53</td><td class="gmail-nick" valign="top" style="color:rgb(128,0,0)">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><td valign="top">16:25:41</td><td class="gmail-nick" valign="top" style="color:rgb(128,0,0)">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><td valign="top">16:25:41</td><td class="gmail-nick" valign="top" style="color:rgb(128,0,0)">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><td valign="top">16:26:00</td><td class="gmail-nick" valign="top" style="color:rgb(128,0,0)">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><td valign="top">16:26:25</td><td class="gmail-nick" valign="top" style="color:rgb(128,0,0)">astroidex:</td><td class="gmail-post" style="font-family:monospace,"Courier New",Courier;font-size:0.9em">good idea</td></tr><tr><td valign="top">16:26:44</td><td class="gmail-nick" valign="top" style="color:rgb(128,0,0)">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><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">gcpp.kalxas@gmail.com</a>> wrote:<br></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>
<br>
The formation of the lexicon committee was discussed during the board <br>
meeting yesterday.<br>
One question that came up is: what is the reason this work cannot be <br>
done under the standards committee, since this involves members from <br>
OSGeo, OGC and ISO?<br>
<br>
Regards,<br>
Angelos<br>
<br>
On 10/24/19 12:16 AM, Cameron Shorter wrote:<br>
> Angelos,<br>
><br>
> We haven't discussed selecting a chair of the committee yet, but I <br>
> will be suggesting Reese and/or Ron as we bootstrap this committee. <br>
> They both have been been very active in setting up this initiative and <br>
> come with lots of experience.<br>
><br>
> On 22/10/19 10:47 pm, Victoria Rautenbach wrote:<br>
>> Dear All<br>
>><br>
>> This is a great initiative, thank you Cameron and Reese. I fully<br>
>> support this initiative and working with the ISO/TC 211 TMG on their<br>
>> mature terminology database.<br>
>><br>
>> Reese, will be great to work with you again!<br>
>><br>
>> Regards<br>
>> Victoria<br>
>><br>
>> On Tue, Oct 22, 2019 at 9:52 AM Angelos Tzotsos <br>
>> <<a href="mailto:gcpp.kalxas@gmail.com" target="_blank">gcpp.kalxas@gmail.com</a>> wrote:<br>
>>> Hi Cameron,<br>
>>><br>
>>> Have you decided on a committee chair?<br>
>>> Who will be the point of contact for the board?<br>
>>><br>
>>> Cheers,<br>
>>> Angelos<br>
>>><br>
>>> On 10/21/19 8:32 PM, Cameron Shorter wrote:<br>
>>><br>
>>> OSGeo Board,<br>
>>><br>
>>> On behalf of Ron, Reese and myself, I've added an item to the board <br>
>>> agenda requested the board's approval for the setting up of an OSGeo <br>
>>> Lexicon Committee. Unfortunately none of us will be awake during <br>
>>> this meeting so will not be in a position to discuss the proposal in <br>
>>> person. Hopefully if you have any questions you can raise them <br>
>>> before hand in this email thread.<br>
>>><br>
>>> We have started a wiki page for the committee here: <br>
>>> <a href="https://wiki.osgeo.org/wiki/Lexicon_Committee" rel="noreferrer" target="_blank">https://wiki.osgeo.org/wiki/Lexicon_Committee</a><br>
>>><br>
>>> Thanks in advance, Cameron<br>
>>><br>
>>> On 19/10/19 4:15 am, Cameron Shorter wrote:<br>
>>><br>
>>><br>
>>> Angelos, the other end of the day would probably be easier. I think <br>
>>> this link shows board locations along with Ron (Hong Kong) and Reese <br>
>>> (Tokyo).<br>
>>><br>
>>> <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">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>
>>> <<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">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>
>>><br>
>>><br>
>>> Does anyone else from the OSGeo board have an opinion on this <br>
>>> proposal and wish to share it? We could make the meeting <br>
>>> coordination easier if we narrow participation to only those with an <br>
>>> interest and an opinion.<br>
>>><br>
>>> On 18/10/19 8:16 pm, Angelos Tzotsos wrote:<br>
>>><br>
>>> Hi,<br>
>>><br>
>>> In that case we should probably arrange a specific call for this topic.<br>
>>> I think the only working timeslot would be around 20:00-22:00 UTC<br>
>>><br>
>>> On 10/17/19 9:24 PM, Cameron Shorter wrote:<br>
>>><br>
>>> Angelos, the board meeting is 3am for me. The 3 of us involved are <br>
>>> in this Asian/Australia timezone.<br>
>>><br>
>>> Reese, we can get you set up with IRC (Internet Chat Relay) quite <br>
>>> easily. It is text based only. Quickest way to get started is with <br>
>>> the web client: <a href="https://webchat.freenode.net/" rel="noreferrer" target="_blank">https://webchat.freenode.net/</a><br>
>>><br>
>>> On 17/10/19 10:19 pm, <a href="mailto:rplews@tc211tmg.org" target="_blank">rplews@tc211tmg.org</a> wrote:<br>
>>><br>
>>> hello Angelos, thank you for the invitation, two issues for me, <br>
>>> local time is 1am and i have never done Internet Relay Chat. i can <br>
>>> do skype or zoom. if you have another time/date let me know. sorry <br>
>>> about this time.<br>
>>> reese<br>
>>><br>
>>><br>
>>> ----- Original Message -----<br>
>>> From:<br>
>>> "Angelos Tzotsos" <<a href="mailto:gcpp.kalxas@gmail.com" target="_blank">gcpp.kalxas@gmail.com</a>><br>
>>><br>
>>> To:<br>
>>> "Cameron Shorter" <<a href="mailto:cameron.shorter@gmail.com" target="_blank">cameron.shorter@gmail.com</a>>,<br>
>>> <<a href="mailto:standards@lists.osgeo.org" target="_blank">standards@lists.osgeo.org</a>>, "<a href="mailto:board@lists.osgeo.org" target="_blank">board@lists.osgeo.org</a>"<br>
>>> <<a href="mailto:board@lists.osgeo.org" target="_blank">board@lists.osgeo.org</a>>, "OSGeo Discussions" <<a href="mailto:discuss@lists.osgeo.org" target="_blank">discuss@lists.osgeo.org</a>><br>
>>> Cc:<br>
>>> "Reese Plews" <<a href="mailto:rplews@gmail.com" target="_blank">rplews@gmail.com</a>><br>
>>> Sent:<br>
>>> Thu, 17 Oct 2019 12:14:37 +0300<br>
>>> Subject:<br>
>>> Re: [OSGeo-Standards] [Board] glossary discussion on<br>
>>> osgeo-standards ....<br>
>>><br>
>>><br>
>>> Hi all,<br>
>>><br>
>>> Would someone be available to join our next board meeting to<br>
>>> discuss this issue?<br>
>>> <a href="https://wiki.osgeo.org/wiki/Board_Meeting_2019-10-28" rel="noreferrer" target="_blank">https://wiki.osgeo.org/wiki/Board_Meeting_2019-10-28</a><br>
>>><br>
>>> Regards,<br>
>>> Angelos<br>
>>><br>
>>> On 10/15/19 9:52 PM, Cameron Shorter wrote:<br>
>>><br>
>>> OSGeo Board, OSGeo Discuss,<br>
>>><br>
>>> I'd like to introduce you to this proposal that Ron and Reese<br>
>>> have been developing on the OSGeo Standards email list, which<br>
>>> I think should fit under the legal structure of an OSGeo<br>
>>> Committee.<br>
>>><br>
>>> I have vague recollections that setting up a committee<br>
>>> requires board approval? I've found some old tips on running a<br>
>>> committee here: <br>
>>> <a href="https://wiki.osgeo.org/wiki/Committee_Guidelines" rel="noreferrer" target="_blank">https://wiki.osgeo.org/wiki/Committee_Guidelines</a><br>
>>><br>
>>> Comments welcomed.<br>
>>><br>
>>> On 15/10/19 4:47 pm, Ronald Tse wrote:<br>
>>><br>
>>> Hi Cameron,<br>
>>><br>
>>> Thank you for the suggestions! I have updated the proposal<br>
>>> to reflect your comments below.<br>
>>><br>
>>> I would be honored to help with terminology management at<br>
>>> OSGeo. Can’t speak for Reese but with his leadership in<br>
>>> already doing terminology cleanup on Felicity’s sheet, he<br>
>>> seems pretty committed already :-)<br>
>>><br>
>>> Ron<br>
>>><br>
>>> ———<br>
>>><br>
>>> Recommendations for OSGeo terminology management<br>
>>><br>
>>> 1. Establish a terminology management group in OSGeo.<br>
>>><br>
>>> ISO/TC 211, IEC Electropedia and OGC all have one for<br>
>>> terminology management. The existence of this group is<br>
>>> crucial to the success of the OSGeo terminology database.<br>
>>> It will play two essential roles:<br>
>>><br>
>>> a) As the gatekeeper of terms to ensure quality checks of<br>
>>> contributions<br>
>>> b) As the seat of central terminology knowledge for<br>
>>> alignment of terms and concepts. To facilitate the flow of<br>
>>> terminology knowledge to terminology authors and users.<br>
>>><br>
>>> It would be helpful to involve representation from ISO/TC<br>
>>> 211 and OGC in this group, in order to leverage their<br>
>>> experience in terminology. Such experience will be useful<br>
>>> in situations such as alerting on cross-organization<br>
>>> alignment of concepts or term duplication.<br>
>>><br>
>>> An email list shall be setup for this group for internal<br>
>>> communication.<br>
>>><br>
>>><br>
>>> 2. Establish a terms of reference for terminology <br>
>>> management.<br>
>>><br>
>>> For the terminology management group, a terms of reference<br>
>>> should be produced so that the steps for approval and data<br>
>>> quality requirements are clear. This should be openly<br>
>>> shared with contributors so they are clear on acceptance<br>
>>> criteria.<br>
>>><br>
>>> Contributors may propose changes to the terminology<br>
>>> database at any time. The terminology management group<br>
>>> shall discuss and approve or disapprove of the proposal<br>
>>> within a reasonable timeframe. This practice is in-line<br>
>>> with the open source, change-based, rapid iteration<br>
>>> mantra, similar to OpenSSL.<br>
>>><br>
>>> For releases, the group shall convene periodically, such<br>
>>> as every 4-6 months, to discuss previously decided<br>
>>> proposals, governance or technical issues related to<br>
>>> terminology management.<br>
>>><br>
>>> The method of submitting change requests shall also be<br>
>>> determined and announced so that contributors understand<br>
>>> the necessary processes and timeline.<br>
>>><br>
>>><br>
>>> 3. Establish an online terminology database presence.<br>
>>><br>
>>> Terminology isn’t useful until people use them, which<br>
>>> means people need to first know they exist and what they<br>
>>> mean. Geolexica is an initiative that currently serves<br>
>>> ISO/TC 211’s terminology management group in making its<br>
>>> multi-lingual geographic information terminology available<br>
>>> on the internet (<a href="https://www.geolexica.org" rel="noreferrer" target="_blank">https://www.geolexica.org</a>). We propose to<br>
>>> use <a href="https://osgeo.geolexica.org/" rel="noreferrer" target="_blank">https://osgeo.geolexica.org/</a> to serve OSGeo in<br>
>>> managing its terminology database. Geolexica not only<br>
>>> serves human-readable concepts and terms, but also serves<br>
>>> in machine-readable JSON, allowing APIs to directly<br>
>>> consume the content.<br>
>>><br>
>>> The structure of Geolexica is designed for efficiency with<br>
>>> streamlined management and operations. Terms are stored in<br>
>>> structured data (YAML) files, and are directly deployable<br>
>>> to the website. The website operates according to best<br>
>>> practices, and is served as a static website with dynamic<br>
>>> search functionality. Security and performance have always<br>
>>> been key considerations.<br>
>>><br>
>>> For terms that originate from other authoritative<br>
>>> terminology databases, such as those from ISO or OGC, a<br>
>>> linkage shall be established from the OSGeo terminology<br>
>>> database back to the source.<br>
>>><br>
>>><br>
>>> 4. Use an issue tracker with source code management<br>
>>> functionality as an open communication platform (e.g.<br>
>>> GitHub).<br>
>>><br>
>>> The issue tracker is used to perform two-way communication<br>
>>> between OSGeo members and the contributors. This requires<br>
>>> every contributor to at least have an account, which helps<br>
>>> minimize spam. The source code management functionality is<br>
>>> used to manage terminology data in a machine-useable way.<br>
>>><br>
>>> There are generally two types of contributors:<br>
>>><br>
>>> a) those who suggest changes via textual description, and<br>
>>> b) those who suggest changes but can also format the<br>
>>> desired content in the data format used by the terminology<br>
>>> database.<br>
>>><br>
>>> People can easily help out with the former in formatting<br>
>>> the changes into a proper data structure change. This<br>
>>> allows the terminology management group to directly<br>
>>> approve, merge and deploy the proposed term modifications<br>
>>> (and creations, deletions), all made effective with a<br>
>>> single click.<br>
>>><br>
>>><br>
>>> 5. Allow easy feedback from terminology users.<br>
>>><br>
>>> To minimize friction in the feedback process, for every<br>
>>> term offered in the OSGeo terminology pages we can offer a<br>
>>> “propose new term” and “propose changes to this term"<br>
>>> buttons. This allows user to directly go to the issue<br>
>>> platform (e.g. GitHub) to make the suggested changes.<br>
>>><br>
>>> A “contributors guide” document will greatly help these<br>
>>> people make the proper suggestions and have them formatted<br>
>>> correctly.<br>
>>><br>
>>><br>
>>> 6. Initial load and data cleanup.<br>
>>><br>
>>> The initial load of the terms will involve a bulk load<br>
>>> from the cleaned terms and definitions that Felicity has<br>
>>> compiled. Geolexica could easily handle the initial<br>
>>> conversion from table format into the desired structured<br>
>>> data format.<br>
>>><br>
>>> The cleanup process has already been started by Reese<br>
>>> Plews, convenor of the TMG at ISO/TC 211.<br>
>>><br>
>>><br>
>>> _____________________________________<br>
>>><br>
>>> Ronald Tse<br>
>>> Ribose Inc.<br>
>>><br>
>>> On Oct 10, 2019, at 3:34 PM, Cameron Shorter<br>
>>> <<a href="mailto:cameron.shorter@gmail.com" target="_blank">cameron.shorter@gmail.com</a>> wrote:<br>
>>><br>
>>> Hi Ron,<br>
>>><br>
>>> I really like your proposal. It looks very practical,<br>
>>> should address quality requirements, and should be<br>
>>> relatively light weight to manage. Some<br>
>>> comments/suggestions:<br>
>>><br>
>>> * You might want to mention the approach to your first<br>
>>> load of terms, which probably should involve a bulk<br>
>>> load from a derivative of the terms that Felicity has<br>
>>> compiled.<br>
>>><br>
>>> * I suggest we set up an email list to discuss terms.<br>
>>> OSGeo can provide that for us, and I can coordinate<br>
>>> that, once we have agreed on our approach.<br>
>>><br>
>>> * I suggest that an updating the glossary be tied to a<br>
>>> periodic event, at least annually. I think we should<br>
>>> tie in with the OSGeoLive annual build cycle for this.<br>
>>><br>
>>> * You haven't mentioned <a href="https://osgeo.geolexica.org/" rel="noreferrer" target="_blank">https://osgeo.geolexica.org/</a><br>
>>> <<a href="https://osgeo.geolexica.org/" rel="noreferrer" target="_blank">https://osgeo.geolexica.org/</a>> in your description. I<br>
>>> assume that would be part of the solution? If so, I<br>
>>> suggest mentioning it.<br>
>>><br>
>>> * Another project I'm helping start up is<br>
>>> <a href="https://thegooddocsproject.dev/" rel="noreferrer" target="_blank">https://thegooddocsproject.dev/</a><br>
>>> <<a href="https://thegooddocsproject.dev/" rel="noreferrer" target="_blank">https://thegooddocsproject.dev/</a>> (Writing templates<br>
>>> to make good docs for open source projects). I expect<br>
>>> that the solution you are proposing would be valuable<br>
>>> for a wide variety of domains, and should be captured<br>
>>> as best practices in TheGoodDocsProject. At some point<br>
>>> in the future, I'm hoping that you might provide a<br>
>>> generic version of your suggestions for others to<br>
>>> follow too.<br>
>>><br>
>>> Feel free to add your ideas below into the wiki at:<br>
>>> <a href="https://trac.osgeo.org/osgeolive/wiki/Glossary%20terms" rel="noreferrer" target="_blank">https://trac.osgeo.org/osgeolive/wiki/Glossary%20terms</a><br>
>>><br>
>>> (Maybe add "DRAFT" at the top, until we have the<br>
>>> process set up.)<br>
>>><br>
>>> * Ron and Reese, I'm hoping that you both will<br>
>>> continue to provide the leadership and stewardship of<br>
>>> the community as it grows? Your advice has been great<br>
>>> to date.<br>
>>><br>
>>> Warm regards, Cameron<br>
>>><br>
>>><br>
>>><br>
>>> _______________________________________________<br>
>>> Standards mailing list<br>
>>> <a href="mailto:Standards@lists.osgeo.org" target="_blank">Standards@lists.osgeo.org</a><br>
>>> <a href="https://lists.osgeo.org/mailman/listinfo/standards" rel="noreferrer" target="_blank">https://lists.osgeo.org/mailman/listinfo/standards</a><br>
>>><br>
>>><br>
>>><br>
>>> _______________________________________________<br>
>>><br>
>>><br>
>>><br>
>>> Board mailing list<br>
>>> <a href="mailto:Board@lists.osgeo.org" target="_blank">Board@lists.osgeo.org</a><br>
>>> <a href="https://lists.osgeo.org/mailman/listinfo/board" rel="noreferrer" target="_blank">https://lists.osgeo.org/mailman/listinfo/board</a><br>
>>><br>
>>><br>
>>><br>
>>> --<br>
>>><br>
>>><br>
>>> Angelos Tzotsos, PhD<br>
>>><br>
>>><br>
>>><br>
>>> Charter Member<br>
>>><br>
>>><br>
>>><br>
>>> Open Source Geospatial Foundation<br>
>>> <a href="http://users.ntua.gr/tzotsos" rel="noreferrer" target="_blank">http://users.ntua.gr/tzotsos</a><br>
>>><br>
>>><br>
>>><br>
>>> -- <br>
>>> Cameron Shorter<br>
>>> Technology Demystifier<br>
>>> Open Technologies and Geospatial Consultant<br>
>>><br>
>>> M +61 (0) 419 142 254<br>
>>><br>
>>><br>
>>><br>
>>> _______________________________________________<br>
>>> Board mailing list<br>
>>> <a href="mailto:Board@lists.osgeo.org" target="_blank">Board@lists.osgeo.org</a><br>
>>> <a href="https://lists.osgeo.org/mailman/listinfo/board" rel="noreferrer" target="_blank">https://lists.osgeo.org/mailman/listinfo/board</a><br>
>>><br>
>>><br>
>>><br>
>>> -- <br>
>>> Angelos Tzotsos, PhD<br>
>>> Charter Member<br>
>>> Open Source Geospatial Foundation<br>
>>> <a href="http://users.ntua.gr/tzotsos" rel="noreferrer" target="_blank">http://users.ntua.gr/tzotsos</a><br>
>>><br>
>>> _______________________________________________<br>
>>> Board mailing list<br>
>>> <a href="mailto:Board@lists.osgeo.org" target="_blank">Board@lists.osgeo.org</a><br>
>>> <a href="https://lists.osgeo.org/mailman/listinfo/board" rel="noreferrer" target="_blank">https://lists.osgeo.org/mailman/listinfo/board</a><br>
><br>
<br>
<br>
-- <br>
Angelos Tzotsos, PhD<br>
Charter Member<br>
Open Source Geospatial Foundation<br>
<a href="http://users.ntua.gr/tzotsos" rel="noreferrer" target="_blank">http://users.ntua.gr/tzotsos</a><br>
<br>
</blockquote></div><br clear="all"><div><br></div>-- <br><div dir="ltr" class="gmail_signature"><div dir="ltr"><div><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div><div><span style="font-size:12.8px">Cameron Shorter</span><br></div><div>Technology Demystifier</div><div>Open Technologies and Geospatial Consultant</div><div><br></div><div>M +61 (0) 419 142 254</div><div><br></div></div><div><br><br></div></div></div></div></div></div></div></div></div>