- 1 Transition Request
- 1.1 Document title, URIs, and estimated publication date
- 1.2 The document Abstract and Status sections
- 1.3 Decision to request transition
- 1.4 Changes
- 1.5 Requirements satisfied
- 1.6 Dependencies met (or not)
- 1.7 Wide Review
- 1.8 Issues addressed
- 1.9 Formal Objections
- 1.10 Implementations
- 1.11 Patent disclosures
- 2 News Item
To: the group (optionally), the acting Director, the domain lead, W3C Comm Team <firstname.lastname@example.org>, "email@example.com" <firstname.lastname@example.org>
This is a transition request for two documents to Candidate Recommendation.
Document title, URIs, and estimated publication date
- "Activity Streams 2.0", and "Activity Vocabulary"
- Latest Published: https://www.w3.org/TR/activitystreams-core/ and https://www.w3.org/TR/activitystreams-vocabulary/
- Editor's Draft: https://w3c.github.io/activitystreams/core/ and https://w3c.github.io/activitystreams/vocab/
- Staged Draft: Not yet staged
- Publication Date: 2016-07-12
The document Abstract and Status sections
- Core: This specification details a model for representing potential and completed activities using the JSON format.
- Vocab: This specification describes the Activity vocabulary.
- Standard Respec
Decision to request transition
- RESOLVED: Take current WDs of AS2, with edits agreed in this telcon to CR
No formal requirements. Charter says:
The Working Group, in conjunction with Social Interest Group, will determine the use cases that derive the requirements for the deliverables. Features that are not implemented due to time constraints can be put in a non-normative "roadmap" document for future work. The scope will include:
The group produced:
Dependencies met (or not)
Normative References are all W3C Rec or RFC.
Charter Dependencies appear not relevant, except horizontal review in progress.
200+ issues on github.
Tally of who raised issues (including pull requests), with a count of issues followed by github username:
- In WG: 85 jasnell 57 evanp 49 elf-pavlik 11 dissolve 9 csarven 8 tantek 8 rhiaro 8 azaroth42 7 cwebber 6 dmitrizagidulin 6 aaronpk 5 kevinmarks 5 gobengo 4 akuckartz 2 sandhawke 1 xray7224 1 melvincarvalho 1 karlitschek 1 BigBlueHat 2 natalieesk 8 rpeinl
- In WG at some point: 9 dret 5 oshepherd 1 bblfish
- Never in WG: 3 sgoendoer 3 muratseyhan 3 MerelyAPseudonym 3 annando 2 lanthaler 2 alexanderkjeldaas 1 wirehead 1 tommorris 1 stevenroose 1 smarts 1 msporny 1 kleiinnn 1 harlantwood 1 abigdreamer
See issue tags and history
W3C invites implementations of ActivityStreams 2.0
The W3C <a href="https://www.w3.org/wiki/Socialwg/">Social Web Working Group</a> is calling for implementations of <a href="https://www.w3.org/TR/activitystreams-core">Activity Streams 2.0 Core</a> and <a href="https://www.w3.org/TR/activitystreams-vocabulary">Activity Streams 2.0 Vocabulary</a>, which are now Candidate Recommendations. Together, the ActivityStreams 2.0 specifications aim to provide a standard and extensible way to represent and pass around social data and streams of interactions on the Web. The Core specification provides a model for representing potential and completed social activities using the JSON format. The Vocabulary describes a number of common activity types and their properties to be used with the core. In particular, we encourage existing implementors of ActivityStreams 1.0 to upgrade to the new model, and the Core specification provides <a href="https://www.w3.org/TR/activitystreams-core/#activitystreams-1.0a">guidance for doing so</a>.