| id | title | sidebar_label | scopetag | date |
|---|---|---|---|---|
man-usr-wiki |
Using Wikis |
Using Wikis (Markdown) |
tev2 |
20220513 |
import useBaseUrl from '@docusaurus/useBaseUrl'
:::caution
The entire section on Terminology Engine v 2 (TEv2) is still under construction.
As TEv2 is not (yet) available, the texts that specify the tool are still 'raw', i.e. not yet processed.
readers will need to see through some (currently unprocessed) notational conventions.
:::
One way in which curators may decide that users can contribute, is by providing a wiki that the users are encouraged to edit, discuss, and evolve to a level of maturity that warrants the text to be ingested into the scope's corpus. The curators SHOULD specify the procedures, the code of conduct, etc. that support and enable the maturing of these texts, and how it is decided that such texts can become part of the scope's corpus. That's outside the scope of this document.
From the TEv2 perspective, users may contribute by creating or editing wiki-pages for a specific terminological artifact. The curators would typically already have various wiki-pages, each of which serves as a template for e.g. the definition of a concept or term, a use-case, a mental model, or any other kind of terminological artifact that is relevant within the scope.
A user can take the template, and follow the associated instructions (e.g. provide content for the various sections). That's basically it.
A user can use term refs to mark the terms that it wants to be linked to a specific meaning (terminological aritfact).
Curators that have decided to use a wiki as a means for users to contribute to the development of it's scope's corpus, should do the following:
-
If you do not already have one, create a git account.
-
Create a (git) repository, either a brand new one, or from a template.
:::note Editor's note: Additional steps need to be written here. The idea is :::
- (etc.)