Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update use_cases.md #466

Merged
merged 6 commits into from
Nov 8, 2023
Merged

Update use_cases.md #466

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
6 commits
Select commit Hold shift + click to select a range
ded61aa
Update use_cases.md
greggish Aug 30, 2023
65f6f2a
Update variations_interoperability.md
greggish Sep 14, 2023
abb3526
Update use_cases.md
dan-odsc Nov 7, 2023
706cb3c
Replaced absolute link with relative to ensure it plays nicely with b…
Nov 8, 2023
679ad5b
Fix merge conflict
Nov 8, 2023
8227581
Fix merge conflict
Nov 8, 2023
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions docs/hsds/use_cases.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -5,14 +5,14 @@ Use Cases
This page is *non-normative*, which means that it doesn't form part of the standard; if there is any ambiguity, the standard takes precedence. This page may be updated at any time in response to community demand.
```

Open Referral's agenda is set by the prerogatives of a set of four types of users:
Open Referral's agenda is shaped by the prerogatives of four types of users:

* help seekers;
* service providers;
* researchers/analysts;
* database administrators.

Read more about each of these personas in [our Types of Use / User Personas documentation](https://docs.openreferral.org/en/latest/initiative/index.html?highlight=types%20of%20use#types-of-use-and-user-personas).
Read more about each of these types of users in [the User Personas documentation](../initiative/index,md#types-of-use-and-user-personas).

In practice, we find that the primary type of user for HSDS and its associated tools are *Database Administrators*. It is still important for us to understand the needs of other types of end users – however we often process this understanding through the lense of Data Administrators to support them directly meeting the needs of end users.

Expand Down
4 changes: 2 additions & 2 deletions docs/hsds/using_profiles.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -12,13 +12,13 @@ To this end, HSDS provides the [Profiles mechanism](profiles) which allows the c

Profiles may do the following:

* extend the HSDS specification by:
* extend HSDS by:
* adding new optional or mandatory fields
* adding new validation rules (including making optional fields 'required')
* adding new structures
* adding new API endpoints to the API specification
* recommending the use of particular value sets such as taxonomies or enumerations.
* overriding or removing parts of the HSDS specification†:
* overriding or removing parts of HSDS†:
* remove fields and their validation rules
* remove entire schemas/Tables/Objects
* remove API endpoints from the API specification
Expand Down
Loading