R: Meeting minutes from April 8th telecon

Hi all,

I would further like to suggest adding a 'private messaging' use case to swat1:
* Alice has an account on Server 1. Her friends are Bob and Donna, both on Server 2.
* Alice sends a private message to Bob and Donna, who are *not* friend with each other.
* Bob and Donna receive Alice's private message (asserted).
* Bob replies to the message by sending it to both Alice and Donna
* Both Donna and Alice receive Bob's message

Cheers
Walter

-----Messaggio originale-----
Da: public-xg-federatedsocialweb-request@w3.org [mailto:public-xg-federatedsocialweb-request@w3.org] Per conto di Goix Laurent Walter
Inviato: luned́ 11 aprile 2011 0.28
A: Harry Halpin; public-xg-federatedsocialweb@w3.org
Cc: Venezia Claudio
Oggetto: R: Meeting minutes from April 8th telecon

Hi all,

Regarding swat1 use cases i guess it could help distinguishing between 'management-related' use cases that related to occasional interactions between the single user with the system (profile mgmt, group mgmt, user search/discovery, data portability, etc) wrt 'functional' use cases that deal with cross-user interactions (group sharing, private/restricted sharing, social news, etc).

Some other thoughts:
- terminology-wise:
        - Wrt "private content" uc I guess in general the wording may be improved to 'restricted' content: the whole point about this uc is related to privacy settings & permissions, being the content not public. In this particular scenario, it may be more accurate to state that alice uploads a 'friends-only' photo set.
        - wrt 'social news' uc the term 'posts' usually refers to an original content from the author, whilst in this case the term 'shares' may be more accurate (see [1])

- architecture-wise: would it be reasonable to think about multiple SN apps running on the same device (suppose mobile) and thus sharing some client/stack that would limit bandwidth transfer over the air thus ensuring local caching & privacy (in case apps have different permissions). Is it the intent of this group to discuss this kind of topic or will the use cases stay at high level?

- requirement-wise: is it envisioned to derive requirements from these use cases (e.g. generalization of the "private content" uc to some permissions/privacy settings features) within this group? What is the next step expected after uc collection?

Cheers
walter

[1] http://activitystrea.ms/schema/1.0/activity-schema-02.html

-----Messaggio originale-----
Da: public-xg-federatedsocialweb-request@w3.org [mailto:public-xg-federatedsocialweb-request@w3.org] Per conto di Harry Halpin
Inviato: domenica 10 aprile 2011 2.25
A: public-xg-federatedsocialweb@w3.org
Oggetto: Meeting minutes from April 8th telecon

Here:

http://www.w3.org/2011/04/08-federated-minutes.html

Quite drafty, but should give you an idea of what was discussed, namely
SWAT1 use-cases. Comment, and feel free to ask for corrections.

 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.



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.

Received on Tuesday, 12 April 2011 07:43:18 UTC