Skip to content

Commit

Permalink
Mention tradeoffs inherent in building designed-for-purpose APIs. (#440)
Browse files Browse the repository at this point in the history
  • Loading branch information
jyasskin authored Oct 23, 2024
1 parent 014831f commit f387e3c
Showing 1 changed file with 3 additions and 1 deletion.
4 changes: 3 additions & 1 deletion index.html
Original file line number Diff line number Diff line change
Expand Up @@ -1912,7 +1912,9 @@

Features that are designed-for-purpose facilitate these principles by providing functionality that is only or primarily
useful for a particular purpose. Designed-for-purpose features make it easier to explain the purpose to people, and may
also limit the feasible secondary uses of data.
also limit the feasible secondary uses of data. When building a designed-for-purpose feature,
<a data-cite="design-principles#high-level-low-level">consider tradeoffs between high and low-level
APIs</a>.

[=Controlled de-identified data=] may be used for additional purposes in ways that are compatible with the specified
purpose.
Expand Down

0 comments on commit f387e3c

Please sign in to comment.