See also: IRC log
<AnnB> aaargh .. when I use code 76244 I'm told I'm the only one in conference
<elf-pavlik> oops!
<AnnB> re-dialing
<elf-pavlik> please rejoin
<harry> Hi Ann
<harry> hi lloyd!
<harry> lloyd, could you scribe as elf did it at the WG conference?
<lehawes> Zakin, +1.978.238.aaaa is lehawes
<harry> Zakin, aaa is lehawes
<harry> Ed or lehawes, want to scribe?
<elf-pavlik> lehawes, harry i did it already :)
<eprodrom> I'm on my way in
<lehawes> Thanks, Elf!
I can scribe this week
<harry> thanks EdK!
<elf-pavlik> scribenick: EdK
<harry> scibe: EdK
<harry> scribe: EdK
<eprodrom> hi
<harry> scribenick: EdK
<eprodrom> I think I like that Zakim knows my phone number
<harry> http://www.w3.org/wiki/Socialig/2015-01-21
First item on agenda is to approve minutes from last meetings.
<harry> PROPOSE: Approve minutes http://www.w3.org/2014/12/03-socialig-minutes.html
<harry> PROPOSAL: Approve minutes http://www.w3.org/2014/12/17-socialig-minutes.html
<harry> RESOLVED: approved http://www.w3.org/2014/12/03-socialig-minutes.html
<harry> RESOLVED: http://www.w3.org/2014/12/17-socialig-minutes.html
Standard meeting is every other week, opposite weeks are for working time.
last week Lloyd and Ann discussed vocabulary. consider engaging with professional ontologists as a side project.
<AnnB> yes, next on agenda
<elf-pavlik> tantek, already there https://www.w3.org/wiki/Socialig/2015-01-21#Agenda_2
Ann had volunteered Julie Martin at Boeing for discussing Boeing's vocabulary, would need to confirm with her agreement to help.
<harry> +1 it simplifies things and more people are in #social
<tantek> Thank you AnnB elf-pavlik
<lehawes> I like the idea of moving both IG and WG to "social" on IRC
<harry> PROPOSED: Move from #socialig to #social
<Lloyd_Fassett> +
<elf-pavlik> +1
<Lloyd_Fassett> +1
<AnnB> +1
<harry> RESOLVED: Move from #socialig to #social
<harry> starting next meeting
<harry> Yes, it's reserved this time at every single week
<Arnaud> I wonder whether lawyers will have a problem with that...
Ann mentioned the social IRC channel is active all week, not just for meetings.
<lehawes> Doing so can only help communication and ambient awareness between the two groups
<Arnaud> harry, it might be worth checking with Wendy
<harry> sorry, microphone still not working, waiting for Lenovo to deliver a new computer
<elf-pavlik> wseltzer, ^
question - do we need more time for working groups other than the opposite week?
<elf-pavlik> +1 keep it weekly for now IG / TF meetings alternating
<lehawes> I don't think we need other reserved times for IG. This time works well and can be used every other week by a task force
Larry - other meetings tend to be ad hoc and scheduled based on sub-team member availability.
<harry> why do we need another telecon?
<Arnaud> +q
still need to smooth out/document how to get an ad hoc dial-in.
<harry> We do not need to talk to W3C lawyers, we just need to make sure trackbot also is associates this telecon with #social
Lloyd agreed to document this.
<Zakim> elf-pavlik, you wanted to discuss tracker
<harry> should be possible with the same IRC channel, will check
<harry> since you have trackbot start/end meetings
Elf noted that we had been looking to use Tracker and this could conflict with combining IRC channels.
<elf-pavlik> harry, can you take ACTION for that?
<harry> the email has already been sent to adminreq
<AdamB> better to answer that question now then later
Arnaud - in favor but with a lot of IP issues recently, we should just double check with Wendy (legal) to make sure there isn't a conflict/issue.
Ad-hoc phone requests take time because it takes admins to tackle, usually only do for regular meetings. Can ask Zachim in IRC to request a room for # users, will get a dial-in code right then and there.
*Zakim* Zakim
<elf-pavlik> ACTION: elf-pavlik to ask wseltzer about possible legal issues with using #social irc channel [recorded in http://www.w3.org/2015/01/21-socialig-minutes.html#action01]
<trackbot> Sorry, but no Tracker is associated with this channel.
<harry> I am listneing
<elf-pavlik> harry, ^
<harry> Yes, I am 99% sure there are no legal issues
<harry> IPR commits are to WG members, thus mailing list restrictions
<harry> I have no idea why the tracker didn't work this time
<AdamB> works fro me to hear form evan first
Ann - switch sequence of agenda, Evan to review social API
<harry> Anyways, we'll reset tracker when we move to #social
<eprodrom> https://www.w3.org/wiki/Socialwg/Social_API
Evan - WG and IG agreed part of charter is to provide http based API for social software
Began discussing what APIs are and how to make it work, there were a variety of ideas
Took as a strategy cataloging social APIs, went through those, analyzed them for payloads, data objects, functionality of API
Striving to define what a social API should do
<eprodrom> https://www.w3.org/wiki/Socialwg/Social_API/Patterns
Went through more than a dozen APIS, including Twitter, Facebook, Foursquare
plus open source
Did analysis, in telecons reviewers went through the APIs for familiarity and understanding of what social APIs are
<AnnB> really interesting, too!
<eprodrom> https://www.w3.org/wiki/Socialwg/Social_API/Requirements
Now at a point where reviewed enough to move on to next stage, which is to take the functionality seen, look at commonalities and craft a set of requirements
As of yesterday, the updated list of requirements are on the wiki in an informal fashion at the moment.
Hope is next WG meeting on Tuesday will discuss and strive for consensus for approval or define another iteration or formality
Goal after requirements are approved by WG will be to solicit candidate definitions
Have some submissions already but can't really judge until requirements are agreed upon.
<lehawes_> At first glance of the draft Social API Requirements, I see a glaring hole: profiles! Perhaps we should take a look at existing use cases for profiles and see if we can derive requirements? What does everyone think of that approach?
<elf-pavlik> +1 profiles!
Goal is to have first public working draft for a MArch meetup, may not actually be a FPWD but a clear proposal that can be discussed toward that direction
<lehawes_> It seems like the draft requirements do a good job of covering common social gestures (i.e. Like, Follow...). Will have to examine in more detail to see if any are missing.
Edit wiki or send suggestions to Evan to help mature the requirements
<Zakim> elf-pavlik, you wanted to discuss documenting features broadly used in Diaspora & Friendica
<harry> Would be good to get Tencent and others more involved
<elf-pavlik> I proposed documenting requirements based on what people use daily in Diaspora and Friendica and make sure that our specs cover them so they can migrate their software to specs we publish
<harry> tencent joined WG, but this meeting time is hard for Asian members
<elf-pavlik> based on meeting during 31C3 from which I will still share more detailed feedback
AnnB wonders if the list is representative of global tools, or should we reach out somehow for Japan, China centric tools
<harry> However, happy to send them an email to take a look at something once we have a draft API
<harry> the offices can translate sometimes if we ask
Evan suggests at least looking at Tencent, might be able to find others and run through automatic translators to do comparisons - if the APIs are published.
<harry> notes that I just reset trackbot to aim at #social, and it seems to work fine
<harry> the reset seemed to fix the issue with this channel, which was an issue with /IG being a redirect
Lloyd asked if there were indicators about shared vocabularies during the analysis.
<harry> ACTION: test action [recorded in http://www.w3.org/2015/01/21-socialig-minutes.html#action02]
<trackbot> Sorry, but no Tracker is associated with this channel.
<harry> trackbot, this is SOCIG
<trackbot> Sorry, harry, I don't understand 'trackbot, this is SOCIG'. Please refer to <http://www.w3.org/2005/06/tracker/irc> for help.
Evan's initial perspective was there wasn't much in the way of shared vocabulary, was some common terms (inbox, stream, etc.)
<harry> ACTION eprodrom examine APIs for Yandex, Vkontakte, Sina Weibo, Tencent, and/or RenRen
<trackbot> Sorry, but no Tracker is associated with this channel.
<elf-pavlik> trackbot, associate this channel with #socialig
Could have been some commonality, but wasn't a big part of the study.
<harry> trackbot, start meeting
<trackbot> Sorry, but no Tracker is associated with this channel.
<harry> I doubt systeam will customize tracker for us, but we can ask
<harry> I'll file a sysreq@w3.org to see if we can do this, otherwise we may want to keep separate IRC channels
Summarize: may see some shared vocabularies that are common but a larger portion may be uncommon and likely not as useful.
<AnnB> Evan -- we lost you!
<eprodrom> Aww crud
<eprodrom> I'll be right back
<harry> Evan, just dial back in
<Loqi> :)
<AnnB> k
Lloyd also suggested that within an API it is directed at a specific ecosystem, and as we consider interaction between ecosystems that context becomes something to think through.
<eprodrom> lehawes_ ?
Larry wondered if looking at enterprise-centric tools/APIs, we might find some unique functionality.
<harry> Notes that we cannot have a separate IRC channel if we want our own tracker
<harry> Notes that we cannot have a *shared* IRC channel if we want our own tracker
<harry> otherwise, this confuses the bots
Ann suggested she and Adam need to help by documenting Boeing's internal API in the context of these requirements.
<harry> So, as I highly doubt systeams will customize this for us, let's just revisit the decision.
Evan suggested that Open Social had been capturing some of those.
Larry suggested Yammer and SocialCast.
<elf-pavlik> AnnB, ^
Ed notes that the top tools include Jive and Tibbr.
<eprodrom> https://developer.yammer.com/restapi/ might be a good place to start
<eprodrom> ack?
<Zakim> elf-pavlik, you wanted to discuss revisit IRC channel resolution because of tracker collision
<harry> basically, tracker can't handle two groups with same IRC channel
<elf-pavlik> thank you eprodrom for this update on Social API!
<AnnB> API requirements:
<AnnB> https://www.w3.org/wiki/Socialwg/Social_API/Requirements
<eprodrom> evan@e14n.com
Evan - closeout; it will help if everyone will review and comment on the requirements. Feedback can be by editing wiki document, use discussion page on wiki, and/or send Evan email.
<elf-pavlik> eprodrom, public-socialweb-comments@w3.org ?
Thank you Evan!!
<harry> We should probably keep this channel if we want a separate tracker
Back to Tracker/IRC issue; if we combine channels we may not be able to have separate trackers, suggest we stay separate until we test and resolve.
<harry> if we don't want to use tracker, it doesn't matter
<harry> PROPOSAL: Continue with #socialig to keep tracker
<harry> RESOLVED: Keep with #socialig in order to use tracker
<elf-pavlik> AnnB, 2min or you can propose extending meeting
Ann reiterates that people can hang out in the other channel to keep abreast of the work
Call for any task force reportouts.
side note Zakim will not kick out people at end of hour, just won't let people join or re-join.
<Arnaud> fyi, the syntax to get a phone bridge on the fly is: zakim, room for <number of people> for <number> minutes? if you don't specify the minutes you will get 60 minutes
Larry: Use cases - no activity over the holidays. One approach could be to review WG API requirements and help prioritize use cases that help that effort.
<harry> cross fingers MarkC can come back
<lehawes_> I don't believe that the Architecture TF has even met officially
Lloyd - Vocabulary. Suggestion had been that Activity streams has been most active, other task forces not highly engaged to work on vocabulary. Interested in working with Boeing to see what is sharable from that effort.
<AdamB> we use it in inSite
Hi James
<lehawes_> EdK: Ford put an information management team in place in 2014, including people concerned with vocabulary. He needs to circle around with them and learn more about what they are doing.
<AnnB> Ann: maybe there is a manufacturing-focused vocabularly?
<eprodrom> I have to leave, thanks everyone
<AnnB> s/vocabularly / vocabulary /
<harry> thanks for chairing Anne!
<lehawes_> EdK: He and Lloyd will talk about vocabulary specifics after Ed has investigated.
Thanks all!
<harry> meeting adjourned
<elf-pavlik> thank you AnnB!
<lehawes_> Bye everyone, and thanks!
<elf-pavlik> trackbot, end meeting
<trackbot> Sorry, but no Tracker is associated with this channel.
<harry> Yep, had to figure out tracker issue
<harry> the minutes are generated, will send to list, elf- can you put in wiki?
<harry> I'm not sure if Ed knows how to do that
<AnnB> thanks to elf and harry for their testing of Tracker
This is scribe.perl Revision: 1.140 of Date: 2014-11-06 18:16:30 Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/ Guessing input format: RRSAgent_Text_Format (score 1.00) Succeeded: s/Zachim/Zakim/ Succeeded: s/fro/for/ FAILED: s/vocabularly / vocabulary / Found ScribeNick: EdK Found Scribe: EdK Found ScribeNick: EdK Default Present: [IPcaller] Present: elf-pavlik hhalpin Ann Lloyd_Fassett lehawes AdamB EdK Arnaud eprodrom dromasca WARNING: No meeting title found! You should specify the meeting title like this: <dbooth> Meeting: Weekly Baking Club Meeting Agenda: http://www.w3.org/wiki/Socialig/2015-01-21 Got date from IRC log name: 21 Jan 2015 Guessing minutes URL: http://www.w3.org/2015/01/21-socialig-minutes.html People with action items: elf-pavlik test WARNING: Input appears to use implicit continuation lines. You may need the "-implicitContinuations" option.[End of scribe.perl diagnostic output]