<div dir="ltr">Jorge,<div>The decision making process we set up is based on other OSGeo projects (and other open source projects), and written here:</div><div><a href="https://wiki.osgeo.org/wiki/Lexicon_Committee#Decisions">https://wiki.osgeo.org/wiki/Lexicon_Committee#Decisions</a><br></div><div><br></div><div>It is basically the principle of do-ocracy. If you are prepared to do the work, and you appear to know what you are talking about, then you get to make the decisions.</div><div><br></div><div>What is basically saying "Thanks for your interest and contributions, we encourage you to continue with your enthusiasm, and want to make space for you to push through on ideas you have, and support you where we can."</div><div><br></div><div>My personal involvement is minimal at the moment. At some point in the future I'm hoping that we can signal boost what you develop at the OSGeo level into the greater Open Source Technical Writing space (through The Good Docs Project).</div><div><br></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Wed, 8 Jul 2020 at 03:28, Reese Plews (ISO/TC211 - TMG) <<a href="mailto:rplews@tc211tmg.org">rplews@tc211tmg.org</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">hello Jorge,<br>
<br>
thank you very much for your interest in the Lexicon Group.<br>
<br>
i was working a couple months back with Cameron and Ron to prepare some <br>
initial documents on how the group may "operate." you can see them at <br>
the following links.<br>
<br>
<a href="https://docs.google.com/document/d/1wdthaqg2ag-GMharAMZO8xSVK5IH1IXQvtCW5YOF6Cw/edit?usp=sharing" rel="noreferrer" target="_blank">https://docs.google.com/document/d/1wdthaqg2ag-GMharAMZO8xSVK5IH1IXQvtCW5YOF6Cw/edit?usp=sharing</a><br>
<br>
<a href="https://docs.google.com/document/d/1s3mnlXc7E41olpqSO24x7c_sfg4UtZSHy-r7xnJfNOw/edit?usp=sharing" rel="noreferrer" target="_blank">https://docs.google.com/document/d/1s3mnlXc7E41olpqSO24x7c_sfg4UtZSHy-r7xnJfNOw/edit?usp=sharing</a><br>
<br>
earlier in the spring we had a telecon to discuss some initial <br>
abbreviated terms and acronyms and wanted to get those cleaned up and <br>
categorized. after that, issues with the virus and other matters took <br>
precedence and i have not had much time to try and work on the file or <br>
communicate with the members.<br>
<br>
<a href="https://docs.google.com/spreadsheets/d/1nFOa7qE309C6rbnhJXd0EjUKEiqCDYvgpCJpyTjbhmo/edit?usp=sharing" rel="noreferrer" target="_blank">https://docs.google.com/spreadsheets/d/1nFOa7qE309C6rbnhJXd0EjUKEiqCDYvgpCJpyTjbhmo/edit?usp=sharing</a><br>
<br>
<a href="https://docs.google.com/document/d/1-ArCFVj38Jsg7qD-90JybI74810hRi_w03GzLjVHZLo/edit?usp=sharing" rel="noreferrer" target="_blank">https://docs.google.com/document/d/1-ArCFVj38Jsg7qD-90JybI74810hRi_w03GzLjVHZLo/edit?usp=sharing</a><br>
<br>
in the initial documents that were prepared, i tried to model some <br>
aspects of how this group may operate similar to how ISO/TC 211 manages <br>
terminology entries. however there are two major differences between ISO <br>
terminology activities and how i assumed those in OSGEO may operate. it <br>
stands to reason there would be differences as the focus of the groups <br>
are different.<br>
<br>
for me, the questions that need more discussion or are perhaps <br>
unanswered: 1) how does this group identify terminology entries, and 2) <br>
how can the OSGEO members or others collaborate or be involved with <br>
feedback on the proposed entries. the documents made some proposals but <br>
testing and discussions were still needed.<br>
<br>
in addition to the abbreviated terms and acronyms there are some <br>
collected terms in that spreadsheet (other worksheet) and the group was <br>
going to consider how to address them after the work on the abbreviated <br>
terms and acronyms was finished.<br>
<br>
after a terminology entry was "approved by the group" it could be <br>
translated. a number of members were interested in this translation <br>
aspect. however, approved entries were needed first.<br>
<br>
the glossarist app which you have discovered is being developed by Ron <br>
and his team to aid in terminology translation in TC211 and elsewhere. <br>
it conforms to a number of ISO terminology standards and will be used <br>
for members in TC211 to translate terminology entries for the ISO/TC 211 <br>
Multi-Lingual Glossary of Terms (MLGT) of which a new edition was <br>
released in early June.<br>
<br>
<a href="https://isotc211.geolexica.org/" rel="noreferrer" target="_blank">https://isotc211.geolexica.org/</a><br>
<br>
or in excel & word<br>
<br>
<a href="https://github.com/ISO-TC211/TMG/releases" rel="noreferrer" target="_blank">https://github.com/ISO-TC211/TMG/releases</a><br>
<br>
you can browse the MLGT directly using the Geolexica Framework, also <br>
developed by Ron's team.<br>
<br>
OSGeo's geolexica prototype site is available and will be used by OSGEO <br>
when terms are "approved", by the lexicon group. after that, those <br>
approved terms would be available for translation through the glossarist <br>
app. however a similar discussion and approval process for the <br>
translated terms should be undertaken by translators of the same <br>
language. in tc211 the national members organize these groups.<br>
<br>
i look forward to hearing from you along with your feedback on the <br>
documents listed above. thank you for your interest in the group.<br>
<br>
best regards,<br>
<br>
reese plews<br>
convenor<br>
iso/tc211 terminology maintenance group (TMG)<br>
<a href="https://github.com/ISO-TC211/TMG" rel="noreferrer" target="_blank">https://github.com/ISO-TC211/TMG</a><br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
---<br>
<br>
<br>
On 2020-07-08 00:12, Jorge Gustavo Rocha wrote:<br>
> Hi Ron,<br>
> <br>
> Thanks for the feedback. Now I think I understood the entire workflow<br>
> (which is really the usual git workflow). I think it is a very nice way<br>
> to have people contributing to the terminology in a open and <br>
> transparent<br>
> way. For developers, the workflow is quite simple.<br>
> <br>
> I'll wait for the update to the osgeo-glossary repo.<br>
> <br>
> By the way, who will have permission to merge PR on this osgeo-glossary<br>
> repo? Is this already defined?<br>
> <br>
> Regards,<br>
> <br>
> Jorge<br>
> <br>
> On 07/07/20 11:21, Ronald Tse wrote:<br>
>> Hi Jorge,<br>
>> <br>
>> Thank you for trying out Glossarist! <br>
>> <br>
>> Actually the OSGeo glossary repository needs to be updated to suit the<br>
>> latest version of Glossarist — which we are going to do so today. The<br>
>> current repo is using an older data schema. The unexpected diffs are <br>
>> due<br>
>> to this reason.<br>
>> <br>
>> In order to submit change requests, you will need write access to the<br>
>> repository. Should the group discuss about it?<br>
>> <br>
>> Now to the questions:<br>
>>> 2) To change something, I must start a change request and make my<br>
>>> changes, right?<br>
>> <br>
>> Yes, you’re right. A change request can contain multiple changes.<br>
>> <br>
>>> 3) Afterwards, in my local<br>
>>> ~/.config/Electron/glossarist-database/change-requests I have the<br>
>>> changes from my change request.<br>
>> <br>
>> Correct. The git “upstream” remote is a deprecated artifact, it will <br>
>> be<br>
>> removed in the next version of Glossarist.<br>
>> <br>
>>> 4) Question: If I want to contribute to the OSGeo terminology, what<br>
>>> should I do next?<br>
>>> <br>
>>> Should I push my changes from the command line or there is some <br>
>>> button<br>
>>> on Glossarist to submit the change request?<br>
>> <br>
>> Glossarist has the Review pane where you can “Propose” a CR, after <br>
>> which<br>
>> you can “Sync” (top left of window) — it will upload the CR.<br>
>> <br>
>> In this case, since you don’t have direct write access, you could:<br>
>> 1. First, work on your fork of the repository — i.e. fork<br>
>> <a href="https://github.com/geolexica/osgeo-glossary" rel="noreferrer" target="_blank">https://github.com/geolexica/osgeo-glossary</a> , and make that your new<br>
>> remote in Glossarist.<br>
>> 2. Create a CR in your own fork<br>
>> 3. Make a Pull Request to submit your CR to the master branch of<br>
>> <a href="https://github.com/geolexica/osgeo-glossary" rel="noreferrer" target="_blank">https://github.com/geolexica/osgeo-glossary</a><br>
>> 4. Whoever has access to merge can bring in your CR to master and<br>
>> review/approve the CR.<br>
>> <br>
>> Would you mind waiting until tomorrow for the new version of <br>
>> Glossarist<br>
>> (due tonight) and the upgrade of the data repo schema?<br>
>> <br>
>> Thanks!<br>
>> <br>
>> Ron<br>
>> <br>
>> _____________________________________<br>
>> <br>
>> Ronald Tse<br>
>> Ribose Inc.<br>
>> <br>
>> +=========================================================+<br>
>> This message may contain confidential and/or privileged<br>
>> information. If you are not the addressee or authorized to<br>
>> receive this for the addressee, you must not use, copy,<br>
>> disclose or take any action based on this message or any<br>
>> information herein. If you have received this message in<br>
>> error, please advise the sender immediately by reply e-mail<br>
>> and delete this message. Thank you for your cooperation.<br>
>> +=========================================================+<br>
>> <br>
>>> On Jul 7, 2020, at 5:03 PM, Jorge Gustavo Rocha <<a href="mailto:jgr@osgeopt.pt" target="_blank">jgr@osgeopt.pt</a><br>
>>> <mailto:<a href="mailto:jgr@osgeopt.pt" target="_blank">jgr@osgeopt.pt</a>>> wrote:<br>
>>> <br>
>>> Hi all,<br>
>>> <br>
>>> I've clone the Glossarist desktop tool repo and started to use it. It<br>
>>> work pretty well on my Ubuntu. Thanks for those working on it.<br>
>>> <br>
>>> I would like to understand the workflow behind it and how can we use <br>
>>> it<br>
>>> in OSGeo.<br>
>>> <br>
>>> 1) I've started Glossarist, identified my self with my Github <br>
>>> account. I<br>
>>> can browse existent entries and the application is working smoothly.<br>
>>> Great!<br>
>>> <br>
>>> 2) To change something, I must start a change request and make my<br>
>>> changes, right?<br>
>>> <br>
>>> 3) Afterwards, in my local<br>
>>> ~/.config/Electron/glossarist-database/change-requests I have the<br>
>>> changes from my change request.<br>
>>> <br>
>>> The folder ~/.config/Electron/glossarist-database is under git <br>
>>> control<br>
>>> (setup done by Glossarist).<br>
>>> <br>
>>> The remote repos are:<br>
>>> <br>
>>> jgr@zoe:~/.config/Electron/glossarist-database$ git remote -v<br>
>>> originhttps://<a href="http://github.com/geolexica/osgeo-glossary" rel="noreferrer" target="_blank">github.com/geolexica/osgeo-glossary</a> (fetch)<br>
>>> originhttps://<a href="http://github.com/geolexica/osgeo-glossary" rel="noreferrer" target="_blank">github.com/geolexica/osgeo-glossary</a> (push)<br>
>>> upstreamhttps://<a href="http://github.com/ISO-TC211/geolexica-database" rel="noreferrer" target="_blank">github.com/ISO-TC211/geolexica-database</a> (fetch)<br>
>>> upstreamhttps://<a href="http://github.com/ISO-TC211/geolexica-database" rel="noreferrer" target="_blank">github.com/ISO-TC211/geolexica-database</a> (push)<br>
>>> <br>
>>> 4) Question: If I want to contribute to the OSGeo terminology, what<br>
>>> should I do next?<br>
>>> <br>
>>> Should I push my changes from the command line or there is some <br>
>>> button<br>
>>> on Glossarist to submit the change request?<br>
>>> <br>
>>> Note: All local files were rewritten and git reports changes in all<br>
>>> terms. I didn't expect such changes. As far as I can understand, git<br>
>>> should report only changes in `change-requests` folder, right?<br>
>>> <br>
>>> My local --stats are:<br>
>>> <br>
>>> jgr@zoe:~/.config/Electron/glossarist-database$ git diff --stat <br>
>>> --cached<br>
>>> origin/master | head -10<br>
>>> change-requests/7a5c63.yaml | 37 +++++++++++++<br>
>>> change-requests/bd20b0.yaml | 61 ++++++++++++++++++++++<br>
>>> concepts/concept-1.yaml | 30 +++++++++--<br>
>>> concepts/concept-10.yaml | 30 +++++++++--<br>
>>> concepts/concept-100.yaml | 30 +++++++++--<br>
>>> concepts/concept-101.yaml | 30 +++++++++--<br>
>>> concepts/concept-102.yaml | 30 +++++++++--<br>
>>> concepts/concept-103.yaml | 30 +++++++++--<br>
>>> concepts/concept-104.yaml | 30 +++++++++--<br>
>>> concepts/concept-105.yaml | 30 +++++++++--<br>
>>> <br>
>>> Unexpected changes (for me!) are like this one:<br>
>>> <br>
>>> jgr@zoe:~/.config/Electron/glossarist-database$ git diff --cached<br>
>>> origin/master concepts/concept-10.yaml<br>
>>> diff --git a/concepts/concept-10.yaml b/concepts/concept-10.yaml<br>
>>> index 0c68c10..54ae114 100644<br>
>>> --- a/concepts/concept-10.yaml<br>
>>> +++ b/concepts/concept-10.yaml<br>
>>> @@ -1,4 +1,3 @@<br>
>>> ----<br>
>>> term: AM/FM<br>
>>> termid: 10<br>
>>> eng:<br>
>>> @@ -8,8 +7,29 @@ eng:<br>
>>> notes: []<br>
>>> examples: []<br>
>>> authoritative_source:<br>
>>> - link:<br>
>>> <a href="https://www.osgeo.org/wp-content/uploads/Newsletter-Vol-5_01.pdf" rel="noreferrer" target="_blank">https://www.osgeo.org/wp-content/uploads/Newsletter-Vol-5_01.pdf</a><br>
>>> + link:<br>
>>> '<a href="https://www.osgeo.org/wp-content/uploads/Newsletter-Vol-5_01.pdf" rel="noreferrer" target="_blank">https://www.osgeo.org/wp-content/uploads/Newsletter-Vol-5_01.pdf</a>'<br>
>>> terms:<br>
>>> - - type: expression<br>
>>> - designation: AM/FM<br>
>>> - normative_status:<br>
>>> + - type: expression<br>
>>> + designation: AM/FM<br>
>>> + normative_status: null<br>
>>> + _revisions:<br>
>>> + current: 0c7724<br>
>>> + tree:<br>
>>> + 0c7724:<br>
>>> + object:<br>
>>> + id: 10<br>
>>> + definition: Automated Mapping/Facilities Management<br>
>>> + language_code: eng<br>
>>> + notes: []<br>
>>> + examples: []<br>
>>> + authoritative_source:<br>
>>> + link:<br>
>>> '<a href="https://www.osgeo.org/wp-content/uploads/Newsletter-Vol-5_01.pdf" rel="noreferrer" target="_blank">https://www.osgeo.org/wp-content/uploads/Newsletter-Vol-5_01.pdf</a>'<br>
>>> + terms:<br>
>>> + - type: expression<br>
>>> + designation: AM/FM<br>
>>> + normative_status: null<br>
>>> + parents: []<br>
>>> + timeCreated: 2020-07-06T21:28:14.660Z<br>
>>> + author:<br>
>>> + name: Glossarist bot<br>
>>> + email: <a href="mailto:glossarist@ribose.com" target="_blank">glossarist@ribose.com</a> <br>
>>> <mailto:<a href="mailto:glossarist@ribose.com" target="_blank">glossarist@ribose.com</a>><br>
>>> <br>
>>> Sorry for this newbie question.<br>
>>> <br>
>>> But soon as I understand the workflow, I can write a short tutorial<br>
>>> about how to use Glossarist to maintain and improve OSGeo <br>
>>> terminology.<br>
>>> <br>
>>> Regards,<br>
>>> <br>
>>> Jorge<br>
>>> <br>
>>> <br>
>>> On 04/07/20 13:47, Richard Duivenvoorde wrote:<br>
>>>> Nice Nice!!!<br>
>>>> <br>
>>>> And good to lift this to an higher (OSGeo) plan!!<br>
>>>> <br>
>>>> Go go! :-)<br>
>>>> <br>
>>>> Regards,<br>
>>>> <br>
>>>> Richard Duivenvoorde<br>
>>>> <br>
>>>> (bcc to our dutch translation master)<br>
>>>> <br>
>>>> On 7/4/20 11:01 AM, Jorge Gustavo Rocha wrote:<br>
>>>>> Hi Ron,<br>
>>>>> <br>
>>>>> Thank you for the update.<br>
>>>>> <br>
>>>>> I've looked in the current <a href="https://osgeodev.geolexica.org" rel="noreferrer" target="_blank">https://osgeodev.geolexica.org</a> and on <br>
>>>>> yours<br>
>>>>> Glossarist desktop tool. Looks like very promising.<br>
>>>>> <br>
>>>>> OSGeo and QGIS in particular would benefit from such a well defined<br>
>>>>> glossary.<br>
>>>>> <br>
>>>>> I'll be watching the project. I'll try to contribute with build<br>
>>>>> instructions for Linux :-)<br>
>>>>> <br>
>>>>> Best regards,<br>
>>>>> <br>
>>>>> Jorge<br>
>>>>> <br>
>>>>> On 04/07/20 04:56, Ronald Tse wrote:<br>
>>>>>> Hi Jorge,<br>
>>>>>> <br>
>>>>>> Thank you for spreading the news!<br>
>>>>>> <br>
>>>>>> The current development site with loaded terms is located here:<br>
>>>>>> <a href="https://osgeodev.geolexica.org" rel="noreferrer" target="_blank">https://osgeodev.geolexica.org</a><br>
>>>>>> <br>
>>>>>> I believe the group is still waiting for some confirmation on<br>
>>>>>> terminology across OSGeo. As you can see on the site, a number of<br>
>>>>>> conflicting definitions exist and the group would need some effort <br>
>>>>>> to<br>
>>>>>> discuss and attempt to settle these — since they are used across<br>
>>>>>> different OSGeo projects.<br>
>>>>>> <br>
>>>>>> Geolexica has also been working with ISO/TC 211 on their latest <br>
>>>>>> efforts<br>
>>>>>> in translating the 5th edition of the TC 211 Multi-Lingual <br>
>>>>>> Glossary of<br>
>>>>>> Terms (MLGT). There is now have a desktop application for managing<br>
>>>>>> translations through change requests, all based off a git <br>
>>>>>> repository on<br>
>>>>>> GitHub:<br>
>>>>>> <a href="https://www.glossarist.org" rel="noreferrer" target="_blank">https://www.glossarist.org</a><br>
>>>>>> <br>
>>>>>> I agree that more love is needed to the lexicon group to move<br>
>>>>>> things ahead!<br>
>>>>>> <br>
>>>>>> Kind regards,<br>
>>>>>> Ron<br>
>>>>>> <br>
>>>>>> _____________________________________<br>
>>>>>> <br>
>>>>>> Ronald Tse<br>
>>>>>> Ribose Inc.<br>
>>>>>> <br>
>>>>>> +=========================================================+<br>
>>>>>> This message may contain confidential and/or privileged<br>
>>>>>> information. If you are not the addressee or authorized to<br>
>>>>>> receive this for the addressee, you must not use, copy,<br>
>>>>>> disclose or take any action based on this message or any<br>
>>>>>> information herein. If you have received this message in<br>
>>>>>> error, please advise the sender immediately by reply e-mail<br>
>>>>>> and delete this message. Thank you for your cooperation.<br>
>>>>>> +=========================================================+<br>
>>>>>> <br>
>>>>>>> On Jul 4, 2020, at 6:23 AM, Jorge Gustavo Rocha <<a href="mailto:jgr@di.uminho.pt" target="_blank">jgr@di.uminho.pt</a><br>
>>>>>>> <mailto:<a href="mailto:jgr@di.uminho.pt" target="_blank">jgr@di.uminho.pt</a>>> wrote:<br>
>>>>>>> <br>
>>>>>>> Hi Ian, hi all,<br>
>>>>>>> <br>
>>>>>>> There are people trying to run an OSGeo "Interest group" on<br>
>>>>>>> "Terminology", to be transversal to all OSGeo projects.<br>
>>>>>>> <br>
>>>>>>> They created a proof of concept, called "geolexica", available <br>
>>>>>>> at:<br>
>>>>>>> <br>
>>>>>>> <a href="https://osgeo.geolexica.org/concepts/" rel="noreferrer" target="_blank">https://osgeo.geolexica.org/concepts/</a><br>
>>>>>>> <br>
>>>>>>> Sources on: <a href="https://github.com/geolexica/osgeo.geolexica.org" rel="noreferrer" target="_blank">https://github.com/geolexica/osgeo.geolexica.org</a><br>
>>>>>>> <br>
>>>>>>> It would be awesome if we were able to fill the translation for <br>
>>>>>>> the<br>
>>>>>>> different languages associated with the English concept, right on <br>
>>>>>>> the<br>
>>>>>>> origin.<br>
>>>>>>> <br>
>>>>>>> As far I as know (I'm cc to lexica group), this project needs <br>
>>>>>>> some<br>
>>>>>>> additional "love" to go on.<br>
>>>>>>> <br>
>>>>>>> Maybe Cameron (in cc) or someone else can make an update on the<br>
>>>>>>> lexicon<br>
>>>>>>> activities/plans.<br>
>>>>>>> <br>
>>>>>>> Regards,<br>
>>>>>>> <br>
>>>>>>> Jorge<br>
>>>>>>> <br>
>>>>>>> On 30/06/20 10:57, Ian Turton wrote:<br>
>>>>>>>> <br>
>>>>>>>> <br>
>>>>>>>> On Tue, 30 Jun 2020 at 10:40, Bo Victor Thomsen<br>
>>>>>>>> <<a href="mailto:bo.victor.thomsen@gmail.com" target="_blank">bo.victor.thomsen@gmail.com</a><br>
>>>>>>>> <mailto:<a href="mailto:bo.victor.thomsen@gmail.com" target="_blank">bo.victor.thomsen@gmail.com</a>>> wrote:<br>
>>>>>>>> <br>
>>>>>>>> Dear developers:<br>
>>>>>>>> <br>
>>>>>>>> As a former translator of the Danish version of QGIS I have a<br>
>>>>>>>> few -<br>
>>>>>>>> very personal, perhaps a bit caustic - comments:<br>
>>>>>>>> <br>
>>>>>>>> * Create a group or list of highly technical GIS related <br>
>>>>>>>> terms<br>
>>>>>>>> that is *not* to be translated. There is a lot of GIS<br>
>>>>>>>> terms that<br>
>>>>>>>> is English in origin, but haven't a well defined local<br>
>>>>>>>> translation. (With some hilarious results if they are<br>
>>>>>>>> translated). Not all translators is well versed in every<br>
>>>>>>>> aspect<br>
>>>>>>>> of GIS. <br>
>>>>>>>> <br>
>>>>>>>> <br>
>>>>>>>> <br>
>>>>>>>> Is this something that OSGEO can help to oversee and/or maintain <br>
>>>>>>>> as I<br>
>>>>>>>> suspect that this list would be useful across many projects.<br>
>>>>>>>> <br>
>>>>>>>> Ian <br>
>>>>>>>> <br>
>>>>>>>> --<br>
>>>>>>>> Ian Turton<br>
>>>>>>>> <br>
>>>>>>>> _______________________________________________<br>
>>>>>>>> QGIS-Developer mailing list<br>
>>>>>>>> <a href="mailto:QGIS-Developer@lists.osgeo.org" target="_blank">QGIS-Developer@lists.osgeo.org</a><br>
>>>>>>>> List info: <br>
>>>>>>>> <a href="https://lists.osgeo.org/mailman/listinfo/qgis-developer" rel="noreferrer" target="_blank">https://lists.osgeo.org/mailman/listinfo/qgis-developer</a><br>
>>>>>>>> Unsubscribe: <br>
>>>>>>>> <a href="https://lists.osgeo.org/mailman/listinfo/qgis-developer" rel="noreferrer" target="_blank">https://lists.osgeo.org/mailman/listinfo/qgis-developer</a><br>
>>>>>>>> <br>
>>>>>>> <br>
>>>>>>> J. Gustavo<br>
>>>>>>> --<br>
>>>>>>> Jorge Gustavo Rocha<br>
>>>>>>> Departamento de Informática<br>
>>>>>>> Universidade do Minho<br>
>>>>>>> 4710-057 Braga<br>
>>>>>>> Gabinete 3.29 (Piso 3)<br>
>>>>>>> Tel: +351 253604480<br>
>>>>>>> Fax: +351 253604471<br>
>>>>>>> Móvel: +351 910333888<br>
>>>>>>> skype: nabocudnosor<br>
>>>>>>> _______________________________________________<br>
>>>>>>> Lexicon mailing list<br>
>>>>>>> <a href="mailto:Lexicon@lists.osgeo.org" target="_blank">Lexicon@lists.osgeo.org</a><br>
>>>>>>> <a href="https://lists.osgeo.org/mailman/listinfo/lexicon" rel="noreferrer" target="_blank">https://lists.osgeo.org/mailman/listinfo/lexicon</a><br>
>>>>>> <br>
>>>>> <br>
>>>>> J. Gustavo<br>
>>>>> <br>
>>>> <br>
>>>> _______________________________________________<br>
>>>> Lexicon mailing list<br>
>>>> <a href="mailto:Lexicon@lists.osgeo.org" target="_blank">Lexicon@lists.osgeo.org</a> <mailto:<a href="mailto:Lexicon@lists.osgeo.org" target="_blank">Lexicon@lists.osgeo.org</a>><br>
>>>> <a href="https://lists.osgeo.org/mailman/listinfo/lexicon" rel="noreferrer" target="_blank">https://lists.osgeo.org/mailman/listinfo/lexicon</a><br>
>>>> <br>
>>> <br>
>>> --<br>
>>> OSGeo Portugal<br>
>>> NIF: 509588190<br>
>>> email: <a href="mailto:geral@osgeopt.pt" target="_blank">geral@osgeopt.pt</a> <mailto:<a href="mailto:geral@osgeopt.pt" target="_blank">geral@osgeopt.pt</a>><br>
>>> <a href="https://www.osgeopt.pt/" rel="noreferrer" target="_blank">https://www.osgeopt.pt/</a><br>
>>> <br>
>>> Próximo evento: SASIG 2017, 20 a 22 de novembro, Porto<br>
>>> Mais informações: <a href="http://osgeopt.pt/sasig2017/" rel="noreferrer" target="_blank">http://osgeopt.pt/sasig2017/</a><br>
>>> _______________________________________________<br>
>>> Lexicon mailing list<br>
>>> <a href="mailto:Lexicon@lists.osgeo.org" target="_blank">Lexicon@lists.osgeo.org</a><br>
>>> <a href="https://lists.osgeo.org/mailman/listinfo/lexicon" rel="noreferrer" target="_blank">https://lists.osgeo.org/mailman/listinfo/lexicon</a><br>
>> <br>
_______________________________________________<br>
Lexicon mailing list<br>
<a href="mailto:Lexicon@lists.osgeo.org" target="_blank">Lexicon@lists.osgeo.org</a><br>
<a href="https://lists.osgeo.org/mailman/listinfo/lexicon" rel="noreferrer" target="_blank">https://lists.osgeo.org/mailman/listinfo/lexicon</a><br>
</blockquote></div><br clear="all"><div><br></div>-- <br><div dir="ltr" class="gmail_signature"><div dir="ltr"><div><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>Technical Writer, Google</div></div><div><br><br></div></div></div></div></div></div></div></div></div></div></div>