Re: [web-nfc] URL objects

That is well understood (we also have explored that option in the 
past), but we break up the original NFC records anyway (think about 
smart poster), and present information to web pages which is basically
 mapped anyway. Therefore it is more straightforward (for clients) to 
use a single mapping, and it's interesting only for the read use case 
- writing does not change. Even the read API does not change, only the
 values of ```type```. So let me edit the spec to record the new API, 
and I will leave a note about this. Let's wait for implementation 
feedback and then choose one way.

-- 
GitHub Notif of comment by zolkis
See https://github.com/w3c/web-nfc/issues/26#issuecomment-130196388

Received on Wednesday, 12 August 2015 07:18:37 UTC