Original text:
This specification defines the following specialty content identifiers: <del> The target request endpoint. (content-request-target) </del> The signature metadata parameters for this signature. (signature- params) <del> Additional specialty content identifiers MAY be defined and registered in the HTTP Signatures Specialty Content Identifier Registry. (content-registry) </del>  <del> 2.3.1. </del>  <del> The request target endpoint, consisting of the request method and the path and query of the effective request URI, is identified by the "@request-target" identifier. </del>  <del> Its value is canonicalized as follows: </del>  <del> Take the lowercased HTTP method of the message. </del>  <del> Append a space " ". </del>  <del> Append the path and query of the request target of the message, formatted according to the rules defined for the :path pseudo- header in HTTP2, Section 8.1.2.3.  The resulting string is the canonicalized value. </del>  <del> 2.3.1.1. </del>  <del> The following table contains non-normative example HTTP messages and their canonicalized "@request-target" values. </del>  <del> 2.3.2. </del>  HTTP Message Signatures have metadata properties that provide <del> information regarding the signature's generation and/or verification. </del>  The signature parameters specialty content is identified by the "@signature-params" identifier.

Reviewer comments:
This adds several new specialty identifiers for requests and responses to cover the method, authority, scheme, origin, path, query, and status code values of the HTTP message. It also edits the identifier's associated value to remove the verb and the string construction rules and instead align with HTTP Semantics.
NAME I haven't added references in yet but I tried to move the language in the direction you are suggesting. NAME I added the target-uri field we discussed, please review the text.
Responded to comments and updated normalization rules, please re-review.
Folding in this PR to the main document, discussion can continue on specifics of identifiers and their values as needed.

Revised text:
This specification defines the following specialty content identifiers:  The signature metadata parameters for this signature. (signature- params)  <ins> The method used for a request. (content-request-method) </ins>  <ins> The full target URI for a request. (content-target-uri) </ins>  <ins> The authority of the target URI for a request. (content-request- authority) </ins>  <ins> The scheme of the target URI for a request. (content-request- scheme) </ins>  <ins> The request target. (content-request-target) </ins>  <ins> The absolute path portion of the target URI for a request. (content-request-path) </ins>  <ins> The query portion of the target URI for a request. (content- request-query) </ins>  <ins> The parsed query parameters of the target URI for a request. (content-request-query-params) </ins>  <ins> The status code for a response. (content-status-code). </ins>  <ins> Additional specialty content identifiers MAY be defined and registered in the HTTP Signatures Specialty Content Identifier Registry. (content-registry) 2.3.1. </ins> HTTP Message Signatures have metadata properties that provide  <ins> information regarding the signature's generation and/or verification, such as the list of covered content, a timestamp, identifiers for verification key material, and other utilities. </ins> The signature parameters specialty content is identified by the "@signature-params" identifier.