New version of the Web NFC specification and the Security and Privacy document.

[zolkis]

Algorithms extended and reworked.
Changed data representation.
New security policies.
Use watches instead of events.
Fixed terminology related issues.
Renamed send() to pushMessage().
Added timeout to push options.
Issues addressed: #2, #3, #22, #26, #28, #30, #31, #32, #33, #35, #36, #38, #39, #40.
Also,
Fixed #4: use wording from [powerful features].
Fixed #29: use "in parallel" instead on "asynchronously".
Fixed #34: add example for sending data to NFC peer.
Fixed #45: add cancelPush() method.
Also, added steps on what happens with watches and push messages when focus is switched to another browsing context.

[mrj]

Should NFCDeviceType be changed to NFCPushTarget?

[zolkis]

We went back and forth between these two names. Perhaps NFCPushTarget is more correct.

[zolkis]

Will make a new commit in this PR to fix it.

[zolkis]

It seems that I have already done that and have already forgotten it :). Perhaps the comment referred to removed code (draft.idl).

[mrj]

Yes, sorry, I thought draft.idl was the latest because it has the latest modification date.

[anssiko]

See also the HTML diff to the latest published version.

[kenchris]

ok lgtm

[anssiko]

Thank you @zolkis and @kenchris. This is a significant update that addresses the open issues. I will merge this now. Couple of comments that can be addressed later:

• In "The pushMessage algorithm", "NFCPushOptions dictionary", and "The watch() method" sections, options is undefined. You want to "Let options be ..."
• The pushMessage algorithm is rather long (by design). If parts of it could be factored out, that might help with readability. This is just an editorial comment, however.

[zolkis]

options is undefined. You want to "Let options be ..."

I thought formal parameters from the IDL don't need steps to explain their name binding.

The pushMessage algorithm is rather long (by design)

Since often the algorithm is terminated in the sub-steps, it would be cumbersome to break it out to sub-algorithms, since then it's not clear what is meta-parameter and return values and what really belongs to the algorithm. I tried that slicing e.g. with the security steps, but it became a mess.