Skip to content

Semantics organisation #368

Description

@mnot

I find that I struggle with the current organisation of Semantics every time I open it. When you're looking for how a given mechanism (e.g., conneg, partial content) works, it's very confusing to have to bounce between parts of s 6, s 8, s 10 and sometimes s 9.

I think the document would read far more easily and logically (especially in the text-only rendering) if we added four new top-level sections, with the content from the listed sections inserted (likely with some rearrangement):

  • Partial Content
    • 8.3 Range
    • 6.3.4 Content-Range
    • 6.3.5 Media Type multipart/bytesranges
    • 10.4.1 Accept-Ranges
  • Content Negotiation
    • 6.4 Content Negotation
    • 8.4 Negotiation
    • 6.2.1 Content-Type
    • 6.2.2 Content-Encoding
    • 6.2.3 Content-Language
  • Conditional Requests
    • 8.2 Preconditions
    • 10.2 Validators
  • Authentication
    • 10.3 Authentication Challenges
    • 8.5 Authentication Credentials

I haven't suggested moving the status codes, as that would be more disruptive, and I think there isn't much value in doing so.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions