THIS PAGE IS NOT READY - IT'S INCOMPLETE, INCORRECT, INCONSISYTENT AND INCOHERENT - IT'S WORK IN PROGRESS
Introduction
The CTWG Mental Model Task Force (MMTF) helps TOIP members and communities to express themselves in ways that enable others to understand what that communication intends to convey to whatever level of precision is needed.
This is important, because contributors/users in TOIP come from various backgrounds. Their culture may not be Western. English may not be their native tongue. They may be experts in non-technological topics that are relevant for TOIP. Working with one another presumes a setting where participants have some level of shared understanding. Often, sharing one's understanding at a superficial level suffices. Other situations require that underlying concepts are shared in a more in-depth fashion. It's like cars: people buying, selling, or driving cars do not need in-depth shared knowledge about cars, whereas (maintenance or construction) engineers or liability lawyers need to share a deeper knowledge of how cars do (or do not) work.
We expect to see situations of "language confusion", i.e. in which people use words or phrases, the intension (not: intention) of which differs from the interpretation of some listeners/readers. CTWG aims to provide means to resolve that. Sometimes a casual glance at a dictionary or glossary is the solution. In other cases, deeper understanding matters, e.g. in when drafting specifications or contracts. Then we need more than a set of definitions.
Scope
The scope of CTWG is to assist TOIP working groups (WGs), task forces (TFs), and other communities of interest or communities of practice that exist both within and outside of the ToIP Foundation to develop the concepts and terms they need for themselves or for particular projects, and make them available to the public. This includes developing artifacts and tools for discovering, documenting, defining, and (deeply) understanding the concepts and terms used within TOIP. Key deliverables include ways to define terms (e.g. terms wikis), maintain a corpus of data underlying these terms, and provide ways to query the corpus to obtain terms e.g. for the creation of glossaries and other artifacts. The data that underlies the terms typically consists of (formally modeled) concepts, plus their relations and constraints, and will encompass perspectives from technical, governance, business, legal and other realms. Although CTWG will maintain this corpus of data via repositories that all TOIP WGs and TFs can contribute to and inherit from, this does not preclude WGs or TFs from maintaining their own specialized glossaries if they require. Such specialized glossaries, together with other generators of concepts and terminology elsewhere in the industry, are expected to feed back into the glossaries and corpus of data maintained by CTWG in a cycle of continuous improvement.
Meetings
Schedule:
Meetings are bi-weekly, every second Monday from 10:00-11:00 PT / 17:00-18:00 UTC. See the ToIP Calendar for full meeting details including Zoom links.
See our Meeting Pages for agendas, notes, and links to recordings of all meetings.
Deliverables
The table below lists all CTWG deliverables that have been approved to move beyond Pre-Draft status.
Name of Deliverable | Deliverable Type | Link to Draft Deliverable | Task Force | Status |
---|---|---|---|---|
ToIP Concepts and Terminology Glossary | Glossary | TBD | TBD | Draft Deliverable (approved 2021-08-16) |
ToIP Concepts and Terminology User Guide | Guide | TBD | TBC | Draft Deliverable (approved 2021-08-16) |
The overall scope of the CTWG includes the following activities:
- Develop and maintain a high-quality corpus of terminology that covers the needs of the TOIP community.
- Develop a process whereby this corpus can be:
- Curated, based on evidence and using expert opinion, such that concepts, relations between concepts and constraints can e.g. be
- carefully defined,
- assigned an identifier (name/number/label) to distinguish it from any other concept in the corpus,
- mapped onto terms that are defined and/or commonly accepted in various relevant domains/contexts,
- their usage and relevance documented from organic sources,
- their status adjudicated into e.g. 'working', 'preferred', 'accepted', 'superseded' and 'deprecated'.
- Enhanced in a collaborative, open, and fair manner by interested community members.
- Versioned.
- Published in different ways (e.g. as a glossary, concept map, use-case stories ...), for specific purposes (e.g. education, reference, , ...) by different means (e.g. a PDF, a website, presentations/webinars, ...) and as needed by different audiences/stakeholders or domains (e.g. business domains, architectural domains, ...)
- Promoted as a valuable public resource and an influence for convergence and excellence.
- Train and organize volunteers so the initiative develops sustainable long-term momentum.
- Disseminate/promote the work across TOIP WGs and other relevant audiences.
Chairs / Leads
- Co-Chairs: Rieks Joosten, Drummond Reed, Daniel Hardman
How to Join
You can join this WG by signing up for the Foundation mailing list at lists.trustoverip.org. Our mailing list is concepts-terminology-wg@lists.trustoverip.org.
Members as well as observers are welcome (see the caveat below).
Participation
For the protection of all Members, participation in working groups, meetings and events is limited to members of the Trust over IP Foundation (including their employees) who have signed the membership documents and thus agreed to the intellectual property rules governing participation. If you or your employer are not a member, we ask that you not participate in meetings by verbal contribution or otherwise take any action beyond observing.
Intellectual Property Rights (Copyright, Patent, Source Code)
The WG inherits the IPR terms from the JDF Charter. These include:
- Copyright mode: Creative Commons Attribution 4.0.
- Patent mode: W3C Mode (based on the W3C Patent Policy).
- Source code: Apache 2.0, available at http://www.apache.org/licenses/LICENSE-2.0.html. The GSWG TA TF is not expected to produce source code.