Page History

...

See the Meeting Pages for agendas, notes, and recordings from all meetings.

Intellectual Property Rights (Copyright, Patent, Source Code)

This WG uses the same IPR licensing selections as other ToIP Foundation WGs:

• Copyright mode: Creative Commons Attribution 4.0.
• Patent mode: W3C Mode(based on the W3C Patent Policy).
• Source code: Apache 2.0. 

Conveners (add your name if you are interested to become one of the conveners)

• Rieks Joosten, TNO
• Drummond Reed, Evernym

Interested Members (add your name and organization if you may be interested in joining this proposed WG)

• Daniel Hardman
• Oskar van Deventer
• Scott Perry
• Shashishekhar S, Dhiway
• Philippe Page
• Paul Knowles
• Taylor Kendal
• Scott Whitmire
• Arjun Govind
• Vinod Panicker
• sankarshan, Dhiway
• Steven Milstein
• Joaquin Salvachua
• James Hazard
• Ajay Madhok
• Eric Drury
• Abilash Soundararajan
• Natarajan Chandrasekhar
• Steven Milstein
• Ken Adler
• RJ Reiser

Deliverables

1. Develop and maintain a high-quality corpus of terminology that covers the needs of the ToIP community.
2. Develop a process whereby this corpus can be:
1. Curated, based on evidence and using expert opinion, such that concepts, relations between concepts and constraints can e.g. be
   1. carefully defined,
   2. assigned an identifier (name/number/label) to distinguish it from any other concept in the corpus,
   3. mapped onto terms that are defined and/or commonly accepted in various relevant domains/contexts,
   4. their usage and relevance documented from organic sources,
   5. their status adjudicated into e.g. 'working', 'preferred', 'accepted', 'superseded' and 'deprecated'.
2. Enhanced in a collaborative, open, and fair manner by interested community members.
3. Versioned.
4. Published in different ways (e.g. as a glossary, concept map, use-case stories ...), for specific purposes (e.g. education, reference, , ...) by different means (e.g. a PDF, a website, presentations/webinars, ...) and as needed by different audiences/stakeholders or domains (e.g. business domains, architectural domains, ...)
5. Promoted as a valuable public resource and an influence for convergence and excellence.
3. Train and organize volunteers so the initiative develops sustainable long-term momentum.
4. Disseminate/promote the work across ToIP WGs and other relevant audiences.

Chairs / Leads 

• Co-Chair: Rieks Joosten
• Co-Chair: Drummond Reed

Description

The primary focus of the ToIP Foundation is not just on technology (e.g. cryptography, DIDs, protocols, VCs, etc.), but also on governance and on business, legal and social aspects. Its mission to construct, maintain and improve a global, pervasive, scalable and interoperable infrastructure for the (international) exchange of verified and certified data is quite complex, and daunting". This not only requires technology to be provided (which is, or should be the same for everyone, i.e. an infrastructure). It also requires that different businesses with their different business models can use it for their specific, subjective purposes. And that each individual business and user is provided with capabilities that facilitate its compliance with the rules, regulations and (internal and external) policies that apply to that entity - the set of such rules, regulations and policies being different for every such entity, and dependent on the society, the legal jurisdictions and individual preferences. All this is to be realized by people and organizations from different backgrounds - different cultures, languages, expertise, jurisdictions etc., all of whom have their own mindset, objectives and interests that they would like to see served.

...

Finally, we expect to see results that we haven't thought of yet, the construction of which will be initiated as the need arises, by (representatives of) those that need such results for a specific purpose. Perhaps we might produce a method for resolving terminological discussions that can be lengthy and do not always get properly resolved (e.g. as in id-core issues #4, #122). Here, we leverage a prior collaboration between Daniel Hardman (Evernym) and  Rieks Joosten (TNO).

Deliverables

...

1. carefully defined,
2. assigned an identifier (name/number/label) to distinguish it from any other concept in the corpus,
3. mapped onto terms that are defined and/or commonly accepted in various relevant domains/contexts,
4. their usage and relevance documented from organic sources,
5. their status adjudicated into e.g. 'working', 'preferred', 'accepted', 'superseded' and 'deprecated'.

...

)

...

.

Requirements

The Corpus of Terminology MUST have:

...