<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<p>Angelos, the other end of the day would probably be easier. I
think this link shows board locations along with Ron (Hong Kong)
and Reese (Tokyo).</p>
<p><a
href="https://www.timeanddate.com/worldclock/meetingtime.html?year=2019&month=10&day=19&p1=240&p2=248&p3=102&p4=269&p5=250&p6=26&p7=37&p8=286&p9=734">https://www.timeanddate.com/worldclock/meetingtime.html?year=2019&month=10&day=20&p1=240&p2=248&p3=102&p4=269&p5=250&p6=26&p7=37&p8=286&p9=734</a></p>
<p>Does anyone else from the OSGeo board have an opinion on this
proposal and wish to share it? We could make the meeting
coordination easier if we narrow participation to only those with
an interest and an opinion.<br>
</p>
<div class="moz-cite-prefix">On 18/10/19 8:16 pm, Angelos Tzotsos
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:de660cd6-18a5-620d-12af-b75f2de009fb@gmail.com">Hi,
<br>
<br>
In that case we should probably arrange a specific call for this
topic.
<br>
I think the only working timeslot would be around 20:00-22:00 UTC
<br>
<br>
On 10/17/19 9:24 PM, Cameron Shorter wrote:
<br>
<blockquote type="cite">Angelos, the board meeting is 3am for me.
The 3 of us involved are in this Asian/Australia timezone.
<br>
<br>
Reese, we can get you set up with IRC (Internet Chat Relay)
quite easily. It is text based only. Quickest way to get started
is with the web client: <a class="moz-txt-link-freetext" href="https://webchat.freenode.net/">https://webchat.freenode.net/</a>
<br>
<br>
On 17/10/19 10:19 pm, <a class="moz-txt-link-abbreviated" href="mailto:rplews@tc211tmg.org">rplews@tc211tmg.org</a> wrote:
<br>
<blockquote type="cite">hello Angelos, thank you for the
invitation, two issues for me, local time is 1am and i have
never done Internet Relay Chat. i can do skype or zoom. if you
have another time/date let me know. sorry about this time.
<br>
reese
<br>
<br>
<br>
----- Original Message -----
<br>
From:
<br>
"Angelos Tzotsos" <a class="moz-txt-link-rfc2396E" href="mailto:gcpp.kalxas@gmail.com"><gcpp.kalxas@gmail.com></a>
<br>
<br>
To:
<br>
"Cameron Shorter" <a class="moz-txt-link-rfc2396E" href="mailto:cameron.shorter@gmail.com"><cameron.shorter@gmail.com></a>,
<br>
<a class="moz-txt-link-rfc2396E" href="mailto:standards@lists.osgeo.org"><standards@lists.osgeo.org></a>, <a class="moz-txt-link-rfc2396E" href="mailto:board@lists.osgeo.org">"board@lists.osgeo.org"</a>
<br>
<a class="moz-txt-link-rfc2396E" href="mailto:board@lists.osgeo.org"><board@lists.osgeo.org></a>, "OSGeo Discussions"
<a class="moz-txt-link-rfc2396E" href="mailto:discuss@lists.osgeo.org"><discuss@lists.osgeo.org></a>
<br>
Cc:
<br>
"Reese Plews" <a class="moz-txt-link-rfc2396E" href="mailto:rplews@gmail.com"><rplews@gmail.com></a>
<br>
Sent:
<br>
Thu, 17 Oct 2019 12:14:37 +0300
<br>
Subject:
<br>
Re: [OSGeo-Standards] [Board] glossary discussion on
<br>
osgeo-standards ....
<br>
<br>
<br>
Hi all,
<br>
<br>
Would someone be available to join our next board meeting
to
<br>
discuss this issue?
<br>
<a class="moz-txt-link-freetext" href="https://wiki.osgeo.org/wiki/Board_Meeting_2019-10-28">https://wiki.osgeo.org/wiki/Board_Meeting_2019-10-28</a>
<br>
<br>
Regards,
<br>
Angelos
<br>
<br>
On 10/15/19 9:52 PM, Cameron Shorter wrote:
<br>
<br>
OSGeo Board, OSGeo Discuss,
<br>
<br>
I'd like to introduce you to this proposal that Ron
and Reese
<br>
have been developing on the OSGeo Standards email
list, which
<br>
I think should fit under the legal structure of an
OSGeo
<br>
Committee.
<br>
<br>
I have vague recollections that setting up a committee
<br>
requires board approval? I've found some old tips on
running a
<br>
committee here:
<a class="moz-txt-link-freetext" href="https://wiki.osgeo.org/wiki/Committee_Guidelines">https://wiki.osgeo.org/wiki/Committee_Guidelines</a>
<br>
<br>
Comments welcomed.
<br>
<br>
On 15/10/19 4:47 pm, Ronald Tse wrote:
<br>
<br>
Hi Cameron,
<br>
<br>
Thank you for the suggestions! I have updated the
proposal
<br>
to reflect your comments below.
<br>
<br>
I would be honored to help with terminology
management at
<br>
OSGeo. Can’t speak for Reese but with his
leadership in
<br>
already doing terminology cleanup on Felicity’s
sheet, he
<br>
seems pretty committed already :-)
<br>
<br>
Ron
<br>
<br>
———
<br>
<br>
Recommendations for OSGeo terminology management
<br>
<br>
1. Establish a terminology management group in
OSGeo.
<br>
<br>
ISO/TC 211, IEC Electropedia and OGC all have one
for
<br>
terminology management. The existence of this
group is
<br>
crucial to the success of the OSGeo terminology
database.
<br>
It will play two essential roles:
<br>
<br>
a) As the gatekeeper of terms to ensure quality
checks of
<br>
contributions
<br>
b) As the seat of central terminology knowledge
for
<br>
alignment of terms and concepts. To facilitate the
flow of
<br>
terminology knowledge to terminology authors and
users.
<br>
<br>
It would be helpful to involve representation from
ISO/TC
<br>
211 and OGC in this group, in order to leverage
their
<br>
experience in terminology. Such experience will be
useful
<br>
in situations such as alerting on
cross-organization
<br>
alignment of concepts or term duplication.
<br>
<br>
An email list shall be setup for this group for
internal
<br>
communication.
<br>
<br>
<br>
2. Establish a terms of reference for terminology
management.
<br>
<br>
For the terminology management group, a terms of
reference
<br>
should be produced so that the steps for approval
and data
<br>
quality requirements are clear. This should be
openly
<br>
shared with contributors so they are clear on
acceptance
<br>
criteria.
<br>
<br>
Contributors may propose changes to the
terminology
<br>
database at any time. The terminology management
group
<br>
shall discuss and approve or disapprove of the
proposal
<br>
within a reasonable timeframe. This practice is
in-line
<br>
with the open source, change-based,
rapid iteration
<br>
mantra, similar to OpenSSL.
<br>
<br>
For releases, the group shall convene
periodically, such
<br>
as every 4-6 months, to discuss previously decided
<br>
proposals, governance or technical issues related
to
<br>
terminology management.
<br>
<br>
The method of submitting change requests shall
also be
<br>
determined and announced so that contributors
understand
<br>
the necessary processes and timeline.
<br>
<br>
<br>
3. Establish an online terminology database
presence.
<br>
<br>
Terminology isn’t useful until people use them,
which
<br>
means people need to first know they exist and
what they
<br>
mean. Geolexica is an initiative that currently
serves
<br>
ISO/TC 211’s terminology management group in
making its
<br>
multi-lingual geographic information
terminology available
<br>
on the internet (<a class="moz-txt-link-freetext" href="https://www.geolexica.org">https://www.geolexica.org</a>). We
propose to
<br>
use <a class="moz-txt-link-freetext" href="https://osgeo.geolexica.org/">https://osgeo.geolexica.org/</a> to serve OSGeo in
<br>
managing its terminology database. Geolexica not
only
<br>
serves human-readable concepts and terms, but also
serves
<br>
in machine-readable JSON, allowing APIs to
directly
<br>
consume the content.
<br>
<br>
The structure of Geolexica is designed for
efficiency with
<br>
streamlined management and operations. Terms are
stored in
<br>
structured data (YAML) files, and are directly
deployable
<br>
to the website. The website operates according to
best
<br>
practices, and is served as a static website with
dynamic
<br>
search functionality. Security and performance
have always
<br>
been key considerations.
<br>
<br>
For terms that originate from other authoritative
<br>
terminology databases, such as those from ISO or
OGC, a
<br>
linkage shall be established from the OSGeo
terminology
<br>
database back to the source.
<br>
<br>
<br>
4. Use an issue tracker with source code
management
<br>
functionality as an open communication platform
(e.g.
<br>
GitHub).
<br>
<br>
The issue tracker is used to perform two-way
communication
<br>
between OSGeo members and the contributors. This
requires
<br>
every contributor to at least have an account,
which helps
<br>
minimize spam. The source code management
functionality is
<br>
used to manage terminology data in a
machine-useable way.
<br>
<br>
There are generally two types of contributors:
<br>
<br>
a) those who suggest changes via textual
description, and
<br>
b) those who suggest changes but can also format
the
<br>
desired content in the data format used by the
terminology
<br>
database.
<br>
<br>
People can easily help out with the former in
formatting
<br>
the changes into a proper data structure change.
This
<br>
allows the terminology management group to
directly
<br>
approve, merge and deploy the proposed term
modifications
<br>
(and creations, deletions), all made
effective with a
<br>
single click.
<br>
<br>
<br>
5. Allow easy feedback from terminology users.
<br>
<br>
To minimize friction in the feedback process, for
every
<br>
term offered in the OSGeo terminology pages we can
offer a
<br>
“propose new term” and “propose changes to this
term"
<br>
buttons. This allows user to directly go to the
issue
<br>
platform (e.g. GitHub) to make the
suggested changes.
<br>
<br>
A “contributors guide” document will greatly help
these
<br>
people make the proper suggestions and have them
formatted
<br>
correctly.
<br>
<br>
<br>
6. Initial load and data cleanup.
<br>
<br>
The initial load of the terms will involve a bulk
load
<br>
from the cleaned terms and definitions that
Felicity has
<br>
compiled. Geolexica could easily handle the
initial
<br>
conversion from table format into the desired
structured
<br>
data format.
<br>
<br>
The cleanup process has already been started by
Reese
<br>
Plews, convenor of the TMG at ISO/TC 211.
<br>
<br>
<br>
_____________________________________
<br>
<br>
Ronald Tse
<br>
Ribose Inc.
<br>
<br>
On Oct 10, 2019, at 3:34 PM, Cameron Shorter
<br>
<a class="moz-txt-link-rfc2396E" href="mailto:cameron.shorter@gmail.com"><cameron.shorter@gmail.com></a> wrote:
<br>
<br>
Hi Ron,
<br>
<br>
I really like your proposal. It looks very
practical,
<br>
should address quality requirements, and
should be
<br>
relatively light weight to manage. Some
<br>
comments/suggestions:
<br>
<br>
* You might want to mention the approach to
your first
<br>
load of terms, which probably should involve a
bulk
<br>
load from a derivative of the terms that
Felicity has
<br>
compiled.
<br>
<br>
* I suggest we set up an email list to discuss
terms.
<br>
OSGeo can provide that for us, and I can
coordinate
<br>
that, once we have agreed on our approach.
<br>
<br>
* I suggest that an updating the glossary be
tied to a
<br>
periodic event, at least annually. I think we
should
<br>
tie in with the OSGeoLive annual build cycle
for this.
<br>
<br>
* You haven't mentioned
<a class="moz-txt-link-freetext" href="https://osgeo.geolexica.org/">https://osgeo.geolexica.org/</a>
<br>
<a class="moz-txt-link-rfc2396E" href="https://osgeo.geolexica.org/"><https://osgeo.geolexica.org/></a> in your
description. I
<br>
assume that would be part of the solution? If
so, I
<br>
suggest mentioning it.
<br>
<br>
* Another project I'm helping start up is
<br>
<a class="moz-txt-link-freetext" href="https://thegooddocsproject.dev/">https://thegooddocsproject.dev/</a>
<br>
<a class="moz-txt-link-rfc2396E" href="https://thegooddocsproject.dev/"><https://thegooddocsproject.dev/></a>
(Writing templates
<br>
to make good docs for open source projects). I
expect
<br>
that the solution you are proposing would be
valuable
<br>
for a wide variety of domains, and should be
captured
<br>
as best practices in TheGoodDocsProject. At
some point
<br>
in the future, I'm hoping that you might
provide a
<br>
generic version of your suggestions for others
to
<br>
follow too.
<br>
<br>
Feel free to add your ideas below into the
wiki at:
<br>
<a class="moz-txt-link-freetext" href="https://trac.osgeo.org/osgeolive/wiki/Glossary%20terms">https://trac.osgeo.org/osgeolive/wiki/Glossary%20terms</a>
<br>
<br>
(Maybe add "DRAFT" at the top, until we have
the
<br>
process set up.)
<br>
<br>
* Ron and Reese, I'm hoping that you both will
<br>
continue to provide the leadership and
stewardship of
<br>
the community as it grows? Your advice has
been great
<br>
to date.
<br>
<br>
Warm regards, Cameron
<br>
<br>
<br>
<br>
_______________________________________________
<br>
Standards mailing list
<br>
<a class="moz-txt-link-abbreviated" href="mailto:Standards@lists.osgeo.org">Standards@lists.osgeo.org</a>
<br>
<a class="moz-txt-link-freetext" href="https://lists.osgeo.org/mailman/listinfo/standards">https://lists.osgeo.org/mailman/listinfo/standards</a>
<br>
<br>
<br>
<br>
_______________________________________________
<br>
<br>
<br>
<br>
Board mailing list
<br>
<a class="moz-txt-link-abbreviated" href="mailto:Board@lists.osgeo.org">Board@lists.osgeo.org</a>
<br>
<a class="moz-txt-link-freetext" href="https://lists.osgeo.org/mailman/listinfo/board">https://lists.osgeo.org/mailman/listinfo/board</a>
<br>
<br>
<br>
<br>
--
<br>
<br>
<br>
Angelos Tzotsos, PhD
<br>
<br>
<br>
<br>
Charter Member
<br>
<br>
<br>
<br>
Open Source Geospatial Foundation
<br>
<a class="moz-txt-link-freetext" href="http://users.ntua.gr/tzotsos">http://users.ntua.gr/tzotsos</a>
<br>
<br>
</blockquote>
</blockquote>
<br>
<br>
</blockquote>
<pre class="moz-signature" cols="72">--
Cameron Shorter
Technology Demystifier
Open Technologies and Geospatial Consultant
M +61 (0) 419 142 254</pre>
</body>
</html>