- Drummond Reed
- Rieks Joosten
- Daniel Hardman
- @Judith Fleenor
- Brian Dill
- Foteinos Mergroupis-Anagnou (GRNET)
- Scott Perry
- RJ Reiser
Main Goal of this Meeting:
To introduce Judith Fleenor as our new ToIP coordinator and discuss in more depth the dedicated use of a Confluence wiki.
|10 mins||Introduction of Judith Fleenor as our new ToIP coordinator||Chairs|
|30 mins||Discussion of using a dedicated Confluence wiki as the "front end" for the ToIP terminology corpus||Chairs|
|10 mins||Open discussion|
|5 mins||Review of Decisions and Action Items and planning for next meeting||Chairs|
- link to the file
- link to the file
- File 1 - link
- New members
- Introducing Judith Fleenor as our new ToIP coordinator
- Judith is now available at firstname.lastname@example.org <== please use this email for her from now on
- Main career track has been technical and computer training—was Worldwide Training Director for Netscape
- Has had a longtime interest in identity and has worked on the U.S. IDESG and NSTIC initiatives
- Rieks asked about the role of terminology in technology and identity
- Judith underscored the need for having a good source context document—and then consistency
- We did introductions of the other CTWG members present on the call (see list above)
- Discussion of using a dedicated Confluence wiki as the "front end" for the ToIP terminology corpus
- Drummond for Judith explained the background to the question about potentially using a dedicated Confluence wiki as a "front end" to the terminology corpus
- Daniel Hardman explained the potential role of the wiki as an input tool for the ToIP "Termopedia"
- Judith asked about the outputs from the terminology corpus
- Daniel Hardman explained that the ToIP Term tool would enable exports from the terminology corpus that could be published in various ways.
- Rieks Joosten explained the importance of scopes as establishing the context for the definitions created by different stakeholders communities.
- This overall design encourages those stakeholders to harmonize terms across their scopes. This could get some subset of the terms in the terminology corpus to align and have the greatest overall utility.
- It provides the flexibility for each stakeholder group to manage their own terminology and glossary entries while leaving it open to harmonization.
- Scott Perry shared from the perspective of the Trust Assurance Task Force in the Governance Stack Working Group that we need to start to publish about the concepts that are new in the context of decentralized digital trust infrastructure.
- Individual ToIP deliverables, such as the ToIP Governance Metamodel, will need terminology sections.
- Brian Dill shared that mapping between different words are quite important for shared understanding
- Rieks Joostensaid that "any effort that requires stakeholders to give up a term they are using (because they need it) will fail if there is no sound alternative".
- He gave the example of the term "risk" at ISO that has over 40 definitions now
- ToIP has an even larger community to serve
- So it must be based on a collective cooperative voluntary effort that seeks to fulfill the actual needs of those that use terms
- No one needs to rely on others to define their terminology.
- Rieks Joosten said that the point is not to harmonize, but to enable one party to (demonstrably) understand what another means when using a specific term. It's also prerequisite for sharing terms and definitions in a (literally as well as figuratively) meaningful way.
- Judith shared her observation that there are two goals here
- The Termopedia need for shared terminology
- Publishing terms in deliverables starting ASAP
- Rieks Joosten it's important to allow the authors define their terms first, and then let the discussion about mapping and harmonization process
- Open discussion
- Review of Decisions and Action Items and planning for next meeting
- Sample Decision Item
- Sample Action Item