<div dir="ltr"><div dir="ltr">Hi Gobe,<div>I can see that you have documented the OGC process, and HOW external people can engage with this process.</div><div>However, I'm really looking for a <b>Vision </b>and <b>Technical Roadmap</b> which OSGeo can follow (re Terminology definitions). I feel you haven't addressed our OSGeo use case. And in particular, I'm not seeing an integration strategy between OGC and OSGeo.</div><div><br></div><div>On behalf of the OSGeo community, I'm offering to help source extra terminology, but I don't want to start a new incompatible system. I'm hoping we can set up something which seamlessly integrates with ISO 211 and OGC. And for that I'm asking for help. Think about the reality of sourcing terms from thousands of individuals. These people are not interested in managing a glossary, but would be fine with suggesting a missing term, or refining a definition - if we make the process easy.</div><div><br></div><div><b>So if you were to advise on setting up an OSGeo Terminology system from scratch what would you suggest?</b> I'm thinking advice should cover crowdsourcing information, include a review process, and particularly pertinent to the OGC, should describe seamlessly integrate into OGC and ISO 211 systems (because we have agreed on the same field names and complementary processes).</div><div><br></div><div><div>Note: In my first 30 sec look I can see there are gaps in OGC definitions. I can't find an edge case word "GeoJSON", but can find a similar transport format "XML".</div><div>I can't find package names such as "QGIS". I'm sure there are more. I feel the OSGeo community could complement OGC hugely in supporting the spatial community around terminology - and we would be so much better with OGC's help.</div></div><div><br></div><div>After collating your thoughts, I suggest we should follow up with a video conference call.</div><div><br></div><div>Sound good?</div><div>Cameron</div><div><br></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Wed, 2 Oct 2019 at 23:50, Gobe Hobona <<a href="mailto:ghobona@ogc.org">ghobona@ogc.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"><div style="overflow-wrap: break-word;"><div>Cameron,</div><div><br></div><div>The OGC publishes definitions through the OGC Definitions Server at <a href="http://www.opengis.net/def" target="_blank">http://www.opengis.net/def</a></div><div><br></div><div>The definitions include, amongst others, terms from the OGC Glossary of Terms <a href="https://www.opengeospatial.org/ogc/glossary" target="_blank">https://www.opengeospatial.org/ogc/glossary</a></div><div><br></div><div>The glossary is represented in the Definitions Server by this resource <a href="http://www.opengis.net/def/glossary/" target="_blank">http://www.opengis.net/def/glossary/</a></div><div><br></div><div>The RDF Turtle files used to populate the Definitions Server with the glossary are at <a href="https://github.com/opengeospatial/NamingAuthority/blob/master/definitions/conceptschemes/ogc_glossary.ttl" target="_blank">https://github.com/opengeospatial/NamingAuthority/blob/master/definitions/conceptschemes/ogc_glossary.ttl</a></div><div><br></div><div>Once published, the definitions are available in RDF/XML, RDF Turtle, JSON-LD and a series of other formats. Some specific definitions, such as those for Coordinate Reference Systems are available in GML.</div><div><br></div><div>Any OGC member or Alliance Partner can submit a proposal for terms or names of resources to be registered. OSGeo is an alliance partner so can also submit a proposal. Upon receipt of the proposal, the proposal is discussed and voted on by the OGC-NA. The OGC-NA relies on subject matter experts from the Domain Working Groups and Standards Working Groups for guidance on whether to approve a proposal.</div><div><br></div><div>The Definitions Server has been developed to support implementors of OGC standards and also the work of the OGC Naming Authority (OGC-NA), a subcommittee of the OGC Technical Committee. It’s procedures are at <a href="https://portal.opengeospatial.org/files/?artifact_id=37800" target="_blank">https://portal.opengeospatial.org/files/?artifact_id=37800</a></div><div><br></div><div>Other policies are at <a href="https://www.opengeospatial.org/standards/na" target="_blank">https://www.opengeospatial.org/standards/na</a></div><div><br></div><div>The definitions are published through the OGC Definitions Server at <a href="http://www.opengis.net/def" target="_blank">http://www.opengis.net/def</a></div><div><br></div><div>Below the Definitions Server is infrastructure to support redirection and proxying to other registers (e.g. Sensor Model Registers, Coordinate Reference System registers, UoM registers etc).</div><div><br></div><div>OGC is not currently looking to replace the Definitions Server, nor the infrastructure on which it is built.</div><div><br></div><div>Some key lessons that we can share are that:</div><div>* The governance, policies and procedures (many of which are described in ISO 19135-1:2015) are very important. </div><div>* The role of subject matter experts is also very important.</div><div><br></div><div>Regards,</div><div><br></div><div>Gobe</div><div>
<div style="overflow-wrap: break-word;"><div style="color:rgb(0,0,0);font-family:Helvetica;font-size:12px;font-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px">__________________________________________<br><br>Gobe Hobona, PhD MRICS<br>Director, Knowledge Management<br>Open Geospatial Consortium (OGC)<br>OGC: Making location count.<br><br><a href="http://www.linkedin.com/in/gobehobona" target="_blank">http://www.linkedin.com/in/gobehobona</a><br>Tel: +44 744 409 6781<br>e-mail: <a href="mailto:ghobona@ogc.org" target="_blank">ghobona@ogc.org</a><br><a href="http://www.opengeospatial.org" target="_blank">www.opengeospatial.org</a></div><br></div><br>
</div>
<br><div><blockquote type="cite"><div>On 30 Sep 2019, at 21:04, Cameron Shorter <<a href="mailto:cameron.shorter@gmail.com" target="_blank">cameron.shorter@gmail.com</a>> wrote:</div><br><div>
<div bgcolor="#FFFFFF"><p>Gobe, Carl, Scott,</p><p>I'm keen to hear the OGC weigh in on the geolexia approach being
proposed. (Ideally before weighing in on the good questions
below). In particular, I'd like to hear discussion about whether
the OGC might adopt a similar approach, or set of processes, or
adopt the same technology stack. I feel we wouldn't have done our
due diligence if we were to propose advice to the OSGeo community
without first getting endorsement from the OGC.<br>
</p><p>I think ISO TC211, the OGC, and OSGeo are key players here, and
it would be good to have us all singing from the same songbook.</p><p>I'm also listening for lessons that we can take from the
geospatial domain into general documentation guidance for all open
source (and other) domains, through TheGoodDocsProject I'm helping
set up.</p><p>Cheers, Cameron</p>
<div>On 30/9/19 9:23 pm, Ronald Tse wrote:<br>
</div>
<blockquote type="cite">
<div style="overflow-wrap: break-word;">
Hi Felicity, Bruce,
<div><br>
</div>
<div>Thanks for the great questions! As a noob to
OSGeo, replies inline…</div>
<div><br>
</div>
<div>
<blockquote type="cite">
<div>• Before we can do any sort of bulk upload
we'll need to add columns for the fields we're missing to
comply with the required format. (For example,
entry_status, authoritative_source, etc)<br>
</div>
</blockquote>
<div><br>
</div>
<div>If it is decided that the Google Sheet will
serve as the authoritative data store for the glossary, we
have the ability to pull from that to generate the site.</div>
<br>
<blockquote type="cite">
<div>• Is this an authoritative OSGeo taxonomy?<br>
</div>
</blockquote>
<div><br>
</div>
<div>It should be?</div>
<br>
<blockquote type="cite">
<div>• What terms do we want included?<br>
</div>
</blockquote>
<div><br>
</div>
<div>Probably all technical terms across OSGeo
projects, I imagine that OSGeoLive documentation would
provide a host of them?</div>
<br>
<blockquote type="cite">
<div>• How do we define the ‘official’,
authoritative definition of the term(s)?<br>
</div>
</blockquote>
<div><br>
</div>
<div>Maybe there should be some terminology group /
list setup to vet these terms and their sources?</div>
<br>
<blockquote type="cite">
<div>• How do we approve new terms? What process is
required to do the approval?<br>
</div>
</blockquote>
<div>
<blockquote type="cite">• Similarly, what process
do we need to modify, retire or remove an existing
‘authoritative’ term?<br>
</blockquote>
</div>
<div><br>
</div>
<div>These actions relating to term lifecycle ought
to be done by people (and probably consensus), especially
since stability is arguably important. Some process should
be required. Maybe a terms of reference for this terminology
management list/group will be needed.</div>
<div><br>
</div>
<div>Ron</div>
<br>
<div>
<div style="letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px">
_____________________________________<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>
+=========================================================+</div>
</div>
<div><br>
<blockquote type="cite">
<div>On Sep 30, 2019, at 10:01 AM, Bruce
Bannerman <<a href="mailto:bruce.bannerman.osgeo@gmail.com" target="_blank">bruce.bannerman.osgeo@gmail.com</a>>
wrote:</div>
<br>
<div>
<div style="overflow-wrap: break-word;">
Hi everyone.
<div><br>
</div>
<div>If we are to set up a taxonomy, I
suggest that we also think about a process behind
the inclusion of ‘authoritative’ terms. </div>
<div><br>
</div>
<div>This will become important for the
future use and re-use of this taxonomy.</div>
<div><br>
</div>
<div>Some items to think about:</div>
<div><br>
</div>
<div>
<ul>
<li>Is this an authoritative OSGeo
taxonomy?</li>
<li>What terms do we want included?</li>
<li>How do we define the ‘official’,
authoritative definition of the term(s)?</li>
<li>How do we approve new terms? What
process is required to do the approval?</li>
<li>Similarly, what process do we need to
modify, retire or remove an existing
‘authoritative’ term?</li>
</ul>
<div><br>
</div>
<div>Thjis will become important as people
come to rely on an OSGeo taxonomy.</div>
<div><br>
</div>
<div>Also, I fully endorse Ron’s comments
about not reinventing the wheel and re-using
existing taxonomies where possible.</div>
<div><br>
</div>
<div>Kind regards,</div>
<div><br>
</div>
<div>Bruce</div>
<div><br>
</div>
<div><br>
<blockquote type="cite">
<div>On 30 Sep 2019, at 09:42, Felicity
Brand <<a href="mailto:felicitybrand@gmail.com" target="_blank">felicitybrand@gmail.com</a>>
wrote:</div>
<br>
<div>
<div dir="ltr">
<div>I spent a few hours yesterday
collating content from sources people had
sent us into a spreadsheet. There's nearly
500 terms in there: <a href="https://docs.google.com/spreadsheets/d/19tulyAEDN5Q5n-u_jlmXIKQjPI2Lwv6fh5Orad1mz1I/edit#gid=0" target="_blank">https://docs.google.com/spreadsheets/d/19tulyAEDN5Q5n-u_jlmXIKQjPI2Lwv6fh5Orad1mz1I/edit#gid=0</a></div>
<div><br>
</div>
<div>As I understand it:</div>
<div>
<ul>
<li style="margin-left:15px">Before
we can do any sort of bulk upload
we'll need to add columns for the
fields we're missing to comply with
the required format. (For example,
entry_status, authoritative_source,
etc)</li>
<li style="margin-left:15px">We'll
need to review and cull terms that are
generic or extraneous - that aren't
quite OSGeo specific.</li>
</ul>
</div>
<div><br>
</div>
<div>Thanks</div>
<div>Felicity</div>
</div>
<br>
<div class="gmail_quote">
<div dir="ltr" class="gmail_attr">On Mon,
Sep 30, 2019 at 9:27 AM 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">
<div dir="ltr">Folks,
<div>As per links below, Ron
has set up an OSGeo Glossary system
that we can play around with.</div>
<div>Feedback welcomed ...</div>
</div>
<br>
<div class="gmail_quote">
<div dir="ltr" class="gmail_attr">On
Mon, 30 Sep 2019 at 07:51, Reese W.
Plews <<a href="mailto:rplews@gmail.com" target="_blank">rplews@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">
hello Cameron, good morning. no
problem moving back to the mail
list.<br>
we just were not sure if you were
ready that it be shown to your group<br>
or not at this time.<br>
<br>
the loading process for geolexica
was built around the requirements of<br>
the ISO MLTG excel file. moving
entries into an excel file with the<br>
same format would be the easiest way
to load content. bringing them in<br>
from another source would require
code additions/modifications. Ron<br>
can tell you where those
modifications would be needed and i
am sure<br>
there are members in your group who
could work up something that meets<br>
your requirements. but if you have
entries already in a list-like<br>
form, putting them into excel is an
easy way.<br>
<br>
i was not aware of the other
projects, but Ron may have heard of
them<br>
before. thank you for mentioning our
work to them. if they are able to<br>
make use of geolexica or some of the
terminology management concepts<br>
that we use within TC211 i think we
are very happy.<br>
<br>
will be in touch,<br>
<br>
reese<br>
<br>
On Mon, Sep 30, 2019 at 5:30 AM
Cameron Shorter<br>
<<a href="mailto:cameron.shorter@gmail.com" target="_blank">cameron.shorter@gmail.com</a>>
wrote:<br>
><br>
> Wow!!!<br>
> I feel like it is Christmas.
Thankyou.<br>
> Do you mind if we take this
email thread back on list?<br>
> Assuming it is okay with you,
I'd like to show it to the rest of
the<br>
> OSGeo community, and start
talking about next steps with them.<br>
><br>
> Questions will cover:<br>
> 1. Do you have any suggestions
for bulk uploading hundreds for
existing<br>
> terms? I suggest a tool be
written to support that.<br>
><br>
> 2. A few months ago, I've
helped kick off TheGoodDocsProject
[1], where<br>
> a bunch of senior tech writers
are building best practice templates
and<br>
> writing instructions for
documenting open source projects. I
think that<br>
> you might have part of the
answer to what goes into a
"Glossary"<br>
> template. So I'd like to
introduce you to that email list
too. [2]<br>
><br>
> [1] <a href="https://thegooddocsproject.dev/" rel="noreferrer" target="_blank">
https://thegooddocsproject.dev/</a><br>
> [2] <a href="https://groups.io/g/thegooddocsproject/" rel="noreferrer" target="_blank">
https://groups.io/g/thegooddocsproject/</a><br>
><br>
> On 30/9/19 12:25 am, Ronald Tse
wrote:<br>
> > And the site branding has
been somewhat updated with OSGeo
branding.<br>
> > We’ll refine the design in
the days to come.<br>
> ><br>
> > Ron<br>
</blockquote>
</div>
<br clear="all">
<div><br>
</div>
<div dir="ltr" class="gmail_attr">From:
<strong class="gmail_sendername" dir="auto">
Ronald Tse</strong> <span dir="auto"><<a href="mailto:tse@ribose.com" target="_blank">tse@ribose.com</a>></span><br>
Date: Sun, 29 Sep 2019 at 23:08<br>
Subject: Re: glossary discussion on
osgeo-standards ....<br>
To: Cameron Shorter <<a href="mailto:cameron.shorter@gmail.com" target="_blank">cameron.shorter@gmail.com</a>><br>
Cc: Reese Plews <<a href="mailto:rplews@gmail.com" target="_blank">rplews@gmail.com</a>><br>
</div>
<br>
<br>
<div>Hi Cameron,
<div><br>
</div>
<div>I’m happy to let you
know the site is somewhat live (the
design, not yet):</div>
<div><a href="https://osgeodev.geolexica.org/" target="_blank">https://osgeodev.geolexica.org</a></div>
<div><br>
</div>
<div>The first term there is
your do-ocracy:</div>
<div><a href="https://osgeodev.geolexica.org/concepts/10/" target="_blank">https://osgeodev.geolexica.org/concepts/10/</a></div>
<div><br>
</div>
<div>The repo is located at:</div>
<div><a href="https://github.com/geolexica/osgeo.geolexica.org" target="_blank">https://github.com/geolexica/osgeo.geolexica.org</a></div>
<div><br>
</div>
<div>I’ve added some
contribution instructions here,
certainly they can be improved:</div>
<div><a href="https://github.com/geolexica/osgeo.geolexica.org#contributing" target="_blank">https://github.com/geolexica/osgeo.geolexica.org#contributing</a></div>
<div><br>
</div>
<div>The deployment is
automated. If you can provide your
(and/or your team's) GitHub
handle(s) I can add you to the group
for direct access, especially for
the addition of terms. </div>
<div><br>
</div>
<div>Hope this helps!</div>
<div><br>
</div>
<div>Ron</div>
<div><br>
<div>
<div>_____________________________________<br>
<br>
Ronald Tse<br>
Ribose Inc.</div>
</div>
</div>
</div>
<div dir="ltr">
<div dir="ltr">
<div>
<div dir="ltr">
<div dir="ltr">
<div dir="ltr">
<div dir="ltr">
<div dir="ltr">
<div>
<div><br>
</div>
</div>
<div><br>
<br>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</blockquote>
</div>
_______________________________________________<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" target="_blank">https://lists.osgeo.org/mailman/listinfo/standards</a></div>
</blockquote>
</div>
<br>
</div>
</div>
</div>
</blockquote>
</div>
<br>
</div>
</div>
<br>
<fieldset></fieldset>
<pre>_______________________________________________
Standards mailing list
<a href="mailto:Standards@lists.osgeo.org" target="_blank">Standards@lists.osgeo.org</a>
<a href="https://lists.osgeo.org/mailman/listinfo/standards" target="_blank">https://lists.osgeo.org/mailman/listinfo/standards</a></pre>
</blockquote>
<pre cols="72">--
Cameron Shorter
Technology Demystifier
Open Technologies and Geospatial Consultant
M +61 (0) 419 142 254</pre>
</div>
</div></blockquote></div><br></div>
<br>
<div style="color:rgb(34,34,34);font-size:small;background-color:rgb(255,255,255)"><a href="http://www.locationpowers.net/events/1911california/" style="color:rgb(17,85,204)" target="_blank"><i>Location Powers: Data Science</i></a> - 90% early bird discount until October 15.<br>Be part of a discussion on how the core methods of data science can provide valuable insights when used with geospatial information.</div><div style="color:rgb(34,34,34);font-size:small;background-color:rgb(255,255,255)">13th & 14th November, 2019 | Google Crittenden Campus, Mountain View, CA | <a href="https://twitter.com/hashtag/LP_DS" style="color:rgb(17,85,204)" target="_blank">#LP_DS</a></div></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></div>