atom feed21 messages in com.googlegroups.opensocial-and-gadgets-specRe: Proposal for Privacy Settings as ...
FromSent OnAttachments
Na LiOct 12, 2011 2:23 am 
Laurent-Walter GoixOct 13, 2011 3:29 am 
rbaxter85Oct 13, 2011 6:38 pm 
Na LiOct 20, 2011 4:37 pm 
Na LiOct 20, 2011 4:45 pm 
James SnellOct 20, 2011 6:10 pm 
James SnellOct 20, 2011 6:10 pm 
rbaxter85Oct 23, 2011 1:05 pm 
Na LiOct 24, 2011 5:24 am 
rbaxter85Oct 24, 2011 6:18 pm 
rbaxter85Oct 25, 2011 12:13 pm 
Mark W.Oct 28, 2011 6:40 am 
Mark W.Oct 29, 2011 1:13 pm 
rbaxter85Oct 30, 2011 6:49 pm 
Na LiOct 31, 2011 10:21 am 
Craig McClanahanOct 31, 2011 10:39 am 
Craig McClanahanOct 31, 2011 10:39 am 
Na LiOct 31, 2011 10:51 am 
Mark W.Nov 1, 2011 5:23 am 
rbaxter85Nov 1, 2011 6:14 am 
Na LiNov 1, 2011 9:28 am 
Subject:Re: Proposal for Privacy Settings as an OpenSocial Extension
From:Na Li ("jia@gmail.com)
Date:Oct 20, 2011 4:37:30 pm
List:com.googlegroups.opensocial-and-gadgets-spec

Hello Laurent-Walter,

Thank you for your feedback. Yes, it's a drafty proposal, and some constrains/rules need to be defined to deal with the conflicts from a server point of view.

I've checked the links you provided. The extension of JSON activity stream defines the audience of activities in a cc/bcc way. The CMIS Spec defines the ACL over folders, including detailed action permissions.

We think that it'd be nice to include the privacy/permission control concept into OpenSocial Social Data Spec (Person, Album, MediaItem, and ActivityEntry), since privacy/permission setting is somehow a key component for these data. Also, being able to retrieve these settings allows gadgets/server to behave in a privacy-aware way. But it's true that the scheme needs to be carefully designed.

On Oct 13, 12:29 pm, Laurent-Walter Goix <laur@gmail.com> wrote:

Hello Na Li,

Thank you for sharing the proposal. Interesting topic to be addressed, related to permissions and ACLs...I guess the proposal captures good concepts (the fact of addressing privacy levels to the granularity of fields), and may deserve some additional "behavioural" rules on how to process them from a server perspective (e.g. you may end up with overlapping, hierarchical or conflicting settings if you combine several entries together for the same piece of information)

have you also been checking the work done in ActivityStreams [1] or CMIS [2] on this? Where do you think this should be best addressed? walter

[1]http://activitystrea.ms/specs/json/targeting/1.0/ [2]http://docs.oasis-open.org/cmis/CMIS/v1.0/cs01/cmis-spec-v1.0.html

On Oct 12, 11:23 am, Na Li <jian@gmail.com> wrote:

Hello,

Our research group at EPFL would like to propose a privacy setting extension for OpenSocial. Every social networking site provides a particular privacy control scheme that manages the sharing audience of different social data, including profile information, activity streams, albums, and media items. However, privacy settings of social data is not included in OpenSocial specification up to the current version.

We believe that for gadgets, being able to retrieve the privacy settings of social data can keep users aware of the sharing audience of their information and give them the control over who can access their data. We propose to add a new data structure PrivacySettingEntry into Social Data and add PrivacySettings attribute to Person, ActivityEntry, Album, and MediaItem.

The example use cases and proposed Spec changes are described in the proposal:https://docs.google.com/document/d/12UH0Dolvd5A1lEAQatez9CbdHgpysfvWe...

Please let me know if you find this extension useful. We are ready to contribute and look forward to your feedback.

Best,