From f2f26419234dfbf53905cedb0c57263a29b16a8f Mon Sep 17 00:00:00 2001 From: Jeffrey Yasskin Date: Tue, 17 Dec 2024 15:23:57 -0800 Subject: [PATCH] Add a section about looking for guidance in other specs. (#542) * Add a section about looking for guidance in other specs. * Take Martin's rewording. Co-authored-by: Martin Thomson * Add #using-http as guidance from a feature specification. Co-authored-by: Martin Thomson * Add guidance to talk to the relevant community. --------- Co-authored-by: Martin Thomson --- index.bs | 26 ++++++++++++++++++++++++++ 1 file changed, 26 insertions(+) diff --git a/index.bs b/index.bs index 3dcc0462..918b1839 100644 --- a/index.bs +++ b/index.bs @@ -545,6 +545,32 @@ i.e. consistency within CSS. There is also a separate section on naming consistency. +

Follow guidance from feature specifications

+ +When using a feature, +follow guidance in the specification for that feature. + +Specifications for features +that will be used by other specifications +should include guidance for using those features. +This ensures that the feature is used correctly +and consistently +throughout the platform. + +An incomplete list of such guidance follows: + +* [[encoding#specification-hooks|Encoding]] +* [[fetch#fetch-elsewhere|Fetch]] +* [[hr-time#sec-tools|Time]] +* [[url#url-apis-elsewhere|URLs]] +* [[#using-http]] + +Consult with the relevant community +when using their specification. +This informs that community about new usage +and creates opportunities for improvements +to both the using and used specifications. +

New features should be detectable

Provide a way for authors to programmatically detect