- From: Zoltan Kis via GitHub <sysbot+gh@w3.org>
- Date: Thu, 20 Aug 2015 08:09:04 +0000
- To: public-web-nfc@w3.org
In our case (NFC) we may include white lists/patterns or black lists/pattern in the (meta)content, but it's easily forgeable by native clients. You said earlier that's OK since we are only concerned about preventing web pages from forging these, which we can achieve. Summarizing the discussion, can we say that 1. same origin read/write access doesn't need prompting 2. empty tags (TNF=0) can be written without prompt 3. cross-origin access (reading from different origin and writing to different origin) is determined by a white list/pattern which is written to the content [*]. [*] for this we have 2 alternate designs, one is using a special Web NFC record and another one using the ID field of each record. This will be outlined later, but first let's agree on what we do. -- GitHub Notif of comment by zolkis See https://github.com/w3c/web-nfc/issues/3#issuecomment-132926810
Received on Thursday, 20 August 2015 08:09:12 UTC