You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
RFC 4918 registers all the headers of RFC 2518 (which it updates), except for one (Status-URI, just added here: a58dff3). currently, there is no way to properly represent this dependency, so that one spec can say that it updates another, and then overwrites whatever also has been specified in the updated spec.
This might get as complicated as distinguishing between "obsoleting" and "updating", so fixing this issue probably is not going to be trivial.
The text was updated successfully, but these errors were encountered:
generally speaking, these kinds of dependencies maybe should better be described externally. at least until there's a clear requirement for the kinds of dependencies that need to be describable.
RFC 4918 registers all the headers of RFC 2518 (which it updates), except for one (Status-URI, just added here: a58dff3). currently, there is no way to properly represent this dependency, so that one spec can say that it updates another, and then overwrites whatever also has been specified in the updated spec.
This might get as complicated as distinguishing between "obsoleting" and "updating", so fixing this issue probably is not going to be trivial.
The text was updated successfully, but these errors were encountered: