- From: Zoltan Kis via GitHub <sysbot+gh@w3.org>
- Date: Thu, 26 Sep 2019 06:17:46 +0000
- To: public-web-nfc@w3.org
> 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. I though the users would just assign `data` to an `NDEFMessage` _object_ and the algo & impl would check if `data` is NDEFMessage (I know that's not trivial, but that's the price), then parse recursively and build the proper byte array by implementation. You may be right that we might want to explicitly clarify the intent by adding a new member to `NDEFRecord`, e.g. a boolean meaning "treat payload as NDEFMessage", now we need a good name for that. -- GitHub Notification of comment by zolkis Please view or discuss this issue at https://github.com/w3c/web-nfc/issues/357#issuecomment-535355650 using your GitHub account
Received on Thursday, 26 September 2019 06:17:47 UTC