About OMA MobSocNet requirements for W3C FSW

Dear all,

I am following up on Claudio's presentation at TPAC last month on OMA activities in the field of Social Networking, and on the liaison update referenced below.
In particular, I would like to refer to the commonly recognized concept of forwarding to this group some requirements from OMA on the "federation" aspects of Social Networking standards, to  trigger some discussion here on how to best address such requirements.

As indicated in the document embedded in the liaison update [1], with specific reference to section 5, here are a set of requirements specifically related to federation for which OMA is seeking feedback from this community.

MSN-HLF-004


The MobSocNet Enabler SHALL allow a user to follow another users activities and follow-up actions on another OMA Compliant SN.


1.0


MSN-HLF-013


The MobSocNet Enabler SHOULD allow a user to exchange private one-shot messages with one or more others users on other OMA Compliant SN.


1.0



MSN-DEV-005


When the component on the device receives information from the OMA Compliant SN, the MobSocNet Enabler SHALL ensure that:

- when the information relates to a deleted action, that action is deleted from the local cache so that it is not available anymore to local device applications;

- when the information relates to an updated action, that action is updated in the local cache so that its new version becomes available to local device applications.


1.0


MSN-SEC-001


The MobSocNet Enabler SHALL allow a user to define the privacy level of his activities or follow-up actions to control visibility by other users, including at least:

·         Public: accessible by all users;

·         Private: accessible only by the user owning the information

·         Followers: accessible only by the user's followers

Informational Note: other users can pertain to the same or another OMA Compliant SN.


1.0


(Note that a large number of other requirements exist, although they are not specifically related to federation.)

With specific reference to this set of requirements, considering "activities and follow-up actions" as the whole set of actions defined by ActivityStrea.ms specification (also including the support for groups), here are some specific (technical) questions:

1.       Wrt HLF-004, OStatus 1.0 and the related specifications seem to address this requirement. Recently, IETF has started addressing the formal specification of WebFinger, but still it seems that a formal/official definition of the "subscription" endpoint would need to be defined (mentioned in OStatus 1.0 draft2). A generic question is hence about the future of OStatus, both in terms of specification work/evolution, and of endorsement from W3C

2.       Wrt HLF-013, this seems like there is currently no standard specification to address such requirement. However some interesting solution is proposed by Diaspora's federation protocol [2]to reuse Salmon for this. What is the group's view on this technical solution ?

3.       Wrt DEV-005, besides the consideration that this is marked as a device-related requirement, it still implies in particular that the notification about "deleted" entries is propagated across SNs. The Atom Tombstone extension [3] seems to address this but here again an opinion from the group would be welcome.

4.       SEC-001 mostly relates to audience targeting. An ongoing proposal is underway in ActivityStrea.ms [4]& [5] but there may be implications in a federated scenario, to guarantee the correct limitation of content propagation.

5.       Generally wrt groups in a federated scenario, I would be interested in hints on how to address at best join/leave and post actions on groups pertaining to a different SN than the user itself (starting from the global group's identifier)

Most of these requirements are actually captured already in SWAT1 use cases although they haven't been discussed in depth so far from a technical perspective. I would love to trigger this discussion now.

I would be happy to discuss this further over email or via call depending on the group's interest.

Thanks
Walter
[1] http://member.openmobilealliance.org/ftp/Public_documents/CD/Permanent_documents/OMA-LS_927-OMA_CD_WG_to_W3C_FSW_XG_on_MobSocNet_Information_Update-20110927-A.zip
[2] https://github.com/diaspora/diaspora/wiki/Diaspora%27s-federation-protocol
[3] http://tools.ietf.org/html/draft-snell-atompub-tombstones-13
[4] http://activitystrea.ms/specs/json/targeting/1.0/
[5] http://groups.google.com/group/activity-streams/browse_thread/thread/5697d3088188af74

Da: public-xg-federatedsocialweb-request@w3.org [mailto:public-xg-federatedsocialweb-request@w3.org] Per conto di Goix Laurent Walter
Inviato: giovedì 6 ottobre 2011 14.36
A: Harry Halpin; public-xg-federatedsocialweb@w3.org
Oggetto: R: TODAY: Federated Social Web XG Meeting - 16:00 UTC - Telecon Details

Hello all,

To support and introduce the OMA activity in the field of social networking (to be discussed during today's call) I am forwarding you a liaison statement from OMA to the group [1]. This material intends to update the group with the latest achievements within the OMA on this topic, and also includes requests to the group.

Such "actions" (and so the entire liaison) are discussed and agreed internally within the group of OMA supporting companies before being sent. Traditionally these actions help the requesting OMA group to gain more information/feedback from the counterpart to better plan the internal activities, whilst the rest of the liaison statement text is usually for disseminating its own activities. Note that this liaison has been accepted by W3C and is now on the official list of liaisons [2].

I will be happy to better introduce this activity and answer questions, doubts or curiosities during today's call.
Hear you soon
Walter
[1] http://member.openmobilealliance.org/ftp/Public_documents/CD/Permanent_documents/OMA-LS_927-OMA_CD_WG_to_W3C_FSW_XG_on_MobSocNet_Information_Update-20110927-A.zip
[2] http://www.w3.org/2001/11/StdLiaison.html

Da: public-xg-federatedsocialweb-request@w3.org [mailto:public-xg-federatedsocialweb-request@w3.org] Per conto di Harry Halpin
Inviato: giovedì 6 ottobre 2011 12.44
A: public-xg-federatedsocialweb@w3.org
Oggetto: TODAY: Federated Social Web XG Meeting - 16:00 UTC - Telecon Details

Thursday, 6 October 16:00-18:00 UTC<http://www.timeanddate.com/worldclock/fixedtime.html?month=10&day=06&year=2011&hour=16&min=00&sec=0&p1=0> (12:00pm-2:00pm Boston local)
Zakim Bridge +1.617.761.6200<tel:+1.617.761.6200>, conference 37994 ("FSWXG")

supplementary IRC chat: [9]#federated on irc.w3.org port 6665

Agenda:

* W3C TPAC Federated Social Web XG Meeting in Silicon Valley Nov 1st.
* W3C Social Jam Nov 8-10th
* OMA work on Social Networking
* Future European gathering
* Transitioning to Community Group details

   cheers,
       harry
Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie.

This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks.
[cid:image001.gif@01CCB044.D0552F10]Rispetta l'ambiente. Non stampare questa mail se non è necessario.


Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie.

This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks.

[cid:00000000000000000000000000000001@TI.Disclaimer]Rispetta l'ambiente. Non stampare questa mail se non è necessario.