Re-structure profiles sections - closes #214 and closes #248 #260
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is a proposed re-structuring of the profiles sections, based on the discussion in #214.
Overview of changes:
After these changes, at a high level the specification looks like:
If we land these changes then we'll also need to update the Introduction and Abstract to reflect renamed sections. I didn't do that in this PR because it's already large enough!
I also think we should consider renaming "HTTP Baseline Profile" to "HTTP Basic Profile", since the name "Baseline Profile" may now be confused with "Common Constraints".
My comments in #214 (comment) regarding the Information Model and Message Format sections are left unresolved for now.
Note: This diff is hard to read because it touches so many lines, but it's slightly easier if you just view the second commit (the first one is pulled in from #249 and may be re-based out if that lands first).
Edit: I've renamed HTTP Profile Common Constraints to Common Constraints for simplicity, since all the profiles are currently HTTP profiles. We can re-visit if other profiles are added in the future.
Preview | Diff