From W3C Wiki
(Redirected from SocialWG)
Jump to: navigation, search

Welcome to the Social Web Working Group (SocialWG) home page (!

Social Web Working Group

Photo of the W3C Social Web Working Group taken at Face to Face Meeting, 2015-03-18 at MIT.
Tantek Çelik (Mozilla)
Arnaud Le Hors (IBM)
Evan Prodromou (e14N)
Staff Contact
Sandro Hawke (W3C/MIT)
Harry Halpin (W3C/MIT)



How to participate

To join this group

If you are officially added to the group, you will automatically receive group email and your login and password will work on this wiki.


Working Drafts: (including Activity Streams drafts)

Editors drafts:



Proposed documents to the working groups


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.

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:


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.

Social Media



Weekly telecons take place on Tuesdays at 1PM US/Eastern (10AM US/Pacific, 19:00 Paris, etc, see time converter for more options), as determined by poll.

Our three chairpersons -- Tantek, Arnaud, and Evan -- rotate through chairing the telecons in that order. 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. Rotation continues normally, though chairs may swap back to make up for missing their turn.

Telecon Information

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 meeting
    • Or, dial: 1-617-324-0000 and follow prompts
    • Meeting number: 642 112 960
    • Meeting password: Note password is no longer 'SOCL' but is available only to WG members here:
    • For your ID number, just press pound and leave it blank.
    • (In case you need to actually see the WebEx meeting URI, it is: )

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.

  1. 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.
    1. If anyone else is chairing, get host key from Tantek, Evan, Arnaud, Harry, Sandro, or Ann
    2. In "Participant" menu (top left), choose "Reclaim host role"
  2. Once you are the host, the "Invite and Remind" button becomes available (in middle of WebEx session screen)
  3. In the "Invite and Remind" window, select the tab for "Phone"
  4. Enter the person's name and phone number, and click "Call"
  5. 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.

Next Meeting

Next Social Web WG f2f:

  • .. Fourth Social Web F2F meeting at Mozilla in San Francisco

Note: This replaces the meeting at TPAC in Sapporo, Japan which was canceled as of 2015-09-08 due to insufficient attendance commitments from WG members.

Teleconferences (telcons) are every week, except during summertime we are doing them every other week.

Next Social Web WG telcon:

Future Meetings

Teleconferences (telcons) are every week, except during summertime we are doing them every other week.

Liaison TF Events list - additional opportunities for spontaneous meetups


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. [1]

Identifying yourself

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.

Past Meetings


As a scribe, after you're done minuting into IRC for a given date, e.g. 2014-10-14:

  1. Get the source of (should have been generated by RRSAgent after chair asked for "trackbot, end meeting" in IRC)
  2. Convert from HTML to Mediawiki syntax, either:
    • Locally run it through pandoc with command: pandoc -f html -t mediawiki -o input-minutes.html
    • or try this online converter (experimental! Comments/bug reports to rhiaro).
  3. Use Socialwg/2014-10-07-minutes as a template to create Socialwg/2014-10-14-minutes


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

Use Cases

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 Vocabulary

Main effort moved to Task Force in Interest Group - Socialig/Vocabulary_TF

Social API

API research

API candidates


Federation candidates

Inputs Into SocialWG

Inputs into SocialWG, including specs from External Groups explicitly listed in the Charter.

Activity Streams

Main article: Activity Streams

See #Drafts at the top of this page for Activity Streams editor's drafts, issues, and github repo links.


Dependent Work

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




The Social Web Working Group workmode is roughly as follows, and may be iterated based on group experience:

  • #Discussion - use IRC, telcons, email for discussion only
  • #Documentation - capture proposals and conclusions here on the wiki


Issues and Actions related to this WG are 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 draft: Oct 2014
  • LC: likely late 2015/early 2016 (charter v1 said Q3 2015)
  • CR: likely early 2016 (charter v1 said Q4 2015)
  • PR: likely late 2016 (charter v1 said Q2 2016)
  • REC: (charter v1 said Q3 2016)
  • 2016-12-31 Charter period ends.

Social API

  • Review: Nov 2014 - ongoing (original review end date was Mar 2015)
  • Commit: unknown
  • First public working draft: unknown (charter v1 said Q3 2014)
  • LC: unknown (charter v1 said Q3 2015)
  • CR: unknown (charter v1 said Q4 2015)
  • PR: Q2 2016 (charter v1)
  • REC:Q3 2016 (charter v1)
  • 2016-12-31 Charter period ends.

Federation protocol

  • Review: unknown in 2015
  • Commit: unknown (was Jul 2015)
  • First public working draft: unknown (charter v1 was Q4 2014, then Aug 2015)
  • LC: Q4 2015 (charter v1)
  • CR: Q1 2016 (charter v1)
  • PR: Q3 2016 (charter v1)
  • REC: Q4 2016 (charter v1)
  • 2016-12-31 Charter period ends.


Related Organizations

For more details see Socialwg/Related

Socialig/Liaison_TF takes care of coordination

The following organizations are also working on Social Web technologies:

mentioned in Charter

W3C Groups

Independent Organizations


not mentioned in Charter

W3C Groups

Independent Organizations

Applied for Membership

Tantek Çelik has encouraged people who have applied for invited expert membership to list themselves 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:


Tantek Çelik:

  • 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


Evan Prodromou

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


W3C Staff Contact Harry Halpin:

  • Temporary Invited Expert status is the most that can be offered to those whose organisation W3C believes should be able to join the W3C, but nonetheless a 6 month "test-run" of the WG was viewed as appropriate.
  • For those organisations,there should be evidence that they have a working or planned product.
  • For independents without an organisation (including universities and small non-profits), a public URL with working code and real users is necessary.
  • A "vocabulary" does not count as working code unless it is actively used by working code with real users.
  • Requests that do not fit these criteria will be redirected to the Social Interest Group.
  • We revisit all accepted IEs, giving them until TPAC to prove their work.

Note also his management chain may have opinions:

  • Wendy Seltzer (his manager)
  • Tim Berners-Lee (her manager)


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

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

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.[2] 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 has a charter which is focused on the research and documentation of social web use-cases.




See Also