Meeting Date

  •  

Zoom Meeting Link / Recording

Attendees

Main Goal of this Meeting

1) Report on terms wiki backfill work, 2) discuss relationship of the eSSIF-Lab Glossary with the ToIP Core Glossary, 3) Next steps with the CTWG User Guide. 

Agenda Items and Notes (including all relevant links)

TimeAgenda ItemLeadNotes
3 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: Filipe Pinto is joining so he can help his company with identity services
5 minGeneral announcementsAll

News and updates of general interest to CTWG members:

  • Scott Perry shared that his CPA firm was purchased by Schellman, a U.S. national assurance and verification firm of ~300. Scott is now Principal, Crypto and Digital Trust Services. 
2 minReview of previous action itemsChairs
  • ACTION: Drummond Reed to prepare CTWG slides about terms wikis & glossaries for the Jan 19 All-Member Meeting.
  • ACTION: Drummond Reed to start the first steps of the action plan to "backfill" the terms already used in ToIP Approved Deliverables.
  • ACTION: Drummond Reed to add this topic—about the relationship of the ToIP Core Glossary and a ToIP Dictionary—to the agenda of our next meeting.
15 minReport on terms wiki "backfill" workDrummond Reed

Drummond started to add some new terms to the ToIP Core terms wiki and the GSWG terms wiki. However he ran into a problem with proxy term entries (terms added to one terms wiki intended to cross-reference a term in another glossary). He will share the problem and see if we can quickly figure out a solution.

  • The issue is the markup notation of a proxy term entry in a terms wiki — one that points to another glossary. For example, see the term entity is the ToIP Core Glossary. 
  • After discussion with Daniel HardmanRieks Joosten, and the group, we agreed that we would just stick with the current format for now (our "V1" cycle). When we develop V2 we can consider what to do about the notation.
  • ACTION: Drummond Reedand other volunteers to complete the "backfill" work of terms from the GSWG specifications that should be in the ToIP Core Glossary.

We also discussed the eSSIF-Lab definition of jurisdiction.

Nicky Hickman pointed to this definition from Merriam Webster:

  • Definition of jurisdiction 1: the power, right, or authority to interpret and apply the law a matter that falls within the court's jurisdiction 2a: the authority of a sovereign power to govern or legislate b: the power or right to exercise authority : CONTROL 3: the limits or territory within which authority may be exercised
  • We concluded that the Merriam Webster definition does indeed (under 2b and 3) include a wider scope than just legal jurisdictions. So the eSSIF-Lab definition is fine.
20 minRelationship of the eSSIF-Lab Glossary to the ToIP Core Glossary

As the eSSIF-Lab Glossary becomes more mature, we discussed the relationship we want it to have with the ToIP Core Glossary.

  • Rieks Joosten explained that many of the eSSIF-Lab term definitions are derived from mental models developed there.
  • Nicky Hickman pointed out in her experience that if you, as an author, start to use a pattern, you want to use all the terms from that pattern. So her advice is "pick your patterns first".
  • Drummond Reed suggested that each mental model/pattern should have its own tag so it can be included as a whole in a glossary.
  • DECISION: We agreed that, whenever possible, the ToIP Core Glossary will reuse (via proxy term entries) the terms already defined in the eSSIF-Lab Glossary. 

We discussed the ToIP Core Glossary and a ToIP Dictionary.

  • Drummond Reed noted that, with the strength of the eSSIF-Lab Glossary, so far he's not found a difference that is important enough to merit a separate definition. So he suggests holding off on the need for a ToIP Dictionary until we have enough different definitions of terms to merit it.
  • Nicky Hickman suggested that a dictionary MAY be needed across the multiple communities — and that would be an ideal project. It would be a very nice-to-have. 
  • We discussed that it could be a good intern project.
10 minCompleting the CTWG User GuideAll

We are at the point where we need to finish a complete current draft of the CTWG User Guide that Rieks Joosten and Daniel Hardman have both contributed to. Who has bandwidth to work on this?

  • We did not come to a conclusion — this will continue to be an action item.
  • ACTION: CHAIRS to recruit one or more volunteers to complete the full V1 draft of the CTWG User Guide.
5 mins
  • Review decisions/action items
  • Planning for next meeting 
Chairs
  • ACTION: Drummond Reed to put the ToIP Term Tool V2 topic on the agenda for the next meeting.

Decisions

  • DECISION: We agreed that, whenever possible, the ToIP Core Glossary will reuse (via proxy term entries) the terms already defined in the eSSIF-Lab Glossary. 

Action Items

  • ACTION: Drummond Reedand other volunteers to complete the "backfill" work of terms from the GSWG specifications that should be in the ToIP Core Glossary.
  • ACTION: CHAIRS to recruit one or more volunteers to complete the full V1 draft of the CTWG User Guide.
  • ACTION: Drummond Reed to put the ToIP Term Tool V2 topic on the agenda for the next meeting.
  • No labels