The 44 controls / TS38

TS38 · URL spaces

Host, case and trailing-slash variants converge on one rule.

Protocol wording · 0.1.0-draft.28 · Documentation view; no website assessment.

Control rule version : 0.1.0-draft.19

Reading guide: start with applicability and required evidence, then read expectations together with their limitations. Understand C, NC, NT and NA outcomes · Prepare a dossier

Expectations and evidence

Required inputs (protocol identifiers)
http, html, sitemap, crawl, intent
When it applies
Host, case and slash variants of resources declared equivalent.
How to check
Replay www/non-www, HTTP/HTTPS, relevant case and trailing-slash variants on sample routes; compare redirect, canonical, sitemap and links.
Expectation
Every tested variant follows the declared rule; redirects, canonicals, sitemaps and links agree without merging distinct resources.
Evidence to retain
One stable final URL per resource, no chain and consistent internal signals.
Non-applicability
No relevant variant after an explicit inventory.
Limitations
Case can be significant depending on the server and application; the rule must be tested, not assumed.
Outcome clarification
C requires all expectations across the declared scope. NC requires evidenced contradiction; otherwise NT. NA requires evidence of non-applicability.
Reference scope
Technical reference; the TSEP acceptance rule remains an editorial proposal.

Atomic rules

This control is documented in the protocol. This version does not yet attach executable atomic rules to it.

Control references