Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support for updated specification #8

Open
dret opened this issue Feb 16, 2015 · 4 comments
Open

Support for updated specification #8

dret opened this issue Feb 16, 2015 · 4 comments
Assignees

Comments

@dret
Copy link
Owner

dret commented Feb 16, 2015

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.

@dret
Copy link
Owner Author

dret commented Jul 21, 2015

another example: LDP updates "describedby" (originally from POWDER) at http://www.w3.org/TR/ldp/#link-relation-describedby

@dret
Copy link
Owner Author

dret commented Jul 21, 2015

added LDP "describedby" at 0e8e6f2 (currently this results in a duplicate entry in the linkrel list)

@dret
Copy link
Owner Author

dret commented Aug 27, 2015

not perfect, but at least grouping header fields with the same name in one table row: 5e4b0a9

@dret
Copy link
Owner Author

dret commented Mar 23, 2016

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.

@dret dret self-assigned this Dec 8, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant