-
Notifications
You must be signed in to change notification settings - Fork 29
/
activity-schema.html
2182 lines (2121 loc) · 109 KB
/
activity-schema.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
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668
669
670
671
672
673
674
675
676
677
678
679
680
681
682
683
684
685
686
687
688
689
690
691
692
693
694
695
696
697
698
699
700
701
702
703
704
705
706
707
708
709
710
711
712
713
714
715
716
717
718
719
720
721
722
723
724
725
726
727
728
729
730
731
732
733
734
735
736
737
738
739
740
741
742
743
744
745
746
747
748
749
750
751
752
753
754
755
756
757
758
759
760
761
762
763
764
765
766
767
768
769
770
771
772
773
774
775
776
777
778
779
780
781
782
783
784
785
786
787
788
789
790
791
792
793
794
795
796
797
798
799
800
801
802
803
804
805
806
807
808
809
810
811
812
813
814
815
816
817
818
819
820
821
822
823
824
825
826
827
828
829
830
831
832
833
834
835
836
837
838
839
840
841
842
843
844
845
846
847
848
849
850
851
852
853
854
855
856
857
858
859
860
861
862
863
864
865
866
867
868
869
870
871
872
873
874
875
876
877
878
879
880
881
882
883
884
885
886
887
888
889
890
891
892
893
894
895
896
897
898
899
900
901
902
903
904
905
906
907
908
909
910
911
912
913
914
915
916
917
918
919
920
921
922
923
924
925
926
927
928
929
930
931
932
933
934
935
936
937
938
939
940
941
942
943
944
945
946
947
948
949
950
951
952
953
954
955
956
957
958
959
960
961
962
963
964
965
966
967
968
969
970
971
972
973
974
975
976
977
978
979
980
981
982
983
984
985
986
987
988
989
990
991
992
993
994
995
996
997
998
999
1000
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
<html lang="en"><head><title>Activity Streams Working Group: Activity Base Schema (Draft)</title>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<meta name="description" content="Activity Base Schema (Draft)">
<meta name="generator" content="xml2rfc v1.36 (http://xml.resource.org/)">
<style type='text/css'><!--
body {
font-family: verdana, charcoal, helvetica, arial, sans-serif;
font-size: small; color: #000; background-color: #FFF;
margin: 2em;
}
h1, h2, h3, h4, h5, h6 {
font-family: helvetica, monaco, "MS Sans Serif", arial, sans-serif;
font-weight: bold; font-style: normal;
}
h1 { color: #900; background-color: transparent; text-align: right; }
h3 { color: #333; background-color: transparent; }
td.RFCbug {
font-size: x-small; text-decoration: none;
width: 30px; height: 30px; padding-top: 2px;
text-align: justify; vertical-align: middle;
background-color: #000;
}
td.RFCbug span.RFC {
font-family: monaco, charcoal, geneva, "MS Sans Serif", helvetica, verdana, sans-serif;
font-weight: bold; color: #666;
}
td.RFCbug span.hotText {
font-family: charcoal, monaco, geneva, "MS Sans Serif", helvetica, verdana, sans-serif;
font-weight: normal; text-align: center; color: #FFF;
}
table.TOCbug { width: 30px; height: 15px; }
td.TOCbug {
text-align: center; width: 30px; height: 15px;
color: #FFF; background-color: #900;
}
td.TOCbug a {
font-family: monaco, charcoal, geneva, "MS Sans Serif", helvetica, sans-serif;
font-weight: bold; font-size: x-small; text-decoration: none;
color: #FFF; background-color: transparent;
}
td.header {
font-family: arial, helvetica, sans-serif; font-size: x-small;
vertical-align: top; width: 33%;
color: #FFF; background-color: #666;
}
td.author { font-weight: bold; font-size: x-small; margin-left: 4em; }
td.author-text { font-size: x-small; }
/* info code from SantaKlauss at http://www.madaboutstyle.com/tooltip2.html */
a.info {
/* This is the key. */
position: relative;
z-index: 24;
text-decoration: none;
}
a.info:hover {
z-index: 25;
color: #FFF; background-color: #900;
}
a.info span { display: none; }
a.info:hover span.info {
/* The span will display just on :hover state. */
display: block;
position: absolute;
font-size: smaller;
top: 2em; left: -5em; width: 15em;
padding: 2px; border: 1px solid #333;
color: #900; background-color: #EEE;
text-align: left;
}
a { font-weight: bold; }
a:link { color: #900; background-color: transparent; }
a:visited { color: #633; background-color: transparent; }
a:active { color: #633; background-color: transparent; }
p { margin-left: 2em; margin-right: 2em; }
p.copyright { font-size: x-small; }
p.toc { font-size: small; font-weight: bold; margin-left: 3em; }
table.toc { margin: 0 0 0 3em; padding: 0; border: 0; vertical-align: text-top; }
td.toc { font-size: small; font-weight: bold; vertical-align: text-top; }
ol.text { margin-left: 2em; margin-right: 2em; }
ul.text { margin-left: 2em; margin-right: 2em; }
li { margin-left: 3em; }
/* RFC-2629 <spanx>s and <artwork>s. */
em { font-style: italic; }
strong { font-weight: bold; }
dfn { font-weight: bold; font-style: normal; }
cite { font-weight: normal; font-style: normal; }
tt { color: #036; }
tt, pre, pre dfn, pre em, pre cite, pre span {
font-family: "Courier New", Courier, monospace; font-size: small;
}
pre {
text-align: left; padding: 4px;
color: #000; background-color: #CCC;
}
pre dfn { color: #900; }
pre em { color: #66F; background-color: #FFC; font-weight: normal; }
pre .key { color: #33C; font-weight: bold; }
pre .id { color: #900; }
pre .str { color: #000; background-color: #CFF; }
pre .val { color: #066; }
pre .rep { color: #909; }
pre .oth { color: #000; background-color: #FCF; }
pre .err { background-color: #FCC; }
/* RFC-2629 <texttable>s. */
table.all, table.full, table.headers, table.none {
font-size: small; text-align: center; border-width: 2px;
vertical-align: top; border-collapse: collapse;
}
table.all, table.full { border-style: solid; border-color: black; }
table.headers, table.none { border-style: none; }
th {
font-weight: bold; border-color: black;
border-width: 2px 2px 3px 2px;
}
table.all th, table.full th { border-style: solid; }
table.headers th { border-style: none none solid none; }
table.none th { border-style: none; }
table.all td {
border-style: solid; border-color: #333;
border-width: 1px 2px;
}
table.full td, table.headers td, table.none td { border-style: _none; }
hr { height: 1px; }
hr.insert {
width: 80%; border-style: none; border-width: 0;
color: #CCC; background-color: #CCC;
}
--></style>
</head>
<body>
<table summary="layout" cellpadding="0" cellspacing="2" class="TOCbug" align="right"><tr><td class="TOCbug"><a href="#toc"> TOC </a></td></tr></table>
<table summary="layout" width="66%" border="0" cellpadding="0" cellspacing="0"><tr><td><table summary="layout" width="100%" border="0" cellpadding="2" cellspacing="1">
<tr><td class="header">Activity Streams Working Group</td><td class="header">J. Snell</td></tr>
<tr><td class="header"> </td><td class="header">IBM</td></tr>
<tr><td class="header"> </td><td class="header">M. Atkins</td></tr>
<tr><td class="header"> </td><td class="header">SAY Media</td></tr>
<tr><td class="header"> </td><td class="header">D. Recordon</td></tr>
<tr><td class="header"> </td><td class="header">Six Apart, Facebook</td></tr>
<tr><td class="header"> </td><td class="header">C. Messina</td></tr>
<tr><td class="header"> </td><td class="header">Citizen Agency, Google</td></tr>
<tr><td class="header"> </td><td class="header">M. Keller</td></tr>
<tr><td class="header"> </td><td class="header">MySpace, Facebook</td></tr>
<tr><td class="header"> </td><td class="header">A. Steinberg</td></tr>
<tr><td class="header"> </td><td class="header">Facebook</td></tr>
<tr><td class="header"> </td><td class="header">R. Dolin</td></tr>
<tr><td class="header"> </td><td class="header">Microsoft</td></tr>
<tr><td class="header"> </td><td class="header">August 30, 2012</td></tr>
</table></td></tr></table>
<h1><br />Activity Base Schema (Draft)</h1>
<h3>Abstract</h3>
<p>This document presents a base set of Object types and Verbs for use
with Activity Streams.
</p>
<h3>Requirements Language</h3>
<p>The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in <a class='info' href='#RFC2119'>RFC 2119<span> (</span><span class='info'>Bradner, S., “Key words for use in RFCs to Indicate Requirement Levels,” March 1997.</span><span>)</span></a> [RFC2119].
</p><a name="toc"></a><br /><hr />
<h3>Table of Contents</h3>
<p class="toc">
<a href="#anchor1">1.</a>
Introduction<br />
<a href="#anchor2">1.1.</a>
Notational Conventions<br />
<a href="#verbs">2.</a>
Verbs<br />
<a href="#object-types">3.</a>
Object Types<br />
<a href="#audio-video">3.1.</a>
Audio and Video Objects<br />
<a href="#binary">3.2.</a>
Binary Objects<br />
<a href="#event">3.3.</a>
Event<br />
<a href="#issue">3.4.</a>
Issue<br />
<a href="#place">3.5.</a>
Place<br />
<a href="#task">3.6.</a>
Task<br />
<a href="#anchor3">4.</a>
Base Extension Properties<br />
<a href="#context">4.1.</a>
Context<br />
<a href="#location">4.2.</a>
Location<br />
<a href="#mood-property">4.3.</a>
Mood<br />
<a href="#rating-property">4.4.</a>
Rating<br />
<a href="#result-property">4.5.</a>
Result<br />
<a href="#source">4.6.</a>
Source<br />
<a href="#startEndTime">4.7.</a>
Starting and Ending Timestamps<br />
<a href="#tags-property">4.8.</a>
Tags<br />
<a href="#multipage-collections">5.</a>
Multi-page Collections<br />
<a href="#external-vocabularies">6.</a>
External Vocabularies<br />
<a href="#dc">6.1.</a>
"dc"<br />
<a href="#geojson">6.2.</a>
"geojson"<br />
<a href="#ld">6.3.</a>
"ld"<br />
<a href="#links">6.4.</a>
"links"<br />
<a href="#link-objects">6.4.1.</a>
Link Objects<br />
<a href="#odata">6.5.</a>
"odata"<br />
<a href="#opengraph">6.6.</a>
"opengraph"<br />
<a href="#schema_org">6.7.</a>
"schema_org"<br />
<a href="#rfc.references1">7.</a>
Normative References<br />
<a href="#rfc.authors">§</a>
Authors' Addresses<br />
</p>
<br clear="all" />
<a name="anchor1"></a><br /><hr />
<table summary="layout" cellpadding="0" cellspacing="2" class="TOCbug" align="right"><tr><td class="TOCbug"><a href="#toc"> TOC </a></td></tr></table>
<a name="rfc.section.1"></a><h3>1.
Introduction</h3>
<p>This document presents a base set of object types and verbs for use
with Activity Streams.
</p>
<a name="anchor2"></a><br /><hr />
<table summary="layout" cellpadding="0" cellspacing="2" class="TOCbug" align="right"><tr><td class="TOCbug"><a href="#toc"> TOC </a></td></tr></table>
<a name="rfc.section.1.1"></a><h3>1.1.
Notational Conventions</h3>
<p>This specification allows the use of <a class='info' href='#RFC3987'>IRIs<span> (</span><span class='info'>Duerst, M. and M. Suignard, “Internationalized Resource Identifiers (IRIs),” January 2005.</span><span>)</span></a> [RFC3987].
Every <a class='info' href='#RFC3986'>URI<span> (</span><span class='info'>Berners-Lee, T., Fielding, R., and L. Masinter, “Uniform Resource Identifier (URI): Generic Syntax,” January 2005.</span><span>)</span></a> [RFC3986] is also an IRI, so a URI MAY be
used wherever an IRI is named. When an IRI that is not also a URI is
given for dereferencing, it MUST be mapped to a URI using the steps in
Section 3.1 of <a class='info' href='#RFC3987'>[RFC3987]<span> (</span><span class='info'>Duerst, M. and M. Suignard, “Internationalized Resource Identifiers (IRIs),” January 2005.</span><span>)</span></a>. When an IRI is serving as an
identifier, it MUST NOT be so mapped.
</p>
<p>Unless otherwise specified, all properties specifying date and
time values MUST conform to the "date-time" production in <a class='info' href='#RFC3339'>[RFC3339]<span> (</span><span class='info'>Klyne, G., Ed. and C. Newman, “Date and Time on the Internet: Timestamps,” July 2002.</span><span>)</span></a>.
In addition, an uppercase "T" character MUST be used to separate date
and time, and an uppercase "Z" character MUST be present in the absence of
a numeric time zone offset.
</p>
<a name="verbs"></a><br /><hr />
<table summary="layout" cellpadding="0" cellspacing="2" class="TOCbug" align="right"><tr><td class="TOCbug"><a href="#toc"> TOC </a></td></tr></table>
<a name="rfc.section.2"></a><h3>2.
Verbs</h3>
<p>This specification defines the following core verbs in addition
to the default <tt>post</tt> verb that is defined in Section 6 of
<a class='info' href='#activitystreams'>[activitystreams]<span> (</span><span class='info'>Snell, J., Atkins, M., Norris, W., Messina, C., Wilkinson, M., and R. Dolin, “JSON Activity Streams 1.0,” May 2011.</span><span>)</span></a>:
</p><table class="full" border="1" cellpadding="2" cellspacing="2">
<col align="left" width="15%"><col align="left">
<tr><th align="left">Verb</th><th align="left">Description</th></tr>
<tr>
<td align="left"><tt>accept</tt> </td>
<td align="left">Indicates that that the actor has accepted the object. For
instance, a person accepting an award, or accepting an assignment.</td>
</tr>
<tr>
<td align="left"><tt>access</tt> </td>
<td align="left">Indicates that the actor has accessed the object. For instance,
a person accessing a room, or accessing a file.</td>
</tr>
<tr>
<td align="left"><tt>acknowledge</tt> </td>
<td align="left">Indicates that the actor has acknowledged the object. This
effectively signals that the actor is aware of the object's
existence.</td>
</tr>
<tr>
<td align="left"><tt>add</tt> </td>
<td align="left">Indicates that the actor has added the object to the target.
For instance, adding a photo to an album.</td>
</tr>
<tr>
<td align="left"><tt>agree</tt> </td>
<td align="left">Indicates that the actor agrees with the object. For example,
a person agreeing with an argument, or expressing agreement with
a particular issue.</td>
</tr>
<tr>
<td align="left"><tt>append</tt> </td>
<td align="left">Indicates that the actor has appended the object to the target.
For instance, a person appending a new record to a database.</td>
</tr>
<tr>
<td align="left"><tt>approve</tt> </td>
<td align="left">Indicates that the actor has approved the object. For instance,
a manager might approve a travel request.</td>
</tr>
<tr>
<td align="left"><tt>archive</tt> </td>
<td align="left">Indicates that the actor has archived the object.</td>
</tr>
<tr>
<td align="left"><tt>assign</tt> </td>
<td align="left">Indicates that the actor has assigned the object to the target.</td>
</tr>
<tr>
<td align="left"><tt>at</tt> </td>
<td align="left">Indicates that the actor is currently located at the object. For
instance, a person being at a specific physical location.</td>
</tr>
<tr>
<td align="left"><tt>attach</tt> </td>
<td align="left">Indicates that the actor has attached the object to the target.
For instance, a person attaching a file to a wiki page or an email.</td>
</tr>
<tr>
<td align="left"><tt>attend</tt> </td>
<td align="left">Indicates that the actor has attended the object. For instance,
a person attending a meeting.</td>
</tr>
<tr>
<td align="left"><tt>author</tt> </td>
<td align="left">Indicates that the actor has authored the object. Note that this
is a more specific form of the verb "create".</td>
</tr>
<tr>
<td align="left"><tt>authorize</tt> </td>
<td align="left">Indicates that the actor has authorized the object. If a target
is specified, it means that the authorization is specifically in
regards to the target. For instance, a service can authorize a
person to access a given application; in which case the actor is the
service, the object is the person, and the target is the application.
In contrast, a person can authorize a request; in which case the
actor is the person and the object is the request and there might be
no explicit target.</td>
</tr>
<tr>
<td align="left"><tt>borrow</tt> </td>
<td align="left">Indicates that the actor has borrowed the object. If a target
is specified, it identifies the entity from which the object was
borrowed. For instance, if a person borrows a book from a library,
the person is the actor, the book is the object and the library
is the target.</td>
</tr>
<tr>
<td align="left"><tt>build</tt> </td>
<td align="left">Indicates that the actor has built the object. For example,
if a person builds a model or compiles code.</td>
</tr>
<tr>
<td align="left"><tt>cancel</tt> </td>
<td align="left">Indicates that the actor has canceled the object. For
instance, canceling a calendar event.</td>
</tr>
<tr>
<td align="left"><tt>close</tt> </td>
<td align="left">Indicates that the actor has closed the object. For instance,
the object could represent a ticket being tracked in an issue
management system.</td>
</tr>
<tr>
<td align="left"><tt>complete</tt> </td>
<td align="left">Indicates that the actor has completed the object.</td>
</tr>
<tr>
<td align="left"><tt>confirm</tt> </td>
<td align="left">Indicates that the actor has confirmed or agrees with the object.
For instance, a software developer might confirm an issue reported
against a product.</td>
</tr>
<tr>
<td align="left"><tt>consume</tt> </td>
<td align="left">Indicates that the actor has consumed the object. The
specific meaning is dependent largely on the object's type.
For instance, an actor may "consume" an audio object, indicating
that the actor has listened to it; or an actor may "consume"
a book, indicating that the book has been read. As such, the
"consume" verb is a more generic form of other more specific
verbs such as "read" and "play".</td>
</tr>
<tr>
<td align="left"><tt>checkin</tt> </td>
<td align="left">Indicates that the actor has checked-in to the object. For
instance, a person checking-in to a Place.</td>
</tr>
<tr>
<td align="left"><tt>create</tt> </td>
<td align="left">Indicates that the actor has created the object.</td>
</tr>
<tr>
<td align="left"><tt>delete</tt> </td>
<td align="left">Indicates that the actor has deleted the object. This
implies, but does not require, the permanent destruction of the
object.</td>
</tr>
<tr>
<td align="left"><tt>deliver</tt> </td>
<td align="left">Indicates that the actor has delivered the object. For example,
delivering a package.</td>
</tr>
<tr>
<td align="left"><tt>deny</tt> </td>
<td align="left">Indicates that the actor has denied the object. For example,
a manager may deny a travel request.</td>
</tr>
<tr>
<td align="left"><tt>disagree</tt> </td>
<td align="left">Indicates that the actor disagrees with the object.</td>
</tr>
<tr>
<td align="left"><tt>dislike</tt> </td>
<td align="left">Indicates that the actor dislikes the object. Note that the
"dislike" verb is distinct from the "unlike" verb which assumes
that the object had been previously "liked".</td>
</tr>
<tr>
<td align="left"><tt>experience</tt> </td>
<td align="left">Indicates that the actor has experienced the object in some
manner. Note that, depending on the specific object types used
for both the actor and object, the meaning of this verb can
overlap that of the "consume" and "play" verbs. For instance,
a person might "experience" a movie; or "play" the movie; or "consume"
the movie. The "experience" verb can be considered a more generic
form of other more specific verbs as "consume", "play", "watch",
"listen", and "read"</td>
</tr>
<tr>
<td align="left"><tt>favorite</tt> </td>
<td align="left">Indicates that the actor marked the object as an item of
special interest.</td>
</tr>
<tr>
<td align="left"><tt>find</tt> </td>
<td align="left">Indicates that the actor has found the object.</td>
</tr>
<tr>
<td align="left"><tt>flag-as-inappropriate</tt> </td>
<td align="left">Indicates that the actor has flagged the object as being
inappropriate for some reason. When using this verb, the
<tt>context</tt> property, as specified
within <a class='info' href='#context'>Section 4.1<span> (</span><span class='info'>Context</span><span>)</span></a> can be used to
provide additional detail about why the object has been
flagged.</td>
</tr>
<tr>
<td align="left"><tt>follow</tt> </td>
<td align="left">Indicates that the actor began following the activity of the
object. In most cases, the objectType will be a "person", but it can
potentially be of any type that can sensibly generate activity.
Processors MAY ignore (silently drop) successive identical "follow"
activities.</td>
</tr>
<tr>
<td align="left"><tt>give</tt> </td>
<td align="left">Indicates that the actor is giving an object to the target.
Examples include one person giving a <tt>badge</tt>
object to another person. The <tt>object</tt>
identifies the object being given. The <tt>target</tt>
identifies the receiver.</td>
</tr>
<tr>
<td align="left"><tt>host</tt> </td>
<td align="left">Indicates that the actor is hosting the object. As in hosting
an event, or hosting a service.</td>
</tr>
<tr>
<td align="left"><tt>ignore</tt> </td>
<td align="left">Indicates that the actor has ignored the object. For instance,
this verb may be used when an actor has ignored a friend request,
in which case the object may be the <tt>request-friend</tt>
activity.</td>
</tr>
<tr>
<td align="left"><tt>insert</tt> </td>
<td align="left">Indicates that the actor has inserted the object into the target.</td>
</tr>
<tr>
<td align="left"><tt>install</tt> </td>
<td align="left">Indicates that the actor has installed the object, as in
installing an application.</td>
</tr>
<tr>
<td align="left"><tt>interact</tt> </td>
<td align="left">Indicates that the actor has interacted with the object. For instance,
when one person interacts with another.</td>
</tr>
<tr>
<td align="left"><tt>invite</tt> </td>
<td align="left">Indicates that the actor has invited the object, typically a
person object, to join or participate in the object described by
the <tt>target</tt>. The target could, for instance,
be an event, group or a service.</td>
</tr>
<tr>
<td align="left"><tt>join</tt> </td>
<td align="left">Indicates that the actor has become a member of the object. This
specification only defines the meaning of this verb when the
<tt>object</tt> of the Activity has an
<tt>objectType</tt> of <tt>group</tt>,
though implementors need to be prepared to handle other types of objects.</td>
</tr>
<tr>
<td align="left"><tt>leave</tt> </td>
<td align="left">Indicates that the actor has left the object. For instance,
a Person leaving a Group or checking-out of a Place.</td>
</tr>
<tr>
<td align="left"><tt>like</tt> </td>
<td align="left">Indicates that the actor marked the object as an item of special
interest. The "like" verb is considered to be an alias of "favorite".
The two verb are semantically identical.</td>
</tr>
<tr>
<td align="left"><tt>listen</tt> </td>
<td align="left">Indicates that the actor has listened to the object. This is typically
only applicable for objects representing audio content, such as music,
an audio-book, or a radio broadcast. The "listen" verb is a more specific
form of the "consume", "experience" and "play" verbs.</td>
</tr>
<tr>
<td align="left"><tt>lose</tt> </td>
<td align="left">Indicates that the actor has lost the object. For instance, if a
person loses a game.</td>
</tr>
<tr>
<td align="left"><tt>make-friend</tt> </td>
<td align="left">Indicates the creation of a friendship that is reciprocated by
the object. Since this verb implies an activity on the part of its object,
processors MUST NOT accept activities with this verb unless they are
able to verify through some external means that there is in fact a
reciprocated connection. For example, a processor may have received
a guarantee from a particular publisher that the publisher will only
use this Verb in cases where a reciprocal relationship exists.</td>
</tr>
<tr>
<td align="left"><tt>open</tt> </td>
<td align="left">Indicates that the actor has opened the object. For instance,
the object could represent a ticket being tracked in an issue
management system.</td>
</tr>
<tr>
<td align="left"><tt>play</tt> </td>
<td align="left">Indicates that the actor spent some time enjoying the object.
For example, if the object is a video this indicates that the subject
watched all or part of the video. The "play" verb is a more specific
form of the "consume" verb.</td>
</tr>
<tr>
<td align="left"><tt>present</tt> </td>
<td align="left">Indicates that the actor has presented the object. For instance,
when a person gives a presentation at a conference.</td>
</tr>
<tr>
<td align="left"><tt>purchase</tt> </td>
<td align="left">Indicates that the actor has purchased the object. If a target is
specified, in indicates the entity from which the object was purchased.</td>
</tr>
<tr>
<td align="left"><tt>qualify</tt> </td>
<td align="left">Indicates that the actor has qualified for the object. If a target
is specified, it indicates the context within which the qualification
applies.</td>
</tr>
<tr>
<td align="left"><tt>read</tt> </td>
<td align="left">Indicates that the actor read the object. This is typically only
applicable for objects representing printed or written content, such
as a book, a message or a comment. The "read" verb is a more specific
form of the "consume", "experience" and "play" verbs.</td>
</tr>
<tr>
<td align="left"><tt>receive</tt> </td>
<td align="left">Indicates that the actor is receiving an object.
Examples include a person receiving a <tt>badge</tt>
object. The <tt>object</tt>
identifies the object being received.</td>
</tr>
<tr>
<td align="left"><tt>reject</tt> </td>
<td align="left">Indicates that the actor has rejected the object.</td>
</tr>
<tr>
<td align="left"><tt>remove</tt> </td>
<td align="left">Indicates that the actor has removed the object from the target.</td>
</tr>
<tr>
<td align="left"><tt>remove-friend</tt> </td>
<td align="left">Indicates that the actor has removed the object from the collection
of friends.</td>
</tr>
<tr>
<td align="left"><tt>replace</tt> </td>
<td align="left">Indicates that the actor has replaced the target with the object.</td>
</tr>
<tr>
<td align="left"><tt>request</tt> </td>
<td align="left">Indicates that the actor has requested the object. If a target is
specified, it indicates the entity from which the object is being
requested.</td>
</tr>
<tr>
<td align="left"><tt>request-friend</tt> </td>
<td align="left">Indicates the creation of a friendship that has not yet been reciprocated by
the object.</td>
</tr>
<tr>
<td align="left"><tt>resolve</tt> </td>
<td align="left">Indicates that the actor has resolved the object. For instance,
the object could represent a ticket being tracked in an issue
management system.</td>
</tr>
<tr>
<td align="left"><tt>return</tt> </td>
<td align="left">Indicates that the actor has returned the object. If a target is
specified, it indicates the entity to which the object was returned.</td>
</tr>
<tr>
<td align="left"><tt>retract</tt> </td>
<td align="left">Indicates that the actor has retracted the object. For instance,
if an actor wishes to retract a previously published activity,
the object would be the previously published activity that is being
retracted.</td>
</tr>
<tr>
<td align="left"><tt>rsvp-maybe</tt> </td>
<td align="left">The "possible RSVP" verb indicates that the actor has made a
possible RSVP for the object. This specification only defines the
meaning of this verb when its object is an event (see <a class='info' href='#event'>Section 3.3<span> (</span><span class='info'>Event</span><span>)</span></a>), though implementors need to be prepared to
handle other object types. The use of this verb is only appropriate
when the RSVP was created by an explicit action by the actor. It
is not appropriate to use this verb when a user has been added as
an attendee by an event organiser or administrator.</td>
</tr>
<tr>
<td align="left"><tt>rsvp-no</tt> </td>
<td align="left">The "negative RSVP" verb indicates that the actor has made a
negative RSVP for the object. This specification only defines the
meaning of this verb when its object is an event (see <a class='info' href='#event'>Section 3.3<span> (</span><span class='info'>Event</span><span>)</span></a>), though implementors need to be prepared to
handle other object types. The use of this verb is only appropriate
when the RSVP was created by an explicit action by the actor. It is
not appropriate to use this verb when a user has been added as an
attendee by an event organiser or administrator.</td>
</tr>
<tr>
<td align="left"><tt>rsvp-yes</tt> </td>
<td align="left">The "positive RSVP" verb indicates that the actor has made a
positive RSVP for an object. This specification only defines the
meaning of this verb when its object is an event (see <a class='info' href='#event'>Section 3.3<span> (</span><span class='info'>Event</span><span>)</span></a>), though implementors need to be prepared to
handle other object types. The use of this verb is only appropriate
when the RSVP was created by an explicit action by the actor. It
is not appropriate to use this verb when a user has been added as
an attendee by an event organiser or administrator.</td>
</tr>
<tr>
<td align="left"><tt>satisfy</tt> </td>
<td align="left">Indicates that the actor has satisfied the object. If a target
is specified, it indicate the context within which the object was
satisfied. For instance, if a person satisfies the requirements for
a particular challenge, the person is the actor; the requirement is
the object; and the challenge is the target.</td>
</tr>
<tr>
<td align="left"><tt>save</tt> </td>
<td align="left">Indicates that the actor has called out the object as being of
interest primarily to him- or herself. Though this action MAY be
shared publicly, the implication is that the object has been saved
primarily for the actor's own benefit rather than to show it to
others as would be indicated by the "share" verb.</td>
</tr>
<tr>
<td align="left"><tt>schedule</tt> </td>
<td align="left">Indicates that the actor has scheduled the object. For instance,
scheduling a meeting.</td>
</tr>
<tr>
<td align="left"><tt>search</tt> </td>
<td align="left">Indicates that the actor is or has searched for the object. If
a target is specified, it indicates the context within which the
search is or has been conducted.</td>
</tr>
<tr>
<td align="left"><tt>sell</tt> </td>
<td align="left">Indicates that the actor has sold the object. If a target is
specified, it indicates the entity to which the object was sold.</td>
</tr>
<tr>
<td align="left"><tt>send</tt> </td>
<td align="left">Indicates that the actor has sent the object. If a target is
specified, it indicates the entity to which the object was sent.</td>
</tr>
<tr>
<td align="left"><tt>share</tt> </td>
<td align="left">Indicates that the actor has called out the object to readers.
In most cases, the actor did not create the object being shared,
but is instead drawing attention to it.</td>
</tr>
<tr>
<td align="left"><tt>sponsor</tt> </td>
<td align="left">Indicates that the actor has sponsored the object. If a target
is specified, it indicates the context within which the sponsorship
is offered. For instance, a company can sponsor an event; or an
individual can sponsor a project; etc.</td>
</tr>
<tr>
<td align="left"><tt>start</tt> </td>
<td align="left">Indicates that the actor has started the object. For instance,
when a person starts a project.</td>
</tr>
<tr>
<td align="left"><tt>stop-following</tt> </td>
<td align="left">Indicates that the actor has stopped following the object.</td>
</tr>
<tr>
<td align="left"><tt>submit</tt> </td>
<td align="left">Indicates that the actor has submitted the object. If a target
is specified, it indicates the entity to which the object was submitted.</td>
</tr>
<tr>
<td align="left"><tt>tag</tt> </td>
<td align="left">Indicates that the actor has associated the object with the target.
For example, if the actor specifies that a particular user
appears in a photo. the object is the user and the target is the photo.</td>
</tr>
<tr>
<td align="left"><tt>terminate</tt> </td>
<td align="left">Indicates that the actor has terminated the object. </td>
</tr>
<tr>
<td align="left"><tt>tie</tt> </td>
<td align="left">Indicates that the actor has neither won or lost the object. This
verb is generally only applicable when the object represents some form
of competition, such as a game.</td>
</tr>
<tr>
<td align="left"><tt>unfavorite</tt> </td>
<td align="left">Indicates that the actor has removed the object from the collection
of favorited items.</td>
</tr>
<tr>
<td align="left"><tt>unlike</tt> </td>
<td align="left">Indicates that the actor has removed the object from the collection
of liked items.</td>
</tr>
<tr>
<td align="left"><tt>unsatisfy</tt> </td>
<td align="left">Indicates that the actor has not satisfied the object. If a target
is specified, it indicates the context within which the object was not
satisfied. For instance, if a person fails to satisfy the requirements
of some particular challenge, the person is the actor; the requirement
is the object and the challenge is the target.</td>
</tr>
<tr>
<td align="left"><tt>unsave</tt> </td>
<td align="left">Indicates that the actor has removed the object from the collection
of saved items.</td>
</tr>
<tr>
<td align="left"><tt>unshare</tt> </td>
<td align="left">Indicates that the actor is no longer sharing the object. If a
target is specified, it indicates the entity with whom the object is
no longer being shared.</td>
</tr>
<tr>
<td align="left"><tt>update</tt> </td>
<td align="left">The "update" verb indicates that the actor has modified the
object. Use of the "update" verb is generally reserved to indicate
modifications to existing objects or data such as changing an existing
user's profile information.</td>
</tr>
<tr>
<td align="left"><tt>use</tt> </td>
<td align="left">Indicates that the actor has used the object in some manner.</td>
</tr>
<tr>
<td align="left"><tt>watch</tt> </td>
<td align="left">Indicates that the actor has watched the object. This verb is
typically applicable only when the object represents dynamic, visible
content such as a movie, a television show or a public performance.
This verb is a more specific form of the verbs "experience", "play"
and "consume".</td>
</tr>
<tr>
<td align="left"><tt>win</tt> </td>
<td align="left">Indicates that the actor has won the object. This verb is typically
applicable only when the object represents some form of competition,
such as a game.</td>
</tr>
</table>
<br clear="all" />
<a name="object-types"></a><br /><hr />
<table summary="layout" cellpadding="0" cellspacing="2" class="TOCbug" align="right"><tr><td class="TOCbug"><a href="#toc"> TOC </a></td></tr></table>
<a name="rfc.section.3"></a><h3>3.
Object Types</h3>
<p>The table contains the core set of common objectTypes in addition
to the <tt>activity</tt> objectType defined in
Section 7 of <a class='info' href='#activitystreams'>[activitystreams]<span> (</span><span class='info'>Snell, J., Atkins, M., Norris, W., Messina, C., Wilkinson, M., and R. Dolin, “JSON Activity Streams 1.0,” May 2011.</span><span>)</span></a>.
</p>
<p>All Activity Stream Objects inherit the same fundamental set of
basic properties as defined in section 3.4 of <a class='info' href='#activitystreams'>[activitystreams]<span> (</span><span class='info'>Snell, J., Atkins, M., Norris, W., Messina, C., Wilkinson, M., and R. Dolin, “JSON Activity Streams 1.0,” May 2011.</span><span>)</span></a>.
In addition to these, objects of any specific type are permitted to
introduce additional optional or required properties that are meaningful
to objects of that type.
</p><table class="full" border="1" cellpadding="2" cellspacing="2">
<col align="left" width="15%"><col align="left">
<tr><th align="left">Object Type</th><th align="left">Description</th></tr>
<tr>
<td align="left"><tt>alert</tt> </td>
<td align="left">Represents any kind of significant notification.</td>
</tr>
<tr>
<td align="left"><tt>application</tt> </td>
<td align="left">Represents any kind of software application.</td>
</tr>
<tr>
<td align="left"><tt>article</tt> </td>
<td align="left">Represents objects such as news articles, knowledge base entries,
or other similar construct. Such objects generally consist of paragraphs
of text, in some cases incorporating embedded media such as photos
and inline hyperlinks to other resources.</td>
</tr>
<tr>
<td align="left"><tt>audio</tt> </td>
<td align="left">Represents audio content of any kind. Objects of this type MAY
contain an additional property as specified in <a class='info' href='#audio-video'>Section 3.1<span> (</span><span class='info'>Audio and Video Objects</span><span>)</span></a>.</td>
</tr>
<tr>
<td align="left"><tt>badge</tt> </td>
<td align="left">Represents a badge or award granted to an object (typically a
<tt>person</tt> object)</td>
</tr>
<tr>
<td align="left"><tt>binary</tt> </td>
<td align="left">Objects of this type are used to carry arbirary Base64-encoded
binary data within an Activity Stream object. It is primarily
intended to attach binary data to other types of objects through
the use of the <tt>attachments</tt> property.
Objects of this type will contain the additional properties specified in
<a class='info' href='#binary'>Section 3.2<span> (</span><span class='info'>Binary Objects</span><span>)</span></a>.</td>
</tr>
<tr>
<td align="left"><tt>bookmark</tt> </td>
<td align="left">Represents a pointer to some URL -- typically a web page. In most
cases, bookmarks are specific to a given user and contain metadata
chosen by that user. Bookmark Objects are similar in principle to the
concept of bookmarks or favorites in a web browser. A bookmark
represents a pointer to the URL, not the URL or the associated resource
itself. Objects of this type SHOULD contain an additional
<tt>targetUrl</tt> property whose value is a
String containing the IRI of the target of the bookmark.</td>
</tr>
<tr>
<td align="left"><tt>collection</tt> </td>
<td align="left">Represents a generic collection of objects of any type. This object
type can be used, for instance, to represent a collection of files
like a folder; a collection of photos like an album; and so forth.
Objects of this type MAY contain an additional <tt>objectTypes</tt>
property whose value is an Array of Strings specifying the expected
objectType of objects contained within the collection.</td>
</tr>
<tr>
<td align="left"><tt>comment</tt> </td>
<td align="left">Represents a textual response to another object. Objects of this
type MAY contain an additional <tt>inReplyTo</tt>
property whose value is an Array of one or more other Activity Stream
Objects for which the object is to be considered a response.</td>
</tr>
<tr>
<td align="left"><tt>device</tt> </td>
<td align="left">Represents a device of any sort.</td>
</tr>
<tr>
<td align="left"><tt>event</tt> </td>
<td align="left">Represents an event that occurs at a certain location during
a particular period of time. Objects of this type MAY contain the
additional properties specified in <a class='info' href='#event'>Section 3.3<span> (</span><span class='info'>Event</span><span>)</span></a>.</td>
</tr>
<tr>
<td align="left"><tt>file</tt> </td>
<td align="left">Represents any form of document or file. Objects of this type
MAY contain an additional <tt>fileUrl</tt>
property whose value a dereferenceable IRI that can be used to
retrieve the file; and an additional <tt>mimeType</tt>
property whose value is the MIME type of the file described by the
object.</td>
</tr>
<tr>
<td align="left"><tt>game</tt> </td>
<td align="left">Represents a game or competition of any kind.</td>
</tr>
<tr>
<td align="left"><tt>group</tt> </td>
<td align="left">Represents a grouping of objects in which member objects can
join or leave.</td>
</tr>
<tr>
<td align="left"><tt>image</tt> </td>
<td align="left">Represents a graphical image. Objects of this type MAY contain
an additional <tt>fullImage</tt> property whose
value is an Activity Streams Media Link to a "full-sized" representation
of the image.</td>
</tr>
<tr>
<td align="left"><tt>issue</tt> </td>
<td align="left">Represents a report about a problem or situation that needs to
be resolved. For instance, the <tt>issue</tt> object
can be used to represent reports detailing software defects, or
reports of acceptable use violations, and so forth. Objects of this
type MAY contain the additional properties specified in <a class='info' href='#issue'>Section 3.4<span> (</span><span class='info'>Issue</span><span>)</span></a>.</td>
</tr>
<tr>
<td align="left"><tt>job</tt> </td>
<td align="left">Represents information about a job or a job posting.</td>
</tr>
<tr>
<td align="left"><tt>note</tt> </td>
<td align="left">Represents a short-form text message. This object is intended
primarily for use in "micro-blogging" scenarios and in systems
where users are invited to publish short, often plain-text messages
whose useful lifespan is generally shorter than that of an article
of weblog entry. A note is similar in structure to an article, but
typically does not have a title or distinct paragraphs and tends to
be much shorter in length.</td>
</tr>
<tr>
<td align="left"><tt>offer</tt> </td>
<td align="left">Represents an offer of any kind.</td>
</tr>
<tr>
<td align="left"><tt>organization</tt> </td>
<td align="left">Represents an organization of any kind.</td>
</tr>
<tr>
<td align="left"><tt>page</tt> </td>
<td align="left">Represents an area, typically a web page, that is representative
of, and generally managed by a particular entity. Such areas are
usually dedicated to displaying descriptive information about the
entity and showcasing recent content such as articles, photographs and
videos. Most social networking applications, for example, provide
individual users with their own dedicated "profile" pages. Several
allow similar types of pages to be created for commercial entities,
organizations or events. While the specific details of how pages
are implemented, their characteristics and use may vary, the one
unifying property is that they are typically "owned" by a single
entity that is represented by the content provided by the page itself.</td>
</tr>
<tr>
<td align="left"><tt>person</tt> </td>
<td align="left">Represents an individual person.</td>
</tr>
<tr>
<td align="left"><tt>place</tt> </td>
<td align="left">Represents a physical location. Locations can be represented
using geographic coordinates, a physical address, a free-form
location name, or any combination of these. Objects of this type
MAY contain the additional properties specified in
<a class='info' href='#place'>Section 3.5<span> (</span><span class='info'>Place</span><span>)</span></a>.</td>
</tr>
<tr>
<td align="left"><tt>process</tt> </td>
<td align="left">Represents any form of process. For instance, a long-running
task that is started and expected to continue operating for a
period of time.</td>
</tr>
<tr>
<td align="left"><tt>product</tt> </td>
<td align="left">Represents a commercial good or service. Objects of this type
MAY contain an additional <tt>fullImage</tt>
property whose value is an Activity Streams Media Link to an image
resource representative of the product.</td>
</tr>
<tr>
<td align="left"><tt>question</tt> </td>
<td align="left">Represents a question or a poll. Objects of this type MAY contain
an additional <tt>options</tt> property whose value
is an Array of possible answers to the question in the form of
Activity Stream objects of any type.</td>
</tr>
<tr>
<td align="left"><tt>review</tt> </td>
<td align="left">Represents a primarily prose-based commentary on another object.
Objects of this type MAY contain a <tt>rating</tt>