Editorial changes around exposing NFC standards related text #361
Conversation
…DEF message'. Signed-off-by: Zoltan Kis <zoltan.kis@intel.com>
…eadability. Signed-off-by: Zoltan Kis <zoltan.kis@intel.com>
Signed-off-by: Zoltan Kis <zoltan.kis@intel.com>
Signed-off-by: Zoltan Kis <zoltan.kis@intel.com>
|
Note: since not supported ATM, I kept signature and handover records sections at minimum. |
Signed-off-by: Zoltan Kis <zoltan.kis@intel.com>
index.html
Outdated
| <!-- - - - - - - - - - - - - - - Introduction - - - - - - - - - - - - - - --> | ||
| <section class="informative"> <h2>Introduction</h2> | ||
| <p> | ||
| In general, there are following groups of user scenarios for NFC: |
There was a problem hiding this comment.
in general, you can group the user scenarios of NFC into the following groups:
There was a problem hiding this comment.
I was taught to use passive constructs in articles (and I assume specs) :).
There was a problem hiding this comment.
Maybe then
NFC user scenarios can be grouped as follows:
There was a problem hiding this comment.
BTW I just copied these use cases, so an English proofreading is due for the whole spec.
index.html
Outdated
| </li> | ||
| <li> | ||
| Hold two active devices, e.g. phones or tablets, in close proximity | ||
| in order to push an <a>NDEF message</a> from one device to the other. |
There was a problem hiding this comment.
why say NDEF message here and 'data' above? Maybe we should just say data
index.html
Outdated
| <li>Card emulation | ||
| <ol> | ||
| <li> | ||
| With a secure element: for payments by holding your phone close to a |
index.html
Outdated
| <ol> | ||
| <li> | ||
| With a secure element: for payments by holding your phone close to a | ||
| point-of-sales terminal, instead of swiping a payment card. |
There was a problem hiding this comment.
remove swiping... many cards support contact less as well
index.html
Outdated
| With a secure element: for payments by holding your phone close to a | ||
| point-of-sales terminal, instead of swiping a payment card. | ||
| </li> | ||
| <li>With host card emulation: for allowing use-cases like using a phone |
There was a problem hiding this comment.
Add (HCE) after host card emulation
index.html
Outdated
| </ul> | ||
| </p> | ||
| <p> | ||
| NFC works using magnetic induction, meaning that the reader will emit a |
There was a problem hiding this comment.
reader (active powered device)
index.html
Outdated
| <a>NDEF record</a>s. <dfn>NDEF</dfn> is an abbreviation for NFC Forum | ||
| Data Exchange Format, a lightweight binary message format. NDEF messages | ||
| can be stored on an <a>NFC tag</a> or exchanged between NFC-enabled devices. | ||
| <a>NDEF record</a>s. NDEF messages can be stored on an <a>NFC tag</a> or exchanged between NFC-enabled devices. |
index.html
Outdated
| <section class="informative"> <h3>NDEF compatible tag types</h3> | ||
| <p> | ||
| The NFC Forum has mandated the support of five different tag types to be | ||
| operable with NFC devices. The same is required on operating systems such |
| </p> | ||
| <p> | ||
| Card emulation mode capabilities also depend on the NFC chip in the device. | ||
| For payments, a Secure Element is often needed. |
There was a problem hiding this comment.
describe secure element? or link to something?
There was a problem hiding this comment.
Maybe not in this PR. I haven't found a good public domain definition at first try.
index.html
Outdated
| For payments, a Secure Element is often needed. | ||
| </p> | ||
| <p class="note"> | ||
| This document does not aim supporting all possible use cases of NFC |
index.html
Outdated
| This document does not aim supporting all possible use cases of NFC | ||
| technology, but only a few use cases which are considered relevant to be | ||
| used by web pages in browsers, using the browser security model. |
There was a problem hiding this comment.
Actually we are trying to expand the scope, so maybe we should just remove this note
index.html
Outdated
| perform certain activities between the two devices, such as sending photos | ||
| to the other device, printing to a Bluetooth printer or streaming video to | ||
| a television set. | ||
| Icon records are <a>MIME type record</a>s. Readers SHOULD select one icon |
There was a problem hiding this comment.
No, one icon record. Will specify like that.
index.html
Outdated
| URI record. | ||
| </p> | ||
| <p> | ||
| The action record has <a>NFC Forum local type</a> "`act`" specific to |
There was a problem hiding this comment.
a double space between record and has
index.html
Outdated
| <p> | ||
| The action record has <a>NFC Forum local type</a> "`act`" specific to | ||
| smart poster and the <a>PAYLOAD field</a> contains a single byte. If its | ||
| value is `0`, it means "do the action" (depending on type, this might mean |
There was a problem hiding this comment.
maybe add a table for showing the values?
There was a problem hiding this comment.
Only 3 valid values... maybe later. Then I'd need to copy the table from the NDEF spec, something I didn't want to do.
There was a problem hiding this comment.
You can redo it from your own text
There was a problem hiding this comment.
That table would be incomplete compared to the NDEF spec, thus it would be confusing. Implementations are only interested in these 3 values. I can also remove this section (just say that it denotes an action specified in the NDEF spec), since Web NFC actually does not act on Sp, it leaves that to apps - so it's the app developers who should read the NDEF spec for Sp.
There was a problem hiding this comment.
OK - I am not even sure Sp records are not hijacked by the underlying platform. I think on Android they are not, but need to check.
There was a problem hiding this comment.
Made a table and added more verbose comments that didn't fit the table.
index.html
Outdated
| <dfn>NDEF Signature</dfn> is defined [[NDEF-SIGNATURE]]. | ||
| Its <a>TYPE field</a> contains "`Sig`" (`0x53`, `0x69`, `0x67`) and its | ||
| <a>PAYLOAD field</a> contains version, signature and a certificate chain. | ||
| Web NFC does not support this at the moment. |
There was a problem hiding this comment.
Well we can read it as toArrayBuffer no?
There was a problem hiding this comment.
I don't know if we read it at all, or should we?
There was a problem hiding this comment.
I think we cannot go for full support now, and we'd need to spec it properly. Out of scope for this release.
There was a problem hiding this comment.
I would say that we should read all and allow to get bytes.. that offers a way for devs to work around us not having specced everything
There was a problem hiding this comment.
This would be a new feature for the current spec and needs to be discussed in its own issue. It's definitely not in the scope for this PR. I can remove all the sig record related text if that makes it better.
There was a problem hiding this comment.
No it's fine, but please file an issue
There was a problem hiding this comment.
OK, I will. I just thought this is not properly spec'd (just basic information) and maybe would be better to skip it now and add it later. But let's leave this text in for now and we'll work on it anyway soon.
There was a problem hiding this comment.
Added a comment and reference to the issue.
index.html
Outdated
| The negotiated communication carrier would then be used (separately) to | ||
| perform certain activities between the two devices, such as sending photos | ||
| to the other device, printing to a Bluetooth printer or streaming video to | ||
| a television set. Web NFC does not support this at the moment. |
There was a problem hiding this comment.
I rather we add an issue and create a "note" or "issue" or what it is called in respec, linking to that
There was a problem hiding this comment.
IMV it's orthogonal if we have or don't have an issue for the missing feature. But we could do it (later), it would be nice.
There was a problem hiding this comment.
Added a comment and reference to the issue.
| application specified data types and are defined in [[[NFC-RTD]]]. | ||
| </p> | ||
| <p> | ||
| The external type is a URN with the prefix `"urn:nfc:ext:"` followed by |
There was a problem hiding this comment.
Mentioning URN is not recommended in W3C specs and the urn is all fictional as well as that is never written anywhere!
There was a problem hiding this comment.
I think we should really just avoid mentioning the URN and just state how it is written
There was a problem hiding this comment.
This comes from the NDEF spec, and they use URN. This is an informative section that explains how NDEF is supposed to work.
There was a problem hiding this comment.
Still there is specs docs from W3C saying to avoid due to a multitude of issues, and all this is useless because it's not even written as a URN...
There was a problem hiding this comment.
We don't use URN in the spec. We explain what URN means in the NDEF spec.
There was a problem hiding this comment.
I thought this was important to understanding how external vs global and local types work. If I remove that text, it remains vaguely explained. With that thinking we could get rid of the whole informative explanation section, as developers can read the NDEF specs themselves.
There was a problem hiding this comment.
They most likely won't read that or have access. I just think we can explain it without referring to URNs at all, but leave it for now
There was a problem hiding this comment.
Let's sleep on this one. I don't see much harm in exposing the NDEF logic for information, but let me think it over, whether talking about URN (which I agree makes little sense in the NDEF spec to start with) would confuse any wandering soul. It would be pity to lose anyone to the dark side of the Web :).
There was a problem hiding this comment.
Kenneth, the URN's are mentioned (by you, AFAICT) in other places in the spec, too.
I suggest we merge this like this and take up the issue of URNs separately.
index.html
Outdated
| <a>TNF field</a> MUST be `6` (unchanged). | ||
| </li> | ||
| <li> | ||
| The terminating chunk record has this flag cleared, and in rest undergo the same rules as the middle chunk records. |
index.html
Outdated
| Forum, many commercial products such as bus cards, door openers may be based | ||
| on the <a>MIFARE Standard</a> which require specific NFC chips (same vendor of | ||
| card and reader) in order to function. | ||
| In general, pushing data to another Web NFC capable device requires that |
There was a problem hiding this comment.
remove Web, it might not even run a web browser
index.html
Outdated
| @@ -1190,6 +1396,10 @@ <h4> | |||
| used for implementing security policies, for instance the authenticity of | |||
| <a>record identifier</a>, unless a <a>prearranged trust relationship</a> exists. | |||
| </p> | |||
| <p> | |||
| Security considerations for media types in general are discussed in | |||
| [[RFC2048]] and for “application” media types in [[RFC2046]]. | |||
There was a problem hiding this comment.
Weird " you are using there
Signed-off-by: Zoltan Kis <zoltan.kis@intel.com>
|
Merging.
|
The spec changes: - w3c/web-nfc#361 - w3c/web-nfc#495 BUG=520391 Change-Id: Ida502501e7ec4775035057d8fa548dfb868a8e70
The spec changes: - w3c/web-nfc#361 - w3c/web-nfc#495 BUG=520391 Change-Id: Ida502501e7ec4775035057d8fa548dfb868a8e70
The spec changes: - w3c/web-nfc#361 - w3c/web-nfc#495 BUG=520391 Change-Id: Ida502501e7ec4775035057d8fa548dfb868a8e70
The spec changes: - w3c/web-nfc#361 - w3c/web-nfc#495 BUG=520391 Change-Id: Ida502501e7ec4775035057d8fa548dfb868a8e70 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2049831 Reviewed-by: Leon Han <leon.han@intel.com> Reviewed-by: Rijubrata Bhaumik <rijubrata.bhaumik@intel.com> Commit-Queue: Wanming Lin <wanming.lin@intel.com> Cr-Commit-Position: refs/heads/master@{#740920}
The spec changes: - w3c/web-nfc#361 - w3c/web-nfc#495 BUG=520391 Change-Id: Ida502501e7ec4775035057d8fa548dfb868a8e70 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2049831 Reviewed-by: Leon Han <leon.han@intel.com> Reviewed-by: Rijubrata Bhaumik <rijubrata.bhaumik@intel.com> Commit-Queue: Wanming Lin <wanming.lin@intel.com> Cr-Commit-Position: refs/heads/master@{#740920}
The spec changes: - w3c/web-nfc#361 - w3c/web-nfc#495 BUG=520391 Change-Id: Ida502501e7ec4775035057d8fa548dfb868a8e70 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2049831 Reviewed-by: Leon Han <leon.han@intel.com> Reviewed-by: Rijubrata Bhaumik <rijubrata.bhaumik@intel.com> Commit-Queue: Wanming Lin <wanming.lin@intel.com> Cr-Commit-Position: refs/heads/master@{#740920}
The spec changes: w3c/web-nfc#361 w3c/web-nfc#495 w3c/web-nfc#536 BUG=520391 Change-Id: I00a363aba07d1f9f2f8e40212dca7650e26047a2
… a=testonly Automatic update from web-platform-tests [webnfc] Add WPT tests for smart poster The spec changes: - w3c/web-nfc#361 - w3c/web-nfc#495 BUG=520391 Change-Id: Ida502501e7ec4775035057d8fa548dfb868a8e70 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2049831 Reviewed-by: Leon Han <leon.han@intel.com> Reviewed-by: Rijubrata Bhaumik <rijubrata.bhaumik@intel.com> Commit-Queue: Wanming Lin <wanming.lin@intel.com> Cr-Commit-Position: refs/heads/master@{#740920} -- wpt-commits: d97d4ef04045fab6457f1ea59c41bec7bd1fd191 wpt-pr: 21746
The spec changes: w3c/web-nfc#361 w3c/web-nfc#495 w3c/web-nfc#536 BUG=520391 Change-Id: I00a363aba07d1f9f2f8e40212dca7650e26047a2
… a=testonly Automatic update from web-platform-tests [webnfc] Add WPT tests for smart poster The spec changes: - w3c/web-nfc#361 - w3c/web-nfc#495 BUG=520391 Change-Id: Ida502501e7ec4775035057d8fa548dfb868a8e70 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2049831 Reviewed-by: Leon Han <leon.han@intel.com> Reviewed-by: Rijubrata Bhaumik <rijubrata.bhaumik@intel.com> Commit-Queue: Wanming Lin <wanming.lin@intel.com> Cr-Commit-Position: refs/heads/master@{#740920} -- wpt-commits: d97d4ef04045fab6457f1ea59c41bec7bd1fd191 wpt-pr: 21746
… a=testonly Automatic update from web-platform-tests [webnfc] Add WPT tests for smart poster The spec changes: - w3c/web-nfc#361 - w3c/web-nfc#495 BUG=520391 Change-Id: Ida502501e7ec4775035057d8fa548dfb868a8e70 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2049831 Reviewed-by: Leon Han <leon.hanintel.com> Reviewed-by: Rijubrata Bhaumik <rijubrata.bhaumikintel.com> Commit-Queue: Wanming Lin <wanming.linintel.com> Cr-Commit-Position: refs/heads/master{#740920} -- wpt-commits: d97d4ef04045fab6457f1ea59c41bec7bd1fd191 wpt-pr: 21746 UltraBlame original commit: 3cf1e0f17a7d54726e6c5f3fce7c4fd46a119f4e
… a=testonly Automatic update from web-platform-tests [webnfc] Add WPT tests for smart poster The spec changes: - w3c/web-nfc#361 - w3c/web-nfc#495 BUG=520391 Change-Id: Ida502501e7ec4775035057d8fa548dfb868a8e70 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2049831 Reviewed-by: Leon Han <leon.hanintel.com> Reviewed-by: Rijubrata Bhaumik <rijubrata.bhaumikintel.com> Commit-Queue: Wanming Lin <wanming.linintel.com> Cr-Commit-Position: refs/heads/master{#740920} -- wpt-commits: d97d4ef04045fab6457f1ea59c41bec7bd1fd191 wpt-pr: 21746 UltraBlame original commit: 3cf1e0f17a7d54726e6c5f3fce7c4fd46a119f4e
… a=testonly Automatic update from web-platform-tests [webnfc] Add WPT tests for smart poster The spec changes: - w3c/web-nfc#361 - w3c/web-nfc#495 BUG=520391 Change-Id: Ida502501e7ec4775035057d8fa548dfb868a8e70 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2049831 Reviewed-by: Leon Han <leon.hanintel.com> Reviewed-by: Rijubrata Bhaumik <rijubrata.bhaumikintel.com> Commit-Queue: Wanming Lin <wanming.linintel.com> Cr-Commit-Position: refs/heads/master{#740920} -- wpt-commits: d97d4ef04045fab6457f1ea59c41bec7bd1fd191 wpt-pr: 21746 UltraBlame original commit: 3cf1e0f17a7d54726e6c5f3fce7c4fd46a119f4e
The spec changes: w3c/web-nfc#361 w3c/web-nfc#495 w3c/web-nfc#536 BUG=520391 Change-Id: I00a363aba07d1f9f2f8e40212dca7650e26047a2
The spec changes: w3c/web-nfc#361 w3c/web-nfc#495 w3c/web-nfc#536 BUG=520391 Change-Id: I00a363aba07d1f9f2f8e40212dca7650e26047a2
The spec changes: w3c/web-nfc#361 w3c/web-nfc#495 w3c/web-nfc#536 BUG=520391 Change-Id: I00a363aba07d1f9f2f8e40212dca7650e26047a2
The spec changes: w3c/web-nfc#361 w3c/web-nfc#495 w3c/web-nfc#536 BUG=520391 Change-Id: I00a363aba07d1f9f2f8e40212dca7650e26047a2 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2038492 Commit-Queue: Leon Han <leon.han@intel.com> Reviewed-by: Reilly Grant <reillyg@chromium.org> Reviewed-by: François Beaufort <beaufort.francois@gmail.com> Cr-Commit-Position: refs/heads/master@{#743864}
The spec changes: w3c/web-nfc#361 w3c/web-nfc#495 w3c/web-nfc#536 BUG=520391 Change-Id: I00a363aba07d1f9f2f8e40212dca7650e26047a2 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2038492 Commit-Queue: Leon Han <leon.han@intel.com> Reviewed-by: Reilly Grant <reillyg@chromium.org> Reviewed-by: François Beaufort <beaufort.francois@gmail.com> Cr-Commit-Position: refs/heads/master@{#743864}
The spec changes: w3c/web-nfc#361 w3c/web-nfc#495 w3c/web-nfc#536 BUG=520391 Change-Id: I00a363aba07d1f9f2f8e40212dca7650e26047a2 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2038492 Commit-Queue: Leon Han <leon.han@intel.com> Reviewed-by: Reilly Grant <reillyg@chromium.org> Reviewed-by: François Beaufort <beaufort.francois@gmail.com> Cr-Commit-Position: refs/heads/master@{#743864}
…oster records, a=testonly Automatic update from web-platform-tests [webnfc] Support reading/writing smart-poster records The spec changes: w3c/web-nfc#361 w3c/web-nfc#495 w3c/web-nfc#536 BUG=520391 Change-Id: I00a363aba07d1f9f2f8e40212dca7650e26047a2 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2038492 Commit-Queue: Leon Han <leon.han@intel.com> Reviewed-by: Reilly Grant <reillyg@chromium.org> Reviewed-by: François Beaufort <beaufort.francois@gmail.com> Cr-Commit-Position: refs/heads/master@{#743864} -- wpt-commits: 89a8f08c2a04508b40c8819d785c5ce7369dcf68 wpt-pr: 21799
…oster records, a=testonly Automatic update from web-platform-tests [webnfc] Support reading/writing smart-poster records The spec changes: w3c/web-nfc#361 w3c/web-nfc#495 w3c/web-nfc#536 BUG=520391 Change-Id: I00a363aba07d1f9f2f8e40212dca7650e26047a2 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2038492 Commit-Queue: Leon Han <leon.han@intel.com> Reviewed-by: Reilly Grant <reillyg@chromium.org> Reviewed-by: François Beaufort <beaufort.francois@gmail.com> Cr-Commit-Position: refs/heads/master@{#743864} -- wpt-commits: 89a8f08c2a04508b40c8819d785c5ce7369dcf68 wpt-pr: 21799
…oster records, a=testonly Automatic update from web-platform-tests [webnfc] Support reading/writing smart-poster records The spec changes: w3c/web-nfc#361 w3c/web-nfc#495 w3c/web-nfc#536 BUG=520391 Change-Id: I00a363aba07d1f9f2f8e40212dca7650e26047a2 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2038492 Commit-Queue: Leon Han <leon.hanintel.com> Reviewed-by: Reilly Grant <reillygchromium.org> Reviewed-by: François Beaufort <beaufort.francoisgmail.com> Cr-Commit-Position: refs/heads/master{#743864} -- wpt-commits: 89a8f08c2a04508b40c8819d785c5ce7369dcf68 wpt-pr: 21799 UltraBlame original commit: 580550ae487bb2e8304198acb730ab591da24e10
…oster records, a=testonly Automatic update from web-platform-tests [webnfc] Support reading/writing smart-poster records The spec changes: w3c/web-nfc#361 w3c/web-nfc#495 w3c/web-nfc#536 BUG=520391 Change-Id: I00a363aba07d1f9f2f8e40212dca7650e26047a2 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2038492 Commit-Queue: Leon Han <leon.hanintel.com> Reviewed-by: Reilly Grant <reillygchromium.org> Reviewed-by: François Beaufort <beaufort.francoisgmail.com> Cr-Commit-Position: refs/heads/master{#743864} -- wpt-commits: 89a8f08c2a04508b40c8819d785c5ce7369dcf68 wpt-pr: 21799 UltraBlame original commit: 580550ae487bb2e8304198acb730ab591da24e10
…oster records, a=testonly Automatic update from web-platform-tests [webnfc] Support reading/writing smart-poster records The spec changes: w3c/web-nfc#361 w3c/web-nfc#495 w3c/web-nfc#536 BUG=520391 Change-Id: I00a363aba07d1f9f2f8e40212dca7650e26047a2 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2038492 Commit-Queue: Leon Han <leon.hanintel.com> Reviewed-by: Reilly Grant <reillygchromium.org> Reviewed-by: François Beaufort <beaufort.francoisgmail.com> Cr-Commit-Position: refs/heads/master{#743864} -- wpt-commits: 89a8f08c2a04508b40c8819d785c5ce7369dcf68 wpt-pr: 21799 UltraBlame original commit: 580550ae487bb2e8304198acb730ab591da24e10
Work might be still needed on consistency of terms between NFC standards informative section and normative sections. Also, Examples need to be checked.
Preview | Diff