Some qualified relations need context

[fosterlynn]

I'm wondering if we want to define vocab for the context for relations that don't have the context embedded in them already. For example, Elf follows Amy. Vs. Elf follows Amy on Facebook (but Elf doesn't follow Amy on Google+). I think the context might always be a Group (?).

Membership has the context already embedded, for example Elf member of Social WG, the context is Social WG.

[rhiaro]

Hey Lynn, a quick note because I've gotta leave the office in a second, but
this is a great issue to raise. I think it might be better thought about by
considering what is meant by [Elf] and [Amy] when creating a relationship.
[Elf] = elf Pavlik the human being, or an account belonging to elf Pavlik
the human being? If we know the account is then hosted by facebook, that
lends some context (note people also have multiple accounts on the same
systems for different social contexts, too).

How to model people / online persons / accounts / profiles (and
transparency of links between them) is something I'm working on at the
moment, so hopefully I'll have some feedback for the group before long.
This is important to think about with regards to federated profiles and
relationships, as different systems model and use these concepts in
slightly different ways. I'm writing up a study of how profiles are
implemented for ten or so social sites in different domains at the moment.

Amy

On 30 April 2015 at 20:13, Lynn Foster notifications@github.com wrote:

I'm wondering if we want to define vocab for the context for relations
that don't have the context embedded in them already. For example, Elf
follows Amy. Vs. Elf follows Amy on Facebook (but Elf doesn't follow Amy on
Google+). I think the context might always be a Group (?).

Membership has the context already embedded, for example Elf member of
Social WG, the context is Social WG.

—
Reply to this email directly or view it on GitHub
#7.

[johnbreslin]

Hi Amy, Lynn

We can do it using a UserAccount in SIOC and a FOAF Person that holds those accounts. Then the follows relationships exist between the accounts which adds that required context.

Some few-year old pictures of the connections between Persons and UserAccounts are given here:

http://sioc-project.org/node/341

Best regards

John
http://Bresl.in

On 30 Apr 2015, at 20:24, Amy Guy notifications@github.com wrote:

Hey Lynn, a quick note because I've gotta leave the office in a second, but
this is a great issue to raise. I think it might be better thought about by
considering what is meant by [Elf] and [Amy] when creating a relationship.
[Elf] = elf Pavlik the human being, or an account belonging to elf Pavlik
the human being? If we know the account is then hosted by facebook, that
lends some context (note people also have multiple accounts on the same
systems for different social contexts, too).

How to model people / online persons / accounts / profiles (and
transparency of links between them) is something I'm working on at the
moment, so hopefully I'll have some feedback for the group before long.
This is important to think about with regards to federated profiles and
relationships, as different systems model and use these concepts in
slightly different ways. I'm writing up a study of how profiles are
implemented for ten or so social sites in different domains at the moment.

Amy

On 30 April 2015 at 20:13, Lynn Foster notifications@github.com wrote:

I'm wondering if we want to define vocab for the context for relations
that don't have the context embedded in them already. For example, Elf
follows Amy. Vs. Elf follows Amy on Facebook (but Elf doesn't follow Amy on
Google+). I think the context might always be a Group (?).

Membership has the context already embedded, for example Elf member of
Social WG, the context is Social WG.

―
Reply to this email directly or view it on GitHub
#7.

―
Reply to this email directly or view it on GitHub.

[fosterlynn]

@rhiaro @johnbreslin Thanks, great clarification! (In the domains I am used to you do actually want to know about the relationships of Persons and/or Organizations, and the UserAccount is just login credentials related to the Person. I need to get acclimated to the social stuff...)

And I totally agree about getting the Person - UserAccount - Profile - etc. issue resolved, seems very core! Looking forward to what you come up with! Then we can nail down the right concept(s) on these relationships.

[elf-pavlik]

Looks like we will have big part of the second day of our F2F in Paris dedicated to ActivityStreams and social vocabulary. IMO we also should clarify distinction between Follow and Subscribe. I can publish multiple Feed/Stream collections, someone can state following me as person in general and then subscribe to my various feeds/streams e.g. check-ins (~Foursquare), videos (~Youtube/Vimeo), photos (~Flickr, Instagram), audio (~Jamendo, Soundcloud) etc. I also emphasized during our last F2F that API should NOT assume that all my feeds will stay hosted on the same domain as my proifle and we need put in place follow your nose discovery! BTW WG ISSUE-17: Identity, Agent, Person, Persona, Account etc. need clarifications