...
Rieks see the two efforts are very closely aligned. Since eSSIF-Lab is a two-year project, he is thinking it may need a landing place, and the ToIP CTWG might be a good home.
Discussion
Dan Gisolfi asked if the ToIP Concepts and Terminology should view the eSSIF-Lab Concepts and Terminology work is an input. Rieks agreed.
Dan felt that we should establish a data model for the underlying work. But we need to establish an extremely lightweight way to provide inputs to the data model.
Dan offered that what eSSIF-Lab has already done with their eSSIF-Lab Functional Architecture is an input into our WG.
Rieks agreed that eSSIF-Lab's terminology in that document is an input, and they are open to evolving it.
Ultimately, Rieks would like to see one kind of governance over as few repositories as possible for incorporating the corpus of terminologies for generating what we need out of it.
Daniel Hardman suggested that If we want to use a professional terminology management product, or if you want to know what features they offer, a good one to study is TRADOS Studio / Multiterm / Termbase.
He suggested that we should work backwards from concrete outputs. Suggestions were:
- Saturn V TIP Glossary
- Bedrock Glossary
- Sovrin Utility Governance Framework Glossary
- Sovrin Ecosystem Governance Framework Glossary
Daniel Hardman suggested we pick one as a concrete goal. Dan Gisolfi suggested the Bedrock glossary.
Dan Gisolfisuggested using the Markdown that's already been created for a process.
Drummond Reed said the the Sovrin Glossary is ready to be contributed to this WG and will be deprecated after that so that any work continues here.
Daniel Hardman suggested these steps:
- Daniel Hardman will design a way to ingest the Sovrin Glossary into Github.
- Dan Gisolfi will input the terms needed for the Bedrock Glossary.
- Drummond Reed will provide a liaison to the Sovrin Utility Governance Framework Task Force and Sovrin Ecosystem Governance Framework Task Force to recruit them for the input process.
Daniel Hardman also has a strong vested interest in also using this output to work on Hyperledger Aries RFCs.
We concluded that we'll meet again in our next meeting in 2 weeks. In the meantime we'll work async, with David Luchukhelping to coordinate.