Move alignment stubs to annex #610
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
There was a problem hiding this comment.
Good idea - we did talk about this, but without the detail. Was your intent to insert this as Appendix A after the linked data stuff (Ch 14)? In which case it needs a h3 header for the appendix title around line 3015. Or were you suggesting we move Ch 14 into an annex as well? I decided that I wasn't sure.....
|
I fixed a couple of headers. For the time-being I left the schema.org and prov-o stubs in the body, and moved the domain alignments to the Annex. But in due course I could see shuflfing the sdo and prov-o into an annex and the others out of the document entirely. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Probably en route out of the rec document -