Re: [web-nfc] Define NDEFMessage's, NDEFRecord's and NDEFReadingEvent's constructors normatively (#622)

> Something similar would work for NDEFMessage, but it would also be good to specify what "add NDEFRecord to NDEFMessage" means in Add ndef to output.

Note that `output` (internal binary representation to be used by lower layers) is not the same as `NDEFMessage` (which is a developer input to generate `output`), i.e. we don't make the promise to update back `NDEFMessage` as `output` is being generated. I think for the methods of the spec it should be enough the specify how to generate `output`, rather than exacting the steps to make `output` presentable as `NDEFMessage`, as this was not an intent and it's quite a mine field. If that is needed, let's handle it separately, since it would require revamping a lot of algorithms. Needs more discussion.

-- 
GitHub Notification of comment by zolkis
Please view or discuss this issue at https://github.com/w3c/web-nfc/issues/622#issuecomment-970397989 using your GitHub account


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config

Received on Tuesday, 16 November 2021 15:40:35 UTC