Welcome to the Social Web Working Group (SocialWG) home page (https://www.w3.org/Social/WG)!
Social Web Working Group
- 1 Social Web Working Group
- 2 Specifications
- 3 Participation
- 4 Discussion
- 5 Documentation
- 6 Implementations
- 7 Process
- 8 Media
- 9 Related Organizations
- 10 Applied for Membership
- 11 Invited Expert Approval
- 12 FAQ
- 13 Past
- 14 Home Page To Do
- 15 See Also
Specifications that the Social Web WG has produced and is working on.
- ActivityPub (Chris Webber, Jessica Tallon) (Editor's Draft, issues, Repo)
- Activity Streams Core (James Snell and Evan Prodromou) (Editor's Draft, Issues, Repo, implementations)
- Activity Streams Vocab (James Snell and Evan Prodromou) (Editor's Draft, Issues, Repo)
- Micropub (Aaron Parecki) (Editor's Draft, Issues, Repo, Implementations)
- Linked Data Notifications (Sarven Capadisli, Amy Guy) (Editor's Draft, Issues, Repo)
Iterating as working drafts:
- JF2 (Ben Roberts) (Editor's Draft, Issues, Repo)
- Post Type Discovery (Tantek Çelik) (Editor's Draft, Issues, Repo)
-  (Julien Genestoux, Aaron Parecki) (Issues, Repo) - formerly PubSub, formerly PubSubHubbub
- no more REC-track documents planned for current charter.
- List of github aliases of Social Web WG contributors: Socialwg/Github
- Resolutions - e.g. to accept & publish drafts, for controversial issues, etc.
Proposed documents to the working groups (as of 2016-09-23 only accepting documents proposed as Notes)
How to participate
To join this group
- W3C Members: If you are affiliated with a W3C member organization:
- Invited Experts: The chairs and staff may permit additional people with experience creating, building, and deploying social web implementations (especially on their own personal site) to join as "invited experts"; to pursue this option:
- Fill out the Invited Expert Application;
- Please indicate, in the form's "Additional information" field, how you expect to contribute to the work of the group, including describing your relevant expertise and motivation.
- The chairs will contact you in about a week. If you haven't heard anything in 10 days, feel free to send an email.
- Send any questions about this process to the staff contact, Sandro Hawke, or firstname.lastname@example.org.
If you are officially added to the group, you will automatically receive group email and your w3.org login and password will work on this wiki.
We currently use IRC, email, telcons, and face-to-face meetings for discussion:
The working group uses IRC nearly daily, and very actively during and after the telcons.
- One-click to join web interface: http://irc.w3.org/?channels=social
- Logs: http://socialwg.indiewebcamp.com/irc/social/today
The IRC channel is logged on the publicly-visible URL above. You can bookmark the URL and it will redirect to the current day.
You can get your photo to appear next to your name in the logs by:
- Add yourself to: IRC-people
We have two mailing lists for informal discussions for those that like email. You don't have to use them to participate in the working group.
- Dedicated to Social Web Working Group discussions. See public-socialweb archive. Read-write for WG members. Read-only for non-members.
- For Social Web public discussions. See public-socialweb-comments archive. Read-write for all, WG members and non-members alike.
Our two chairs -- Tantek and Evan -- rotate through chairing the telecons. Agenda items for a telecon should be posted to its wiki page by the Friday before, no guarantee of getting to anything posted after that. If the scheduled chair is unavailable when telcon time happens, the backup chair steps in. Chairs typically swap back to make up for missing their turn.
IRC is a key element of how W3C teleconferences are run, please join the IRC channel (#social) before dialing in!
- Join IRC (#social) before dialing in
- Join WebEx by following the instructions at https://www.w3.org/2015/10/social-wg-telecon. (Please keep those instructions secret.) If that link doesn't work for you, contact email@example.com.
Once you are connected to WebEx, select "Call Using Computer" (large 'button' on left), to have WebEx make the audio connection to you
- Choices: WebEx can call you, or you can call in.
- (Note: when using "Test Audio Connection", you will be muted).
If you cannot use WebEx, the host can initiate a call to you.
- The Chairs have a "host key". When one of them starts the WebEx session, they should enter that number, to be identified as the host.
- If anyone else is chairing, get host key from Tantek, Evan, or Sandro
- In "Participant" menu (top left), choose "Reclaim host role"
- Once you are the host, the "Invite and Remind" button becomes available (in middle of WebEx session screen)
- In the "Invite and Remind" window, select the tab for "Phone"
- Enter the person's name and phone number, and click "Call"
- That person will be called, and needs to follow the prompt ("press 1") to enter the meeting
Note we are no longer using Zakim for dialing-in, but we are still using IRC for meetings.
telcon: Social Web WG telcon:
- chair: Evan
- 2016-12-06 Telecon chair: Evan (Regrets: Tantek, at Moz mtg)
- 2016-12-13 Telecon chair: Evan (Regrets: Tantek, at AB mtg)
- 2016-12-20 Telecon chair: Tantek
- 2016-12-27 Telecon chair: Tantek (hoping to cancel this telcon)
Additional social web related future events:
- See https://indiewebcamp.com/events
In case you can not participate in next meeting, please add your name to Regrets section on Agenda page of next telecon. If you sending last minute regrets and don't have possibility to edit wiki page, please reply over mailing list on agenda thread already started by chair of this meeting. 
For record keeping it is important that everyone attending our teleconference is identified. W3C's IRC bot, Zakim, which helps facilitate meetings using IRC in conjunction with the W3C's audio teleconference bridge, can help identify you but there are cases when Zakim needs your input. It is therefore important that before you call in, you first join the IRC channel (#social) and monitor it. For more info on this refer to Zakim's page.
- 2016-11-29 Telecon, Minutes (pending approval)
- 2016-11-22 Telecon, Minutes
- 2016-11-17…18 F2F, Minutes Day 1 Minutes Day 2
- 2016-11-15 Telecon CANCELLED (as of 2016-11-0 8)
- 2016-11-08 Telecon, Minutes
- 2016-11-01 Telecon, Minutes
- 2016-10-25 Telecon, Minutes
- 2016-10-18 Telecon, Minutes
- 2016-10-11 Telecon, Minutes
- 2016-10-04 Telecon, Minutes
- 2016-09-27 Telecon CANCELED by backup chair Evan
- 2016-09-22..23 (ThF) Seventh Social Web F2F meeting at Lisbon, Portugal during W3C TPAC week
- 2016-09-21 Redecentralization and Social Web breakout session at TPAC, IRC Log / minutes
- 2016-09-20 Telecon canceled (TPAC week)
- 2016-09-13 Telecon, Minutes
- 2016-09-06 Telecon, Minutes
- 2016-08-23 Telecon, Minutes
- 2016-08-30 Telecon canceled
- 2016-08-23 Telecon, Minutes
- 2016-08-16 Telecon canceled (informal editor's IRC chat)
- 2016-08-09 Telecon canceled (informal editor's telcon)
- 2016-08-02 Telecon, Minutes
- 2016-07-26 Telecon, Minutes
- 2016-07-19 Telecon, Minutes
- 2016-07-12 Telecon, Minutes
- 2016-07-05 Telecon, Minutes
- 2016-06-28 Telecon, Minutes
- 2016-06-21 Telecon, Minutes
- 2016-06-14 telecon skipped - post f2f
- .. (MT) Sixth Social Web F2F meeting in Portland, OR, USA Minutes Day 1 Minutes Day 2 (awaiting approval)
- 2016-05-31 Telecon, Minutes
- 2016-05-24 Telecon, Minutes
- 2016-05-17 Telecon, Minutes
- 2016-05-10 Telecon, Minutes
- 2016-05-03 Telecon, Minutes
- 2016-04-26 Telecon, Minutes
- 2016-04-19 Telecon, Minutes
- 2016-04-12 Telecon, Minutes
- 2016-04-05 Telecon, Minutes
- 2016-03-29 Telecon, Minutes
- 2016-03-22 telecon canceled - W3C AC Meeting overlap (Arnaud, Sandro, Tantek, all busy)
- .. (WTh) Fifth Social Web F2F meeting at MIT in Cambridge, MA, USA (federated event: https://aaronparecki.com/2016/03/16/13/) Minutes Day 1 Minutes Day 2
- 2016-03-08 Telecon, Minutes
- 2016-03-01 Telecon, Minutes
- 2016-02-23 Telecon, Minutes
- 2016-02-16 Telecon, Minutes
- 2016-02-09 Telecon, Minutes
- 2016-02-02 Telecon, Minutes
- 2016-01-26 Telecon, Minutes
- 2016-01-19 Telecon, Minutes
- 2016-01-12 Telecon, Minutes
- 2016-01-05 Telecon, Minutes
- 2015-12-29 telecon canceled
- 2015-12-22 telecon canceled
- 2015-12-15 Telecon, Minutes
- 2015-12-08 Telecon, Minutes
- 2015-12-01 F2F in SF, Minutes: Day 1 Day 2
- 2015-11-24 Telecon, Minutes
- 2015-11-17 no telecon: many regrets, no urgent agenda items
- 2015-11-10 Telecon, Minutes
- 2015-11-03 Telecon, Minutes
- 2015-10-28 Social Web break out session during TPAC, Minutes
- 2015-10-27 no telecon, TPAC week
- 2015-10-20 Telecon, Minutes
- 2015-10-13 Telecon, Minutes
- 2015-10-06 Telecon, Minutes
- 2015-09-29 Telecon, Minutes
- 2015-09-22 Telecon, Minutes
- 2015-09-15 Telecon, Minutes
- 2015-09-08 Telecon, Minutes
- 2015-08-25 Telecon, Minutes
- 2015-08-11 Telecon, Minutes
- 2015-07-28 Telecon, Minutes
- 2015-07-14 Telecon, Minutes
- 2015-07-07 Telecon, Minutes
- 2015-06-30 Telecon, Minutes
- 2015-06-23 Telecon, Minutes
- 2015-06-16 Telecon, Minutes
- 2015-06-09 Telecon, Minutes
- 2015-06-02 Telecon, Minutes
- 2015-05-26 Telecon, Minutes
- 2015-05-19 Telecon canceled due to telephone bridge issues
- 2015-05-12 Telecon, Minutes
- 2015-05-04&05 Third Social Web F2F meeting at INRIA, Paris, Minutes for 04, Minutes for 05
- 2015-04-28 Telecon, Minutes
- 2015-04-21 Telecon, Minutes
- 2015-04-14 Telecon, Minutes
- 2015-04-07 Telecon, Minutes
- 2015-03-31 Telecon, Minutes
- 2015-03-24 Telecon, Minutes
- 2015-03-17&18 F2F (MIT), Minutes for 17, Minutes for 18
- 2015-03-10 Telecon, Minutes
- 2015-03-03 Telecon, Minutes
- 2015-02-24 Telecon, Minutes
- 2015-02-17 Telecon, Minutes
- 2015-02-10 Telecon, Minutes
- 2015-02-03 Telecon, Minutes
- 2015-01-27 Telecon, Minutes
- 2015-01-20 Telecon, Minutes
- 2015-01-13 Telecon, Minutes
- 2015-01-06 Telecon, Minutes
- 2014-12-16 Telecon, Minutes
- 2014-12-09 Telecon, Minutes
- 2014-12-02 Telecon, Minutes
- 2014-11-25 Telecon, Minutes
- 2014-11-18 Telecon, Minutes
- 2014-11-11 Telecon, Minutes
- 2014-11-04 Telecon, Minutes
- 2014-10-27&28 F2F (at TPAC), List of registrants
- 2014-10-21 Telecon, Minutes
- 2014-10-14 Telecon, Minutes
- 2014-10-07 Telecon, Minutes
- 2014-09-30 Telecon, Minutes
- 2014-09-23 Telecon, Minutes
- 2014-09-16 Telecon, Minutes
- 2014-09-09 Telecon, Minutes
- 2014-09-02 Telecon, Minutes
- 2014-08-26 Telecon, IRC log - First formal WG call
- 2014-08-19 Telecon, IRC log - Informal call
- 2014-08-12 Telecon, IRC log - Informal call
- 2014-08-05 Telecon, IRC log - Informal call
- 2014-07-29 Telecon, IRC log - Informal call
- 2014-07-09 IRC log - Chairs meeting
- 2014-05-14 IRC log - Chairs meeting
- Scribes list - who's next? If it's you, you may want to check Scribe 101 and Common Scribe Manual and keep in mind key scribing prefixes:
- Scribe: Topic: subtopic: PROPOSED: RESOLVED:
As a scribe, after you're done minuting into IRC for a given date, e.g. 2014-10-14:
- Get the source of http://www.w3.org/2014/10/14-social-minutes.html (should have been generated by RRSAgent after chair asked for "trackbot, end meeting" in IRC)
- Convert from HTML to Mediawiki syntax, either:
- Use Socialwg/2014-10-07-minutes as a template to create Socialwg/2014-10-14-minutes
- Add any resolutions from the meeting to Socialwg/resolutions
To document proposals, ideas, even specifications that are social web related, please create pages for them on this wiki and add a link to them from here.
You may preface your page names with "socialwg/" if you pick a particularly generic name and/or wish to indicate the scope in the name.
Social Web Glossary - precise definitions for terms we use in specs and documentation
So far WG adopted only one use case from previous work in this field: SWAT0
- Main effort moved to Task Force in Interest Group - Socialig/Use_Case_TF
Social Data Syntax
- Social syntax
- Collection Comparison
- Online Identity
- User Stories
Main effort moved to Task Force in Interest Group - Socialig/Vocabulary_TF
Inputs Into SocialWG
Inputs into SocialWG, including specs from External Groups explicitly listed in the Charter.
See #Specifications at the top of this page for Activity Streams editor's drafts, issues, and github repo links.
Adopted into the group (see [#Specifications]] at the top of this page)
Work we don't expect to accomplish as part of this charter but which we need to keep in mind while making decisions about the architecture. This includes both work that is already partly defined, and work that isn't but falls outside of our charter.
Documentation which is abstract (i.e. lacking documented real world use-cases).
There are likely additional documents above that need to be moved here.
The Social Web Working Group workmode is roughly as follows, and may be iterated based on group experience:
- GitHub - for all specifications and technical issues
- #Discussion - use IRC, telcons, email for discussion only
- #Documentation - capture proposals and conclusions here on the wiki
Issues for each specification are managed in the GitHub repo for each specification. See top of page for those links.
Issues and Actions for the working group overall were managed via the W3C Tracker. See Social Web WG Tracker.
resolutions will be highlighted in minutes, and people not at meeting can bring up their concerns within the following week
A rough schedule for the work of the WG, originally based on Social Web WG Charter Milestones.
Social data syntax
- Review: Jul-Sep 2014
- Commit: Oct 2014
- First public working drafts: AS2 Oct 2014 (and PTD Jul 2016)
- LC: likely late 2015/early 2016 (charter v1 said Q3 2015)
- CR: Q3 2016 (charter v1 said Q4 2015)
- Test Suite Feature Complete:
- 2016-10-18 Activitystreams.rocks test suite feature complete
- PR: likely Feb 2017 (charter v1 said Q2 2016)
- REC: possibly Mar 2017 (charter v1 said Q3 2016)
- 2016-12-31 Charter period ends (proposing extension til 2017-06-30)
- Review: Nov 2014 - ongoing (original review end date was Mar 2015)
- Commit: Dec 2015 decided to develop both Micropub and ActivityPub as Working Drafts
- First public working drafts: Jan 2016 (charter v1 said Q3 2014)
- LC: Q2/Q3 2016 (charter v1 said Q3 2015)
- CR: Q3/Q4 2016 (charter v1 said Q4 2015)
- Test Suite Feature Complete:
- 2016-10-18 Micropub.rocks test suite feature complete
- PR: likely Jan/Feb 2017 (charter v1 said Q2 2016)
- REC: likely Feb/Mar 2017 (charter v1 said Q3 2016)
- 2016-12-31 Charter period ends (proposing extension til 2017-06-30)
- Review: completed with three approaches
- Commit: Webmention, ActivityPub server to server (see above for links), LDN
- Dec 2015 decided to start with Webmention
- First public working draft: Jan, Jul, Oct 2016 (charter v1 was Q4 2014, then Aug 2015)
- LC: Q2 2016 (charter v1 said Q4 2015)
- CR: Q2&Q4 2016 (charter v1 said Q2 2016)
- Test Suite Feature Complete:
- 2016-05-30 Webmention.rocks test suite feature complete
- PR: Q4 2016 (charter v1 said Q3 2016)
- 2016-11-01 Webmention PR
- REC: likely Q4 2016 (charter v1 said Q4 2016)
- 2016-12-31 Charter period ends.
The Social Web Working Group actively coordinates with several other groups, organizations, and communities.
- HTML Working Group (transitioned to Web Platform Working Group)
- Web Applications Working Group
- WebAppSec Working Group and Web Security Interest Group
- Linked Data Platform WG
- Privacy Interest Group
- Protocols and Formats Working Group
- Web and Mobile Interest Group
- Federated Social Web CG
- Social Business Community Group
- IndieWebCamp Community
- Internet Engineering Task Force
- ActivityStreams Community
- Open Mobile Alliance (Social Network Web)
Additional Active Coordination
In addition to the above, the working group has been actively coordinating with:
and previously (2014?) Socialig/Liaison_TF did some early coordination.
All Social Web Related CGs
Current incubation CG:
- Social Web Incubator CG (SWICG)
The following CGs either incubated drafts which the working group took on, previously worked on or otherwise contributed in-charter-scope materials/ideas to the working group, and are planned for closure and incorporation into SWICG.
- PubSubHubbub CG (incubated PubSub spec)
- Federated Social Web CG
- ActivityPub CG
- Microposts CG
- Ostatus CG
Other Misc Groups
Other groups that were previously listed here but either nothing that was incoporated into anything in the working group, or orthogonal building blocks (could likely trim this section or move to a separate page)
- JSON for Linking Data CG / JSON-LD
- Hydra CG represented by Markus Lanthaler
- Web Schemas / schema.org
- Credentials CG
- Data Shapes WG
- RWW CG
- WebID CG
- Unhosted Web CG
- ODRL Policy CG - Web Usage/Privacy Permissions - represented by Renato Iannella
- Unhosted Movement
- DCENT Project mentioned in http://www.w3.org/Social/
Applied for Membership
Tantek Çelik has encouraged people who have applied for invited expert membership to list themselves here, but there is no requirement to do so.
Include the date you submitted the form.
- Michael Vogel Friendica maintainer github No Application Received. After applying, put the date here.
Invited Expert Approval
To be approved as an invited expert, one or more of the chairs and/or W3C staff contact and/or their management have to vouch for you. They likely have different criteria for vouching, and may or may not document (all of) their criteria publicly. E.g. chairs & staff contacts:
- For me, an expert on the social web MUST be actively publishing social content on their own website. Merely sharecropping on silos or contributing to open source projects only makes you a hobbyist, not an "expert". -Tantek
- For me, an invited expert should be implementing social software, or represent a company implementing social software.
Arnaud Le Hors
- Given the applicability of this technology behind the firewall of an enterprise, I don't share Tantek's view on what constitutes an expert in the matter.
- In keeping with the W3C Process I will consider applications for Invited Expert status on a case by case basis. It's fair to say that I'm rather conservative in that matter, which means that by default requests will be declined. Invited Experts are typically well known to the community through participation in different forums, conferences, etc. When that's not the case, applicants have the burden of convincing the chairs and Team that they should still be granted this status by explaining why. Invited Expert status is a privilege, not a right.
Please add questions which have been answered in IRC by the chairs here:
Am I Relevant To This WG
Q: Am I important or relevant to this working group?
A: Do you:
- implement social web technologies?
- or publish social content on a website you control? (social content, from you to others, regarding yourself and/or others, blogrolls (e.g. using XFN for social relationships, e.g. http://schepers.cc/ )
Or both? In either case, the working group can use your input relating to your personal experience with doing so.
Q: Will the teleconference call audio be made public after the meeting?
A: No. However, they will be annotated by a scribe and minutes will be made publicly available shortly after a working group meeting. For example socialwg/2014-09-02-minutes.
What is the role of the WG IG CG
Note: Social IG has been closed. Federated Social Web CG is being transitioned to Social Web Incubator CG.
Q: We should clarifiy the role of Social Web WG & IG and Federated Social Web CG?
A: Community groups are free form, can produce documents but binding only to members of that community group. Working groups are in charge of producing actual specifications and have set time to deliver. The Social Web Working Group (WG) has a charter with fairly specific deliverables (syntax, API, protocol) that it is focusing on. The Social Web Interest Group also had a charter which is focused on the research and documentation of social web use-cases.
Some background and past of the working group.
Previous W3C Groups
- 2012-10-26 Federated Social Web Summit (notes, etherpad)
- 2012-10-31 TPAC Plenary breakout session: "Social Web" (minutes, IRC log)
- 2013-08-07..08 W3C Workshop on Social Standards in San Francisco, CA, USA - generated sufficient interest to drive the creation of this working group
Unofficial social media created by former working group participants:
- Facebook group
- https://www.facebook.com/social.w3.org (UNOFFICIAL, run by WG participant elf Pavlik)
- Appears to have nothing to do with actual work done in the group.
- Twitter account
- https://twitter.com/SocialWebWG (UNOFFICIAL, was run by Erik Wilde, WG participant til 2015-07-07)
- Anyone have contact info for Erik? Can you get the keys to @SocialWebWG and send them to to chairs? - Tantek Çelik (talk)
Past Work Items
Past work items that the working group has dropped:
Home Page To Do
To Do for our group home page in particular.
Problem: "It's kind of overwhelming" (aaronpk, IRC 2016-04-19)
Goal: smaller, simpler, shorter page that you could send to someone not in the group, to let them know what the group is doing
- "Documentation" section - most of that should be moved to a Socialwg/research page - it's background for work that we're doing
- the red links in Documentation should just be deleted
- some stuff like the Use Cases and Inputs Into SocialWG should be separated out
- "Related Organizations" could be moved to a subpage
- "Invited Expert Application" and "FAQ" could also be moved to subpages
- socialig (in the process of closing)