- From: Kenneth Rohde Christiansen via GitHub <sysbot+gh@w3.org>
- Date: Wed, 04 Sep 2019 14:08:41 +0000
- To: public-web-nfc@w3.org
> * should payload `id` (per record) be mandatory (to write) in Web NFC I will say no. It is not mandatory by NFC specs and existing solutions might not be using it today nor waning to add it when moving to Web NFC > * should we call it `payload id` instead of `message id` ? It is more like a record ID though and a record might have it and no payload. NFC specs call it message id, so we might at least need to clarify that in the spec, even if we call it record id. > If the idea is that in a message every `id` is the same, then yes, we can use `message id`, but that would be an extra constraint over NDEF. I don't see such a constrain, but in chunked records, it is only present in the first one (illegal to have in the other chunks). Can we fix this afterward? Like file issue, then discuss and then do global rename -- GitHub Notification of comment by kenchris Please view or discuss this issue at https://github.com/w3c/web-nfc/pull/340#issuecomment-527917467 using your GitHub account
Received on Wednesday, 4 September 2019 14:08:42 UTC