-
Notifications
You must be signed in to change notification settings - Fork 0
/
index.html
233 lines (214 loc) · 9.85 KB
/
index.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
<!DOCTYPE html>
<html>
<head>
<title>Social Web Use Cases and Requirements</title>
<meta charset='utf-8'>
<script src='http://www.w3.org/Tools/respec/respec-w3c-common'
async class='remove'></script>
<script class='remove'>
var respecConfig = {
// specification status (e.g. WD, LCWD, WG-NOTE, etc.). If in doubt use ED.
specStatus: "unofficial",
// the specification's short name, as in http://www.w3.org/TR/short-name/
shortName: "socal-ucr",
// if your specification has a subtitle that goes below the main
// formal title, define it here
// subtitle : "an excellent document",
// if you wish the publication date to be other than the last modification, set this
// publishDate: "2009-08-06",
// if the specification's copyright date is a range of years, specify
// the start date here:
// copyrightStart: "2005"
// if there is a previously published draft, uncomment this and set its YYYY-MM-DD date
// and its maturity status
// previousPublishDate: "1977-03-15",
// previousMaturity: "WD",
// if there a publicly available Editor's Draft, this is the link
// edDraftURI: "http://berjon.com/",
// if this is a LCWD, uncomment and set the end of its review period
// lcEnd: "2009-08-05",
// editors, add as many as you like
// only "name" is required
editors: [
{
name: "elf Pavlik"
, url: "http://wwelves.org/perpetual-tripper"
, company: "hackers4peace"
, companyURL: "http://hackers4peace.net"
}
],
authors: [
{
name: "elf Pavlik"
, url: "http://wwelves.org/perpetual-tripper"
, company: "hackers4peace"
, companyURL: "http://hackers4peace.net"
}
],
// name of the WG
wg: "In Charge Of This Document Working Group",
// URI of the public WG page
wgURI: "http://example.org/really-cool-wg",
// name (without the @w3c.org) of the public mailing to which comments are due
wgPublicList: "spec-writers-anonymous",
// URI of the patent status for this WG, for Rec-track documents
// !!!! IMPORTANT !!!!
// This is important for Rec-track documents, do not copy a patent URI from a random
// document unless you know what you're doing. If in doubt ask your friendly neighbourhood
// Team Contact.
wgPatentURI: "",
// !!!! IMPORTANT !!!! MAKE THE ABOVE BLINK IN YOUR HEAD
};
</script>
</head>
<body>
<section id='abstract'>
<p>
This is the abstract for your specification.
</p>
</section>
<section id='sotd'>
<p>
You need to have a custom SotD paragraph. Maybe give a succinct description of your spec's
status.
</p>
</section>
<section>
<h2>Scope and Motivation</h2>
</section>
<section>
<h2>Organization of this Document</h2>
</section>
<section>
<h2>User Stories</h2>
<section>
<h3>Posting a Note</h3>
<ol>
<li> Eric writes a short note to be shared with his followers.
</li>
<li> After posting the note, he notices a spelling error. He edits the note and re-posts it.
</li>
<li> Later, Eric decides that the information in the note is incorrect. He deletes the note.
</li>
</ol>
<a href="https://www.w3.org/wiki/Socialwg/Social_API/User_stories#">Social WG wiki version</a>
</section>
<section>
<h3>Reading Recent Posts</h3>
<ol>
<li> Iris finds a comment by Sam on one of her photos funny. She'd like to read more posts by Sam.
</li>
<li> Iris reads the latest notes by Sam. She also reviews his latest photos.
</li>
</ol>
<a href="https://www.w3.org/wiki/Socialwg/Social_API/User_stories#Reading_a_user.27s_recent_posts">Social WG wiki version</a>
</section>
<section>
<h3>Following</h3>
<ol>
<li> Delano meets Beth at a company meeting. They are both user interface designers. He finds her ideas interesting.
</li>
<li> Delano follows Beth on their company social network.
</li>
<li> Beth posts a photo from a whiteboarding session at a company retreat.
</li>
<li> Delano sees the photo in his inbox stream.
</li>
<li> Ted, Delano's coworker, wants to find new people to follow. He looks at the list of people that Delano follows. He finds Beth in the list, reads her stream, enjoys it, and decides to follow her, too.
</li>
<li> Beth posts frequently. Delano is having a hard time reading his inbox stream because Beth's activities drown out everyone else's. He stops following Beth.
</li>
</ol>
<a href="https://www.w3.org/wiki/Socialwg/Social_API/User_stories#Following_a_person">Social WG wiki version</a>
</section>
<section>
<h3>Inbox</h3>
<ol>
<li> Jake is bored at work. He checks his social inbox stream to see what his friends, family, and coworkers are up to.
</li>
<li> Jake sees in his social stream a note by Tammy about her new apartment. Tammy is his friend.
</li>
<li> Jake sees in his social stream a photo by Edith from her concert last night. Jake follows Edith but Edith doesn't know Jake. Edith has thousands of followers.
</li>
<li> Jake sees in his social stream a video from Damon. Damon and Jake are both in the "Boxing Fans" group. Damon posted the video to the group.
</li>
<li> Jake sees in his social stream a sound file from Carol. Carol is Jake's wife. The sound file is a reminder to stop for groceries after work. Carol posted the sound file only for Jake.
</li>
<li> Jake sees in his social stream that his friend Tammy has added a new friend, Denise. Jake remembers Denise from high school. Jake requests to add Denise as a friend, too.
</li>
</ol>
<a href="https://www.w3.org/wiki/Socialwg/Social_API/User_stories#Inbox">Social WG wiki version</a>
</section>
<section>
<h3>Direct Messaging</h3>
<ol>
<li> Kyle wants to tell Lisa something privately.
</li>
<li> Kyle sends her a message that no one else can view.
</li>
<li> Lisa is notified she has a message.
</li>
<li> Lisa reads the message and responds privately.
</li>
</ol>
<a href="https://www.w3.org/wiki/Socialwg/Social_API/User_stories#Direct_Messaging">Social WG wiki version</a>
</section>
<section>
<h3>Adding Recommendations to Bestpoke Software</h3>
<ol>
<li> James maintains an application for managing architectural designs
</li>
<li> Maggie, a senior architect would like to recommend many of the better designs
</li>
<li> James uses an existing liking service which allows him to post any recommendations, to provide this
</li>
<li> This service also allows James to present existing likes for the design in question
</li>
<li> Maggie gets to like specific designs, and her followers see these as do viewers of these designs
</li>
<li> James achieves this with a simple inclusion on the associated web page, but could have chosen a more detailed integration if greater control was needed over the user interface
</li>
</ol>
<a href="https://www.w3.org/wiki/Socialwg/Social_API/User_stories#Integration_:_Adding_recommendations_to_bespoke_software">Social WG wiki version</a>
</section>
<section>
<h3>Adding Comments to Bestpoke Software</h3>
<ol>
<li> Maria, an IT Architect, has been tasked with encouraging better collaboration on the development of her companies Industrial Processes
</li>
<li> As these processes are tightly controlled (though generally visible) an associated discussion and evangelisation capability is required
</li>
<li> Maria integrates with an existing comment capability to store and retrieve comments rather than redeveloping
</li>
<li> May-Ling sees the comment area with the Processes and suggests changes, as she herself does not have rights to update
</li>
<li> The process owner gets a notification that someone has commented on this Process
</li>
<li> Followers of both the Process owner and May-Ling will see this comment event
</li>
<li> Maria achieves this with a simple inclusion on the associated web page, but could have chosen a more detailed integration if greater control was needed over the user interface
</li>
</ol>
<a href="https://www.w3.org/wiki/Socialwg/Social_API/User_stories#Integration_:_Adding_comments_to_bespoke_software">Social WG wiki version</a>
</section>
</section>
<section>
<h2>Use Cases</h2>
</section>
<section>
<h2>Requiements</h2>
<section>
<h3>Functional Requirements</h3>
</section>
<section>
<h3>Non-Functional Requirements</h3>
</section>
</section>
<section class='appendix'>
<h2>Acknowledgements</h2>
<p>
Many thanks to Robin Berjon for making our lives so much easier with his cool tool.
</p>
</section>
</body>
</html>