- From: Jeffrey Yasskin via GitHub <sysbot+gh@w3.org>
- Date: Mon, 17 Aug 2015 17:25:26 +0000
- To: public-web-nfc@w3.org
Step 6 says "set _scope_ to the DOMString describing the document base URL." That makes _scope_ a local variable in the algorithm, but it's not used after that. Did you mean to set `message.scope` to that DOMString? But even then, `message.scope` isn't used in the rest of the algorithm either. If you intend to write `message.scope` into the "additional Web NFC record", you need to say that, possibly by defining an "Assemble an NDEF message" algorithm. Is "the receiving side" the tag or peer in steps 10–12? What's a "client"? It looks like you may be talking about later web sites that read the tag/peer, but in #2, @sicking is worried about the effect of writing data to the NFC tag/peer, not just the effect on later websites. -- GitHub Notif of comment by jyasskin See https://github.com/w3c/web-nfc/issues/32#issuecomment-131896224
Received on Monday, 17 August 2015 17:25:28 UTC