This repository was archived by the owner on Mar 15, 2022. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 0
/
Copy pathvocabulary.html
102 lines (102 loc) · 4.58 KB
/
vocabulary.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
<!DOCTYPE html>
<html lang="en">
<head>
<meta charset="UTF-8">
<title>Intent Class in Activity Streams 2.0 Vocabulary</title>
</head>
<body>
<h1>Intent Class In Activity Streams 2.0 Vocabulary</h1>
<p>Author: Akihiko Odaki <<a href="mailto:[email protected]">[email protected]</a>></p>
<p>Copyright © 2017 Akihiko Odaki. Licensed under
<a href="https://creativecommons.org/publicdomain/zero/1.0/deed.en">CC0
1.0</a>.</p>
<section>
<h2>Abstract</h2>
<p>This specification describes <code>Intent</code> class in Activity
vocabulary. It is intended to be used in the context of the
ActivityStreams 2.0 format and provides an extension for [Activity
Vocabulary] to implement intent feature with Activity Streams 2.0.</p>
<section>
<h3>Author's Note</h3>
<p><i>This section is non-normative.</i></p>
<p>This draft is written to implement intent feature in Mastodon, an
Activity Streams implementation. This draft is heavily influenced by
[Activity Vocabulary]. The author is glad to use Mastodon utilizing
the format, and hope further development and other applications of
Activity Streams. Some portions of [Activity Vocabulary] are used in
this document.</p>
</section>
</section>
<section>
<h2>Status of This Document</h2>
<p><i>This section describes the status of this document at the time of
its publication. Other documents may supersede this document.</i></p>
<p>This document was published by the author as a proposal for Mastodon
and other Activity Streams applications. Please write comments
regarding this document to the following issue in Mastodon:<br>
<a href="https://github.com/tootsuite/mastodon/issues/2291">URL scheme
for remote follow, share buttons · Issue #2291 ·
tootsuite/mastodon</a></p>
<p>This document is expected to be useful also for other Activity Streams
applications. If you have any request to change for them, please
contact the author. E-mail is the most reliable means for that, but
OStatus2 is also acceptable. Send a note to
<a href="https://pawoo.net/@fn_aki">@[email protected]</a>.</p>
</section>
<section>
<h2>1. Introduction</h2>
<p>[Activity Vocabulary] defines Activity class for Activity Streams. This
document defines vocabulary properties to describe an intent for
activities represented by the class.</p>
<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 [RFC2119].</p>
</section>
<section>
<h2>2. Intent Class</h2>
<section>
<h3>2.1 URI</h3>
<p><code>Intent</code> class is identified with the following URI:
<code>https://akihikodaki.github.io/activity-intent/ns#Intent</code></p>
<p>The URI is temporary and subject to later change.</p>
</section>
<section>
<h3>2.2 Subtype and Semantics</h3>
<p>An intent is a subtype of <code>IntransitiveActivity</code>. An
intent is about an activity.</p>
</section>
<section>
<h3>2.3 object property</h3>
<p><code>object</code> property describes an activity intended to be
performed.</p>
</section>
<section>
<h3>2.4 Example</h3>
<p><i>This section is non-normative.</i></p>
<pre><code>{
"@context": "https://www.w3.org/ns/activitystreams",
"type": "https://akihikodaki.github.io/activity-intent/ns#Intent",
"summary": "Mallory is going to follow someone",
"actor": "https://example.net/~mallory",
"object": {
"type": "Follow"
}
}</code></pre>
<p>An user agent received the above intent MAY ask Mallory the person to
be followed.</p>
</section>
</section>
<section>
<h2>A. References</h2>
<dl>
<dt>[Activity Vocabulary]</dt>
<dd>James M Snell; Evan Prodromou. W3C. URL:
<a href="https://www.w3.org/TR/activitystreams-vocabulary/">https://www.w3.org/TR/activitystreams-vocabulary/</a></dd>
<dt>[RFC2119]</dt>
<dd>Key words for use in RFCs to Indicate Requirement Levels. S.
Bradner. IETF. March 1997. Best Current Practice. URL:
<a href="https://tools.ietf.org/html/rfc2119">https://tools.ietf.org/html/rfc2119</a></dd>
</dl>
</section>
</body>
</html>