w3c/presentation-api

* Update references to the latest Permissions API
* Link to the TR version of the WebRTC API
* Fix nfc-forum.org certificate warning by downgrade

* First round of edits

* Finish edits

* Tidy

* Address @anssiko comment

* Further editing

* Clarify use of trademarks in spec.

* Allow termination via connections in a connecting state.

* Tidy

The charter of the Second Screen WG is explicit that the group will use the
W3C Software and Document License for all its deliverable:
http://www.w3.org/2014/secondscreen/charter-2016.html#licensing

Now, that seems to have fallen through the cracks until now as drafts have
actually been published under the more restrictive W3C Document License.

…426)

The allow-presentation sandbox attribute value and related flags have been
integrated in HTML5.2, so the temporary section we had in the Presentation API
can now be dropped.

I kept things simple for now, referencing HTML 5.2 only for that flag, keeping
references to HTML 5.1 otherwise. I propose to check whether we can switch all
references to HTML 5.2 when we get ready to publish the spec as Proposed
Recommendation.

Relaxed CR exit criteria to match known implementation plans

See related discussion in: #406

Adds preview and diff links to pull requests.

https://github.com/tobie/pr-preview/

* Add notes around sandboxing flags in receiving browsing context.

* Tidy

The Status of This Document section also highlights the restriction to secure
contexts.

)

* Add modal and top-level flags to receiving browsing context

* Attach [SecureContext] to IDL.

* Fix http:// URLs

* tidy

* Fix typo

Fix WebIDL references

* Added change log section with list of changes since first CR

This commit also updates the Status of This Document section to highlight main
changes and reference the change log.

* Fixed links to issues on GitHub in Change log

Followup to close out Issue #396: Migrate HTML 5.0 references to HTML 5.1.

* Issue #396: Migrate HTML 5.0 references to HTML 5.1

This commit updates all HTML 5.0 references to HTML 5.1.

To help assess references stability (issue #295), the spec now also directly
references the WebIDL Level 1 Recommendation, pointing out that NotAllowedError
is defined in WebIDL Level 2. References to the WHATWG version of HTML for
"current settings object" and "relevant settings object" now target HMTL 5.1
as well.

Other changes introduced in this commit:
- Correct nesting of <a>, <code>, <dfn> to make sure code definitions get
styled in red as expected
- ReSpec now automatically supports aliases such as "start()" for method, so
dropped the now redundant alias definitions.
- Turned references incorrectly marked as informative into normative references
(UUID, cookies, RFCs).

* HTML 5.1 terms moved to a list, () dropped from method references

Addressing @mfoltzgoogle comments on previous commit, the list of HTML 5.1
terms are now defined in a list, sorted by alphabetic order.

Parentheses next to method names now dropped throughout the specification.

* Issue 397 - Make sur all IDL terms have <dfn> in prose

Done:

- All IDL terms have <dfn> in prose
- Added constructor logic for custom Events
- Added missing reference to Web Messaging spec
- Linked terms to definition whenever possible
- Improved support for linking to methods with parentheses: "start()"
- Occurrences of "presentation" that should link to "controlling browsing context" now effectively link to it
- Occurrences of "Presentation" that should link to the interface definition now effectively link to it

Notes:

- No way to define an idiom "presentation" and an interface "Presentation" using ReSpec, so "presentation" (as an idiom) links are hardcoded
- Some definitions are not real definitions (e.g. BinaryType is merely defined as the type of the binaryType attribute), but they do not seem to warrant proper definitions.
- Description of custom events constructors could be turned into real algorithms but that seems straightforward enough not to require crisper language.

* Tidy

…nt (#392)

* Issue #387: Monitoring algo now takes pending request to start into account

Main changes:

- Prose similar to that used in the Web Bluetooth spec used for the garbage
collection note for the "presentation display availability" to clarify the
intent. We may want to adjust this text in #391.
- Notion of "presentation availability promise" dropped. That promise is now
referenced in `getAvailability` as "an unsettled Promise from a previous call
to `getAvailability` on `presentationRequest`". This avoids having to be
explicit about garbage collection rules.
- Step that instructs the UA to run the monitoring algorithm no longer runs
"in parallel" (see #381)
- Note added next to that step to clarify that the monitoring algorithm needs
to run again even if it is still running
- The monitoring algorithm now starts by making a shallow copy of the "set of
presentation availability objects" which gets completed with the right tuple if
there is a pending call to `start` (note there can be at most one such pending
call per controlling browsing context)
- Steps that update the `value` property adjusted to set the value directly for
`PresentationAvailability` objects that have not yet been exposed to ECMAScript
object. This is triggered by the following (new) problem: the `getAvailibility`
promise gets resolved with a `PresentationAvailability` object as soon as the
monitoring algorithm is done running, but the monitoring algorithm "queued a
task" to update the `value` property of `PresentationAvailability` objects. The
`value` property of the returned `PresentationAvailability` object would always
have been the initial value (`false` in most cases), even if the monitoring
algorithm had found an available display. Also, we probably do not want to fire
`change` events for properties that JS code has not yet been given any chance
to read. Here as well, we may want to adjust this text in #391.
- The initial `value` of newly created `PresentationAvailability` objects is
now always `false`. There should be no need to set it to `true` given that the
monitoring algorithm refreshes that value right after that (and given the
previous fix).
- I added a note next to the monitoring algorithm to clarify that a user agent
may interrupt and re-run the algorithm to group requests, which seems like a
possible optimization.

* Issue #387: Use availabilitySet in the monitoring algorithm

The variable is obviously useless if it is not referenced. This should have
been part of previous commit.

* Issue #387: drop "exposed to JS" and allow monitoring aggregation

This commit drops the fuzzy "exposed to ECMAScript" wording in the monitoring
algorithm, and replaces it with a more common "initialized" concept. The notion
is clarified in an editorial note next to the step that uses it.

The editorial note that follows the monitoring algorithm was also complete to
mention that user agents may aggregate monitoring activities across browsing
contexts.

* Issue #387: Update notes with @mfoltzgoogle suggestions