Re: FW: User stories for Social API

Thanks Ann!

In particular, these are Social API user stories. The Social API is a 
REST API provided by a social network for Web and native applications.

The way I think of this API is: what things can you do from a 
third-party iOS client? Posting pictures is probably one thing; creating 
a new user account, say, would be out of scope.

There is a lot to the social web that's not encompassed by the 
client-to-server API.

I'll be on the call today and I'd be happy to present these stories and 
answer any questions.

-Evan

On 2015-02-04 02:39 AM, Bassetti, Ann wrote:
>
> Greetings Social Web IG folks –
>
> Today, Evan Prodromou created an excellent succinct list of social web 
> user "stories".  Link and explanation below.
>
> I know I'm sending this very late (west coast USA), but it would be 
> really helpful if you could read this list before our meeting tomorrow 
> morning. Did he forget any significant user stories?  Any specific 
> steps you would add to a story?  Note that Evan also included some 
> "developer" stories.  If you are a developer, think about how would 
> you use the eventual W3C standard and APIs?
>
> Looking forward to the conversation – Ann
>
> *From:*Evan Prodromou [mailto:evan@e14n.com]
> *Sent:* Tuesday, February 03, 2015 9:23 PM
> *To:* public-socialweb@w3.org
> *Subject:* User stories for Social API
>
> Per our discussion on the telecon this afternoon, I've posted a first 
> draft of some user stories on the wiki here:
>
> https://www.w3.org/wiki/Socialwg/Social_API/User_stories
>
> I've tried to capture in narrative form with named actors the 
> requirements from the Requirements page. I've tried to keep the user 
> stories short (~5 steps), and keep them clustered around an functional 
> theme.
>
> This has usually been successful with the exception of the Groups user 
> story, which has about 11 steps.
>
> I also tried to capture some developer stories, to give an indication 
> of how I think developers will use the standard and the APIs that 
> implement it.
>
> https://www.w3.org/wiki/Socialwg/Social_API/User_stories#Proposed_developer_stories
>
> I think it's probably worthwhile to keep these to make evaluating API 
> proposals easier.
>
> Please:
>
>   * Feel free to update the user stories.
>   * Try to keep them roughly within the boundaries I've defined above
>     (narrative form, ~5 steps, clustered around a theme)
>   * Remember that API != UI. It's probably bad to assume that users
>     will "push a button" or "go to a Web page".
>   * Talk to me by email before reorganizing the entire page to meet
>     your personal idea of "user story".
>   * Don't add votes yet. These user stories are still in flux and it's
>     going to be awkward if we have to work around your vote.
>
> Thanks,
>
> -Evan
>