- From: Han Leon via GitHub <sysbot+gh@w3.org>
- Date: Thu, 26 Sep 2019 02:56:02 +0000
- To: public-web-nfc@w3.org
About `toRecords`(), yeah I agree we need to make our spec clarify that it's only for TNF=1 "Sp" and TNF=4. About writing, > IMHO the API can already express defining a message tree by simply assigning data of NDEFRecord to an NDEFMessage object for instance. Implementation can do that but it would be quite hard for users to prepare a properly formatted raw bytes (NDEFRecord#data) from which we can make out a valid NDEFMessage. We can also consider adding a new member "`NDEFMessageInit payloadMessage;`" into `NDEFRecordInit`, so users can construct the tree easily, but this makes things complex, Web IDL with recursive things seems so hard to understand, in addition we also need to point out that `payloadMessage` is only for "Sp" and external type records... I'm unsure whether it's worth doing that, seems more considerations are needed. -- GitHub Notification of comment by leonhsl Please view or discuss this issue at https://github.com/w3c/web-nfc/issues/357#issuecomment-535309887 using your GitHub account
Received on Thursday, 26 September 2019 02:56:04 UTC