new Social Architecture effort

You're the beesknees, Melvin!  I really appreciate thenew energy you're bringing to this work. And, Ed, we've missed you! Before this goes very far, I wanted to voice my perception that what you describe as "architectural best practices for modeling people" ... sound very SoLiD-centric. I'm not saying I agree nor disagree. 

It does seem to me that the foundations of "social" rest on the social graph. I'm not sure if that is universally agreed-to, or not. If not, then what do others suggest?
In any case, before we call something a "best practice", I'd like to be sure we have some consensus from the various technical points-of-view.  

(I hope the godsdon't send lightning down because I'm inserting a comment ..... I'm only 1 day into my "dark" phase,but couldn't resist. :-)
   -- Ann
PS. I updated the subject line.
  <!--#yiv4275458903 _filtered #yiv4275458903 {font-family:"Cambria Math";panose-1:2 4 5 3 5 4 6 3 2 4;} _filtered #yiv4275458903 {font-family:Calibri;panose-1:2 15 5 2 2 2 4 3 2 4;} _filtered #yiv4275458903 {font-family:"Franklin Gothic Medium";panose-1:2 11 6 3 2 1 2 2 2 4;} _filtered #yiv4275458903 {font-family:Tahoma;panose-1:2 11 6 4 3 5 4 4 2 4;}#yiv4275458903 #yiv4275458903 p.yiv4275458903MsoNormal, #yiv4275458903 li.yiv4275458903MsoNormal, #yiv4275458903 div.yiv4275458903MsoNormal {margin:0in;margin-bottom:.0001pt;font-size:12.0pt;font-family:"Times New Roman", serif;}#yiv4275458903 a:link, #yiv4275458903 span.yiv4275458903MsoHyperlink {color:blue;text-decoration:underline;}#yiv4275458903 a:visited, #yiv4275458903 span.yiv4275458903MsoHyperlinkFollowed {color:purple;text-decoration:underline;}#yiv4275458903 p {margin-right:0in;margin-left:0in;font-size:12.0pt;font-family:"Times New Roman", serif;}#yiv4275458903 span.yiv4275458903EmailStyle18 {font-family:"Calibri", sans-serif;color:#1F497D;}#yiv4275458903 .yiv4275458903MsoChpDefault {font-family:"Calibri", sans-serif;} _filtered #yiv4275458903 {margin:1.0in 1.0in 1.0in 1.0in;}#yiv4275458903 div.yiv4275458903WordSection1 {}-->      From: Melvin Carvalho [mailto:melvincarvalho@gmail.com]
Sent: Thursday, October 01, 2015 4:15 PM
To: Krebs, Edward (E.C.)
Cc: Bassetti, Ann; Larry Hawes; Social Web Working Group; public-social-interest@w3.org
Subject: Re: Boeing resignations (hopefully temporary for me)          On 1 October 2015 at 18:46, Melvin Carvalho <melvincarvalho@gmail.com> wrote: 
      On 1 October 2015 at 17:39, Melvin Carvalho <melvincarvalho@gmail.com> wrote: 
      On 1 October 2015 at 15:02, Krebs, Edward (E.C.) <ekrebs@ford.com> wrote: 
There are some good architecture starting points. The social Headlights task Force started on this path. I suggested one view based on that initial work in theWorkshop on Social Standards in August 2013. http://www.w3.org/2013/socialweb/papers/An%20Enterprise%20Social%20Network%20Reference%20Architecture.pdf   IBM presented one in 2014:http://www.slideshare.net/heathwulf/social-architecture-1-h2014 
   Thanks Edward, these are great slides. What really struck me was the call for a: - People Centric - Relationship Driven architecture.  I think the work we've started out on has a gap here.  While there's a lot of work done to cater for micro blogging enthusiasts the enterprise has been less well served, imho.  I think these presentations could be a great basis to create an architecture document, which is missing, not just in this group, but in the social web in general.  In creating a people centric, relationship driven architecture we can talk about people and relationships.  How this can be achieved technically, as part of a social graph.  The declarative nature using the law of least power.  Having open ended extensibility to cater for enterprise use cases as well as common social networking features. Essentially creating the awww [1] of the social web.  An essential document for anyone creating a system in the social web, either in an enterprise or public setting, that will cover all the base work needed to get started with real world use cases.  It's something that's been missing for 10 years, and imho, one reason that has lead to balkanization. 

This is an IG deliverable.  Would anyone in the IG wish to help with this?  

Where could we get started -- perhaps a wiki page, then migrate to a github repo? 
   elf has suggested building on :

http://w3c-social.github.io/social-arch/ Which I think is a great idea.  I've chatted to Amy too, who hopefully may have some cycles free to collaborate. Input here or on in the github issues very welcome! :) 
   Im going to start working on this document, but my initial thoughts are: "Data Model" is too broad a section, I'd like to see it broken down as follows: "People" -- this is a loose term that can mean nodes in general, referring to people, agents, accounts, profiles, groups etc. but try to capture that the social people is people oriented. Have architectural best practices for modeling people: 1. Give a person a URL 2. Give that url a type (as exemplified by open graph protocol,schema.org and foaf) 3. Distinguish between the (HTTP) document and the person, as this could cause processor problems 4. Allow people to have relationships Then cover "Relationships" as a basis of relationship driven design 1. Show the nature of relationships as one way and two way 2. Show typical relationship styles such as, follow, friend, co-worker etc. 3. Show an open ended architecture for extensibility and reuse Once these two core pieces are described, show how they are combined to form a social graph.  Talk about the read, write and search functionality etc. I would suggest moving as much of the technical decisions as possible out into another doc, and keeping the architecture document clean and minimal yet, covering all the basics an implementor would need to get started and to tackle the user stories.   
  

[1] http://www.w3.org/TR/webarch/
  
  Regards,
Edward C. Krebs 
Enterprise Architect
Enterprise Technology Research
Ford Motor Company Information Technology Quote of the day:
"The best way to predict the future is to invent it." -- Alan Kay