This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
check to see if all "required" uses are meant to be RFC2119 uses: Enum: change all "required" to "REQUIRED" change all "not required" to "NOT REQUIRED" Eventing: change all "required" to "REQUIRED" Frag: change all "required" to "REQUIRED" Mex: change all "required" to "REQUIRED" Transfer: change all "required" to "REQUIRED" except for: -- For example, the representations required by Create or Put can differ from the representation returned by Get, depending on the semantic requirements of the service. -- s/required/needed/ -- In some cases, the initial representation MAY constitute the representation of a logical constructor for the resource and can thus differ structurally from the representation returned by Get or the one required by Put. -- s/required/needed/
check to see if all "required" uses are meant to be RFC2119 uses: Enum: change all "required" to "REQUIRED" change all "not required" to "NOT REQUIRED" Eventing: change all "required" to "REQUIRED" Frag: change all "required" to "REQUIRED" Mex: change all "required" to "REQUIRED" Transfer: change all "required" to "REQUIRED" except for: -- For example, the representations required by Create or Put can differ from the representation returned by Get, depending on the semantic requirements of the service. -- s/required/used/ -- In some cases, the initial representation MAY constitute the representation of a logical constructor for the resource and can thus differ structurally from the representation returned by Get or the one required by Put. -- s/required/used/
In security sections: s/required/needed/
Reesolved as proposed in comment Nr 1 and 2
Please make my changes