Page Comparison

...

1. New members
2. White papers and using hover links that produce a pop-up
   1. This works the same way as Wikipedia - rich text and graphics but still constrained
   2. All of those in attendance on this call were in favor of doing this
   3. Daniel Hardman pointed out that there may be challenges about what part of the definition shows up in the pop-up
   4. Rieks would like to use a paper we are the authors of to flesh out the specifications—he suggests starting with the proposed Decentralized SSI Governance paper—or one of the Sovrin Governance documents
3. Report on tooling and process planning meetings
   1. Daniel Hardman and Dan Gisolfi met and have some new thoughts
   2. Daniel Hardman and Rieks Joosten met last week and ended out refining the thinking about process
   3. Daniel Hardman shared his takeaways and recommendations in this slide deck
   4. See the Data Lifecycle slide below for the process overview
   5. He showed an example of the ingested form of the data (a proposed definition of the term "Agent"). The ingested form is not normalized.
   6. In the second stage, the data is normalized using a script (that should be fairly easy)
      1. It separates terms from concepts
      2. Terms are cross-linked to concepts
      3. This can solve many issues, including multi-lingual terms, multiple terms for the same concept, etc.
   7. We discussed issues around multiple terms for the same concept
      1. In the same language
      2. In different languages
      3. Rieks pointed out that all definitions should be provided within contexts (also called scopes or vocabularies)
   8. In the third stage, we "glue them all back together", but we will include metadata that explains what the CTWG knows about the term
      1. Edit history
      2. Term status
      3. Comments
   9. Daniel wanted to see if we had overall consensus on the three forms of data (ingest, curate, produce) as show in the Data Lifecycle diagram below. YES.
   10. Rieks then reported on a richer internal data model (see second slide below)
       1. This allows extensibility of the internal data model to meet more needs over time
       2. The id of a type=term can be a text string
       3. This should future-proof the model
   11. Daniel noted that the hyperlinks to the corpus are important. There are two kinds of hyperlinks that are needed:
       1. One is an absolute reference to the corpus as a whole
       2. The other is a cross-reference within a specific output document
       3. Rieks made the distinction between links between terms and concepts in vocabularies and in specific documents
       4. We agreed that hyperlinks to vocabularies and terms within vocabularies
       5. We discussed the actual structure of the hyperlinks and using git artifacts and metadata for the links
       6. One particular question is version identifiers: do we need human-friendly version identifiers OR git commit hashes OR both?
          1. We discussed these two options and their respective advantages
          2. The git commit hash is "cheap" but not human-friendly.
          3. Rieks suggested that git commits can also have tags.
          4. Daniel liked the idea of tags for the human-friendly portion.
          5. Daniel raised the issue of forks and branches—which is why git uses commit hashes.
          6. Rieks noted that their are indeed good use cases for forking a terminology repo, including personal glossaries, or handing off authority for a terminology.
4. Workplan going forward
5. Review of Decisions and Action Items
6. Next meeting

Slides

Image Added

Decisions

•  Sample Decision Item

...