Versions Compared

Old Version 4

changes.mady.by.user Rieks Joosten

Saved on

compared with

New Version 5

changes.mady.by.user Drummond Reed

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

TimeAgenda ItemLeadNotes
5 min
  • Start recording
  • Welcome & antitrust notice
  • Introduction of new members
  • Agenda review
Chairs
  • Antitrust Policy Notice: Attendees are reminded to adhere to the meeting agenda and not participate in activities prohibited under antitrust and competition laws. Only members of ToIP who have signed the necessary agreements are permitted to participate in this activity beyond an observer role.
  • New Members: None
5 minReview of previous action itemsChairs
  •  ACTION: Drummond Reed to determine where to move Daniel Hardman's documentation of how to use the ToIP Term Tool.
    •  CTWG repo is where it needs to go (the "User Guide"). This is where we should keep all of our core documentation. 
  •  ACTION: Drummond Reed to contact Judith Fleenor to confirm that the $20K bounty is still available to put towards ToIP Term Tool V2.
5 minCTWG Slack discussionsAll

We have had some very robust discussions in our Slack channel. How do we want to continue these?

  • Naming terms and defining concepts
  • "Trust" and "transitive trust"

Discussion

  • Steven Milstein suggested GitHub Discussions is an alternative
    • It is also a good onboarding tool for new ToIP members — they can get comfortable with it
    • We can decide any time a disucusdiscussion is worth going deeper on
  • ACTION: Steven Milstein to help us bootstrap the first discussions
10 minTerms wiki user feedback

Drummond Reed
Scott Perry

Feedback from using the ToIP Core terms wiki and the GSWG terms wiki to prepare the glossaries for the ToIP Governance Architecture Specification, the ToIP Governance Metamodel Specification, and the ToIP Governance Metamodel Specification Companion Guide.

  • Scott shared that we want to see ToIP-wide policies that ToIP deliverables have glossaries.
  • One of the key questions was what term should go where.
  • Rieks agreed that it is good for us to have this experience.
  • By default each terms community will define a term in its own terms wiki.
  • But if the term is defined in another terms wiki, then you have two choices:
    • You can include the term from the external terms wiki in your glossary
    • You can use the markup with the "@sign".
    • You can participate in the other terms community.
  • The ToIP Core terminology is a challenge because it is a superset community.
    • The curation of this terminology is the responsibility of the CTWG.
    --
5 minsReferencing eSSIF-Lab Glossary termsRieks Joosten

Seek Rieks recommendation as to how ToIP terms wikis should reference eSSIF-Lab Glossary terms until they are in a terms wiki. 

  • Rieks would like the ToIP Term Tool to not refer exclusively to terms wiki pages, but to glossary entries.
  • Terms wikis are one form of ingestible input for the CTWG corpus.
  • So ideally links would be to glossary entries.
  • Daniel Hardman's feedback was that it will be necessary to refer to the superset glossary.
  • RE referencing the eSSIF-Lab Glossary in the short term should be a matter of "stuffing" the eSSIF-Lab Glossary into a ToIP repo.
  • So the answer is to TODO
25 minToIP Term Tool Requirements documentAll

Review the new ToIP Term Tool Requirements document that proposes features for the V1.x, V2, and V3+ versions of the ToIP Term Tool.

  • --
5 minAny other business


  • Review decisions/action items
  • Planning for next meeting 
Chairs

...