Re: a common understanding of profiles

On 26 June 2015 at 14:23, Evan Prodromou <evan@e14n.com> wrote:

> On 2015-06-26 07:37 AM, Melvin Carvalho wrote:
>
>> Regarding the URI above.  It can become slightly problematic attaching
>> key value pairs to an HTTP document, also doubling as a Person.
>>
> I'm pretty sure I didn't do that in the example I gave.
>

Well I thought you were tying (for example) the key "@type" and value
"Person" to the http doc : https://evanprodmorou.example/profile


>
>> So, how to get interoperable profiles?
>>
> Pick a data standard, and a way to find the profiles. Then, everybody
> implements that.
>
> It would be wrong to assume that the point of this working group is to
> make Melvin's site implemented in FOAF with Turtle talk to Aaron's site
> implemented in HTML with microformats.
>

I guess Im not quite seeing it how to implement an interoperable social API
without interoperable social profiles.  However, Kingley's reply seems to
make sense. I'll fwd them to the public list.


>
> We're here for the important goals of defining a social syntax, and social
> API, and a federation protocol for the seven billion people on the entire
> planet -- not to build ad hoc bridges for the few dozen people
> participating in this group.
>
> Ultimately, that means some people here are going to have to compromise,
> hold their nose, and implement a data standard that they don't usually use
> or like.
>
> -Evan
>
>