Main Goal of this Meeting:
To do a complete walk-through of the CTWG workflow process for one term.
|1 min||Welcome & Antitrust Policy Notice||Chairs|
|2 mins||Introduction of new members||Chairs|
|1 min||Agenda review||Chairs|
Update on the offline meeting on CTWG workflow
|30 mins||Walk-through of one term through the entire CTWG workflow||Daniel Hardman|
|2 mins||Review of Decisions and Action Items||Chairs|
|1 min||Next meeting||Chairs|
- Update on the offline meeting on CTWG workflow (given that Daniel Hardmanwas not able to attend today)
- Rieks Joostensummarized what he and Daniel Hardmandiscussed in their offline meeting
- This is documented in an update to the Specification for Creating and Using Terms
- The Ingest phase is as simple and broad as possible.
- The Curate phase is where the CTWG adds value.
- The Produce stage is where the outputs re formed prior to processing.
- Rieks and Daniel agreed that documents/inputs are owned (controlled, authoritatively updated, ...) by a single party (person or group).
- Rieks and Daniel also talked about versioning.
- GitHub has robust tools for versioning.
- However it could be too difficult for authors to use GitHub values. Rieks favored using human-readable version numbers.
- The decision was to face the problems as they would arise, because versioning may not be needed at the start.
- As we go forward, we could learn what's needed.
- Dan Gisolfi asked about next steps, e.g., APIs for getting terms from the corpus?
- Rieks said that Daniel Hardman was going to do a walk-through of the complete workflow in order to determine what those APIs would be.
- Foteinos then showed what has been developed for terminology management at GR Net (see one screen shot below)
- This tool, called Docusaurus Terminology, is a way for generating terminology
- He showed how it works based on Markdown files written in a specific format
- It also is able to display pop-ups for terms
- Once written up in Markdown, the document is submitted to Docusaurus, all instances of the term are automatically mapped
- Foteinos demonstrated how it worked (in earlier meetings the eSSIF-Lab framework, its glossary, etc. were presented, which show what the results of the tool can look like).
- We then discussed how this tool could be used at ToIP
- It's currently a single repository for all terminology, not really designed for multiple overlapping communities
- These current limitations are something we need to consider closely
- In particular we need to look at how we can manage multiple terminologies with one overall tool
- We need to consider how to evolve the tooling over time
- Drummond asked about using this tool as a starting point
- Rieks suggested that Daniel Hardmanand Dan Gisolfishould both review this tool carefully to see how well it fits our initial requirements
- Rieks said that ESSIF-Labs also has several issues filed for feature requests
- Rieks also said we would have to open it up carefully, so as not to get swamped with support-service requests prematurely
- Foteinos suggested that if we have developers available, we could provide feedback for the next steps
- This could help drive the requirements for the next version
- Foteinos said the he believed that they would be open to pull requests
- Next steps
- Foteinos will check on how the tool might be licensed, open source, pull requests, etc.
- Foteinos and Rieks will analyze the tool in comparison to our requirements to determine what we would need in the short run
- Based on that analysis, the ToIP Foundation could potentially provide bounties for new features
- Review of Decisions and Action Items
- Drummond Reed to propose a separate meeting in Slack
- Next meeting
Example of Docusaurus as demonstrated by Foteinos:
- The WG will investigate the Docusaurus Terminology tool as a potential starting point of tooling for our terminology workflow
- Foteinos will check on how the Docusaurus Terminology tool might be licensed, open source, pull requests, etc.
- Foteinos and Rieks Joosten will analyze the tool in comparison to our requirements to determine what we would need in the short run
- Drummond Reedwill connect with Daniel Hardman to share the outcomes of this meeting
- Drummond Reedto propose in Slack if Rieks Joosten Daniel Hardman, Dan Gisolfi, and Foteinos can meet in the next week to see if they can work out a specific plan for proceeding with Docusaurus Terminology as our primary tooling.