Skip to content

Commit 4dbf569

Browse files
committed
Explain terms types
1 parent 409bffc commit 4dbf569

File tree

1 file changed

+54
-0
lines changed

1 file changed

+54
-0
lines changed
Lines changed: 54 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,54 @@
1+
---
2+
title: "Understanding terms types"
3+
linkTitle: Terms types
4+
weight: 1
5+
---
6+
7+
# Terms types: a foundation of a consistent archive
8+
9+
## What are terms types?
10+
11+
Terms types are standardized categories that classify the different kinds of terms and conditions documents, serving as a common language for organizing and comparing terms across services.
12+
13+
## Why standardized terms types are needed
14+
15+
Services often use different names for the same type of terms. For instance, "Terms and Conditions" might be called "Terms of Use" or "Terms of Service" by different services. This kind of inconsistency creates significant challenges in finding and comparing similar terms documents across different services. It also makes it difficult to maintain a consistent structure in all collections, and to ensure a comprehensive coverage of all legal documents.
16+
17+
Without standardization, activists, journalists, researchers, lawmakers and regulators struggle to track changes, conduct comparative analyses, and maintain organized collections of terms. Standardized terms types serve as a common language that bridges these naming variations, enabling more efficient organization, improved searchability, and clearer understanding of the legal landscape across different services.
18+
19+
## How Open Terms Archive handles terms types
20+
21+
Open Terms Archive maintains an [official list of terms types](https://github.com/OpenTermsArchive/terms-types) that serves as a reference for all collections. This standardization is used for automated validation of service declarations, ensuring that all terms are properly categorized.
22+
23+
When you encounter a validation error related to terms type, it looks like this:
24+
25+
```shell
26+
1) Service declarations validation
27+
<service_name>
28+
valid declaration schema:
29+
Error:
30+
31+
data/terms must be equal to one of the allowed values (in entire file)
32+
```
33+
34+
This means the terms type you're trying to use isn't in the official list of supported types.
35+
36+
## When a new terms type needs to be suggested
37+
38+
Situations may arise where a terms type used by a service is not yet included in the official list. Such situations typically occur when:
39+
40+
- A document is specific to a domain that is not yet covered by Open Terms Archive collections
41+
- A service uses a unique name for their document
42+
- A new type of document emerges in the digital landscape
43+
- A service combines multiple documents in an unusual way
44+
45+
## What are the benefits of contributing new terms types
46+
47+
When a new terms type is suggested to the Open Terms Archive community and accepted, it contributes to a larger ecosystem and has the following benefits:
48+
49+
- It makes the new terms type available to all collections
50+
- It eliminates the need for custom solutions or forks for validating terms types
51+
- It helps build a more comprehensive shared vocabulary
52+
- It enables better comparison and analysis of terms across services
53+
54+
To contribute a new terms type, follow the [contribution process](https://github.com/OpenTermsArchive/terms-types/blob/main/CONTRIBUTING.md#add-new-terms-types) in the `terms-types` repository.

0 commit comments

Comments
 (0)