fixing termref errors

Signed-off-by: Rieks <RieksJ@users.noreply.github.com>

docs/essifLab-collaborative-understanding.md

@@ -41,7 +41,7 @@ Traditional tools usually come with drawbacks that reduce their practical useful
 The eSSIF-Lab terminology effort is an attempt to improve on this, by
 - creating and using tools that help authors and readers to understand the texts the create/read;
 - creating and maintaining a [Terminology Corpus](corpus@) that documents such understanding;
-- automatically regenerate [knowledge artifacts (e.g. [glossaries](@) or [dictionaries](@)) as the [corpus](@) is being updated.
+- automatically regenerate [semantic units](@) (e.g. [glossaries](@) or [dictionaries](@)) as the [corpus](@) is being updated.
 
 ### eSSIF-Lab Terminology Engine
 

docs/essifLab-fw.md

@@ -138,7 +138,7 @@ It is expected that there are already some interfaces out there that may turn ou
 
 [ABC] Its origins lie with the [*ABC4Trust project*](https://abc4trust.eu/). Extensive [*documentation*](https://abc4trust.eu/index.php/pub) is available, e.g. an [*Architecture for Attribute-based Credential Technologies*](https://abc4trust.eu/download/Deliverable_D2.2.pdf) (also one [*for developers*](https://abc4trust.eu/download/ABC4Trust-H2.2_ABC4Trust_Architecture_for_Developers.pdf)).
 
-[eIDAS5] [*"Regulation (EU) No 910/2014 of the European Parliament and of the Council of 23 July 2014 on electronic identification and trust services for electronic [transactions](@) in the internal market and repealing Directive 1999/93/EC"*](http://eur-lex.europa.eu/legal-content/EN/TXT/?uri=uriserv:OJ.L_.2014.257.01.0073.01.ENG). *EUR-Lex*. The European Parliament and the Council of the European Union.
+[eIDAS5] [*"Regulation (EU) No 910/2014 of the European Parliament and of the Council of 23 July 2014 on electronic identification and trust services for electronic transactions in the internal market and repealing Directive 1999/93/EC"*](http://eur-lex.europa.eu/legal-content/EN/TXT/?uri=uriserv:OJ.L_.2014.257.01.0073.01.ENG). *EUR-Lex*. The European Parliament and the Council of the European Union.
 
 ------
 

docs/saf.yaml

@@ -42,6 +42,7 @@ versions:
     - term[concept,property,relation,pattern,semantic-unit]@tev2
     - term[glossary,dictionary,terminology,vocabulary]@tev2
     - term[semantics,term,define,definition]@tev2
+    - termid[pattern:terminology]@tev2
     - "*" # import all terms as curated in the current scope.
   - vsntag: ctext # this version contains all terms that are curated by essiflab
     termselection:

docs/terms/definition.md

@@ -7,7 +7,6 @@ term: definition
 formPhrases: [ "definition{ss}" ]
 status: draft
 grouptags:
-hoverText: "Definition: a text that helps Parties to have the same understanding about the meaning of (and Concepts behind) a Term, ideally in such a way that these Parties can determine whether or not they make the same distinction."
 glossaryTerm: "Definition"
 glossaryText: "a text that helps [parties](@) to have the same understanding about the meaning of (and [concept](@) behind) a [term](@), ideally in such a way that these [parties](@) can determine whether or not they make the same distinction."
 date: 20210601
@@ -45,11 +44,6 @@ A **definition** is a text that comprises at a minimum:
 - a [criterion](https://www.lexico.com/definition/criterion) that specifies the necessary and sufficient conditions for determining what does and what does not constitute some [concept](@) (idea, class of [entities](@));
 - a [name or phrase](term@) that is used within the [scope](@) to refer to (unidentified, or arbitrary, or specific) [entities](@) that satisfy the criterion.
 
-### Examples
-
-- The definition of the term [definition](@) (a) is defined in, and hence valid in the scope `eSSIFLab`, (b) specifies a criterion (see the `Criteria` section above), and (d) has a name (i.e. `definition`) associated with it. Since it satisfies the criteria of `definition`, it can be referred to as 'the definition of `definition`'.
-- The [concepts](@) defined within the scope eSSIFLab have definitions associated with them, where the criteria, relevance and terms are defined in the [concept-file](@) of that concept.
-
 ### Related Concepts
 
 * [Term](@) is a label that is used in some context to refer to a [Concept](@), the set of entities that satisfy the concept's criteria, or an arbitrary element of that set. Different contexts may use different terms to refer to a single concept. In a single context, a single term should be used to refer to an individual concept.

docs/terms/pattern-semantics.md

@@ -32,7 +32,7 @@ Storyline that needs to be worked out:
 - it is impossible to really understand one another because Knowledge is intangible.
 - next best is to create tangible, so called (terminological) artifacts that a party can be create/obtain, store, process, disseminate, for the purpose of enabling other parties to 'understand' (parts of) what it knows.
 - [definitions](@) are the prime examples of such artifacts; ideally, they are phrased as criteria so that different [parties](@) can all assess these criteria in different use-cases (relevant for the [objectives](@) they all seek to realize), and subsequently agree on whether or not they have all interpreted some criteria in some use-case in the same manner, and _if_ they do, conclude that they have the same understanding about the disctincion that the criteria makes (at least to the extent to where the use-cases go).
-- other artifacts may also help in understanding each other's knowledge. Such artifacts include more casual explanations, a formal or informal description of how the various concepts that are being explained (or defined) relate to one another, etc. Thus, we expect to see [knowledge artifacts of different kinds to be created, maintained, evaluated and continually improved on.
+- other artifacts may also help in understanding each other's knowledge. Such artifacts include more casual explanations, a formal or informal description of how the various concepts that are being explained (or defined) relate to one another, etc. Thus, we expect to see [semantic units](@) of different kinds to be created, maintained, evaluated and continually improved on.
 - establishing a set of such [definitions](@), associated [terms](@) (a 'common [terminology](@)') enables the [parties](@) to express characteristics of [entities](@) as (scoped!) [attributes](@), and hence a [partial identity](@) of an [entity](@) in a (digital) representation.
 
 The [pattern](@) also hints at the relation between [semantics](@) and

docs/terms/scoped-term.md

@@ -3,7 +3,7 @@ id: scoped-term
 displayed_sidebar: essifLabSideBar
 scopetag: essifLabTerminology
 termType: concept
-term: term
+term: scoped-term
 status: draft
 grouptags:
 hoverText: "Scoped Term: a Term, the meaning of which is determined by the Definition to which it refers in a specific Scope/context."

docs/terms/tag.md

@@ -21,7 +21,7 @@ A **Tag** is an alphanumeric string that is used to identify [scope](@) (so call
 
 Scopetags [identify](@) a [scope](@) (from within a given [scope](@)), and hence can be used (within that given [scope](@)) to disambiguate [terms](@). For example, `#essif-lab:term` is an [identifier](@) for the [concept](@) that within the [scope](@) [identified](identify@) by the scopetag `essif-lab` is referred to by the [term](@) 'term'. Scopetags typically satisfy the regex `#[a-z0-9_-]+` and is often preceded by the `#` character to designate that it is a tag.
 
-Grouptags may be used within a [scope](@) to tag various sorts or [knowledge artifacts such as [terms](@), [concepts](@) and the like. One can then say that this tag represents the group of artifacts that are associated with that tag. This may be used for different purposes. One example is to tag every term that is part of a [pattern](@) with a pattern-specific tag. Grouptags typically satisfy the regex `#[a-z0-9_-]+` and is often preceded by the `#` character to designate that it is a tag.
+Grouptags may be used within a [scope](@) to tag various sorts or [semantic units](@) such as [terms](@), [concepts](@) and the like. One can then say that this tag represents the group of artifacts that are associated with that tag. This may be used for different purposes. One example is to tag every term that is part of a [pattern](@) with a pattern-specific tag. Grouptags typically satisfy the regex `#[a-z0-9_-]+` and is often preceded by the `#` character to designate that it is a tag.
 
 Versiontags are used to identify a specific version of the [terminology](@) of the [scope](@) within which the versiontag lives. It may have various forms, and would typically be chosen such that it comes in handy with the tools that the [terms community](@) has decided to use to curate that [scope](@).