Merge pull request #750 from mandy-chessell/dev-dojo

Add samplingMethod property to SampleData relationship

site/docs/services/omvs/glossary-workflow/harvested-glossary.md

@@ -11,4 +11,3 @@ In the example below, the team working on a new sustainability initiative have a
 
 The harvested style of glossary helps teams that do not have the time/resources to create their own glossary terms.
 
---8<-- "snippets/abbr.md"

site/docs/services/omvs/glossary-workflow/multi-level-glossaries.md

@@ -14,7 +14,3 @@ Whether the term is accepted or not, the originating team is free to continue to
 
 In this example, the company glossary’s content is controlled.   All editing of terms happens in the division glossaries.   There is little support to reconcile differences in the definition of a term across the divisions.
 
-
-
-
---8<-- "snippets/abbr.md"

site/docs/services/omvs/glossary-workflow/open-contribution-glossary.md

@@ -11,4 +11,3 @@ The contributions are batched into small updates - for example, providing change
 
 This style of glossary allows an organization to draw on the expertise from across its teams and build the glossary in an evolutionary manner.
 
---8<-- "snippets/abbr.md"

site/docs/services/omvs/glossary-workflow/overview.md

@@ -117,8 +117,6 @@ The rolling staging glossary pattern of operation is where an editing glossary i
 
 The patterns above show how copies of terms are linked and managed throughout the update process.  While a specific term is under review it may be helpful to identify where it is in the review process.
 
-## ControlledGlossaryTerm entity
-
 The [*ControlledGlossaryTerm*](/types/3/0385-Controlled-Glossary-Development) extends the standard [GlossaryTerm](/types/3/0330-Terms) with additional valid [instance statuses](/concepts/instance-status) for supporting a complex development lifecycle.  The statuses are:
 
 * DRAFT      - The term is incomplete.
@@ -132,7 +130,7 @@ The [*ControlledGlossaryTerm*](/types/3/0385-Controlled-Glossary-Development) ex
 
 These status values can be thought of as the system-defined statuses.  It is possible to replace, or extend these statuses using the `userDefinedStatus` attribute that can be controlled through the use of [valid metadata values](/guides/planning/valid-metadata-values/overview).
 
-## Relationship statuses
+### Relationship statuses
 
 Similarly, the relationship between glossary terms have a status that can also be used to show where the relationship is in the review process.
 

site/docs/services/omvs/glossary-workflow/release-controlled-glossary.md

@@ -8,5 +8,3 @@ A released-controlled glossary is one where changes to the glossary terms are ma
 ![Release-controlled glossary](release-controlled-glossary.svg)
 
 
-
---8<-- "snippets/abbr.md"

site/docs/types/3/0330-Terms.md

@@ -21,7 +21,16 @@ Model 0330 shows the glossary term.
 
 *TermCategorization* is a relationship used to organize terms into categories (like organizing files into folders on your disk).  A term may be linked with many categories and a category may have many terms linked to it.  This relationship may connect terms and categories both in the same glossary and in different glossaries.
 
-## 
+## TermRelationshipStatus enumeration
+
+The *TermRelationshipStatus* defines how reliable the relationship is between two glossary terms:
+
+* DRAFT means the relationship is under development.
+* ACTIVE means the relationship is validated and in use.
+* DEPRECATED means the the relationship is being phased out.
+* OBSOLETE means that the relationship should not be used anymore.
+* OTHER means that the status is not one of the statuses listed above.  The description field can be used to add more details.
+
 ## LibraryTermReference relationship
 
 *LibraryTermReference* provides reference information for how this term corresponds to a term in an external glossary.