fix(guidelines): remove consumer-facing rules that have been included…

… in API Portal (#62)
otto-de · Feb 5, 2024 · d3a84df · d3a84df
1 parent 50ee093
commit d3a84df
Show file tree

Hide file tree

Showing 7 changed files with 1 addition and 46 deletions.
diff --git a/.../global/compatibility/deprecation/rules/must-not-start-using-deprecated-apis.md b/.../global/compatibility/deprecation/rules/must-not-start-using-deprecated-apis.md
diff --git a/api-guidelines/global/compatibility/preview/README.md b/api-guidelines/global/compatibility/preview/README.md
diff --git a/api-guidelines/global/compatibility/preview/rules/must-not-rely-on-preview.md b/api-guidelines/global/compatibility/preview/rules/must-not-rely-on-preview.md
diff --git a/...st/compatibility/client-behavior/rules/must-accept-undocumented-status-codes.md b/...st/compatibility/client-behavior/rules/must-accept-undocumented-status-codes.md
diff --git a/api-guidelines/rest/compatibility/client-behavior/rules/must-follow-redirection.md b/api-guidelines/rest/compatibility/client-behavior/rules/must-follow-redirection.md
diff --git a/...ion-of-http-apis/rules/should-add-deprecation-and-sunset-header-to-responses.md b/...ion-of-http-apis/rules/should-add-deprecation-and-sunset-header-to-responses.md
@@ -6,7 +6,7 @@ id: R000069
 
 During the deprecation phase, the API provider should add a `Deprecation` header (see [draft: RFC Deprecation HTTP Header](https://tools.ietf.org/html/draft-dalal-deprecation-header)) and - if also planned - a `Sunset` header (see [RFC 8594](https://tools.ietf.org/html/rfc8594#section-3)) to each response affected by a deprecated element (see [MUST reflect deprecation in API specifications](../../../../global/compatibility/deprecation/rules/must-reflect-deprecation-in-api-specifications.md)).
 
-The `Deprecation` header can either be set to `true` when a feature is disabled, or it can carry a deprecation timestamp at which a replacement is made available and consumers are no longer allowed to use the feature (see [MUST NOT start using deprecated APIs](../../../../global/compatibility/deprecation/rules/must-not-start-using-deprecated-apis.md)).
+The `Deprecation` header can either be set to `true` when a feature is disabled, or it can carry a deprecation timestamp at which a replacement is made available and consumers are no longer allowed to use the feature.
 The optional `Sunset` timestamp indicates when consumers have to stop using a feature at the latest.
 The sunset timestamp should always offer an appropriate time interval for switching to a replacement feature.
 

diff --git a/...headers/rules/should-honor-available-etag-header-on-subsequent-modifications.md b/...headers/rules/should-honor-available-etag-header-on-subsequent-modifications.md