Meeting Date
Attendees
- Drummond Reed
- Rieks Joosten
- Daniel Hardman
- Dan Gisolfi
- Foteinos Mergroupis-Anagnou (GRNET)
- Brian Dill
- Line Kofoed
- Michael Herman
- sankarshan
- Scott Whitmire
- Scott Perry
- Steve Magennis
- Steven Milstein
Main Goal of this Meeting:
Discuss two potential revisions to the ToIP Term tool spec; approve the ToIP Term tool bounty writeup; share updates on several other time-sensitive CTWG topics.
Agenda
Time | Item | Lead | Notes |
5 min | Start recording | Chairs | |
5 mins | ToIP Term tool internal data model: adding a Scope/Context object (including Licensing Info) | Drummond Reed | |
5 mins | ToIP Term tool: question about scope-specific definitions | Drummond Reed | |
10 mins | ToIP Term Tool bounty writeup — are we ready to approve? | Daniel Hardman | |
10 mins | Placing the bounty - next steps | All | |
10 mins | Progress on the Good Health Pass Ecosystem Governance Framework Glossary | Drummond Reed | |
10 mins | Can we/should we import the ESSIF-Labs Glossary and Mental Models? | ||
5 mins | Review of Decisions and Action Items and planning for next meeting | Chairs |
Recording
- link to the file
Presentation(s)
- link to the file
Documents
- File 1 - link
Notes
- New members
ToIP Term tool internal data model: adding a Scope/Context object
- The purpose of this object is to define the following properties
- Purpose
- Description
- Governing entity name
- Governing entity URI
- Licensing type URI
- Licensing info (everything necessary to generate the Licensing Page)
- Notes with any additional information
- Daniel had not considered some of these elements, but they could be included in a document at the root of the Scope directory for each scope.
- Rieks Joosten agreed that these were good properties.
- A purpose is needed because each concept should be fit or that purpose.
- He encourage us to keep an open mind about what this may be used or.
- Michael Herman pointed out that if the same entity is contributing multiple scopes, it would be ideal if there was one reference to that scope definition.
- ACTION: Take it to Slack to figure out the best way to add to the data model.
- The purpose of this object is to define the following properties
- ToIP Term tool: question about scope-specific definitions
- What do we do if two scopes are using the same term with slightly different definitions?
- Example: the term "agent" in scope A and scope B
- Each would have its own definition of the concept associated with the term "agent" in its scope
- To harmonize them, the stewards for scope A and scope B could decide to harmonize and point at one definition, or create a new one
- Daniel Hardman pointed out a subtlety that, if there are two different governing entities, will one agree to defer to the other in perpetuity, or will they agree to point to a specific version but reserve the right to evolve it independently in the future. This question of evolution of thinking is supported, but an open question of how it will work.
- Rieks Joosten pointed out that it is important for an author to be able to link to the exact version of a definition.
- That raised the question of whether a term itself can be versioned
- Daniel Hardman gave an example of the term "organization" being changed to "organisation", or a change in punctuation.
- Rieks Joosten shared that it could be handled by the status of the term.
- Daniel Hardman clarified that the original URI for the file is different from the representation of the term in the Markdown file. He proposed the following:
- The URI of the term is intended to stay the same provided the authors believe it is the same term.
- Daniel Hardman pointed out that we have the ability to point to an exact version of any file.
- This led us to a discussion of linking to versions. The author can link to:
- The most recent version of a term
- A specific version of a term at a point in time
- ToIP Term Tool bounty writeup — are we ready to approve?
- Progress on the Good Health Pass Ecosystem Governance Framework Glossary
- Can we/should we import the ESSIF-Labs Glossary and Mental Models?
- Review of Decisions and Action Items and planning for next meeting
Slides
#1 —
Decisions
- Sample Decision Item
Action Items
- Sample Action Item