Conversation
|
Assuming I'm reading the tags right, you mark this as a "defined term," but just drop the link to the definition. I don't feel like that helps, since you now have a dangling defined term. |
|
@MikeBishop as I said in #311, this is the most minimal approach. To do more, I think we need to rename 4. Header and Trailer Fields to something like "Messages", and expand its introduction accordingly. Any thoughts about that? |
|
It seems like most of the content you'd want for defining a message is already there in 2.1:
Rearranging text a little to put that definition (and make it a definition, rather than "a common abstraction") by the introduction of the term "message" seems like it would work without having to rearchitect Section 4. |
|
@MikeBishop |
httpwg/http-core#343 • Adjust multiple Content-Length handling httpwg/http-core#346 • Rework invalidation definition • Roy's suggestions • grammar httpwg/http-core#353 • Make text body narrower for readability httpwg/http-core#354 • Remove H1-specific connection-related requirements • Roy's feedback httpwg/http-core#316 • map request target to target URI/resource • fix one leftover of "effective request URI" • Adjust anchor names • push note into <aside> and move index entry • sort change log • restore indentation • re-add missing closing brackets • fix change log section title • fix change log • remove semantics HTML too • removing HTML from PR httpwg/http-core#344 • Don't rely on the HTTP/1.1 Messaging specification to define "message" httpwg/http-core#357 • Present If-[none]-Match evaluation more clearly httpwg/http-core#72 • Semantics of If-Match httpwg/http-core#345 • remove ref to close option • remove HTML from PR
Fixes #311