- From: Zoltan Kis via GitHub <sysbot+gh@w3.org>
- Date: Fri, 11 Oct 2019 15:12:12 +0000
- To: public-web-nfc@w3.org
FWIW the "json" part is artificial, created by us in the Web NFC. Otherwise both `"opaque" and "json" map to Media type records that have a MIME type and we could just merge them to be "media" (replacing "json" and "opaque"). The simplicity of this is tempting. I am asking myself, given that we can provide examples for good patterns, is the "json" use case so relevant that we want to keep it as a separate thing (for people coming from NFC side, it would be easier if we simply handled it as a media type). Maybe "json" and "opaque" add enough semantics that they are useful, but I don't see people would have any problem invoking `JSON.parse()` and `JSON.stringify()` if examples/patterns would be given. -- GitHub Notification of comment by zolkis Please view or discuss this issue at https://github.com/w3c/web-nfc/issues/366#issuecomment-541105101 using your GitHub account
Received on Friday, 11 October 2019 15:12:13 UTC