OSGeo - User contributions [en]

Season Of Docs 2021 Proposal

2021-03-23T07:41:12Z

Wiki-Tc211 tmg:

<center>
[[Image:SeasonofDocs_Logo_SecondaryGrey_300ppi.png|400px|link=https://developers.google.com/season-of-docs/]] <font size="+3"> @ </font>
[[Image:Osgeo-logo.png|300px|link=http://www.osgeo.org]]
</center>

= Cross-organizational glossaries guide - OSGeo Foundation =

This is a proposal to have a technical writer sponsored under [https://developers.google.com/season-of-docs Google’s Season of Docs] to:

* Document processes for establishing cross-organizational glossaries.
* Support others set up pilot glossaries within some of the geospatial open source projects.

== About OSGeo ==

The Open Source Geospatial Foundation (OSGeo) is a not-for-profit organization whose mission is to foster global adoption of open geospatial technology by being an inclusive software foundation devoted to an open philosophy and participatory community driven development. OSGeo works with organizations worldwide promoting open source geospatial.

== Cross-organizational glossaries project ==

Glossaries are easy to set up for simple examples but extremely hard to scale - especially when a project wants to inherit or share terms with other organizations.

The cross-organizational glossaries project covers software, information schemas and best practice processes required to set up and manage glossaries which have interdependencies with other glossaries.

It is initially focusing on glossaries within the geospatial domain, where most of our volunteers are actively involved.

=== Backing organizations ===

The project is jointly backed by volunteers from multiple organizations:

* The [https://osgeo.org Open Source Geospatial (OSGeo) Foundation]
** An umbrella foundation, representing 50+ geospatial open source projects, sub-committees, and local chapters.
** The OSGeo Foundation is heading this Season of Docs proposal.
* [https://thegooddocsproject.dev The Good Docs Project]
** An open source community of technical writers building best practice templates and writing instructions for documenting open source software.
** A best practices glossary template and how-to guide is to be developed as part of this project.
* The [https://www.glossarist.org/ Glossarist] open source project
** A project dedicated to standing up and managing standards based, interoperable glossaries.
** This software is for government sized glossaries and is based on best practice standards.
** This software is being used within the project.
* The [https://www.ogc.org/ Open Geospatial Consortium (OGC)]
** An international geospatial standards setting body.
** The OGC volunteers have decades of experience with lexicon standards and terminology management which they are contributing to the project.
* [https://committee.iso.org/home/tc211 The ISO/TC211 geospatial standards committee]
** A committee managing geospatial glossary terminology.
** This committee is providing terminology, and mentoring in managing terminology.

=== Mentors ===

The following glossary project community members have offered to act as volunteer Season of Docs mentors for this project. Each brings a unique set of skills to the project and collective creates a robust community.

Ilie Codrina Maria

* OSGeo Foundation board member

Nikos Lambrinos

* Geography Professor
* Chief Editor of GeoForAll Newsletter and GeoForAll glossary
* (GeoForAll is an initiative under the OSGeo Foundation)

Cameron Shorter

* One of the coordinators of The Good Docs Project
* Ex OSGeo board member, and open source project coordinator/contributor
* Tech writer at Google

Rob Atkinson

* Expert on structured data, schemas, glossaries, interoperability, …
* Open Geospatial Consortium staff member

Ronald Tse

* Lead developer of the open source glossarist software being used
* ISO/TC 211 and OGC member

Reese Plews

* Convenor of the ISO/TC 211 Terminology Management Group (TMG)
* Coordinator of the ISO/TC 211 Multi-Lingual Glossary of Terms (MLGT)

Ankita Tripathi (if not engaged as the tech writer for this project)

* Technical Writer
* Project Steering Committee member of The Good Docs Project

=== Umbrella project ===

The cross-organizational glossary project is a bit unusual in that it is acting as an umbrella project, with much of the generated material being deliberately kept inside other projects.

For evidence of a mature and active community, refer to:

* [https://osgeo.geolexica.org/concepts/ Geospatial glossary terms], compiled by our team.
* [https://github.com/thegooddocsproject/templates The Good Docs Project templates repository], where the glossary template will fit.
* [https://github.com/OSGeo/OSGeoLive-doc Docs repository for the OSGeo-Live] distribution, where we intend to add glossary entries.
* [https://github.com/glossarist Glossarist github repository], which stores the glossary software.
* [https://docs.google.com/document/d/1yzncnQB7uYktPnAQ4DqZYVPDdYnqDrWmqHzcpXrjkPg/edit Minutes from weekly meetings].

== Season of Docs focus ==

From the perspective of projects under the umbrella of the OSGeo Foundation’s perspective:

* Existing documentation has immature glossaries - if one exists. And while there is significant overlap in the terminology used between projects, there is minimal integration and coordination in glossary terms. This hinders communication about common concepts.

From our cross-organisational glossary’s project perspective:

* While our team has collated significant best practices expertise, it hasn’t been collated in explanations and how-tos which are easy-to-follow by everyday people wanting to stand up an interoperable glossary.

The focus of this Season of Docs initiative is to engage a technical writer to develop such documentation, and test it with pilot users.

=== Season of Docs scope ===

==== In scope ====

Deliverable: Cross-organizational glossaries concept document

* This document will explain concepts and theory behind cross-organizational glossaries. It will potentially cover topics such as:
** Why you should care.
** When you should care?
** What should you care about?
** Options and recommendations for information schemas.
** Options and recommendations for governance.
** Relevant standards.
** References to further research.

Deliverable: glossary-template and glossary-template-guide

* These template documents will align with the base-template provided by The Good Docs Project, and will provide practical guidance on how to set up a glossary.

Deliverable: Support pilot projects testing the documentation

* The tech writer will participate in discussions with people testing the templates and concept documentation, provide advice, and absorb feedback.
* This deliverable is dependent upon the project sourcing appropriate volunteers within the timeframe of the project.

Deliverable: Project Case Study

* The tech writer will act as the primary author of a case study in the success and challenges faced during the Season of Docs project.
* This case study will be co-authored by the project mentors, and interested community mentors.

Note: Due to the unknowns in this project, the tech writer and mentors may agree to adjust the scope by mutual written agreement.

==== Source material ====

Source material is to be collated from existing team material and know-how.

==== Quality ====

As this project is breaking a significant amount of new ground, we don’t expect to get it right the first time.

We anticipate the resulting documentation to be of pilot quality. It is likely to contain placeholders and sections to be filled in later.

==== Out of scope ====

* Installing or configuring specific glossaries. This will be the responsibility of participating projects.
* Contributing to the term definitions within specific glossaries. This will be the responsibility of glossary owners.
* Establishing governance processes for a specific glossary.
* Establishing a measurement framework for the success of this project.

==== Potential tech writers ====

We have a tech writer, Ankita Tripathi, who we would like to engage for this project.

* Ankita is a professional technical writer.
* She has been actively involved with OSGeo communities, the cross-organizational glossary project and The Good Docs Project on a volunteer basis, and has a strong background understanding of the problem.
* She has shown significant competence, initiative and dedication as an open source technical writer, and will be well positioned to tackle this project.

If Ankita’s availability changes, there are others in our community we could approach.

If our project is selected, we intend to engage our technical writer soon after the April 16 selection date. This should spread the workload and mitigate schedule risk.

=== Measuring Season of Docs success ===

There is a difference between metrics we’d like to have compared to metrics which we can easily and sustainably measure within our community. Here we list what we think we can sustain, described using (Goal, Indicator, Metric).

Goal: Help communicators reduce cognitive load

Sub-goal: Help communicators build and manage glossaries which explain terms used by the communitators

Sub-goal: Provide a scalable framework for cross-organizational glossary management

Sub-goal: Reduce effort required for cross-organizational glossary management

* Indicator: Projects stand up standards compliant glossary services
** Measure: Count the number of standards compliant glossary services stood up based on our instructions, that we are aware of.
*** Success criteria: Within the project timeframe, we will consider this project a success if two glossaries are stood up and interoperate with each other, based on instructions provided.

Sub-goal: Educate people on the benefits and challenges of cross-organizational glossary management

* Indicator: Explanation document is read
** Metric: Count the views of an explanation document
*** Success criteria: Within the project timeframe, we don’t expect to have collected enough page views to gain any meaningful results.

== Project budget ==
{| class="wikitable"
|-
! Item !! Amount $US !! Notes
|-
| Technical writer || 4,500 ||
|-
| Supporting organization overheads || 300 || Incidentals such as bank processing fees, and general good will.
|-
| Swag || 200 || Due to our high mentor:writer and likely high community:writer ratios, we would prefer to invest more than the $200 minimum for goodwill with our community. Details to be confirmed, but may cover something like 10 tee shirts for volunteers.
|-
| Total || 5,000 ||
|}

== Additional information ==

* The OSGeo Foundation, The Good Docs Project, and some of our mentors have participated in both Google Season of Docs and Google Summer of Code.
* Some of our mentors and participating community members are professional technical writers.
* Our mentors collectively have decades of experience with structured data, glossaries. They are also associated with international standards bodies which enables us to both learn from and influence these bodies.

We believe that this depth of experience provides us with insights, experience, and the drive required to tackle this difficult documentation use case.

Lexicon Committee

2020-03-11T07:24:11Z

Wiki-Tc211 tmg: /* Communication */

The Lexicon committee is an [https://wiki.osgeo.org/wiki/Interest_Groups OSGeo Special Interest Group], responsible for coordinating official definitions for terminology used within the Open Source Geospatial (OSGeo) context. The committee is drawn from the OSGeo, OGC and ISO communities and is based on merit and interest.

= Purpose =

The Lexicon committee plays the following roles:

# Act as the gatekeeper of terms to ensure quality checks of contributions.
# Provide a central terminology knowledge for alignment of terms and concepts.
# Facilitate the flow of terminology knowledge to terminology authors and users.
# Support the use of best practices in writing terms.
# Facilitate developing consistent terminology between OSGeo projects.
# Act as a conduit of terms between OSGeo projects, OSGeo, OGC and ISO.

The committee involves individual representation from external groups including ISO/TC 211 and OGC in order to leverage their experience in terminology, which is useful in situations such as alerting on cross-organization alignment of concepts or term duplication.

= Online presence =

Terminology isn’t useful until people use them, which means people need to first know they exist and what they mean. The Geolexica initiative has setup https://osgeo.geolexica.org/ to serve OSGeo in managing the lexicon database.

Geolexica serves human-readable concepts and terms, as well as machine-readable JSON, allowing APIs to directly consume the content. It currently serves ISO/TC 211’s terminology management group in making its multi-lingual geographic information terminology available on the internet (https://www.geolexica.org).

To minimize friction in the feedback process, for every term offered in the OSGeo terminology pages it provides a “propose new term” and “propose changes to this term" buttons. This allows users to directly go to the issue platform (e.g. GitHub) to make the suggested changes.

The structure of Geolexica is designed for efficiency with streamlined management and operations. Terms are stored in structured data (YAML) files, and are directly deployable to the website. The website operates according to best practices, and is served as a static website with dynamic search functionality. Security and performance have always been key considerations.

TBD: We should mention that the Geolexia management software is based on Open Source (which mitigates project risk). We should link to the source code project in github.

OSGeo terms will additionally be published at:
* OSGeoLive
* TBD OSGeo Journal?

= Coordination =

== Initial load and data cleanup ==

The initial load of the terms will involve a bulk load from cleaned terms and definitions sourced from prior OSGeo glossaries. Geolexica could easily handle the initial conversion from table format into the desired structured data format.

As of 2019-10, the cleanup process has already [https://docs.google.com/spreadsheets/d/19tulyAEDN5Q5n-u_jlmXIKQjPI2Lwv6fh5Orad1mz1I/edit#gid=0 started].

== Updates ==
* New terms, or improvements to existing terms may be proposed at any time, by anyone in the community.
* It is recommended that proposed term updates are initially discussed and refined on the Lexicon email list. TBD: Link to list once setup.
* Terms can then be submitted to the GeoLexia website. TBD explain how.
* The lexicon committee will periodically review and approve new terms.
* The lexicon committee will review and update terms at least annually, in line with the OSGeoLive documentation build cycle.

== Communication ==
* Mail List: We communicate on the [https://lists.osgeo.org/mailman/listinfo/lexicon OSGeo Lexicon email list].
* Meetings
** Telecon 1: 2020-03-06 [https://drive.google.com/open?id=1JdvCmmOJWdZgch0AdVG1YSEQ8J9Oq_Jy Minutes]

== Committee members ==
* [[User:camerons| Cameron Shorter]] (OSGeoLive, WriteTheDocs)
* Rob Atkinson (OGC)
* Ronald Tse (ISO/TC 211, ISO Geodetic Registry Registration Authority, Ribose Inc.)
* Reese Plews (ISO/TC 211, Terminology Management Group)
* [[User:Jgrocha|Jorge Gustavo Rocha]] (OSGeo/QGIS)
* [[User:Codrina|Ilie Codrina Maria]] (OSGeo)
* [[User:Peter_Loewe|Peter Löwe]] (OSGeo/GRASS/RDA/EGU-ESSI)
* ... others welcomed

Past members. We thank these prior members for their contributions:
* None yet

Selection of new members is determined by committee member vote. Committee members may retire at any time. If a committee member becomes inactive for many months they may be invited to retire, and if unresponsive they may be retired by the existing committee.

==Decisions==
Decisions are based on voting using the following:
* +1: For
* +0: Mildly for, but mostly indifferent
* 0: Indifferent
* -0: Mildly against, but mostly indifferent
* -1: Strongly against. This is expected to be accompanied by a reason.

For most decisions, a motion is raised within one of the committee open forums (IRC, email list, etc) and those present vote and decide. Should a decision:
* Be strategic or impact many within the committee,
* Or if there be contention in deciding, and after discussion at least one member is still strongly against the motion, by continuing to vote -1,
* Then the motion should be referred to the committee.

For motions presented to the committee, a motion is considered passed when there are more committee +1 votes than -1 votes, and either all committee members have voted, or 1 week has passed. In the case of a tie, the committee chair shall have 1.5 votes.

==Expectations of committee members==
* Contribute to or related activities when the committee is active.
* Help with whatever dirty work is required to keep the project moving forward.
* Monitor committee conversations on our email list.

[[Category: Lexicon]]

Lexicon Committee

2020-03-11T06:59:01Z

Wiki-Tc211 tmg: /* Communication */

The Lexicon committee is an [https://wiki.osgeo.org/wiki/Interest_Groups OSGeo Special Interest Group], responsible for coordinating official definitions for terminology used within the Open Source Geospatial (OSGeo) context. The committee is drawn from the OSGeo, OGC and ISO communities and is based on merit and interest.

= Purpose =

The Lexicon committee plays the following roles:

# Act as the gatekeeper of terms to ensure quality checks of contributions.
# Provide a central terminology knowledge for alignment of terms and concepts.
# Facilitate the flow of terminology knowledge to terminology authors and users.
# Support the use of best practices in writing terms.
# Facilitate developing consistent terminology between OSGeo projects.
# Act as a conduit of terms between OSGeo projects, OSGeo, OGC and ISO.

The committee involves individual representation from external groups including ISO/TC 211 and OGC in order to leverage their experience in terminology, which is useful in situations such as alerting on cross-organization alignment of concepts or term duplication.

= Online presence =

Terminology isn’t useful until people use them, which means people need to first know they exist and what they mean. The Geolexica initiative has setup https://osgeo.geolexica.org/ to serve OSGeo in managing the lexicon database.

Geolexica serves human-readable concepts and terms, as well as machine-readable JSON, allowing APIs to directly consume the content. It currently serves ISO/TC 211’s terminology management group in making its multi-lingual geographic information terminology available on the internet (https://www.geolexica.org).

To minimize friction in the feedback process, for every term offered in the OSGeo terminology pages it provides a “propose new term” and “propose changes to this term" buttons. This allows users to directly go to the issue platform (e.g. GitHub) to make the suggested changes.

The structure of Geolexica is designed for efficiency with streamlined management and operations. Terms are stored in structured data (YAML) files, and are directly deployable to the website. The website operates according to best practices, and is served as a static website with dynamic search functionality. Security and performance have always been key considerations.

TBD: We should mention that the Geolexia management software is based on Open Source (which mitigates project risk). We should link to the source code project in github.

OSGeo terms will additionally be published at:
* OSGeoLive
* TBD OSGeo Journal?

= Coordination =

== Initial load and data cleanup ==

The initial load of the terms will involve a bulk load from cleaned terms and definitions sourced from prior OSGeo glossaries. Geolexica could easily handle the initial conversion from table format into the desired structured data format.

As of 2019-10, the cleanup process has already [https://docs.google.com/spreadsheets/d/19tulyAEDN5Q5n-u_jlmXIKQjPI2Lwv6fh5Orad1mz1I/edit#gid=0 started].

== Updates ==
* New terms, or improvements to existing terms may be proposed at any time, by anyone in the community.
* It is recommended that proposed term updates are initially discussed and refined on the Lexicon email list. TBD: Link to list once setup.
* Terms can then be submitted to the GeoLexia website. TBD explain how.
* The lexicon committee will periodically review and approve new terms.
* The lexicon committee will review and update terms at least annually, in line with the OSGeoLive documentation build cycle.

== Communication ==
* Mail List: We communicate on the [https://lists.osgeo.org/mailman/listinfo/lexicon OSGeo Lexicon email list].
* Meetings
** Telecon 1: 2020-03-06 (Minutes)

== Committee members ==
* [[User:camerons| Cameron Shorter]] (OSGeoLive, WriteTheDocs)
* Rob Atkinson (OGC)
* Ronald Tse (ISO/TC 211, ISO Geodetic Registry Registration Authority, Ribose Inc.)
* Reese Plews (ISO/TC 211, Terminology Management Group)
* [[User:Jgrocha|Jorge Gustavo Rocha]] (OSGeo/QGIS)
* [[User:Codrina|Ilie Codrina Maria]] (OSGeo)
* [[User:Peter_Loewe|Peter Löwe]] (OSGeo/GRASS/RDA/EGU-ESSI)
* ... others welcomed

Past members. We thank these prior members for their contributions:
* None yet

Selection of new members is determined by committee member vote. Committee members may retire at any time. If a committee member becomes inactive for many months they may be invited to retire, and if unresponsive they may be retired by the existing committee.

==Decisions==
Decisions are based on voting using the following:
* +1: For
* +0: Mildly for, but mostly indifferent
* 0: Indifferent
* -0: Mildly against, but mostly indifferent
* -1: Strongly against. This is expected to be accompanied by a reason.

For most decisions, a motion is raised within one of the committee open forums (IRC, email list, etc) and those present vote and decide. Should a decision:
* Be strategic or impact many within the committee,
* Or if there be contention in deciding, and after discussion at least one member is still strongly against the motion, by continuing to vote -1,
* Then the motion should be referred to the committee.

For motions presented to the committee, a motion is considered passed when there are more committee +1 votes than -1 votes, and either all committee members have voted, or 1 week has passed. In the case of a tie, the committee chair shall have 1.5 votes.

==Expectations of committee members==
* Contribute to or related activities when the committee is active.
* Help with whatever dirty work is required to keep the project moving forward.
* Monitor committee conversations on our email list.

[[Category: Lexicon]]

Lexicon Committee

2019-10-22T12:10:00Z

Wiki-Tc211 tmg: /* Background */

The Lexicon committee is responsible for coordinating official definitions for terminology used within the OSGeo context. The committee is drawn from the OSGeo, OGC and ISO communities and is based on merit and interest.

An email list shall be setup for this group for internal communication.

= Purpose =

The Lexicon committee plays two essential roles:

a) As the gatekeeper of terms to ensure quality checks of contributions
b) As the seat of central terminology knowledge for alignment of terms and concepts. To facilitate the flow of terminology knowledge to terminology authors and users.

The committee involves individual representation from external groups including ISO/TC 211 and OGC in order to leverage their experience in terminology, which is useful in situations such as alerting on cross-organization alignment of concepts or term duplication.

= Coordination =

= Committee members =
TBD: Once formed, the following people have volunteered to join this committee:

OSGEO Representation
* Cameron Shorter
* Felicity Brand (proposed)
* ... others welcomed
Outside Representation (Non-OSGEO)
* Ronald Tse (TC?/Ribose Inc.)
* Reese Plews (ISO/TC211, TMG)

* ... others welcomed

Selection of new members is determined by committee member vote. Committee members may retire any time. If a committee member becomes inactive for many months they may be invited to retire, and if unresponsive they may be removed by the existing committee.

==Decisions==
Decisions are based on voting using the following:
* +1: For
* +0: Mildly for, but mostly indifferent
* 0: Indifferent
* -0: Mildly against, but mostly indifferent
* -1: Strongly against. This is expected to be accompanied by a reason.

For most decisions, a motion is raised within one of the committee open forums (IRC, email list, etc) and those present vote and decide. Should a decision:
* Be strategic or impact many within the committee,
* Or if there be contention in deciding, and after discussion at least one member is still strongly against the motion, by continuing to vote -1,
* Then the motion should be referred to the committee.

For motions presented to the committee, a motion is considered passed when there are more committee +1 votes than -1 votes, and either all committee members have voted, or 1 week has passed. In the case of a tie, the committee chair shall have 1.5 votes.

==Expectations of committee members==
* Contribute to or related activities when the committee is active.
* Help with whatever dirty work is required to keep the project moving forward.
* Monitor committee conversations on our email list.

==Background==

Standards driven terminology vs. Software project driven terminology (highly simplified overviews)
* OGC: create/promote implementation standards which are built in part with terminology entries
* ISO/TC 211: create/promote conceptual standards which are built in part with terminology entries
* OSGEO: Foster global adoption of open geospatial technology by being an inclusive software foundation devoted to an open philosophy and participatory community driven development.

How do terminology entries (terms and definitions) "come into" OSGEO?
* through education texts (basic concepts)
* through software related documentation (user guides, tutorials)
* other

Who are experts in specific (project/domain) related terminology?
* educators, teachers
* project developers, programmers
* documentation writers

Who are experts in terminology management?
* lexicon committee members

==Terms of reference==

The terms of reference for the Lexicon Committee describes steps for lexicon approval and data quality requirements. This is openly shared with contributors for transparent acceptance criteria.

Contributors may propose changes to the terminology database at any time. The terminology management group shall discuss and approve or disapprove of the proposal within a reasonable timeframe. This practice is in-line with the open source, change-based, rapid iteration mantra, similar to OpenSSL.

For releases, the group shall convene periodically, such as every 4-6 months, to discuss previously decided proposals, governance or technical issues related to terminology management.

The method of submitting change requests shall also be determined and announced so that contributors understand the necessary processes and timeline.

=Documenting terms=

* TBD: This section will describe the process for managing terms.
* TBD: Information as guidance from https://www.iso.org/sites/directives/current/part2/index.xhtml#_idTextAnchor196

=Process for adding and maintaining terms=
* TBD: Describe a process
* Anyone can suggest a new term or modify an existing term or its definition.
* As part of the annual OSGeoLive build process, all existing and proposed new terms will be reviewed, and discussed with proposers.
* Valid terms will be added to ... (Explain how).
* They will then be ...

= Term data structure =

Terms/Concepts are stored in structured data (YAML) files.

TODO: describe Concept YAML structure.

For terms that originate from other authoritative terminology databases, such as those from ISO or OGC, a linkage shall be established from the OSGeo terminology database back to the source.

TODO: A “contributors guide” document will greatly help these people make the proper suggestions and have them formatted correctly.

= Online presence =

Terminology isn’t useful until people use them, which means people need to first know they exist and what they mean. The Geolexica initiative has volunteered to setup https://osgeo.geolexica.org/ to serve OSGeo in managing its lexicon database.

Geolexica serves human-readable concepts and terms, as well as machine-readable JSON, allowing APIs to directly consume the content. It currently serves ISO/TC 211’s terminology management group in making its multi-lingual geographic information terminology available on the internet (https://www.geolexica.org).

To minimize friction in the feedback process, for every term offered in the OSGeo terminology pages we can offer a “propose new term” and “propose changes to this term" buttons. This allows user to directly go to the issue platform (e.g. GitHub) to make the suggested changes.

The structure of Geolexica is designed for efficiency with streamlined management and operations. Terms are stored in structured data (YAML) files, and are directly deployable to the website. The website operates according to best practices, and is served as a static website with dynamic search functionality. Security and performance have always been key considerations.

= Initial load and data cleanup =

The initial load of the terms will involve a bulk load from the cleaned terms and definitions that Felicity has compiled. Geolexica could easily handle the initial conversion from table format into the desired structured data format.

The cleanup process has already been started.

[[Category: Education]]

Lexicon Committee

2019-10-22T12:08:04Z

Wiki-Tc211 tmg: /* Background */

The Lexicon committee is responsible for coordinating official definitions for terminology used within the OSGeo context. The committee is drawn from the OSGeo, OGC and ISO communities and is based on merit and interest.

An email list shall be setup for this group for internal communication.

= Purpose =

The Lexicon committee plays two essential roles:

a) As the gatekeeper of terms to ensure quality checks of contributions
b) As the seat of central terminology knowledge for alignment of terms and concepts. To facilitate the flow of terminology knowledge to terminology authors and users.

The committee involves individual representation from external groups including ISO/TC 211 and OGC in order to leverage their experience in terminology, which is useful in situations such as alerting on cross-organization alignment of concepts or term duplication.

= Coordination =

= Committee members =
TBD: Once formed, the following people have volunteered to join this committee:

OSGEO Representation
* Cameron Shorter
* Felicity Brand (proposed)
* ... others welcomed
Outside Representation (Non-OSGEO)
* Ronald Tse (TC?/Ribose Inc.)
* Reese Plews (ISO/TC211, TMG)

* ... others welcomed

Selection of new members is determined by committee member vote. Committee members may retire any time. If a committee member becomes inactive for many months they may be invited to retire, and if unresponsive they may be removed by the existing committee.

==Decisions==
Decisions are based on voting using the following:
* +1: For
* +0: Mildly for, but mostly indifferent
* 0: Indifferent
* -0: Mildly against, but mostly indifferent
* -1: Strongly against. This is expected to be accompanied by a reason.

For most decisions, a motion is raised within one of the committee open forums (IRC, email list, etc) and those present vote and decide. Should a decision:
* Be strategic or impact many within the committee,
* Or if there be contention in deciding, and after discussion at least one member is still strongly against the motion, by continuing to vote -1,
* Then the motion should be referred to the committee.

For motions presented to the committee, a motion is considered passed when there are more committee +1 votes than -1 votes, and either all committee members have voted, or 1 week has passed. In the case of a tie, the committee chair shall have 1.5 votes.

==Expectations of committee members==
* Contribute to or related activities when the committee is active.
* Help with whatever dirty work is required to keep the project moving forward.
* Monitor committee conversations on our email list.

==Background==

Standards driven terminology vs. Software project driven terminology (highly simplified overviews)
* OGC create/promote implementation standards which are built in part with terminology entries
* ISO/TC 211 create/promote conceptual standards which are built in part with terminology entries
* OSGEO
*Foster global adoption of open geospatial technology by being an inclusive software foundation devoted to an open philosophy and participatory community driven development.*

How do terminology entries (terms and definitions) "come into" OSGEO?
* through education texts (basic concepts)
* through software related documentation (user guides, tutorials)
* other

Who are experts in specific (project/domain) related terminology?
* educators, teachers
* project developers, programmers
* documentation writers

Who are experts in terminology management?
* lexicon committee members

==Terms of reference==

The terms of reference for the Lexicon Committee describes steps for lexicon approval and data quality requirements. This is openly shared with contributors for transparent acceptance criteria.

Contributors may propose changes to the terminology database at any time. The terminology management group shall discuss and approve or disapprove of the proposal within a reasonable timeframe. This practice is in-line with the open source, change-based, rapid iteration mantra, similar to OpenSSL.

For releases, the group shall convene periodically, such as every 4-6 months, to discuss previously decided proposals, governance or technical issues related to terminology management.

The method of submitting change requests shall also be determined and announced so that contributors understand the necessary processes and timeline.

=Documenting terms=

* TBD: This section will describe the process for managing terms.
* TBD: Information as guidance from https://www.iso.org/sites/directives/current/part2/index.xhtml#_idTextAnchor196

=Process for adding and maintaining terms=
* TBD: Describe a process
* Anyone can suggest a new term or modify an existing term or its definition.
* As part of the annual OSGeoLive build process, all existing and proposed new terms will be reviewed, and discussed with proposers.
* Valid terms will be added to ... (Explain how).
* They will then be ...

= Term data structure =

Terms/Concepts are stored in structured data (YAML) files.

TODO: describe Concept YAML structure.

For terms that originate from other authoritative terminology databases, such as those from ISO or OGC, a linkage shall be established from the OSGeo terminology database back to the source.

TODO: A “contributors guide” document will greatly help these people make the proper suggestions and have them formatted correctly.

= Online presence =

Terminology isn’t useful until people use them, which means people need to first know they exist and what they mean. The Geolexica initiative has volunteered to setup https://osgeo.geolexica.org/ to serve OSGeo in managing its lexicon database.

Geolexica serves human-readable concepts and terms, as well as machine-readable JSON, allowing APIs to directly consume the content. It currently serves ISO/TC 211’s terminology management group in making its multi-lingual geographic information terminology available on the internet (https://www.geolexica.org).

To minimize friction in the feedback process, for every term offered in the OSGeo terminology pages we can offer a “propose new term” and “propose changes to this term" buttons. This allows user to directly go to the issue platform (e.g. GitHub) to make the suggested changes.

The structure of Geolexica is designed for efficiency with streamlined management and operations. Terms are stored in structured data (YAML) files, and are directly deployable to the website. The website operates according to best practices, and is served as a static website with dynamic search functionality. Security and performance have always been key considerations.

= Initial load and data cleanup =

The initial load of the terms will involve a bulk load from the cleaned terms and definitions that Felicity has compiled. Geolexica could easily handle the initial conversion from table format into the desired structured data format.

The cleanup process has already been started.

[[Category: Education]]

Lexicon Committee

2019-10-22T12:03:14Z

Wiki-Tc211 tmg: /* Committee members */

The Lexicon committee is responsible for coordinating official definitions for terminology used within the OSGeo context. The committee is drawn from the OSGeo, OGC and ISO communities and is based on merit and interest.

An email list shall be setup for this group for internal communication.

= Purpose =

The Lexicon committee plays two essential roles:

a) As the gatekeeper of terms to ensure quality checks of contributions
b) As the seat of central terminology knowledge for alignment of terms and concepts. To facilitate the flow of terminology knowledge to terminology authors and users.

The committee involves individual representation from external groups including ISO/TC 211 and OGC in order to leverage their experience in terminology, which is useful in situations such as alerting on cross-organization alignment of concepts or term duplication.

= Coordination =

= Committee members =
TBD: Once formed, the following people have volunteered to join this committee:

OSGEO Representation
* Cameron Shorter
* Felicity Brand (proposed)
* ... others welcomed
Outside Representation (Non-OSGEO)
* Ronald Tse (TC?/Ribose Inc.)
* Reese Plews (ISO/TC211, TMG)

* ... others welcomed

Selection of new members is determined by committee member vote. Committee members may retire any time. If a committee member becomes inactive for many months they may be invited to retire, and if unresponsive they may be removed by the existing committee.

==Decisions==
Decisions are based on voting using the following:
* +1: For
* +0: Mildly for, but mostly indifferent
* 0: Indifferent
* -0: Mildly against, but mostly indifferent
* -1: Strongly against. This is expected to be accompanied by a reason.

For most decisions, a motion is raised within one of the committee open forums (IRC, email list, etc) and those present vote and decide. Should a decision:
* Be strategic or impact many within the committee,
* Or if there be contention in deciding, and after discussion at least one member is still strongly against the motion, by continuing to vote -1,
* Then the motion should be referred to the committee.

For motions presented to the committee, a motion is considered passed when there are more committee +1 votes than -1 votes, and either all committee members have voted, or 1 week has passed. In the case of a tie, the committee chair shall have 1.5 votes.

==Expectations of committee members==
* Contribute to or related activities when the committee is active.
* Help with whatever dirty work is required to keep the project moving forward.
* Monitor committee conversations on our email list.

==Background==

Standards driven terminology vs. Software project driven terminology (highly simplified overviews)
* OGC create/promote implementation standards which are built in part with terminology entries
* ISO/TC 211 create/promote conceptual standards which are built in part with terminology entries
* OSGEO _Foster global adoption of open geospatial technology by being an inclusive software foundation devoted to an open philosophy and participatory community driven development._

How do terminology entries (terms and definitions) "come into" OSGEO?
* through education texts (basic concepts)
* through software related documentation (user guides, tutorials)
* other

Who are experts in specific (project/domain) related terminology?
* educators, teachers
* project developers, programmers
* documentation writers

Who are experts in terminology management?
* lexicon committee members

==Terms of reference==

The terms of reference for the Lexicon Committee describes steps for lexicon approval and data quality requirements. This is openly shared with contributors for transparent acceptance criteria.

Contributors may propose changes to the terminology database at any time. The terminology management group shall discuss and approve or disapprove of the proposal within a reasonable timeframe. This practice is in-line with the open source, change-based, rapid iteration mantra, similar to OpenSSL.

For releases, the group shall convene periodically, such as every 4-6 months, to discuss previously decided proposals, governance or technical issues related to terminology management.

The method of submitting change requests shall also be determined and announced so that contributors understand the necessary processes and timeline.

=Documenting terms=

* TBD: This section will describe the process for managing terms.
* TBD: Information as guidance from https://www.iso.org/sites/directives/current/part2/index.xhtml#_idTextAnchor196

=Process for adding and maintaining terms=
* TBD: Describe a process
* Anyone can suggest a new term or modify an existing term or its definition.
* As part of the annual OSGeoLive build process, all existing and proposed new terms will be reviewed, and discussed with proposers.
* Valid terms will be added to ... (Explain how).
* They will then be ...

= Term data structure =

Terms/Concepts are stored in structured data (YAML) files.

TODO: describe Concept YAML structure.

For terms that originate from other authoritative terminology databases, such as those from ISO or OGC, a linkage shall be established from the OSGeo terminology database back to the source.

TODO: A “contributors guide” document will greatly help these people make the proper suggestions and have them formatted correctly.

= Online presence =

Terminology isn’t useful until people use them, which means people need to first know they exist and what they mean. The Geolexica initiative has volunteered to setup https://osgeo.geolexica.org/ to serve OSGeo in managing its lexicon database.

Geolexica serves human-readable concepts and terms, as well as machine-readable JSON, allowing APIs to directly consume the content. It currently serves ISO/TC 211’s terminology management group in making its multi-lingual geographic information terminology available on the internet (https://www.geolexica.org).

To minimize friction in the feedback process, for every term offered in the OSGeo terminology pages we can offer a “propose new term” and “propose changes to this term" buttons. This allows user to directly go to the issue platform (e.g. GitHub) to make the suggested changes.

The structure of Geolexica is designed for efficiency with streamlined management and operations. Terms are stored in structured data (YAML) files, and are directly deployable to the website. The website operates according to best practices, and is served as a static website with dynamic search functionality. Security and performance have always been key considerations.

= Initial load and data cleanup =

The initial load of the terms will involve a bulk load from the cleaned terms and definitions that Felicity has compiled. Geolexica could easily handle the initial conversion from table format into the desired structured data format.

The cleanup process has already been started.

[[Category: Education]]

Lexicon Committee

2019-10-22T12:02:19Z

Wiki-Tc211 tmg: /* Initial load and data cleanup */

The Lexicon committee is responsible for coordinating official definitions for terminology used within the OSGeo context. The committee is drawn from the OSGeo, OGC and ISO communities and is based on merit and interest.

An email list shall be setup for this group for internal communication.

= Purpose =

The Lexicon committee plays two essential roles:

a) As the gatekeeper of terms to ensure quality checks of contributions
b) As the seat of central terminology knowledge for alignment of terms and concepts. To facilitate the flow of terminology knowledge to terminology authors and users.

The committee involves individual representation from external groups including ISO/TC 211 and OGC in order to leverage their experience in terminology, which is useful in situations such as alerting on cross-organization alignment of concepts or term duplication.

= Coordination =

= Committee members =
TBD: Once formed, the following people have volunteered to join this committee:

OSGEO Representation
* Cameron Shorter
* Felicity Brand (proposed)
Outside Representation (Non-OSGEO)
* Ronald Tse (TC?/Ribose Inc.)
* Reese Plews (ISO/TC211, TMG)

* ... others welcomed

Selection of new members is determined by committee member vote. Committee members may retire any time. If a committee member becomes inactive for many months they may be invited to retire, and if unresponsive they may be removed by the existing committee.

==Decisions==
Decisions are based on voting using the following:
* +1: For
* +0: Mildly for, but mostly indifferent
* 0: Indifferent
* -0: Mildly against, but mostly indifferent
* -1: Strongly against. This is expected to be accompanied by a reason.

For most decisions, a motion is raised within one of the committee open forums (IRC, email list, etc) and those present vote and decide. Should a decision:
* Be strategic or impact many within the committee,
* Or if there be contention in deciding, and after discussion at least one member is still strongly against the motion, by continuing to vote -1,
* Then the motion should be referred to the committee.

For motions presented to the committee, a motion is considered passed when there are more committee +1 votes than -1 votes, and either all committee members have voted, or 1 week has passed. In the case of a tie, the committee chair shall have 1.5 votes.

==Expectations of committee members==
* Contribute to or related activities when the committee is active.
* Help with whatever dirty work is required to keep the project moving forward.
* Monitor committee conversations on our email list.

==Background==

Standards driven terminology vs. Software project driven terminology (highly simplified overviews)
* OGC create/promote implementation standards which are built in part with terminology entries
* ISO/TC 211 create/promote conceptual standards which are built in part with terminology entries
* OSGEO _Foster global adoption of open geospatial technology by being an inclusive software foundation devoted to an open philosophy and participatory community driven development._

How do terminology entries (terms and definitions) "come into" OSGEO?
* through education texts (basic concepts)
* through software related documentation (user guides, tutorials)
* other

Who are experts in specific (project/domain) related terminology?
* educators, teachers
* project developers, programmers
* documentation writers

Who are experts in terminology management?
* lexicon committee members

==Terms of reference==

The terms of reference for the Lexicon Committee describes steps for lexicon approval and data quality requirements. This is openly shared with contributors for transparent acceptance criteria.

Contributors may propose changes to the terminology database at any time. The terminology management group shall discuss and approve or disapprove of the proposal within a reasonable timeframe. This practice is in-line with the open source, change-based, rapid iteration mantra, similar to OpenSSL.

For releases, the group shall convene periodically, such as every 4-6 months, to discuss previously decided proposals, governance or technical issues related to terminology management.

The method of submitting change requests shall also be determined and announced so that contributors understand the necessary processes and timeline.

=Documenting terms=

* TBD: This section will describe the process for managing terms.
* TBD: Information as guidance from https://www.iso.org/sites/directives/current/part2/index.xhtml#_idTextAnchor196

=Process for adding and maintaining terms=
* TBD: Describe a process
* Anyone can suggest a new term or modify an existing term or its definition.
* As part of the annual OSGeoLive build process, all existing and proposed new terms will be reviewed, and discussed with proposers.
* Valid terms will be added to ... (Explain how).
* They will then be ...

= Term data structure =

Terms/Concepts are stored in structured data (YAML) files.

TODO: describe Concept YAML structure.

For terms that originate from other authoritative terminology databases, such as those from ISO or OGC, a linkage shall be established from the OSGeo terminology database back to the source.

TODO: A “contributors guide” document will greatly help these people make the proper suggestions and have them formatted correctly.

= Online presence =

Terminology isn’t useful until people use them, which means people need to first know they exist and what they mean. The Geolexica initiative has volunteered to setup https://osgeo.geolexica.org/ to serve OSGeo in managing its lexicon database.

Geolexica serves human-readable concepts and terms, as well as machine-readable JSON, allowing APIs to directly consume the content. It currently serves ISO/TC 211’s terminology management group in making its multi-lingual geographic information terminology available on the internet (https://www.geolexica.org).

To minimize friction in the feedback process, for every term offered in the OSGeo terminology pages we can offer a “propose new term” and “propose changes to this term" buttons. This allows user to directly go to the issue platform (e.g. GitHub) to make the suggested changes.

The structure of Geolexica is designed for efficiency with streamlined management and operations. Terms are stored in structured data (YAML) files, and are directly deployable to the website. The website operates according to best practices, and is served as a static website with dynamic search functionality. Security and performance have always been key considerations.

= Initial load and data cleanup =

The initial load of the terms will involve a bulk load from the cleaned terms and definitions that Felicity has compiled. Geolexica could easily handle the initial conversion from table format into the desired structured data format.

The cleanup process has already been started.

[[Category: Education]]

Lexicon Committee

2019-10-22T12:01:01Z

Wiki-Tc211 tmg: /* Documenting terms */

The Lexicon committee is responsible for coordinating official definitions for terminology used within the OSGeo context. The committee is drawn from the OSGeo, OGC and ISO communities and is based on merit and interest.

An email list shall be setup for this group for internal communication.

= Purpose =

The Lexicon committee plays two essential roles:

a) As the gatekeeper of terms to ensure quality checks of contributions
b) As the seat of central terminology knowledge for alignment of terms and concepts. To facilitate the flow of terminology knowledge to terminology authors and users.

The committee involves individual representation from external groups including ISO/TC 211 and OGC in order to leverage their experience in terminology, which is useful in situations such as alerting on cross-organization alignment of concepts or term duplication.

= Coordination =

= Committee members =
TBD: Once formed, the following people have volunteered to join this committee:

OSGEO Representation
* Cameron Shorter
* Felicity Brand (proposed)
Outside Representation (Non-OSGEO)
* Ronald Tse (TC?/Ribose Inc.)
* Reese Plews (ISO/TC211, TMG)

* ... others welcomed

Selection of new members is determined by committee member vote. Committee members may retire any time. If a committee member becomes inactive for many months they may be invited to retire, and if unresponsive they may be removed by the existing committee.

==Decisions==
Decisions are based on voting using the following:
* +1: For
* +0: Mildly for, but mostly indifferent
* 0: Indifferent
* -0: Mildly against, but mostly indifferent
* -1: Strongly against. This is expected to be accompanied by a reason.

For most decisions, a motion is raised within one of the committee open forums (IRC, email list, etc) and those present vote and decide. Should a decision:
* Be strategic or impact many within the committee,
* Or if there be contention in deciding, and after discussion at least one member is still strongly against the motion, by continuing to vote -1,
* Then the motion should be referred to the committee.

For motions presented to the committee, a motion is considered passed when there are more committee +1 votes than -1 votes, and either all committee members have voted, or 1 week has passed. In the case of a tie, the committee chair shall have 1.5 votes.

==Expectations of committee members==
* Contribute to or related activities when the committee is active.
* Help with whatever dirty work is required to keep the project moving forward.
* Monitor committee conversations on our email list.

==Background==

Standards driven terminology vs. Software project driven terminology (highly simplified overviews)
* OGC create/promote implementation standards which are built in part with terminology entries
* ISO/TC 211 create/promote conceptual standards which are built in part with terminology entries
* OSGEO _Foster global adoption of open geospatial technology by being an inclusive software foundation devoted to an open philosophy and participatory community driven development._

How do terminology entries (terms and definitions) "come into" OSGEO?
* through education texts (basic concepts)
* through software related documentation (user guides, tutorials)
* other

Who are experts in specific (project/domain) related terminology?
* educators, teachers
* project developers, programmers
* documentation writers

Who are experts in terminology management?
* lexicon committee members

==Terms of reference==

The terms of reference for the Lexicon Committee describes steps for lexicon approval and data quality requirements. This is openly shared with contributors for transparent acceptance criteria.

Contributors may propose changes to the terminology database at any time. The terminology management group shall discuss and approve or disapprove of the proposal within a reasonable timeframe. This practice is in-line with the open source, change-based, rapid iteration mantra, similar to OpenSSL.

For releases, the group shall convene periodically, such as every 4-6 months, to discuss previously decided proposals, governance or technical issues related to terminology management.

The method of submitting change requests shall also be determined and announced so that contributors understand the necessary processes and timeline.

=Documenting terms=

* TBD: This section will describe the process for managing terms.
* TBD: Information as guidance from https://www.iso.org/sites/directives/current/part2/index.xhtml#_idTextAnchor196

=Process for adding and maintaining terms=
* TBD: Describe a process
* Anyone can suggest a new term or modify an existing term or its definition.
* As part of the annual OSGeoLive build process, all existing and proposed new terms will be reviewed, and discussed with proposers.
* Valid terms will be added to ... (Explain how).
* They will then be ...

= Term data structure =

Terms/Concepts are stored in structured data (YAML) files.

TODO: describe Concept YAML structure.

For terms that originate from other authoritative terminology databases, such as those from ISO or OGC, a linkage shall be established from the OSGeo terminology database back to the source.

TODO: A “contributors guide” document will greatly help these people make the proper suggestions and have them formatted correctly.

= Online presence =

Terminology isn’t useful until people use them, which means people need to first know they exist and what they mean. The Geolexica initiative has volunteered to setup https://osgeo.geolexica.org/ to serve OSGeo in managing its lexicon database.

Geolexica serves human-readable concepts and terms, as well as machine-readable JSON, allowing APIs to directly consume the content. It currently serves ISO/TC 211’s terminology management group in making its multi-lingual geographic information terminology available on the internet (https://www.geolexica.org).

To minimize friction in the feedback process, for every term offered in the OSGeo terminology pages we can offer a “propose new term” and “propose changes to this term" buttons. This allows user to directly go to the issue platform (e.g. GitHub) to make the suggested changes.

The structure of Geolexica is designed for efficiency with streamlined management and operations. Terms are stored in structured data (YAML) files, and are directly deployable to the website. The website operates according to best practices, and is served as a static website with dynamic search functionality. Security and performance have always been key considerations.

= Initial load and data cleanup =

The initial load of the terms will involve a bulk load from the cleaned terms and definitions that Felicity has compiled. Geolexica could easily handle the initial conversion from table format into the desired structured data format.

The cleanup process has already been started by Reese Plews, convenor of the TMG at ISO/TC 211.

[[Category: Education]]

Lexicon Committee

2019-10-22T11:59:08Z

Wiki-Tc211 tmg: /* Background */

The Lexicon committee is responsible for coordinating official definitions for terminology used within the OSGeo context. The committee is drawn from the OSGeo, OGC and ISO communities and is based on merit and interest.

An email list shall be setup for this group for internal communication.

= Purpose =

The Lexicon committee plays two essential roles:

a) As the gatekeeper of terms to ensure quality checks of contributions
b) As the seat of central terminology knowledge for alignment of terms and concepts. To facilitate the flow of terminology knowledge to terminology authors and users.

The committee involves individual representation from external groups including ISO/TC 211 and OGC in order to leverage their experience in terminology, which is useful in situations such as alerting on cross-organization alignment of concepts or term duplication.

= Coordination =

= Committee members =
TBD: Once formed, the following people have volunteered to join this committee:

OSGEO Representation
* Cameron Shorter
* Felicity Brand (proposed)
Outside Representation (Non-OSGEO)
* Ronald Tse (TC?/Ribose Inc.)
* Reese Plews (ISO/TC211, TMG)

* ... others welcomed

Selection of new members is determined by committee member vote. Committee members may retire any time. If a committee member becomes inactive for many months they may be invited to retire, and if unresponsive they may be removed by the existing committee.

==Decisions==
Decisions are based on voting using the following:
* +1: For
* +0: Mildly for, but mostly indifferent
* 0: Indifferent
* -0: Mildly against, but mostly indifferent
* -1: Strongly against. This is expected to be accompanied by a reason.

For most decisions, a motion is raised within one of the committee open forums (IRC, email list, etc) and those present vote and decide. Should a decision:
* Be strategic or impact many within the committee,
* Or if there be contention in deciding, and after discussion at least one member is still strongly against the motion, by continuing to vote -1,
* Then the motion should be referred to the committee.

For motions presented to the committee, a motion is considered passed when there are more committee +1 votes than -1 votes, and either all committee members have voted, or 1 week has passed. In the case of a tie, the committee chair shall have 1.5 votes.

==Expectations of committee members==
* Contribute to or related activities when the committee is active.
* Help with whatever dirty work is required to keep the project moving forward.
* Monitor committee conversations on our email list.

==Background==

Standards driven terminology vs. Software project driven terminology (highly simplified overviews)
* OGC create/promote implementation standards which are built in part with terminology entries
* ISO/TC 211 create/promote conceptual standards which are built in part with terminology entries
* OSGEO _Foster global adoption of open geospatial technology by being an inclusive software foundation devoted to an open philosophy and participatory community driven development._

How do terminology entries (terms and definitions) "come into" OSGEO?
* through education texts (basic concepts)
* through software related documentation (user guides, tutorials)
* other

Who are experts in specific (project/domain) related terminology?
* educators, teachers
* project developers, programmers
* documentation writers

Who are experts in terminology management?
* lexicon committee members

==Terms of reference==

The terms of reference for the Lexicon Committee describes steps for lexicon approval and data quality requirements. This is openly shared with contributors for transparent acceptance criteria.

Contributors may propose changes to the terminology database at any time. The terminology management group shall discuss and approve or disapprove of the proposal within a reasonable timeframe. This practice is in-line with the open source, change-based, rapid iteration mantra, similar to OpenSSL.

For releases, the group shall convene periodically, such as every 4-6 months, to discuss previously decided proposals, governance or technical issues related to terminology management.

The method of submitting change requests shall also be determined and announced so that contributors understand the necessary processes and timeline.

=Documenting terms=

* TBD: This section will describe the process for managing terms.
* TBD: Information sourced from https://www.iso.org/sites/directives/current/part2/index.xhtml#_idTextAnchor196

=Process for adding and maintaining terms=
* TBD: Describe a process
* Anyone can suggest a new term or modify an existing term or its definition.
* As part of the annual OSGeoLive build process, all existing and proposed new terms will be reviewed, and discussed with proposers.
* Valid terms will be added to ... (Explain how).
* They will then be ...

= Term data structure =

Terms/Concepts are stored in structured data (YAML) files.

TODO: describe Concept YAML structure.

For terms that originate from other authoritative terminology databases, such as those from ISO or OGC, a linkage shall be established from the OSGeo terminology database back to the source.

TODO: A “contributors guide” document will greatly help these people make the proper suggestions and have them formatted correctly.

= Online presence =

Terminology isn’t useful until people use them, which means people need to first know they exist and what they mean. The Geolexica initiative has volunteered to setup https://osgeo.geolexica.org/ to serve OSGeo in managing its lexicon database.

Geolexica serves human-readable concepts and terms, as well as machine-readable JSON, allowing APIs to directly consume the content. It currently serves ISO/TC 211’s terminology management group in making its multi-lingual geographic information terminology available on the internet (https://www.geolexica.org).

To minimize friction in the feedback process, for every term offered in the OSGeo terminology pages we can offer a “propose new term” and “propose changes to this term" buttons. This allows user to directly go to the issue platform (e.g. GitHub) to make the suggested changes.

The structure of Geolexica is designed for efficiency with streamlined management and operations. Terms are stored in structured data (YAML) files, and are directly deployable to the website. The website operates according to best practices, and is served as a static website with dynamic search functionality. Security and performance have always been key considerations.

= Initial load and data cleanup =

The initial load of the terms will involve a bulk load from the cleaned terms and definitions that Felicity has compiled. Geolexica could easily handle the initial conversion from table format into the desired structured data format.

The cleanup process has already been started by Reese Plews, convenor of the TMG at ISO/TC 211.

[[Category: Education]]

Lexicon Committee

2019-10-22T11:41:54Z

Wiki-Tc211 tmg: /* Background */

The Lexicon committee is responsible for coordinating official definitions for terminology used within the OSGeo context. The committee is drawn from the OSGeo, OGC and ISO communities and is based on merit and interest.

An email list shall be setup for this group for internal communication.

= Purpose =

The Lexicon committee plays two essential roles:

a) As the gatekeeper of terms to ensure quality checks of contributions
b) As the seat of central terminology knowledge for alignment of terms and concepts. To facilitate the flow of terminology knowledge to terminology authors and users.

The committee involves individual representation from external groups including ISO/TC 211 and OGC in order to leverage their experience in terminology, which is useful in situations such as alerting on cross-organization alignment of concepts or term duplication.

= Coordination =

= Committee members =
TBD: Once formed, the following people have volunteered to join this committee:

OSGEO Representation
* Cameron Shorter
* Felicity Brand (proposed)
Outside Representation (Non-OSGEO)
* Ronald Tse (TC?/Ribose Inc.)
* Reese Plews (ISO/TC211, TMG)

* ... others welcomed

Selection of new members is determined by committee member vote. Committee members may retire any time. If a committee member becomes inactive for many months they may be invited to retire, and if unresponsive they may be removed by the existing committee.

==Decisions==
Decisions are based on voting using the following:
* +1: For
* +0: Mildly for, but mostly indifferent
* 0: Indifferent
* -0: Mildly against, but mostly indifferent
* -1: Strongly against. This is expected to be accompanied by a reason.

For most decisions, a motion is raised within one of the committee open forums (IRC, email list, etc) and those present vote and decide. Should a decision:
* Be strategic or impact many within the committee,
* Or if there be contention in deciding, and after discussion at least one member is still strongly against the motion, by continuing to vote -1,
* Then the motion should be referred to the committee.

For motions presented to the committee, a motion is considered passed when there are more committee +1 votes than -1 votes, and either all committee members have voted, or 1 week has passed. In the case of a tie, the committee chair shall have 1.5 votes.

==Expectations of committee members==
* Contribute to or related activities when the committee is active.
* Help with whatever dirty work is required to keep the project moving forward.
* Monitor committee conversations on our email list.

==Background==

How do terminology entries (terms and definitions) "come into" OSGEO?
* through education texts (basic concepts)
* through software related documentation (user guides, tutorials)
* other

Who are experts in specific (project/domain) related terminology?
* educators, teachers
* project developers, programmers
* documentation writers

Who are experts in terminology management?
* lexicon committee members

==Terms of reference==

The terms of reference for the Lexicon Committee describes steps for lexicon approval and data quality requirements. This is openly shared with contributors for transparent acceptance criteria.

Contributors may propose changes to the terminology database at any time. The terminology management group shall discuss and approve or disapprove of the proposal within a reasonable timeframe. This practice is in-line with the open source, change-based, rapid iteration mantra, similar to OpenSSL.

For releases, the group shall convene periodically, such as every 4-6 months, to discuss previously decided proposals, governance or technical issues related to terminology management.

The method of submitting change requests shall also be determined and announced so that contributors understand the necessary processes and timeline.

=Documenting terms=

* TBD: This section will describe the process for managing terms.
* TBD: Information sourced from https://www.iso.org/sites/directives/current/part2/index.xhtml#_idTextAnchor196

=Process for adding and maintaining terms=
* TBD: Describe a process
* Anyone can suggest a new term or modify an existing term or its definition.
* As part of the annual OSGeoLive build process, all existing and proposed new terms will be reviewed, and discussed with proposers.
* Valid terms will be added to ... (Explain how).
* They will then be ...

= Term data structure =

Terms/Concepts are stored in structured data (YAML) files.

TODO: describe Concept YAML structure.

For terms that originate from other authoritative terminology databases, such as those from ISO or OGC, a linkage shall be established from the OSGeo terminology database back to the source.

TODO: A “contributors guide” document will greatly help these people make the proper suggestions and have them formatted correctly.

= Online presence =

Terminology isn’t useful until people use them, which means people need to first know they exist and what they mean. The Geolexica initiative has volunteered to setup https://osgeo.geolexica.org/ to serve OSGeo in managing its lexicon database.

Geolexica serves human-readable concepts and terms, as well as machine-readable JSON, allowing APIs to directly consume the content. It currently serves ISO/TC 211’s terminology management group in making its multi-lingual geographic information terminology available on the internet (https://www.geolexica.org).

To minimize friction in the feedback process, for every term offered in the OSGeo terminology pages we can offer a “propose new term” and “propose changes to this term" buttons. This allows user to directly go to the issue platform (e.g. GitHub) to make the suggested changes.

The structure of Geolexica is designed for efficiency with streamlined management and operations. Terms are stored in structured data (YAML) files, and are directly deployable to the website. The website operates according to best practices, and is served as a static website with dynamic search functionality. Security and performance have always been key considerations.

= Initial load and data cleanup =

The initial load of the terms will involve a bulk load from the cleaned terms and definitions that Felicity has compiled. Geolexica could easily handle the initial conversion from table format into the desired structured data format.

The cleanup process has already been started by Reese Plews, convenor of the TMG at ISO/TC 211.

[[Category: Education]]

Lexicon Committee

2019-10-22T11:32:45Z

Wiki-Tc211 tmg:

The Lexicon committee is responsible for coordinating official definitions for terminology used within the OSGeo context. The committee is drawn from the OSGeo, OGC and ISO communities and is based on merit and interest.

An email list shall be setup for this group for internal communication.

= Purpose =

The Lexicon committee plays two essential roles:

a) As the gatekeeper of terms to ensure quality checks of contributions
b) As the seat of central terminology knowledge for alignment of terms and concepts. To facilitate the flow of terminology knowledge to terminology authors and users.

The committee involves individual representation from external groups including ISO/TC 211 and OGC in order to leverage their experience in terminology, which is useful in situations such as alerting on cross-organization alignment of concepts or term duplication.

= Coordination =

= Committee members =
TBD: Once formed, the following people have volunteered to join this committee:

OSGEO Representation
* Cameron Shorter
* Felicity Brand (proposed)
Outside Representation (Non-OSGEO)
* Ronald Tse (TC?/Ribose Inc.)
* Reese Plews (ISO/TC211, TMG)

* ... others welcomed

Selection of new members is determined by committee member vote. Committee members may retire any time. If a committee member becomes inactive for many months they may be invited to retire, and if unresponsive they may be removed by the existing committee.

==Decisions==
Decisions are based on voting using the following:
* +1: For
* +0: Mildly for, but mostly indifferent
* 0: Indifferent
* -0: Mildly against, but mostly indifferent
* -1: Strongly against. This is expected to be accompanied by a reason.

For most decisions, a motion is raised within one of the committee open forums (IRC, email list, etc) and those present vote and decide. Should a decision:
* Be strategic or impact many within the committee,
* Or if there be contention in deciding, and after discussion at least one member is still strongly against the motion, by continuing to vote -1,
* Then the motion should be referred to the committee.

For motions presented to the committee, a motion is considered passed when there are more committee +1 votes than -1 votes, and either all committee members have voted, or 1 week has passed. In the case of a tie, the committee chair shall have 1.5 votes.

==Expectations of committee members==
* Contribute to or related activities when the committee is active.
* Help with whatever dirty work is required to keep the project moving forward.
* Monitor committee conversations on our email list.

==Background==

==Terms of reference==

The terms of reference for the Lexicon Committee describes steps for lexicon approval and data quality requirements. This is openly shared with contributors for transparent acceptance criteria.

Contributors may propose changes to the terminology database at any time. The terminology management group shall discuss and approve or disapprove of the proposal within a reasonable timeframe. This practice is in-line with the open source, change-based, rapid iteration mantra, similar to OpenSSL.

For releases, the group shall convene periodically, such as every 4-6 months, to discuss previously decided proposals, governance or technical issues related to terminology management.

The method of submitting change requests shall also be determined and announced so that contributors understand the necessary processes and timeline.

=Documenting terms=

* TBD: This section will describe the process for managing terms.
* TBD: Information sourced from https://www.iso.org/sites/directives/current/part2/index.xhtml#_idTextAnchor196

=Process for adding and maintaining terms=
* TBD: Describe a process
* Anyone can suggest a new term or modify an existing term or its definition.
* As part of the annual OSGeoLive build process, all existing and proposed new terms will be reviewed, and discussed with proposers.
* Valid terms will be added to ... (Explain how).
* They will then be ...

= Term data structure =

Terms/Concepts are stored in structured data (YAML) files.

TODO: describe Concept YAML structure.

For terms that originate from other authoritative terminology databases, such as those from ISO or OGC, a linkage shall be established from the OSGeo terminology database back to the source.

TODO: A “contributors guide” document will greatly help these people make the proper suggestions and have them formatted correctly.

= Online presence =

Terminology isn’t useful until people use them, which means people need to first know they exist and what they mean. The Geolexica initiative has volunteered to setup https://osgeo.geolexica.org/ to serve OSGeo in managing its lexicon database.

Geolexica serves human-readable concepts and terms, as well as machine-readable JSON, allowing APIs to directly consume the content. It currently serves ISO/TC 211’s terminology management group in making its multi-lingual geographic information terminology available on the internet (https://www.geolexica.org).

To minimize friction in the feedback process, for every term offered in the OSGeo terminology pages we can offer a “propose new term” and “propose changes to this term" buttons. This allows user to directly go to the issue platform (e.g. GitHub) to make the suggested changes.

The structure of Geolexica is designed for efficiency with streamlined management and operations. Terms are stored in structured data (YAML) files, and are directly deployable to the website. The website operates according to best practices, and is served as a static website with dynamic search functionality. Security and performance have always been key considerations.

= Initial load and data cleanup =

The initial load of the terms will involve a bulk load from the cleaned terms and definitions that Felicity has compiled. Geolexica could easily handle the initial conversion from table format into the desired structured data format.

The cleanup process has already been started by Reese Plews, convenor of the TMG at ISO/TC 211.

[[Category: Education]]

Lexicon Committee

2019-10-22T11:28:26Z

Wiki-Tc211 tmg: /* Purpose */

The Lexicon committee is responsible for coordinating official definitions for terminology used within the OSGeo context. The committee is drawn from the OSGeo, OGC and ISO communities and is based on merit and interest.

An email list shall be setup for this group for internal communication.

= Purpose =

The Lexicon committee plays two essential roles:

a) As the gatekeeper of terms to ensure quality checks of contributions
b) As the seat of central terminology knowledge for alignment of terms and concepts. To facilitate the flow of terminology knowledge to terminology authors and users.

The committee involves individual representation from external groups including ISO/TC 211 and OGC in order to leverage their experience in terminology, which is useful in situations such as alerting on cross-organization alignment of concepts or term duplication.

= Coordination =

= Committee members =
TBD: Once formed, the following people have volunteered to join this committee:

OSGEO Representation
* Cameron Shorter
* Felicity Brand (proposed)
Outside Representation (Non-OSGEO)
* Ronald Tse (TC?/Ribose Inc.)
* Reese Plews (ISO/TC211, TMG)

* ... others welcomed

Selection of new members is determined by committee member vote. Committee members may retire any time. If a committee member becomes inactive for many months they may be invited to retire, and if unresponsive they may be removed by the existing committee.

==Decisions==
Decisions are based on voting using the following:
* +1: For
* +0: Mildly for, but mostly indifferent
* 0: Indifferent
* -0: Mildly against, but mostly indifferent
* -1: Strongly against. This is expected to be accompanied by a reason.

For most decisions, a motion is raised within one of the committee open forums (IRC, email list, etc) and those present vote and decide. Should a decision:
* Be strategic or impact many within the committee,
* Or if there be contention in deciding, and after discussion at least one member is still strongly against the motion, by continuing to vote -1,
* Then the motion should be referred to the committee.

For motions presented to the committee, a motion is considered passed when there are more committee +1 votes than -1 votes, and either all committee members have voted, or 1 week has passed. In the case of a tie, the committee chair shall have 1.5 votes.

==Expectations of committee members==
* Contribute to or related activities when the committee is active.
* Help with whatever dirty work is required to keep the project moving forward.
* Monitor committee conversations on our email list.

==Terms of reference==

The terms of reference for the Lexicon Committee describes steps for lexicon approval and data quality requirements. This is openly shared with contributors for transparent acceptance criteria.

Contributors may propose changes to the terminology database at any time. The terminology management group shall discuss and approve or disapprove of the proposal within a reasonable timeframe. This practice is in-line with the open source, change-based, rapid iteration mantra, similar to OpenSSL.

For releases, the group shall convene periodically, such as every 4-6 months, to discuss previously decided proposals, governance or technical issues related to terminology management.

The method of submitting change requests shall also be determined and announced so that contributors understand the necessary processes and timeline.

=Documenting terms=

* TBD: This section will describe the process for managing terms.
* TBD: Information sourced from https://www.iso.org/sites/directives/current/part2/index.xhtml#_idTextAnchor196

=Process for adding and maintaining terms=
* TBD: Describe a process
* Anyone can suggest a new term or modify an existing term or its definition.
* As part of the annual OSGeoLive build process, all existing and proposed new terms will be reviewed, and discussed with proposers.
* Valid terms will be added to ... (Explain how).
* They will then be ...

= Term data structure =

Terms/Concepts are stored in structured data (YAML) files.

TODO: describe Concept YAML structure.

For terms that originate from other authoritative terminology databases, such as those from ISO or OGC, a linkage shall be established from the OSGeo terminology database back to the source.

TODO: A “contributors guide” document will greatly help these people make the proper suggestions and have them formatted correctly.

= Online presence =

Terminology isn’t useful until people use them, which means people need to first know they exist and what they mean. The Geolexica initiative has volunteered to setup https://osgeo.geolexica.org/ to serve OSGeo in managing its lexicon database.

Geolexica serves human-readable concepts and terms, as well as machine-readable JSON, allowing APIs to directly consume the content. It currently serves ISO/TC 211’s terminology management group in making its multi-lingual geographic information terminology available on the internet (https://www.geolexica.org).

To minimize friction in the feedback process, for every term offered in the OSGeo terminology pages we can offer a “propose new term” and “propose changes to this term" buttons. This allows user to directly go to the issue platform (e.g. GitHub) to make the suggested changes.

The structure of Geolexica is designed for efficiency with streamlined management and operations. Terms are stored in structured data (YAML) files, and are directly deployable to the website. The website operates according to best practices, and is served as a static website with dynamic search functionality. Security and performance have always been key considerations.

= Initial load and data cleanup =

The initial load of the terms will involve a bulk load from the cleaned terms and definitions that Felicity has compiled. Geolexica could easily handle the initial conversion from table format into the desired structured data format.

The cleanup process has already been started by Reese Plews, convenor of the TMG at ISO/TC 211.

[[Category: Education]]

Lexicon Committee

2019-10-22T11:25:58Z

Wiki-Tc211 tmg: /* Committee members */

The Lexicon committee is responsible for coordinating official definitions for terminology used within the OSGeo context. The committee is drawn from the OSGeo, OGC and ISO communities and is based on merit and interest.

An email list shall be setup for this group for internal communication.

= Purpose =

The Lexicon committee plays two essential roles:

a) As the gatekeeper of terms to ensure quality checks of contributions
b) As the seat of central terminology knowledge for alignment of terms and concepts. To facilitate the flow of terminology knowledge to terminology authors and users.

The committee involves representation from external groups including ISO/TC 211 and OGC in order to leverage their experience in terminology, which is useful in situations such as alerting on cross-organization alignment of concepts or term duplication.

= Coordination =

= Committee members =
TBD: Once formed, the following people have volunteered to join this committee:

OSGEO Representation
* Cameron Shorter
* Felicity Brand (proposed)
Outside Representation (Non-OSGEO)
* Ronald Tse (TC?/Ribose Inc.)
* Reese Plews (ISO/TC211, TMG)

* ... others welcomed

Selection of new members is determined by committee member vote. Committee members may retire any time. If a committee member becomes inactive for many months they may be invited to retire, and if unresponsive they may be removed by the existing committee.

==Decisions==
Decisions are based on voting using the following:
* +1: For
* +0: Mildly for, but mostly indifferent
* 0: Indifferent
* -0: Mildly against, but mostly indifferent
* -1: Strongly against. This is expected to be accompanied by a reason.

For most decisions, a motion is raised within one of the committee open forums (IRC, email list, etc) and those present vote and decide. Should a decision:
* Be strategic or impact many within the committee,
* Or if there be contention in deciding, and after discussion at least one member is still strongly against the motion, by continuing to vote -1,
* Then the motion should be referred to the committee.

For motions presented to the committee, a motion is considered passed when there are more committee +1 votes than -1 votes, and either all committee members have voted, or 1 week has passed. In the case of a tie, the committee chair shall have 1.5 votes.

==Expectations of committee members==
* Contribute to or related activities when the committee is active.
* Help with whatever dirty work is required to keep the project moving forward.
* Monitor committee conversations on our email list.

==Terms of reference==

The terms of reference for the Lexicon Committee describes steps for lexicon approval and data quality requirements. This is openly shared with contributors for transparent acceptance criteria.

Contributors may propose changes to the terminology database at any time. The terminology management group shall discuss and approve or disapprove of the proposal within a reasonable timeframe. This practice is in-line with the open source, change-based, rapid iteration mantra, similar to OpenSSL.

For releases, the group shall convene periodically, such as every 4-6 months, to discuss previously decided proposals, governance or technical issues related to terminology management.

The method of submitting change requests shall also be determined and announced so that contributors understand the necessary processes and timeline.

=Documenting terms=

* TBD: This section will describe the process for managing terms.
* TBD: Information sourced from https://www.iso.org/sites/directives/current/part2/index.xhtml#_idTextAnchor196

=Process for adding and maintaining terms=
* TBD: Describe a process
* Anyone can suggest a new term or modify an existing term or its definition.
* As part of the annual OSGeoLive build process, all existing and proposed new terms will be reviewed, and discussed with proposers.
* Valid terms will be added to ... (Explain how).
* They will then be ...

= Term data structure =

Terms/Concepts are stored in structured data (YAML) files.

TODO: describe Concept YAML structure.

For terms that originate from other authoritative terminology databases, such as those from ISO or OGC, a linkage shall be established from the OSGeo terminology database back to the source.

TODO: A “contributors guide” document will greatly help these people make the proper suggestions and have them formatted correctly.

= Online presence =

Terminology isn’t useful until people use them, which means people need to first know they exist and what they mean. The Geolexica initiative has volunteered to setup https://osgeo.geolexica.org/ to serve OSGeo in managing its lexicon database.

Geolexica serves human-readable concepts and terms, as well as machine-readable JSON, allowing APIs to directly consume the content. It currently serves ISO/TC 211’s terminology management group in making its multi-lingual geographic information terminology available on the internet (https://www.geolexica.org).

To minimize friction in the feedback process, for every term offered in the OSGeo terminology pages we can offer a “propose new term” and “propose changes to this term" buttons. This allows user to directly go to the issue platform (e.g. GitHub) to make the suggested changes.

The structure of Geolexica is designed for efficiency with streamlined management and operations. Terms are stored in structured data (YAML) files, and are directly deployable to the website. The website operates according to best practices, and is served as a static website with dynamic search functionality. Security and performance have always been key considerations.

= Initial load and data cleanup =

The initial load of the terms will involve a bulk load from the cleaned terms and definitions that Felicity has compiled. Geolexica could easily handle the initial conversion from table format into the desired structured data format.

The cleanup process has already been started by Reese Plews, convenor of the TMG at ISO/TC 211.

[[Category: Education]]

Lexicon Committee

2019-10-22T11:24:52Z

Wiki-Tc211 tmg: /* Committee members */

The Lexicon committee is responsible for coordinating official definitions for terminology used within the OSGeo context. The committee is drawn from the OSGeo, OGC and ISO communities and is based on merit and interest.

An email list shall be setup for this group for internal communication.

= Purpose =

The Lexicon committee plays two essential roles:

a) As the gatekeeper of terms to ensure quality checks of contributions
b) As the seat of central terminology knowledge for alignment of terms and concepts. To facilitate the flow of terminology knowledge to terminology authors and users.

The committee involves representation from external groups including ISO/TC 211 and OGC in order to leverage their experience in terminology, which is useful in situations such as alerting on cross-organization alignment of concepts or term duplication.

= Coordination =

= Committee members =
TBD: Once formed, the following people have volunteered to join this committee:
OSGEO Representation
* Cameron Shorter
* Felicity Brand (proposed)
Outside Representation (Non-OSGEO)
* Ronald Tse (TC?/Ribose Inc.)
* Reese Plews (ISO/TC211, TMG)

* ... others welcomed

Selection of new members is determined by committee member vote. Committee members may retire any time. If a committee member becomes inactive for many months they may be invited to retire, and if unresponsive they may be removed by the existing committee.

==Decisions==
Decisions are based on voting using the following:
* +1: For
* +0: Mildly for, but mostly indifferent
* 0: Indifferent
* -0: Mildly against, but mostly indifferent
* -1: Strongly against. This is expected to be accompanied by a reason.

For most decisions, a motion is raised within one of the committee open forums (IRC, email list, etc) and those present vote and decide. Should a decision:
* Be strategic or impact many within the committee,
* Or if there be contention in deciding, and after discussion at least one member is still strongly against the motion, by continuing to vote -1,
* Then the motion should be referred to the committee.

For motions presented to the committee, a motion is considered passed when there are more committee +1 votes than -1 votes, and either all committee members have voted, or 1 week has passed. In the case of a tie, the committee chair shall have 1.5 votes.

==Expectations of committee members==
* Contribute to or related activities when the committee is active.
* Help with whatever dirty work is required to keep the project moving forward.
* Monitor committee conversations on our email list.

==Terms of reference==

The terms of reference for the Lexicon Committee describes steps for lexicon approval and data quality requirements. This is openly shared with contributors for transparent acceptance criteria.

Contributors may propose changes to the terminology database at any time. The terminology management group shall discuss and approve or disapprove of the proposal within a reasonable timeframe. This practice is in-line with the open source, change-based, rapid iteration mantra, similar to OpenSSL.

For releases, the group shall convene periodically, such as every 4-6 months, to discuss previously decided proposals, governance or technical issues related to terminology management.

The method of submitting change requests shall also be determined and announced so that contributors understand the necessary processes and timeline.

=Documenting terms=

* TBD: This section will describe the process for managing terms.
* TBD: Information sourced from https://www.iso.org/sites/directives/current/part2/index.xhtml#_idTextAnchor196

=Process for adding and maintaining terms=
* TBD: Describe a process
* Anyone can suggest a new term or modify an existing term or its definition.
* As part of the annual OSGeoLive build process, all existing and proposed new terms will be reviewed, and discussed with proposers.
* Valid terms will be added to ... (Explain how).
* They will then be ...

= Term data structure =

Terms/Concepts are stored in structured data (YAML) files.

TODO: describe Concept YAML structure.

For terms that originate from other authoritative terminology databases, such as those from ISO or OGC, a linkage shall be established from the OSGeo terminology database back to the source.

TODO: A “contributors guide” document will greatly help these people make the proper suggestions and have them formatted correctly.

= Online presence =

Terminology isn’t useful until people use them, which means people need to first know they exist and what they mean. The Geolexica initiative has volunteered to setup https://osgeo.geolexica.org/ to serve OSGeo in managing its lexicon database.

Geolexica serves human-readable concepts and terms, as well as machine-readable JSON, allowing APIs to directly consume the content. It currently serves ISO/TC 211’s terminology management group in making its multi-lingual geographic information terminology available on the internet (https://www.geolexica.org).

To minimize friction in the feedback process, for every term offered in the OSGeo terminology pages we can offer a “propose new term” and “propose changes to this term" buttons. This allows user to directly go to the issue platform (e.g. GitHub) to make the suggested changes.

The structure of Geolexica is designed for efficiency with streamlined management and operations. Terms are stored in structured data (YAML) files, and are directly deployable to the website. The website operates according to best practices, and is served as a static website with dynamic search functionality. Security and performance have always been key considerations.

= Initial load and data cleanup =

The initial load of the terms will involve a bulk load from the cleaned terms and definitions that Felicity has compiled. Geolexica could easily handle the initial conversion from table format into the desired structured data format.

The cleanup process has already been started by Reese Plews, convenor of the TMG at ISO/TC 211.

[[Category: Education]]

Lexicon Committee

2019-10-22T11:24:19Z

Wiki-Tc211 tmg: /* Committee members */

The Lexicon committee is responsible for coordinating official definitions for terminology used within the OSGeo context. The committee is drawn from the OSGeo, OGC and ISO communities and is based on merit and interest.

An email list shall be setup for this group for internal communication.

= Purpose =

The Lexicon committee plays two essential roles:

a) As the gatekeeper of terms to ensure quality checks of contributions
b) As the seat of central terminology knowledge for alignment of terms and concepts. To facilitate the flow of terminology knowledge to terminology authors and users.

The committee involves representation from external groups including ISO/TC 211 and OGC in order to leverage their experience in terminology, which is useful in situations such as alerting on cross-organization alignment of concepts or term duplication.

= Coordination =

= Committee members =
TBD: Once formed, the following people have volunteered to join this committee:
OSGEO Representation
* Cameron Shorter
* Felicity B. (proposed)
Outside Representation (Non-OSGEO)
* Ronald Tse (TC?/Ribose Inc.)
* Reese Plews (ISO/TC211, TMG)

* ... others welcomed

Selection of new members is determined by committee member vote. Committee members may retire any time. If a committee member becomes inactive for many months they may be invited to retire, and if unresponsive they may be removed by the existing committee.

==Decisions==
Decisions are based on voting using the following:
* +1: For
* +0: Mildly for, but mostly indifferent
* 0: Indifferent
* -0: Mildly against, but mostly indifferent
* -1: Strongly against. This is expected to be accompanied by a reason.

For most decisions, a motion is raised within one of the committee open forums (IRC, email list, etc) and those present vote and decide. Should a decision:
* Be strategic or impact many within the committee,
* Or if there be contention in deciding, and after discussion at least one member is still strongly against the motion, by continuing to vote -1,
* Then the motion should be referred to the committee.

For motions presented to the committee, a motion is considered passed when there are more committee +1 votes than -1 votes, and either all committee members have voted, or 1 week has passed. In the case of a tie, the committee chair shall have 1.5 votes.

==Expectations of committee members==
* Contribute to or related activities when the committee is active.
* Help with whatever dirty work is required to keep the project moving forward.
* Monitor committee conversations on our email list.

==Terms of reference==

The terms of reference for the Lexicon Committee describes steps for lexicon approval and data quality requirements. This is openly shared with contributors for transparent acceptance criteria.

Contributors may propose changes to the terminology database at any time. The terminology management group shall discuss and approve or disapprove of the proposal within a reasonable timeframe. This practice is in-line with the open source, change-based, rapid iteration mantra, similar to OpenSSL.

For releases, the group shall convene periodically, such as every 4-6 months, to discuss previously decided proposals, governance or technical issues related to terminology management.

The method of submitting change requests shall also be determined and announced so that contributors understand the necessary processes and timeline.

=Documenting terms=

* TBD: This section will describe the process for managing terms.
* TBD: Information sourced from https://www.iso.org/sites/directives/current/part2/index.xhtml#_idTextAnchor196

=Process for adding and maintaining terms=
* TBD: Describe a process
* Anyone can suggest a new term or modify an existing term or its definition.
* As part of the annual OSGeoLive build process, all existing and proposed new terms will be reviewed, and discussed with proposers.
* Valid terms will be added to ... (Explain how).
* They will then be ...

= Term data structure =

Terms/Concepts are stored in structured data (YAML) files.

TODO: describe Concept YAML structure.

For terms that originate from other authoritative terminology databases, such as those from ISO or OGC, a linkage shall be established from the OSGeo terminology database back to the source.

TODO: A “contributors guide” document will greatly help these people make the proper suggestions and have them formatted correctly.

= Online presence =

Terminology isn’t useful until people use them, which means people need to first know they exist and what they mean. The Geolexica initiative has volunteered to setup https://osgeo.geolexica.org/ to serve OSGeo in managing its lexicon database.

Geolexica serves human-readable concepts and terms, as well as machine-readable JSON, allowing APIs to directly consume the content. It currently serves ISO/TC 211’s terminology management group in making its multi-lingual geographic information terminology available on the internet (https://www.geolexica.org).

To minimize friction in the feedback process, for every term offered in the OSGeo terminology pages we can offer a “propose new term” and “propose changes to this term" buttons. This allows user to directly go to the issue platform (e.g. GitHub) to make the suggested changes.

The structure of Geolexica is designed for efficiency with streamlined management and operations. Terms are stored in structured data (YAML) files, and are directly deployable to the website. The website operates according to best practices, and is served as a static website with dynamic search functionality. Security and performance have always been key considerations.

= Initial load and data cleanup =

The initial load of the terms will involve a bulk load from the cleaned terms and definitions that Felicity has compiled. Geolexica could easily handle the initial conversion from table format into the desired structured data format.

The cleanup process has already been started by Reese Plews, convenor of the TMG at ISO/TC 211.

[[Category: Education]]