<div dir="ltr"><div dir="ltr"><a class="gmail_plusreply" id="plusReplyChip-0" href="mailto:lexicon@lists.osgeo.org" tabindex="-1">+lexicon@lists.osgeo.org</a> <div><br></div><div>Looping in the OSGeo lexicon list (which has the other Glossary pilot participants).</div><div><br></div><div>Hi Vaclav,</div><div>Sorry for the delayed response. I was interrupted while responding, then this fell under a bunch of todos.</div><div><br></div><div>Yes, I'm very hopeful that our community and processes we are developing will help you folks in GRASS, although I want to be careful we don't over promise.</div><div>We also have plenty of questions in this space - but we also have commitment and expertise to work through these problems.</div><div><br></div><div>Re "what process will look like?":</div><div>I'd suggest:</div><div>* Ankita and Naini (tech writers) can help review how your terms are written and provide feedback if needed. Reese also from OGC and ISO/TC211 who has deep experience in writing spatial terms.</div><div>* We are standing up an OSGeo glossary software using Glossarist open source software. We can either include GRASS terms in there, and harmonize with existing terms, or stand up a separate GRASS glossary (see discussion below). Ron, the main software author should be able to help with this.</div><div>* We should set up a governance process. We want to write generic processes that others can customize. I'm hoping the GRASS project can work with us to help pilot that.</div><div><br></div><div>Timeframe for this will be to have something ready by ~ February/March 2021</div><div><br></div><div><br></div><div>Further from our <a href="https://join.slack.com/t/thegooddocs/shared_invite/enQtODkyNjI5MDc0NjE0LTUyNGFiZmU1MjIzNDMwN2E3NmQwODQwZmRkYWI5MDhlMzdjYzg4Nzg4YjM3ODA0NGE4MTgyYzdkMGViMTI2MDM">slack chat</a> (in case you haven't seen it):</div><div><br></div><div><div class="gmail-c-virtual_list__item" tabindex="-1" id="gmail-1606162670.012500" style="box-sizing:inherit;width:632.995px;color:rgb(29,28,29);font-family:Slack-Lato,appleLogo,sans-serif;font-size:15px;font-variant-ligatures:common-ligatures"><div class="gmail-c-message_kit__background gmail-c-message_kit__background--hovered gmail-p-message_pane_message__message gmail-c-message_kit__message" style="box-sizing:inherit;line-height:1.46668"><div class="gmail-c-message_kit__hover gmail-c-message_kit__hover--hovered" style="box-sizing:inherit"><div class="gmail-c-message_kit__actions gmail-c-message_kit__actions--default" style="box-sizing:inherit"><div class="gmail-c-message_kit__gutter" style="box-sizing:inherit;display:flex;padding:8px 20px"><div class="gmail-c-message_kit__gutter__right" style="box-sizing:inherit;min-width:0px;padding:8px 8px 8px 16px"><span class="gmail-c-message__sender gmail-c-message_kit__sender" style="box-sizing:inherit;font-weight:900;word-break:break-word"><a target="_blank" rel="noopener noreferrer" class="gmail-c-link gmail-c-message__sender_link" href="https://app.slack.com/team/UKTGLQNGG" style="box-sizing:inherit;text-decoration-line:none;display:inline-block">cameronshorter<span class="gmail-c-opens_in_new_tab" style="box-sizing:inherit"></span></a></span> <a class="gmail-c-link gmail-c-timestamp" href="https://thegooddocs.slack.com/archives/C019A1EQJMC/p1606162670012500" style="box-sizing:inherit;text-decoration-line:none;font-size:12px"><span class="gmail-c-timestamp__label" style="box-sizing:inherit">7:17 AM</span></a><br style="box-sizing:inherit"><div class="gmail-c-message_kit__blocks gmail-c-message_kit__blocks--rich_text" style="box-sizing:inherit;max-width:none;margin-bottom:4px"><div class="gmail-c-message__message_blocks gmail-c-message__message_blocks--rich_text" style="box-sizing:inherit;max-width:none"><div class="gmail-p-block_kit_renderer" style="box-sizing:inherit;width:549.002px"><div class="gmail-p-block_kit_renderer__block_wrapper gmail-p-block_kit_renderer__block_wrapper--first" style="box-sizing:inherit;display:flex"><div class="gmail-p-rich_text_block" dir="auto" style="box-sizing:inherit;width:549.002px;line-height:1.46668"><div class="gmail-p-rich_text_section" style="box-sizing:inherit">This is really valuable feedback <span dir="ltr" style="box-sizing:inherit"><a class="gmail-c-link gmail-c-member_slug gmail-c-member_slug--light gmail-c-member_slug--link" tabindex="0" href="https://thegooddocs.slack.com/team/U01ABLZMV7E" rel="noopener noreferrer" style="box-sizing:inherit;text-decoration-line:none;padding:0px 2px 1px;border-radius:3px">@Codrina Maria Ilie</a></span>. Thankyou for coordinating this. I believe we have enough information in here already that we could set up a GRASS collection of terms. As we are only doing a pilot, we could be using dummy terms, but using these GRASS terms is so much better. It is going to help us uncover use cases. In particular, GRASS have highlighted a use case I hadn't considered - where the same concept is called different things by different organizations. (In GRASS's case, it is difference between ESRI and GRASS). It seems obvious when we write it down.<br style="box-sizing:inherit">We have the option of creating a GRASS collection inside the OSGeo terms, or to stand up a separate GRASS glossary, and then we can work through the painful use case of trying to rationalize two glossaries. (Which I think is a use case worth pursuing) . It shouldn't be too much effort from the GRASS community, but will be a lot of effort for us around setting up the processes for integrating glossaries.<span class="gmail-c-message__edited_label" dir="ltr" style="box-sizing:inherit;font-size:13px;white-space:nowrap"> (edited) </span></div></div></div></div></div></div></div></div><div class="gmail-c-message_actions__container gmail-c-message__actions" style="box-sizing:inherit;display:inline-flex"><div class="gmail-c-message_actions__group" style="box-sizing:inherit;line-height:1;margin-left:8px;border:unset;display:flex;padding:2px;border-radius:0.375em"><button class="gmail-c-button-unstyled gmail-c-icon_button gmail-c-icon_button--light gmail-c-icon_button--size_small gmail-c-message_actions__button" type="button" style="box-sizing:inherit;padding:0px;background-image:none;background-position:initial;background-size:initial;background-repeat:initial;background-origin:initial;background-clip:initial;border-width:0px;border-style:initial;border-color:initial;font:inherit;margin:0px;overflow:initial;text-align:initial;vertical-align:initial;border-radius:4px;display:inline-flex;height:32px;width:32px"><i class="gmail-c-icon gmail-c-icon--add-reaction" type="add-reaction" style="box-sizing:inherit;display:inline-flex;width:20px;height:20px"></i></button><button class="gmail-c-button-unstyled gmail-c-icon_button gmail-c-icon_button--light gmail-c-icon_button--size_small gmail-c-message_actions__button" type="button" style="box-sizing:inherit;padding:0px;background-image:none;background-position:initial;background-size:initial;background-repeat:initial;background-origin:initial;background-clip:initial;border-width:0px;border-style:initial;border-color:initial;font:inherit;margin:0px;overflow:initial;text-align:initial;vertical-align:initial;border-radius:4px;display:inline-flex;height:32px;width:32px"><i class="gmail-c-icon gmail-c-icon--comment-alt" type="comment-alt" style="box-sizing:inherit;display:inline-flex;width:20px;height:20px"></i></button><button class="gmail-c-button-unstyled gmail-c-icon_button gmail-c-icon_button--light gmail-c-icon_button--size_small gmail-c-message_actions__button" type="button" style="box-sizing:inherit;padding:0px;background-image:none;background-position:initial;background-size:initial;background-repeat:initial;background-origin:initial;background-clip:initial;border-width:0px;border-style:initial;border-color:initial;font:inherit;margin:0px;overflow:initial;text-align:initial;vertical-align:initial;border-radius:4px;display:inline-flex;height:32px;width:32px"><i class="gmail-c-icon gmail-c-icon--forward" type="forward" style="box-sizing:inherit;display:inline-flex;width:20px;height:20px"></i></button><button class="gmail-c-button-unstyled gmail-c-icon_button gmail-c-icon_button--light gmail-c-icon_button--size_small gmail-c-message_actions__button" type="button" style="box-sizing:inherit;padding:0px;background-image:none;background-position:initial;background-size:initial;background-repeat:initial;background-origin:initial;background-clip:initial;border-width:0px;border-style:initial;border-color:initial;font:inherit;margin:0px;overflow:initial;text-align:initial;vertical-align:initial;border-radius:4px;display:inline-flex;height:32px;width:32px"><i class="gmail-c-icon gmail-c-icon--bookmark" type="bookmark" style="box-sizing:inherit;display:inline-flex;width:20px;height:20px"></i></button><button class="gmail-c-button-unstyled gmail-c-icon_button gmail-c-icon_button--light gmail-c-icon_button--size_small gmail-c-message_actions__button" type="button" style="box-sizing:inherit;padding:0px;background-image:none;background-position:initial;background-size:initial;background-repeat:initial;background-origin:initial;background-clip:initial;border-width:0px;border-style:initial;border-color:initial;font:inherit;margin:0px;overflow:initial;text-align:initial;vertical-align:initial;border-radius:4px;display:inline-flex;height:32px;width:32px"><i class="gmail-c-icon gmail-c-icon--vertical-ellipsis" type="vertical-ellipsis" style="box-sizing:inherit;display:inline-flex;width:20px;height:20px"></i></button></div></div></div></div></div></div><div class="gmail-c-virtual_list__item" tabindex="-1" id="gmail-1606164824.018800" style="box-sizing:inherit;width:632.995px;color:rgb(29,28,29);font-family:Slack-Lato,appleLogo,sans-serif;font-size:15px;font-variant-ligatures:common-ligatures"><div class="gmail-c-message_kit__background gmail-p-message_pane_message__message gmail-c-message_kit__message" style="box-sizing:inherit;line-height:1.46668"><div class="gmail-c-message_kit__hover" style="box-sizing:inherit"><div class="gmail-c-message_kit__actions gmail-c-message_kit__actions--default" style="box-sizing:inherit"><div class="gmail-c-message_kit__labels__offscreen_message" style="box-sizing:inherit;overflow:hidden;height:1px;width:1px;padding:0px;border:0px"></div><div class="gmail-c-message_kit__gutter" style="box-sizing:inherit;display:flex;padding:8px 20px"><div class="gmail-c-message_kit__gutter__left" style="box-sizing:inherit;margin-right:8px;display:flex"><button class="gmail-c-button-unstyled gmail-c-message_kit__avatar gmail-c-avatar gmail-c-avatar--interactive" tabindex="-1" type="button" style="box-sizing:inherit;padding:0px;background-image:none;background-position:initial;background-size:initial;background-repeat:initial;background-origin:initial;background-clip:initial;border-width:0px;border-style:initial;border-color:initial;font:inherit;margin:0px;overflow:initial;text-align:initial;vertical-align:initial;outline:none;height:36px;width:36px"><img src="https://ca.slack-edge.com/TKFJE6LDR-U01ABLZMV7E-322d8ad14d52-48" class="gmail-c-base_icon gmail-c-base_icon--image" alt="" style="box-sizing: inherit; border-radius: 4px; flex-shrink: 0; background-size: 100%; background-repeat: no-repeat; display: inline-block; height: 36px; width: 36px;"></button></div><div class="gmail-c-message_kit__gutter__right" style="box-sizing:inherit;min-width:0px;padding:8px 8px 8px 16px"><span class="gmail-c-message__sender gmail-c-message_kit__sender" style="box-sizing:inherit;font-weight:900;word-break:break-word"><a target="_blank" rel="noopener noreferrer" class="gmail-c-link gmail-c-message__sender_link" href="https://app.slack.com/team/U01ABLZMV7E" style="box-sizing:inherit;text-decoration-line:none;display:inline-block">Codrina Maria Ilie<span class="gmail-c-opens_in_new_tab" style="box-sizing:inherit"></span></a></span> <a class="gmail-c-link gmail-c-timestamp" href="https://thegooddocs.slack.com/archives/C019A1EQJMC/p1606164824018800" style="box-sizing:inherit;text-decoration-line:none;font-size:12px"><span class="gmail-c-timestamp__label" style="box-sizing:inherit">7:53 AM</span></a><br style="box-sizing:inherit"><div class="gmail-c-message_kit__blocks gmail-c-message_kit__blocks--rich_text" style="box-sizing:inherit;max-width:none;margin-bottom:4px"><div class="gmail-c-message__message_blocks gmail-c-message__message_blocks--rich_text" style="box-sizing:inherit;max-width:none"><div class="gmail-p-block_kit_renderer" style="box-sizing:inherit;width:549.002px"><div class="gmail-p-block_kit_renderer__block_wrapper gmail-p-block_kit_renderer__block_wrapper--first" style="box-sizing:inherit;display:flex"><div class="gmail-p-rich_text_block" dir="auto" style="box-sizing:inherit;width:549.002px;line-height:1.46668"><div class="gmail-p-rich_text_section" style="box-sizing:inherit">Wonderful! I am happy I could help a bit! I am curious, why do you think it would be a better approach to have 2 glossaries - OSGeo and GRASS - instead of a collection inside the “mother” glossary? Are there some technical limitations that I don’t foresee given the maturity/longevity and complexity of GRASS terminology? If, and hopefully, the Lexicon plan is successful, then, in time, more and more projects will join. Will they join as OSGeo collections or independent glossaries, following the GRASS example? Are there specific benefits for the project for to have a glossary and not be a collection ?</div></div></div></div></div></div></div></div></div></div></div></div><div class="gmail-c-virtual_list__item" tabindex="-1" id="gmail-1606180831.023200" style="box-sizing:inherit;width:632.995px;outline-width:0px;outline-style:none;color:rgb(29,28,29);font-family:Slack-Lato,appleLogo,sans-serif;font-size:15px;font-variant-ligatures:common-ligatures"><div class="gmail-c-message_kit__background gmail-p-message_pane_message__message gmail-c-message_kit__message" style="box-sizing:inherit;line-height:1.46668"><div class="gmail-c-message_kit__hover" style="box-sizing:inherit"><div class="gmail-c-message_kit__actions gmail-c-message_kit__actions--default" style="box-sizing:inherit"><div class="gmail-c-message_kit__labels__offscreen_message" style="box-sizing:inherit;overflow:hidden;height:1px;width:1px;padding:0px;border:0px"></div><div class="gmail-c-message_kit__gutter" style="box-sizing:inherit;display:flex;padding:8px 20px"><div class="gmail-c-message_kit__gutter__left" style="box-sizing:inherit;margin-right:8px;display:flex"><button class="gmail-c-button-unstyled gmail-c-message_kit__avatar gmail-c-avatar gmail-c-avatar--interactive" tabindex="-1" type="button" style="box-sizing:inherit;padding:0px;background-image:none;background-position:initial;background-size:initial;background-repeat:initial;background-origin:initial;background-clip:initial;border-width:0px;border-style:initial;border-color:initial;font:inherit;margin:0px;overflow:initial;text-align:initial;vertical-align:initial;outline:none;height:36px;width:36px"><img src="https://ca.slack-edge.com/TKFJE6LDR-UKTGLQNGG-d6f4de222bb1-48" class="gmail-c-base_icon gmail-c-base_icon--image" alt="" style="box-sizing: inherit; border-radius: 4px; flex-shrink: 0; background-size: 100%; background-repeat: no-repeat; display: inline-block; height: 36px; width: 36px;"></button></div><div class="gmail-c-message_kit__gutter__right" style="box-sizing:inherit;min-width:0px;padding:8px 8px 8px 16px"><span class="gmail-c-message__sender gmail-c-message_kit__sender" style="box-sizing:inherit;font-weight:900;word-break:break-word"><a target="_blank" rel="noopener noreferrer" class="gmail-c-link gmail-c-message__sender_link" href="https://app.slack.com/team/UKTGLQNGG" style="box-sizing:inherit;text-decoration-line:none;display:inline-block">cameronshorter<span class="gmail-c-opens_in_new_tab" style="box-sizing:inherit"></span></a></span> <a class="gmail-c-link gmail-c-timestamp" href="https://thegooddocs.slack.com/archives/C019A1EQJMC/p1606180831023200" style="box-sizing:inherit;text-decoration-line:none;font-size:12px"><span class="gmail-c-timestamp__label" style="box-sizing:inherit">12:20 PM</span></a><br style="box-sizing:inherit"><div class="gmail-c-message_kit__blocks gmail-c-message_kit__blocks--rich_text" style="box-sizing:inherit;max-width:none;margin-bottom:4px"><div class="gmail-c-message__message_blocks gmail-c-message__message_blocks--rich_text" style="box-sizing:inherit;max-width:none"><div class="gmail-p-block_kit_renderer" style="box-sizing:inherit;width:549.002px"><div class="gmail-p-block_kit_renderer__block_wrapper gmail-p-block_kit_renderer__block_wrapper--first" style="box-sizing:inherit;display:flex"><div class="gmail-p-rich_text_block" dir="auto" style="box-sizing:inherit;width:549.002px;line-height:1.46668"><div class="gmail-p-rich_text_section" style="box-sizing:inherit"><span dir="ltr" style="box-sizing:inherit"><a class="gmail-c-link gmail-c-member_slug gmail-c-member_slug--light gmail-c-member_slug--link" tabindex="0" href="https://thegooddocs.slack.com/team/U01ABLZMV7E" rel="noopener noreferrer" style="box-sizing:inherit;text-decoration-line:none;padding:0px 2px 1px;border-radius:3px">@Codrina Maria Ilie</a></span> There Pros and Cons for both approaches. From a pilot perspective, it will be valuable to try and get two glossaries to talk with each other (hence my suggestion of two glossaries). From an OSGeo/GRASS perspective - it will be more work up front to get alignment around terms, but will likey be better later to have all the terms under the one OSGeo glossary. Note that what we decide now in our pilot can be changed later.</div></div></div></div></div></div></div></div></div></div></div></div></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Tue, 24 Nov 2020 at 13:38, Vaclav Petras <<a href="mailto:wenzeslaus@gmail.com">wenzeslaus@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"><div dir="ltr"><div dir="ltr"><div>Hi Cameron,</div><div><br></div><div>I'm curious how this will turn out. I hope this formalization will help the GRASS GIS community with some renaming/terminology issues we are now discussing.<br></div><div><br></div><div>I subscribed to the mailing list. Feel free to continue the conversation there or include other people here. I'm still unclear on what the process would be. How do you want to proceed with the resources Codrina and I collected?<br></div><div><br></div><div>Best,<br></div><div>Vaclav<br></div></div><div><br></div><div><br></div><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Mon, Nov 23, 2020 at 1:27 PM Cameron Shorter <<a href="mailto:cameron.shorter@gmail.com" target="_blank">cameron.shorter@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"><div dir="ltr">Hi Codrina and Vaclav,<div>This GRASS use case is excellent and would be really helpful for us to use to test our software and processes within our glossaries pilot.</div><div>I have more I'd like to add to this thread, and would like to loop in the other glossary pilot participants.</div><div>Vaclav (and Codrina), do you mind if I introduce you and this thread to the public osgeo lexicon email list?</div><div>Cheers, Cameron</div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Mon, 23 Nov 2020 at 23:28, Codrina Maria Ilie <<a href="mailto:codrina@geo-spatial.org" target="_blank">codrina@geo-spatial.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">Hi, Vaclav,<br>
<br>
Thanks for the resources!<br>(...)<br>
<br>
I did add to our thread Cameron Shorter, that I mentioned earlier and <br>
Ankita, an experienced tech writer volunteering for the OSGeo glossary. <br>
They are much more experienced and thus can provide a clearer insight <br>
into the topic.<br>
<br>
<br>
Cheers,<br>
Codrina<br>
<br>
On 23/11/2020 06:26, Vaclav Petras wrote:<br>
> <br>
> <br>
> On Sun, Nov 22, 2020 at 7:32 AM Codrina Maria Ilie <br>
> <<a href="mailto:codrina@geo-spatial.org" target="_blank">codrina@geo-spatial.org</a> <mailto:<a href="mailto:codrina@geo-spatial.org" target="_blank">codrina@geo-spatial.org</a>>> wrote:<br>
> <br>
> Hi, Vaclav,<br>
> <br>
> I hope all is good on your side.<br>
> <br>
> We are trying to advance with the pilot glossaries wihtin OSGeo and I<br>
> was looking for resources where GRASS GIS terms are written down,<br>
> defined and/or discussed in the attempt to include them.<br>
> <br>
> I put together these resources:<br>
> <br>
> [1] <a href="https://grasswiki.osgeo.org/wiki/GRASS_Translation_Glossary" rel="noreferrer" target="_blank">https://grasswiki.osgeo.org/wiki/GRASS_Translation_Glossary</a><br>
> <<a href="https://grasswiki.osgeo.org/wiki/GRASS_Translation_Glossary" rel="noreferrer" target="_blank">https://grasswiki.osgeo.org/wiki/GRASS_Translation_Glossary</a>><br>
> [2]<br>
> <a href="https://grasswiki.osgeo.org/wiki/Terminology_comparison_between_ArcGIS_and_GRASS_GIS" rel="noreferrer" target="_blank">https://grasswiki.osgeo.org/wiki/Terminology_comparison_between_ArcGIS_and_GRASS_GIS</a><br>
> <<a href="https://grasswiki.osgeo.org/wiki/Terminology_comparison_between_ArcGIS_and_GRASS_GIS" rel="noreferrer" target="_blank">https://grasswiki.osgeo.org/wiki/Terminology_comparison_between_ArcGIS_and_GRASS_GIS</a>><br>
> [3] <a href="https://grasswiki.osgeo.org/wiki/GRASS_7_Terminology" rel="noreferrer" target="_blank">https://grasswiki.osgeo.org/wiki/GRASS_7_Terminology</a><br>
> <<a href="https://grasswiki.osgeo.org/wiki/GRASS_7_Terminology" rel="noreferrer" target="_blank">https://grasswiki.osgeo.org/wiki/GRASS_7_Terminology</a>><br>
> <br>
> Are there other wikis or docs or repositories that I've missed?<br>
> <br>
> <br>
> Mostly valid even now:<br>
> <br>
> <a href="https://grasswiki.osgeo.org/wiki/GRASS_6_Terminology" rel="noreferrer" target="_blank">https://grasswiki.osgeo.org/wiki/GRASS_6_Terminology</a> <br>
> <<a href="https://grasswiki.osgeo.org/wiki/GRASS_6_Terminology" rel="noreferrer" target="_blank">https://grasswiki.osgeo.org/wiki/GRASS_6_Terminology</a>><br>
> <br>
> With some old discussion and attempts for rename:<br>
> <br>
> <a href="https://grasswiki.osgeo.org/wiki/GRASS_7_Terminology" rel="noreferrer" target="_blank">https://grasswiki.osgeo.org/wiki/GRASS_7_Terminology</a> <br>
> <<a href="https://grasswiki.osgeo.org/wiki/GRASS_7_Terminology" rel="noreferrer" target="_blank">https://grasswiki.osgeo.org/wiki/GRASS_7_Terminology</a>><br>
> <br>
> Some sections are terms with definitions:<br>
> <br>
> <a href="https://grasswiki.osgeo.org/wiki/GIS_Concepts" rel="noreferrer" target="_blank">https://grasswiki.osgeo.org/wiki/GIS_Concepts</a> <br>
> <<a href="https://grasswiki.osgeo.org/wiki/GIS_Concepts" rel="noreferrer" target="_blank">https://grasswiki.osgeo.org/wiki/GIS_Concepts</a>><br>
> <br>
> The above has links to documentation which sometimes has definitions, <br>
> most notably:<br>
> <br>
> <a href="https://grass.osgeo.org/grass78/manuals/rasterintro.html" rel="noreferrer" target="_blank">https://grass.osgeo.org/grass78/manuals/rasterintro.html</a> <br>
> <<a href="https://grass.osgeo.org/grass78/manuals/rasterintro.html" rel="noreferrer" target="_blank">https://grass.osgeo.org/grass78/manuals/rasterintro.html</a>><br>
> <a href="https://grass.osgeo.org/grass78/manuals/vectorintro.html" rel="noreferrer" target="_blank">https://grass.osgeo.org/grass78/manuals/vectorintro.html</a> <br>
> <<a href="https://grass.osgeo.org/grass78/manuals/vectorintro.html" rel="noreferrer" target="_blank">https://grass.osgeo.org/grass78/manuals/vectorintro.html</a>><br>
> <a href="https://grass.osgeo.org/grass78/manuals/raster3dintro.html" rel="noreferrer" target="_blank">https://grass.osgeo.org/grass78/manuals/raster3dintro.html</a> <br>
> <<a href="https://grass.osgeo.org/grass78/manuals/raster3dintro.html" rel="noreferrer" target="_blank">https://grass.osgeo.org/grass78/manuals/raster3dintro.html</a>><br>
> <a href="https://grass.osgeo.org/grass78/manuals/temporalintro.html" rel="noreferrer" target="_blank">https://grass.osgeo.org/grass78/manuals/temporalintro.html</a> <br>
> <<a href="https://grass.osgeo.org/grass78/manuals/temporalintro.html" rel="noreferrer" target="_blank">https://grass.osgeo.org/grass78/manuals/temporalintro.html</a>><br>
> <a href="https://grass.osgeo.org/grass78/manuals/projectionintro.html" rel="noreferrer" target="_blank">https://grass.osgeo.org/grass78/manuals/projectionintro.html</a> <br>
> <<a href="https://grass.osgeo.org/grass78/manuals/projectionintro.html" rel="noreferrer" target="_blank">https://grass.osgeo.org/grass78/manuals/projectionintro.html</a>><br>
> <br>
> Even more, but mostly duplication of above:<br>
> <br>
> <a href="https://grasswiki.osgeo.org/wiki/Location_and_Mapsets" rel="noreferrer" target="_blank">https://grasswiki.osgeo.org/wiki/Location_and_Mapsets</a> <br>
> <<a href="https://grasswiki.osgeo.org/wiki/Location_and_Mapsets" rel="noreferrer" target="_blank">https://grasswiki.osgeo.org/wiki/Location_and_Mapsets</a>><br>
> <a href="https://grasswiki.osgeo.org/wiki/GRASS_raster_semantics" rel="noreferrer" target="_blank">https://grasswiki.osgeo.org/wiki/GRASS_raster_semantics</a> <br>
> <<a href="https://grasswiki.osgeo.org/wiki/GRASS_raster_semantics" rel="noreferrer" target="_blank">https://grasswiki.osgeo.org/wiki/GRASS_raster_semantics</a>><br>
> <br>
> <br>
> Probably, it would be best if you take out Anna, Vero and Moritz from <br>
> the email thread and include whomever you think should be part of the <br>
> conversation from your side.<br>
> <br>
> <br>
> Any suggestion is highly appreciated.<br>
> <br>
> Cheers,<br>
> Codrina<br>
> <br>
> <br>
> <br>
> On 09/11/2020 12:43, Codrina Maria Ilie wrote:<br>
> > Hi, Vaclav,<br>
> ><br>
> > It seems that asynchronous communication works best for me as<br>
> well in<br>
> > these times. As the end of the year is approaching, tasks just<br>
> keep on<br>
> > pilling up.<br>
> ><br>
> > I will do my best to answer you questions, yet - if it is OK with<br>
> you -<br>
> > I'd also like to invite into our conversation Cameron Shorter. He<br>
> is a<br>
> > technical writer and mentor within The Good Docs Project [1] and the<br>
> > main initiator of this initiative within OSGeo.<br>
> ><br>
> > Now, regarding your questions, for (1) and (2) - GRASS GIS would<br>
> become<br>
> > a pilot project for the OSGeo glossary Geolexica.<br>
> ><br>
> > At this point, OSGeo Geolexica [2] is populated with terms that have<br>
> > been gathered over time by the GeoForAll group. The list is of<br>
> course<br>
> > far from exhaustive, but it is a good start. The terms you see there<br>
> > have already been curated by the tech writers from the Lexicon<br>
> > Committee. You can take a look here [3] to get an idea on how<br>
> things<br>
> > evolved. It is a spreadsheet because the initial GeoForAll list<br>
> was a<br>
> > spreadsheet and it was faster to start as such, to get the ball<br>
> rolling.<br>
> ><br>
> > Being a pilot project means that a collection will be added in OSGeo<br>
> > Geolexica - lets say, named GRASS GIS - and you will be able to<br>
> select<br>
> > terms from the OSGeo "main" glossary to include into the GRASS GIS<br>
> > collection. Working further, you can propose new terms relevant to<br>
> > OSGeo, propose changes and opening discussions on existing ones.<br>
> ><br>
> > Technically speaking, for all these actions, we will have a<br>
> bullet list<br>
> > howto for the Geolexica desktop interface we'll use [4].<br>
> Conceptually<br>
> > speaking, regarding how a debate on a specific term is lead and<br>
> how a<br>
> > conclusion is reached - Cameron can help us both better<br>
> understand the<br>
> > process.<br>
> ><br>
> > Regarding question (3), it would be something like 2h /week<br>
> initially.<br>
> > Our volunteer tech writers need to understand the project, what<br>
> are your<br>
> > requirements, what are the processes you normally use to define<br>
> GRASS<br>
> > terms, what happens when a term become obsolete etc. Usually, for<br>
> that<br>
> > it's easier to have a call because it's faster, but it's not<br>
> mandatory,<br>
> > of course. We have a Slack channel we use for the Lexicon<br>
> committee, you<br>
> > can join that, or do it in a mail thread, whatever works.<br>
> ><br>
> > I hope I managed to shed a bit of light on your questions. Is it<br>
> OK for<br>
> > you if you also cc Cameron (<a href="mailto:cameron.shorter@gmail.com" target="_blank">cameron.shorter@gmail.com</a><br>
> <mailto:<a href="mailto:cameron.shorter@gmail.com" target="_blank">cameron.shorter@gmail.com</a>>) in your next email?<br>
> ><br>
> ><br>
> > Cheers,<br>
> > Codrina<br>
> ><br>
> > [1] <a href="https://thegooddocsproject.dev/" rel="noreferrer" target="_blank">https://thegooddocsproject.dev/</a> <<a href="https://thegooddocsproject.dev/" rel="noreferrer" target="_blank">https://thegooddocsproject.dev/</a>><br>
> > [2] <a href="https://osgeo.geolexica.org/" rel="noreferrer" target="_blank">https://osgeo.geolexica.org/</a> <<a href="https://osgeo.geolexica.org/" rel="noreferrer" target="_blank">https://osgeo.geolexica.org/</a>><br>
> > [3]<br>
> ><br>
> <a href="https://docs.google.com/spreadsheets/d/1keonRLT3chmqlRZsMMF9UaCI_vzNEHmJx6t9LB3jBjM/edit#gid=32744342" rel="noreferrer" target="_blank">https://docs.google.com/spreadsheets/d/1keonRLT3chmqlRZsMMF9UaCI_vzNEHmJx6t9LB3jBjM/edit#gid=32744342</a><br>
> <<a href="https://docs.google.com/spreadsheets/d/1keonRLT3chmqlRZsMMF9UaCI_vzNEHmJx6t9LB3jBjM/edit#gid=32744342" rel="noreferrer" target="_blank">https://docs.google.com/spreadsheets/d/1keonRLT3chmqlRZsMMF9UaCI_vzNEHmJx6t9LB3jBjM/edit#gid=32744342</a>><br>
> <br>
> ><br>
> > [4] <a href="https://github.com/glossarist/glossarist-desktop/" rel="noreferrer" target="_blank">https://github.com/glossarist/glossarist-desktop/</a><br>
> <<a href="https://github.com/glossarist/glossarist-desktop/" rel="noreferrer" target="_blank">https://github.com/glossarist/glossarist-desktop/</a>><br>
> ><br>
> ><br>
> ><br>
> ><br>
> > On 03/11/2020 06:20, Vaclav Petras wrote:<br>
> >> Thank you for the explanation, Codrina. I especially like your<br>
> point 4<br>
> >> about translations. I have some more thoughts, but I will focus<br>
> just<br>
> >> on what should be the next step for us.<br>
> >><br>
> >> (1) Since standardization/harmonization is a goal (or the<br>
> goal?), my<br>
> >> question is how I or GRASS GIS should approach this? There is a<br>
> >> precedence in icon themes which seems to still work out well,<br>
> but this<br>
> >> is much more complex. A recent usability survey for GRASS GIS<br>
> >> suggested that working on terminology might be a good next step for<br>
> >> GRASS GIS and that's of course not the first time this was<br>
> brought up.<br>
> >> Of course, if that would be straightforward, we would not be having<br>
> >> this discussion in the first place.<br>
> >><br>
> >> Taking the first item from the ArcGIS vs GRASS GIS list as an<br>
> example<br>
> >> (which is sufficiently interesting and controversial :-), should<br>
> GRASS<br>
> >> GIS project now start arguing for its term /map/ (or /mapping/)<br>
> to be<br>
> >> used for basic unit of geographic data as /mapping/ is a more<br>
> >> mathematically fitting term for what many use a<br>
> visualization-oriented<br>
> >> GIS term /layer/ which usually refers to one of flat components<br>
> of a<br>
> >> bigger object? Or should we go ahead and prepare for a big<br>
> rename of<br>
> >> /raster map/ to /image/ and /vector map/ to /feature collection/ or<br>
> >> whatever is the most popular term for that these days. Or perhaps<br>
> >> both? I'm to get a clear sense of what is expected from us.<br>
> >><br>
> >> (2) Regardless of the answer to the above question, it seems to me<br>
> >> that there might be value in including the /current/ terms from<br>
> GRASS<br>
> >> GIS. Even in the scenario where they would become obsolete, it<br>
> would<br>
> >> be good as a reference. There seems to be a way to depreciate<br>
> terms.<br>
> >> However, I don't see multiple definitions for one term (which,<br>
> e.g.,<br>
> >> /map/ or /layer/ would need) or project-specific definitions<br>
> marked as<br>
> >> such, although some of the current definitions seem to be<br>
> specific to<br>
> >> specific projects.<br>
> >><br>
> >> (3) Finally, it is not clear to me what time commitment is<br>
> required to<br>
> >> participate in this. As there is no immediate benefit, it seems<br>
> like<br>
> >> something which is hard to do without direct funding. What is the<br>
> >> system to get "your voice heard" with limited time commitment?<br>
> Do the<br>
> >> volunteer technical writers somewho fit into this?<br>
> >><br>
> >> Asynchronous email works better for me at this point. We can call<br>
> >> later if needed.<br>
> >><br>
> >> Best,<br>
> >> Vaclav<br>
> >><br>
> >> On Sun, Nov 1, 2020 at 3:33 PM Codrina Maria Ilie<br>
> >> <<a href="mailto:codrina@geo-spatial.org" target="_blank">codrina@geo-spatial.org</a> <mailto:<a href="mailto:codrina@geo-spatial.org" target="_blank">codrina@geo-spatial.org</a>><br>
> <mailto:<a href="mailto:codrina@geo-spatial.org" target="_blank">codrina@geo-spatial.org</a> <mailto:<a href="mailto:codrina@geo-spatial.org" target="_blank">codrina@geo-spatial.org</a>>>><br>
> wrote:<br>
> >><br>
> >> Hi, Vaclav,<br>
> >><br>
> >> Thanks for getting back to me.<br>
> >><br>
> >> The initiative is doing both, creating a terminology pool and<br>
> >> allowing<br>
> >> standardization and harmonization of terms across all OSGeo<br>
> >> projects, as<br>
> >> well as outside OSGeo. Your work highlighting the<br>
> differences between<br>
> >> GRASS and ArcGIS terminology is perfect to demonstrate the need<br>
> >> for it<br>
> >> in the geospatial field.<br>
> >><br>
> >> There are several aspects that - I think - makes this initiative<br>
> >> relevant:<br>
> >><br>
> >> (1) we are aligned with OGC and ISO/TC 211. Rob Atkinson, who is<br>
> >> involved in the development, maintenance and research around<br>
> >> sharing of<br>
> >> 'definitions' in general and Reese Plews, who is the<br>
> convenor of the<br>
> >> ISO/TC 211 Terminology Maintenance Group (TMG) - are both<br>
> part of the<br>
> >> Lexicon Committee in OSGeo. This helps us with<br>
> cross-organization<br>
> >> alignment of concepts or avoiding term duplication so<br>
> hopefully, in<br>
> >> time, there will be no more need for terms comparison across<br>
> >> solutions,<br>
> >> organizations, projects etc.<br>
> >><br>
> >> We've also reached out to EU Re3gistry [1] trying to link to<br>
> their<br>
> >> efforts as well, but without much success until now. I<br>
> suppose this<br>
> >> would somehow exceed their EC requirements and responsibilities.<br>
> >> We'll see.<br>
> >><br>
> >> (2) defining terms in a structure way, following best<br>
> practices - for<br>
> >> this particular aspect we are working with 2 volunteer technical<br>
> >> writers.<br>
> >><br>
> >> (3) we are using Geolexica [2], [3] for the actual<br>
> development of the<br>
> >> glossary - which is an Open Source solution commissioned by<br>
> ISO/TC211<br>
> >> specifically for their glossary [4]. Basically, the<br>
> terminology is<br>
> >> stored in a gitlab repository to which an editor connects to<br>
> >> through an<br>
> >> easy interface using hers/his git username. Of course, not<br>
> >> everyone can<br>
> >> edit everything, there are some roles assigned etc. etc. but<br>
> these<br>
> >> details are not relevant at this point.<br>
> >><br>
> >> (4) it helps with the software and documentation creation and<br>
> >> translations. Geolexica supports multiple languages (example<br>
> from<br>
> >> ISO/TC<br>
> >> 211 [5]), so if you are a translator for Arabic, you can<br>
> look for the<br>
> >> term in English and see if there is an official translation to<br>
> >> use. If<br>
> >> not, you can propose one. Not to mention the help for new<br>
> >> documentation<br>
> >> writers/translators volunteers that have one stop-shop for<br>
> terms used<br>
> >> within the filed and within the specific software that they<br>
> work at.<br>
> >><br>
> >> (5) this way of working with terminology allows all kinds of<br>
> >> automatic<br>
> >> integrations, such as inherit terms already defined and accepted<br>
> >> existing in the foundation glossary into one's documentations,<br>
> >> inserting<br>
> >> glossary-like functionalities into the software etc.<br>
> >><br>
> >> I could go on a bit longer, but this email is shameless<br>
> long, for<br>
> >> which<br>
> >> fact I apologise :) I hope, though, that it gives a clearer<br>
> view on<br>
> >> what<br>
> >> we're trying to do and why.<br>
> >><br>
> >> To resume, we want to build up and then maintain the OSGeo<br>
> glossary -<br>
> >> that is standardized and harmonized with the works of specific<br>
> >> mandated<br>
> >> geo-institutions - and we can only do it with support from the<br>
> >> community.<br>
> >><br>
> >> Please, don't hesitate to ask me if you have any other<br>
> questions. We<br>
> >> can<br>
> >> even set a call, in hopes of escaping long emails. :)<br>
> >><br>
> >> Cheers,<br>
> >> Codrina<br>
> >><br>
> >><br>
> >> [1] <a href="https://joinup.ec.europa.eu/solution/re3gistry" rel="noreferrer" target="_blank">https://joinup.ec.europa.eu/solution/re3gistry</a><br>
> <<a href="https://joinup.ec.europa.eu/solution/re3gistry" rel="noreferrer" target="_blank">https://joinup.ec.europa.eu/solution/re3gistry</a>><br>
> >> [2] <a href="https://github.com/geolexica" rel="noreferrer" target="_blank">https://github.com/geolexica</a> <<a href="https://github.com/geolexica" rel="noreferrer" target="_blank">https://github.com/geolexica</a>><br>
> >> [3] <a href="https://osgeo.geolexica.org/" rel="noreferrer" target="_blank">https://osgeo.geolexica.org/</a> <<a href="https://osgeo.geolexica.org/" rel="noreferrer" target="_blank">https://osgeo.geolexica.org/</a>><br>
> >> [4] <a href="https://isotc211.geolexica.org/" rel="noreferrer" target="_blank">https://isotc211.geolexica.org/</a><br>
> <<a href="https://isotc211.geolexica.org/" rel="noreferrer" target="_blank">https://isotc211.geolexica.org/</a>><br>
> >> [5] <a href="https://isotc211.geolexica.org/stats/" rel="noreferrer" target="_blank">https://isotc211.geolexica.org/stats/</a><br>
> <<a href="https://isotc211.geolexica.org/stats/" rel="noreferrer" target="_blank">https://isotc211.geolexica.org/stats/</a>><br>
> >><br>
> >><br>
> >> On 01/11/2020 05:50, Vaclav Petras wrote:<br>
> >> > Hi Codrina,<br>
> >> ><br>
> >> > Thanks for reaching out to us. I don't understand how this is<br>
> >> related to<br>
> >> > project-specific concepts or terminology. Is this just<br>
> trying to<br>
> >> put all<br>
> >> > terms into one pool or is the idea to also standardize<br>
> the terms<br>
> >> across<br>
> >> > projects? For example, I created /Terminology//comparison<br>
> between<br>
> >> ArcGIS<br>
> >> > and GRASS GIS/ which shows some of the issues of different<br>
> >> terminologies.<br>
> >> ><br>
> >> > Best,<br>
> >> > Vaclav<br>
> >> ><br>
> >> ><br>
> >><br>
> >><br>
> <a href="https://grasswiki.osgeo.org/wiki/Terminology_comparison_between_ArcGIS_and_GRASS_GIS" rel="noreferrer" target="_blank">https://grasswiki.osgeo.org/wiki/Terminology_comparison_between_ArcGIS_and_GRASS_GIS</a><br>
> <<a href="https://grasswiki.osgeo.org/wiki/Terminology_comparison_between_ArcGIS_and_GRASS_GIS" rel="noreferrer" target="_blank">https://grasswiki.osgeo.org/wiki/Terminology_comparison_between_ArcGIS_and_GRASS_GIS</a>><br>
> <br>
> >><br>
> >> ><br>
> >> > On Fri, Oct 30, 2020 at 2:01 PM Codrina Maria Ilie<br>
> >> > <<a href="mailto:codrina@geo-spatial.org" target="_blank">codrina@geo-spatial.org</a> <mailto:<a href="mailto:codrina@geo-spatial.org" target="_blank">codrina@geo-spatial.org</a>><br>
> <mailto:<a href="mailto:codrina@geo-spatial.org" target="_blank">codrina@geo-spatial.org</a> <mailto:<a href="mailto:codrina@geo-spatial.org" target="_blank">codrina@geo-spatial.org</a>>><br>
> >> <mailto:<a href="mailto:codrina@geo-spatial.org" target="_blank">codrina@geo-spatial.org</a><br>
> <mailto:<a href="mailto:codrina@geo-spatial.org" target="_blank">codrina@geo-spatial.org</a>> <mailto:<a href="mailto:codrina@geo-spatial.org" target="_blank">codrina@geo-spatial.org</a><br>
> <mailto:<a href="mailto:codrina@geo-spatial.org" target="_blank">codrina@geo-spatial.org</a>>>>><br>
> >> wrote:<br>
> >> ><br>
> >> > Hi, Anna, Vero, Vaclav and Moritz,<br>
> >> ><br>
> >> > I hope you all - as well as your close ones - are<br>
> healthy and<br>
> >> OK during<br>
> >> > these complicated times. Romania, like the rest of<br>
> Europe, is<br>
> >> severely<br>
> >> > hit by the second pandemic wave and the authorities<br>
> seem to<br>
> >> be worried<br>
> >> > more about political capital when deciding on potentially<br>
> >> life saving<br>
> >> > restrictions.<br>
> >> ><br>
> >> > I am writing to you - at the suggestion of Markus -<br>
> >> regarding an<br>
> >> > initiative within OSGeo that you might have heard at<br>
> the AGM<br>
> >> or saw the<br>
> >> > email below sent to the OSGeo discuss list - OSGeo<br>
> Geolexica.<br>
> >> ><br>
> >> > What we - the Lexicon Committee - are trying to do<br>
> now is set<br>
> >> up some<br>
> >> > pilot glossaries for specific OSGeo projects that can<br>
> feed<br>
> >> from the<br>
> >> > OSGeo Geolexica [1].<br>
> >> ><br>
> >> > I was wondering if any of you would be interested to<br>
> >> contribute on<br>
> >> > behalf of GRASS, or any other of OSGeo projects you're<br>
> >> working on. That<br>
> >> > would translate into activities like reviewing terms<br>
> from the<br>
> >> OSGeo<br>
> >> > glossary and deciding whether they should be included<br>
> in your<br>
> >> pilot or<br>
> >> > identify new terms that are specific for you.<br>
> >> ><br>
> >> > The initiative is built together with OGC and ISO/TC211.<br>
> >> We've also<br>
> >> > reached out to EU Re3gistry trying to link to their<br>
> efforts<br>
> >> as well,<br>
> >> > but<br>
> >> > without much success until now. I suppose this would<br>
> somehow<br>
> >> exceed<br>
> >> > their EC requirements and responsibilities. We'll see.<br>
> >> ><br>
> >> > More details on the initiative are in our Manifesto<br>
> [2] or<br>
> >> on the<br>
> >> > Lexicon Committee wiki [3]. Of course, if you have any<br>
> >> questions, feel<br>
> >> > free to ask away.<br>
> >> ><br>
> >> > So, please let me know if any of this is of interest and<br>
> >> also, of<br>
> >> > course, if your time allows any engagements.<br>
> >> ><br>
> >> ><br>
> >> > Cheers,<br>
> >> > Codrina<br>
> >> ><br>
> >> ><br>
> >> ><br>
> >> > [1] <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>><br>
> >> > [2]<br>
> >> ><br>
> >><br>
> >><br>
> <a href="https://docs.google.com/document/d/1Fjrl34ErnYammel9WmvXJ3rMWFANjoSiiGyyNSYOXUg/edit" rel="noreferrer" target="_blank">https://docs.google.com/document/d/1Fjrl34ErnYammel9WmvXJ3rMWFANjoSiiGyyNSYOXUg/edit</a><br>
> <<a href="https://docs.google.com/document/d/1Fjrl34ErnYammel9WmvXJ3rMWFANjoSiiGyyNSYOXUg/edit" rel="noreferrer" target="_blank">https://docs.google.com/document/d/1Fjrl34ErnYammel9WmvXJ3rMWFANjoSiiGyyNSYOXUg/edit</a>><br>
> <br>
> >><br>
> >> > [3] <a href="https://wiki.osgeo.org/wiki/Lexicon_Committee" rel="noreferrer" target="_blank">https://wiki.osgeo.org/wiki/Lexicon_Committee</a><br>
> <<a href="https://wiki.osgeo.org/wiki/Lexicon_Committee" rel="noreferrer" target="_blank">https://wiki.osgeo.org/wiki/Lexicon_Committee</a>><br>
> >> ><br>
> >> ><br>
> >> ><br>
> >> ><br>
> >> > -------- Forwarded Message --------<br>
> >> ><br>
> >> ><br>
> >> > Hi all,<br>
> >> ><br>
> >> > I am writing to let you know of a new initiative<br>
> within our<br>
> >> community -<br>
> >> > the OSGeo Glossary - led by the Lexicon committee (in<br>
> >> formation) with<br>
> >> > the scope of defining and managing geospatial terms<br>
> across<br>
> >> communities.<br>
> >> > First operative steps have already been made with<br>
> setting up<br>
> >> OSGeo<br>
> >> > Geolexica [1] for managing the lexicon database, as<br>
> well as<br>
> >> an initial<br>
> >> > load of terms that was done by a bulk load from cleaned<br>
> >> terms and<br>
> >> > definitions compiled by the GeoForAll group.<br>
> >> ><br>
> >> > The work is done in collaboration with folks from<br>
> ISO/TC 211,<br>
> >> OGC and<br>
> >> > The Good Docs Project [2] that have joined the Lexicon<br>
> >> committee, which<br>
> >> > is very constructive given their decades long<br>
> experience in<br>
> >> > terminology,<br>
> >> > as well as helping us with cross-organization<br>
> alignment of<br>
> >> concepts or<br>
> >> > avoiding term duplication.<br>
> >> ><br>
> >> > Gracefully helping us with the groundwork are two<br>
> experienced<br>
> >> technical<br>
> >> > writers that I’d like to introduce to our community,<br>
> Ankita<br>
> >> and Naini -<br>
> >> > in cc. Their contributions will support us in doing a<br>
> clean,<br>
> >> sharp job<br>
> >> > when it comes to the actual process of glossary<br>
> construction.<br>
> >> ><br>
> >> > A next big step for the Lexicon Committee is setting<br>
> up pilot<br>
> >> glossary<br>
> >> > projects for specific OSGeo projects, irrespective of<br>
> their<br>
> >> status,<br>
> >> > incubated, in the process or community. So, if this<br>
> could<br>
> >> be of<br>
> >> > interest<br>
> >> > to you, please let me, Cameron, Ankita or Naini know<br>
> or by<br>
> >> joining and<br>
> >> > presenting yourself on the Lexicon mailing list [3]<br>
> or Slack<br>
> >> channel<br>
> >> > [4].<br>
> >> ><br>
> >> ><br>
> >> > Cheers and stay safe,<br>
> >> > Codrina<br>
> >> ><br>
> >> ><br>
> >> > [1] <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>><br>
> >> > [2] <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>><br>
> >> > [3] <a href="https://lists.osgeo.org/mailman/listinfo/lexicon" rel="noreferrer" target="_blank">https://lists.osgeo.org/mailman/listinfo/lexicon</a><br>
> <<a href="https://lists.osgeo.org/mailman/listinfo/lexicon" rel="noreferrer" target="_blank">https://lists.osgeo.org/mailman/listinfo/lexicon</a>><br>
> >> > [4]<br>
> >> ><br>
> >><br>
> >><br>
> <a href="https://thegooddocs.slack.com/join/shared_invite/zt-be2gay0m-Ukq_5SI0MHp20IQP3auQjg#/" rel="noreferrer" target="_blank">https://thegooddocs.slack.com/join/shared_invite/zt-be2gay0m-Ukq_5SI0MHp20IQP3auQjg#/</a><br>
> <<a href="https://thegooddocs.slack.com/join/shared_invite/zt-be2gay0m-Ukq_5SI0MHp20IQP3auQjg#/" rel="noreferrer" target="_blank">https://thegooddocs.slack.com/join/shared_invite/zt-be2gay0m-Ukq_5SI0MHp20IQP3auQjg#/</a>><br>
> <br>
> >><br>
> >> ><br>
> >><br>
> <br>
</blockquote></div><br clear="all"><div><br></div>-- <br><div dir="ltr"><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>
</blockquote></div></div>
</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></div>