Socialwg/AS2 CR

From W3C Wiki

published as https://www.w3.org/TR/2016/CR-activitystreams-core-20160906/ and https://www.w3.org/TR/2016/CR-activitystreams-vocabulary-20160906/. See also Socialwg/AS2 CR2.

To: the group (optionally), the acting Director, the domain lead, W3C Comm Team <w3t-comm@w3.org>, "chairs@w3.org" <chairs@w3.org>

Archived at: https://lists.w3.org/Archives/Public/public-socialweb/2016Jun/0094.html


Transition Request

This is a transition request for two documents to Candidate Recommendation.

Document title, URIs, and estimated publication date

The document Abstract and Status sections

Abstract:

  • Core: This specification details a model for representing potential and completed activities using the JSON format.
  • Vocab: This specification describes the Activity vocabulary.

SOTD:

  • Standard Respec

Decision to request transition

Changes

See https://w3c.github.io/activitystreams/core/#changelog and https://w3c.github.io/activitystreams/vocab/#changelog

Requirements satisfied

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:

A transfer syntax for social data such as activities (such as status updates) should include at least the ability to describe the data using URIs in an extensible manner, time-stamping, and should include a serialization compatible with Javascript (JSON) and possibly JSON-LD. Formats based on XML or other data serializations are out-of-scope.

https://www.w3.org/2013/socialweb/social-wg-charter

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.

Wide Review

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

Issues addressed

See issue tags and history

Formal Objections

None.

Implementations

Being gathered at https://github.com/w3c/activitystreams/tree/master/implementation-reports

Patent disclosures

None

News Item

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>.