-
Notifications
You must be signed in to change notification settings - Fork 69
/
use-cases.html
213 lines (206 loc) · 7.95 KB
/
use-cases.html
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
<!DOCTYPE html>
<html>
<head>
<title>Web NFC API Use Cases</title>
<meta charset="UTF-8">
<script src='https://www.w3.org/Tools/respec/respec-w3c-common'
class='remove'>
</script>
<script class="remove">
var respecConfig = {
specStatus: "CG-DRAFT",
shortName: "web-nfc",
noLegacyStyle: true,
publishDate: "",
previousPublishDate: "",
previousMaturity: "",
edDraftURI: "https://w3c.github.io/web-nfc/",
crEnd: "",
editors: [
{ name: "Kenneth Rohde Christiansen", company: "Intel",
companyURL: "http://www.intel.com/" },
{ name: "Zoltan Kis", company: "Intel",
companyURL: "http://www.intel.com/" },
],
inlineCSS: true,
noIDLIn: true,
// extraCSS: ["../ReSpec.js/css/respec.css"],
wg: "Web NFC Community Group",
wgURI: "https://www.w3.org/community/web-nfc/",
wgPublicList: "public-web-nfc",
otherLinks: [
{
key: "Repository",
data: [{
value: "We are on Github.",
href: "https://github.com/w3c/web-nfc"
}, {
value: "File a bug.",
href: "https://github.com/w3c/web-nfc/issues"
}, {
value: "Commit history.",
href: "https://github.com/w3c/web-nfc/commits/gh-pages"
}
]
},
]
};
</script>
</head>
<body>
<!-- - - - - - - - - - - - - - - - Abstract - - - - - - - - - - - - - - - - -->
<section id="abstract">
<p>
This document provides a collection of use cases and usage scenarios for
web pages and applications using Near Field Communication (NFC).
More information about Web NFC can be found
<a href="http://w3c.github.io/web-nfc/index.html#abstract">here</a>.
</p>
<p>
This specification defines an API to manage selected NFC use cases from Web
applications and pages, and to enable new use cases based on NFC technology.
</p>
<p class="advisement">
Low-level I/O operations (e.g. ISO-DEP, NFC-A/B, NFC-F) and Host-based Card
Emulation (HCE) are <b>not</b> supported within the current scope.
</p>
</section>
<section id="sotd">
<p>
This document provides informative background to the
<a href="http://w3c.github.io/web-nfc/index.html">Web NFC specification</a>.
Comments on the document should be filed as issues at
<a href="https://github.com/w3c/web-nfc/issues">
https://github.com/w3c/web-nfc/issues</a>.
</p>
</section>
<section> <h2>Terminology</h2>
<p>
For NFC terminology see the
<a href="http://w3c.github.io/web-nfc/index.html#terminology">
Web NFC specification</a>.
</p>
</section>
<section class="informative"> <h2>Use Cases</h2>
<p>
A few NFC user scenarios have been enumerated
<a href="http://www.w3.org/2009/dap/wiki/Near_field_communications_%28NFC%29#Use_cases_submitted_to_DAP_mailing_list">
here</a>. For the Web NFC API in particular, a few examples of intended
user scenarios follow next. Some of them are <b>not</b> supported in the
current scope.
</p>
<section> <h3>Reading generic information in a museum</h3>
<p>
The user touches an NFC capable device to information points of works of
arts in a museum, obtaining information about the exposed items. Also,
by touching information points in halls, the user can get suggested
itineraries, schedule and other information to the personal device for
later consultation.
</p>
</section>
<section> <h3>Reading information in administration office</h3>
<p>
In a population administration office, the user touches in information
point in order to save a list of documents required for renewing a
passport, and obtaining a the next queuing number for the clerk.
</p>
</section>
<section> <h3>Updating tag information</h3>
<p>
A museum employee touches information points with a special device which
can write to the museum's NFC tags in order to update (read, then write)
information on them.
</p>
</section>
<section> <h3>Sending image to another Web NFC capable device</h3>
<p>
While a user is actively interacting with web site, e.g.
https://images.example.com/, and if the user taps the device with
another device where another user is actively interacting with the
same web site https://images.example.com/, then they can initiate
sending an image from one device to the other, using the NFC
connection or by handover to Bluetooth or WiFi connection.
The second device may be for instance a TV set to show the picture,
or a personal computer for image processing.
</p>
<p class="note">
This use case is not supported within the current scope of the
specification.
</p>
</section>
<section><h3>Handover to Bluetooth</h3>
<p>
NFC supports handover protocols to Bluetooth or WiFi connectivity for
the purpose of larger volume data transfer. The user touches another
NFC capable device, and as a result configuration data is sent for a
new Bluetooth or WiFi connection, which is then established between the
devices.
</p>
<p>
A related use case for gaming has been described
<a href=":https://webbluetoothcg.github.io/web-bluetooth/use-cases.html">
here</a>.
Other use cases may include bulk transfer of contacts cards, photos,
and other data.
</p>
<p class="note">
This use case is not supported within the current scope of the
specification.
</p>
</section>
<section><h3>Verifying unusual purchase activities</h3>
<p>
NFC can be used to verify unusual purchase activities, by having the user
touch the the credit card for additional authentication.
</p>
</section>
<section><h3>Scenarios along side payment</h3>
<p>
Payment using NFC should be handled at a platform level due to security
considerations and is thus not within the scope of Web NFC. On the other
hand it is possible to associate the payment status with
a web page in order to have secondary actions. For instance,
the user buys goods in a store, and payment options include contactless
payment using NFC technology.
</p>
<p>
In general, touching the device to the point of sales terminal receiver
area will result in a transaction between the secure element from the
device and the point of sales terminal. With Web NFC, if the
user navigates to a web site before paying, there may be interaction
with that site regarding the payment, e.g. the user could get points and
discounts, or get delivered application or service specific data (e.g.
tickets, keys, etc) to the device.
</p>
<p class="note">
This use case is not supported within the current scope of the
specification.
</p>
</section>
<!--
<section> <h3>Payment to another user</h3>
<p>
The user navigates to a web site which manages seller and buyer accounts
and touches the device to another device of another user. A payment can
be made between the two users' accounts.
</p>
</section>
<section> <h3>Payment for services</h3>
<p>
On an automated point of sales terminal, such as ticketing machines,
the user navigates to a web site which offers the paid service.
By touching the receiver area of the point of sales, the payment can be
done and the ticket can be delivered electronically to the user's
device.
</p>
</section>
-->
</section>
<section id="acknowledgments"> <h2>Acknowledgments</h2>
<p>
The editors would like to express their gratitude to Jonas Sicking and
Jeffrey Yasskin.
</p>
</section>
</body>
</html>