Adds terminology and requirements to spec. #103
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
louaybassbouss
approved these changes
Aug 29, 2018
There was a problem hiding this comment.
Thanks @mfoltzgoogle LGTM. Since the index.html is auto-generated, I only reviewed index.bs
tidoust
reviewed
Aug 30, 2018
|
Merging now - if there are any follow up comments, feel free to add to this thread or open an issue. |
mfoltzgoogle
added a commit
that referenced
this pull request
Sep 21, 2018
Merge PR #103 to gh-pages.
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.
Addresses Issue #99 to complete the introduction, terminology and requirements section (excepting that for Remote Playback API). This is a lightly edited version of the content in requirements.md.
Note: Use the initialize-spec as the base branch for this PR.
Editor's notes:
A best effort was undertaken to leverage Bikeshed's autolinking functionality. Specifically, the Second Screen specs are not in the Bikeshed database, so terms have to be defined in an "anchors" block at the beginning of the document. In that block, I didn't see a way to define shortened forms, e.g. ("controller" for "controlling browsing context"), so they will need to be linked in the upstream spec, or perhaps there's a Bikeshed feature I'm missing.