From W3C Wiki
Jump to: navigation, search

socialwg Teleconf 2015-04-07

Tuesdays at 10am US/Pacific, 1pm US/Eastern time for 90 minutes

  • Check your timezone
  • Dial-in +1-617-761-6200 , SIP Instructions, Zakim Code "SOCL"

Previous Meeting



  • Chair: Arnaud
  • Scribe:
  • Regrets:
    • (put your name here)


Chair to start the meeting by typing on irc:

trackbot, start meeting

Trackbot should already be on the channel but if for some reason it is not call it with the following command:

/invite trackbot

Zakim won't know what meeting it is. Just ignore it. Pick a scribe from the list or ask Zakim to pick one up with the following command:

Zakim, pick a victim

Unfortunately Zakim has no idea who's scribed before so you may have to ask several times before getting an acceptable answer...

Then type:

scribe: xxx

Also, with WebEx, Zakim doesn't know who is on the call so, as people join they should record their attendance with the command: present+ <nickname>

For additional info, see the Zakim documentation page.



  • Participation is limited to members

Approval of Minutes of 31 March 2015 Teleconf

Next Teleconf

Next F2F

everyone who answered Yes in pool, please add yourself to participants list on a wiki!

Next Next F2F

  • TPAC2015 is 2015-10-26…30 in Sapporo, JP.
    • PROPOSAL: Meet 2015-10-29…30 (ThF) at TPAC2015.
    • Avoid MT as it conflicts with CSS[1]
    • additional request: avoid WebApps conflict[2] (they haven't chosen their TPAC days yet[3]).

Tracking of Actions and Issues

Activity Streams 2.0

  • ISSUE-16 better separate grammar/vocabulary and improved spec structure — Pavlik elf (talk) 10:10, 15 March 2015 (UTC)
  • ISSUE-36 Role and evolution of recommended JSON-LD contexts — Pavlik elf (talk) 14:32, 3 April 2015 (UTC)
  • PROPOSAL: Open raised issues ISSUE-26-36
    • James's email
    • ISSUE-26, Representing Profiles (James)
    • ISSUE-27, Representing Changs to Profiles, (James)
    • ISSUE-28, Remodel "Connect" and "FriendRequest" or remove them, (James)
    • ISSUE-29, Removing Activity Types not used by User Stories, (James)
    • ISSUE-30, Deprecate "actor" in favor of "attributedTo", (James)
    • ISSUE-31, Refactor "target", "origin" and audience targeting, (James)
    • ISSUE-32, Deprecate "generator" and "provider" (James)
    • ISSUE-33, Deprecate or remove the "rating" property (James)
    • ISSUE-34, Context vs Motivation (James)
    • ISSUE-35, Simplify the Actor Types (see Issue-17 also) (James)
    • ISSUE-36, Leveraging JSON-LD context vs. RDF vocabulary (elf). Specifically, do we want to leverage JSON-LD mechanisms for reverse properties. There are inherent complexities with this approach when working strictly with the JSON-LD expanded form.
  • PROPOSAL: Close the following issues: ISSUE-4, ISSUE-7, ISSUE-12, ISSUE-14, ISSUE-15, ISSUE-20
    • James's email
    • ISSUE-4 - Explicit typing or support implicit typing - Already addressed in current draft
    • ISSUE-7 - Are AS consumers required to understand the pre-JSON-LD syntax - Already addressed in current draft
    • ISSUE-12 - Action Types Structure and Processing Model - it was decided already that RDF style reasoning should be supported but not required.
    • ISSUE-14 - as:Link complexity - the spec already includes language that deals with the relationship between as:Link and as:Object and how they relate to one another. If there are specific suggestions to improve the language, then ok. If the proposal is to remove as:Link, then it ought to be a specific proposal to remove as:Link
    • ISSUE-15 - AS2.0 vocab duplicating and efforts - microformats and are not normative dependencies for AS2.0. Some duplication is ok and ought to be expected.
    • ISSUE-20 - Support JSON Text Sequences? - out of scope, recommend first seeing if there are ways of having JSON-LD generically support JSON Text Sequences

Social API

ActivityPump call for help

See the newly forked standard page and the mailing list thread

  • History of the ActivityPump spec (and relation to the pump api)
  • What needs to be done
  • How to help!

WG+IG Workflows

Closing WG agenda on Friday

PROPOSAL: wiki page for n+1 meeting already exists during n meeting, we prepare agenda together Tue-Fri and chair of the meeting closes it on Friday. This gives everyone at least one full day to prepare prior to the meeting — Pavlik elf (talk) 14:42, 3 April 2015 (UTC)

W3C github orga and Social team

Coordination with IG

Additional Agenda Items

DO NOT REMOVE THIS Additional Agenda Items SECTION, add more agenda items here (or in a NEW === section === previous to this section)

  • ...

back to socialwg