2021-01-04 CTWG Meeting Notes

Meeting Date

• 04 Jan 2021 

Attendees

• David Luchuk

• Drummond Reed
• Rieks Joosten
• Daniel Hardman
• Dan Gisolfi
• Scott Perry
• Steven Milstein
• @Foteinos Mergoupis-Anagnou
• @Georgios Tsoukalas
• Scott Whitmire
• Paul Knowles
• RJ Reiser

Main Goal of this Meeting:

To discuss the remaining steps necessary to putting the end-to-end CTWG workflow process in place.

Agenda 

Recording

• link to the file

Presentation(s)

• link to the file
  

Documents

• File 1 - link
• File 2 - link
  
• File 3 - link

Notes

1. New members
   1. @Georgios Tsoukalas and Foteinos Mergoupis-Anagnou are from TNO and have worked on the eSSIF-Labs terminology work
2. Using the Decentralized Governance white paper as a test of the hyperlinking pop-up proposal
   1. The idea is to make this white paper an example of how you can link to terminology in the CTWG corpus.
   2. This particular white paper refers to term defined in several different glossaries that have been ingested into the CTWG corpus.
   3. So as a first step, the white paper needs to be converted into a Markdown file.
   4. Then we need to figure out how the hyperlinked references and pop-up links will work.
   5. We looked at Wikipedia pages and how they do pop-ups and how the markup behind them worked.
   6. So the problem breaks into two parts:
      1. How to add the necessary hyperlinks.
      2. How to render the pop-up.
   7. Daniel proposed that we accept this as a use case and example to implement.
   8. We discussed the potential to ingest white papers that provide definitional input to the corpus.
   9. Rieks shared two links to eSSIF-Lab terminology work that provides examples of how it works.
      1. https://gitlab.grnet.gr/essif-lab/framework/-/blob/master/docs/terms/agent.md
      2. https://gitlab.grnet.gr/essif-lab/framework/-/blob/master/docs/functional-architecture.md
   10. Dan Gisolfi found this information about how Wikipedia produces pop-up definitions in Wikipedia pages ("WikiLink Support requires Markdown Enhancement Plugins"
       
       1. https://github.com/yzhang-gh/vscode-markdown/issues/638
       2. So common rendering work has already been done for using Markdown for such popups.
3. Discuss Terminology Engine V2 (TEV2) being developed at eSSIF-Lab by GRNET
4. Review of URL / hyperlinking proposal - Daniel Hardman
   1. GitHub-style URLs to Markdown files render as HTML - example is Hyperledger Aries RFC documents
   2. We should take advantage of several features GitHub already offers
   3. Daniel Hardman recommends that we don't include mscope in the hyperlinks
   4. Labels should be composed of both a human-friendly label and a number (the number identifying a different definition of the term)
   5. For concepts, we might reverse it (number before name)
   6. For versions, Daniel proposes that we use GitHub commit hashes
   7. This gives up some human-friendliness but takes advantage of GitHub features
   8. Dan Gisolfi asked a key question: is the primary output of our process a specific kind of an output?
      1. Pop-ups like Wikipedia are only possible with live web pages
      2. PDFs, for example, would not support pop-ups
   9. Rieks pointed out that a PDF or a print version could include an Appendix to a document that provided an alphabetical glossary for the document
   10. We had a long discussion about the separation of the curated artifacts and the rendered versions and what we need for authoring vs. what we need to be displayed. It focused on the Data Lifecycle slide below, and the question of which stage the hyperlink URLs should be produced: Curate, Produce, or Process.
   11. Daniel Hardman was okay with the idea of having a standard default GitHub Pages version of the curated content, but does not want to focus there; he would rather focus on the Process cycle.
   12. Dan Gisolfi wants to focus on a standard ToIP rendering of the glossary.
5. Review of Decisions and Action Items
6. Next meeting

Slides

From URL / hyperlinking proposal (Daniel Hardman)

This last slide (above) is from the last meeting.

Decisions

• We will use the 

Action Items

• Sample Action Item