Time

Agenda Item

Lead

Notes

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:

  • Sid Haniff is a software architect with 30+ years experience. Started with reservation systems for British Airways; online delivery for an online banking platform; currently working on a healthcare platform. Sid has volunteered to help Rieks with the Terms Toolbox 2.0 work.

5 min

General announcements

All

Any news and updates of general interest to CTWG members

• @Drummond Reed shared that ETSI, the EU technical standards body, is defining terms for the European Digital Identity Wallets initiative and we may influence those.

2 min

Review of previous action items

Chairs

10 min

Progress on Terms Tool 2.0 planning

@Rieks Joosten 

Update from Rieks on his thinking about Terms Tool 2.0 and any feedback from the posting of interested developers in the ToIP community.

• @Rieks Joosten said that Sid responded to his request for volunteers for the ToIP Terms Tool 2.0 and they are now collaborating together.

• Sid has already begun a small prototype, starting with a Scope Administration File (SAF).

• At the moment he's developing in a local GitHub directory, but then we can work out where it will go in the ToIP GitHub.

• @Drummond Reed suggested that Sid will benefit from a meeting with @Daniel Hardman. Sid and Rieks agreed.

• ACTION: @Drummond Reed to connect Sid Haniff and @Rieks Joosten with @Daniel Hardman to help with the transition from Terms Toolbox 1.0 to Terms Toolbox 2.0.

• All of this is currently documented in GitHub at https://essif-lab.github.io/framework/docs/tev2/tev2-overview

• @Drummond Reed suggested that it is fine to continue in those repos; we can decide how to transition them to ToIP when the time is right.

• Drummond asked what else that CTWG members could do to assist.

• Rieks said that it would be helpful to have some additional "bricks" in the TT V2 infrastructure.

  • Sid said that the place he'd like the most help would be in the human-readable glossary side. These could be based on the general direction that @Daniel Hardman started.

  • What Rieks would really like is to see if some academics using Latex could test the tooling to see if it could work with Latex white papers.

    • @Carly would be one candidate.

    • Mary Lacity would be another.

  • ACTION: @Sid Haniff will work with @Rieks Joosten to write up a description of the skill set(s) that will be most helpful with the next set of "bricks".

10 min

Human Experience WG Terms Wiki

@Nicky Hickman 

Huge kudos to @Daniel Hardman for creating https://github.com/trustoverip/hxwg and https://trustoverip.github.io/hxwg/glossary. Nicky can update us on progress.

• Nicky is working on the terms wiki for the Harms Task Force and other uses in the HXWG.

• Also very much needed for market-facing language.

• Nicky will be one curator for the HXWG glossary. 

• ACTION: @Nicky Hickman will recruit at least one additional curator for the HXWG glossary.

10 min

Technology Architecture Task Force Terms Wiki

@Drummond Reed 

The TATF is ready now for its own terms wiki to support the ToIP Technology Architecture Specification. The URL should be https://github.com/trustoverip/tswg.

• As an interim measure, they are already gathering terms in this Google doc.

• The TSWG terms wiki should have the same relationship to the ToIP Core terms wiki (https://github.com/trustoverip/toip/wiki) as the GSWG terms wiki (https://github.com/trustoverip/gswg/wiki). 

• @Rieks Joosten shared a concern that terms wikis do not have clear "ownership".

  • He suggests that the home page for each terms wiki include some standard metadata.

  • Contact information for at least one, preferably more than one, curators

  • A pointer about where to go with any issues (email, Slack channel, etc.)

  • A status indicator, i.e., in drafting, stable, in transition, etc.

  • A statement of the license for the content in the terms wiki (e.g., the standard ToIP license)

  • This is summarized in https://essif-lab.github.io/framework/docs/tev2/tev2-spec-saf#terminology — this should tell you anything related to the scope.

  • @Brian Dill suggests that in the documentation we include a table of name/value pairs of this metadata.

  • @Rieks Joosten seconded that and said it is required for ingestion.

• Rieks recommended that the contributors to the wiki follow the advice in the links below.

  • https://repository.tno.nl//islandora/object/uuid:964a90da-da81-4d38-9f45-84f3f5fa96b3

  • https://essif-lab.github.io/framework/docs/terms/definition

  • https://essif-lab.github.io/framework/docs/terms/pattern-terminology 

10 min

Meta-mental model discussion (if time permits)

@Rieks Joosten 
@Drummond Reed 

If time permits (and Rieks is open to it), review a fascinating new mental model he is developing — the Semantics Pattern. See screenshot #3 below.

Unfortunately we ran out of time to review this mental model but CTWG are encouraged to review it and provide Rieks with any feedback.

5 mins

• Review decisions/action items

• Planning for next meeting 

Chairs