Re: a common understanding of profiles

On 2015-06-24 07:16 AM, Melvin Carvalho wrote:
> So, I was wondering if it could be possible to try to come to a common 
> understanding of profiles.
A "profile" should be a retrievable resource with some representation of 
an "actor" in our system -- a node in a social network, preferably one 
that authors (=creates) content and can make connections to other 
actors. Usually a real person, but sometimes a fictional person, or a 
company, or a product, or a physical object, or a software process.

Since we're standardizing on AS 2.0 as our social syntax, and since our 
Social API and Federation protocol are supposed to use that social 
syntax, a "profile" should be a resource represented by a AS 2.0 actor 
object -- usually a Person.

So when you GET https://evanprodromou.example/profile the response would 
be something like:

    {
       "@context":  "http://www.w3.org/ns/activitystreams",
       "@type":  "Person",
       "@id": "https://evanprodromou.example/",
       "displayName": "Evan Prodromou",
       "alias": "eprodrom",
       "summary": "Founder of Fuzzy.io. Past founder of*  *Wikitravel and StatusNet. Founding CTO of Breather.",
       "icon":  {
         "@type":  "Image",
         "url":  "https://evanprodromou.example/avatar.png",
         "width":  128,
         "height":  128
       },
       "url": {
           "@type":  "Link",
           "href":  "https://evanprodromou.example/",
           "mediaType":  "text/html"
       },
       "location": {
            "@type": "Place",
            "displayName": "Montreal, Quebec, Canada"
       }
    }

Figuring out where to look for "Evan Prodromou's profile" is an 
important part of the Social API.

-Evan