58
edits
Labs/PAC/Contacts: Difference between revisions
no edit summary
No edit summary |
No edit summary |
||
| (3 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
{{FeatureStatus | {{FeatureStatus | ||
|Feature name=Contacts | |Feature name=Contacts Mediator | ||
|Feature stage=Draft | |Feature stage=Draft | ||
|Feature status=In progress | |Feature status=In progress | ||
| Line 7: | Line 7: | ||
{{FeatureTeam}} | {{FeatureTeam}} | ||
{{FeaturePageBody | {{FeaturePageBody | ||
|Feature open issues and risks=* Do we provide our own contacts server? | |||
* How is caching/offline access handled? | |||
* How does it interact with the Profile Mediator and Profile Servers? Does this point to other users' Profile Servers? Or do they just return similar data types (jcard vs list of jcards)? | |||
|Feature overview=It's helpful to be able to have a central repository for all of your contacts across your networks. This centralized access point also allows for easier definition of relationships and access control. | |Feature overview=It's helpful to be able to have a central repository for all of your contacts across your networks. This centralized access point also allows for easier definition of relationships and access control. | ||
From this repository, sites can request access to a user's social graph to increase the site's features' social relevancy, and the user can limit the scope of social graph which said site can access. | From this repository, sites can request access to a user's social graph to increase the site's features' social relevancy, and the user can limit the scope of social graph which said site can access. As with all OWA Mediators, it allows for user selection of which services they wish to provide data to interested parties, be it Google Contacts, their Facebook graph, or a local Address Book. | ||
This feature will provide such | This feature will provide such an access point. Through interaction with a user's activity streams manager (Delta), the Contact Manager will also be able to know which of a user's contacts are already on sites which are requesting access to the graph, and only let the site know the relevant pieces of their social graph. | ||
|Feature users and use cases=* Provide a centralized access point for a user's contacts across various sites | |Feature users and use cases=* Provide a centralized access point for a user's contacts across various sites | ||
* Empower users to control sites' knowledge of their social graph | * Empower users to control sites' knowledge of their social graph | ||
| Line 21: | Line 24: | ||
* Storage server | * Storage server | ||
* Support for friend, follow, and private profile follow models | * Support for friend, follow, and private profile follow models | ||
|Feature ux design=* | |Feature ux design=* [http://stanford.edu/~bluenote/hosting/mozilla/contacts.get.png A site requesting limited contacts] | ||
* [http://stanford.edu/~bluenote/hosting/mozilla/contacts.view.png Browsing your address book] | |||
The site-based prefs will be implemented in content at an about page (<code>about:contacts</code>). It will be in-content (much like [about:addons]), and is intended to build off of the mechanisms of the [[Privacy/Features/Site-based_data_management_UI|Site-based data management UI]] as appropriate. | The site-based prefs will be implemented in content at an about page (<code>about:contacts</code>). It will be in-content (much like [about:addons]), and is intended to build off of the mechanisms of the [[Privacy/Features/Site-based_data_management_UI|Site-based data management UI]] as appropriate. | ||
|Feature implementation | |Feature implementation plan=* Salvage old Contacts Addon for API | ||
* | * Build mediator | ||
* Salvage old Contacts Addon for caching/offline access | |||
}} | }} | ||
{{FeatureInfo | {{FeatureInfo | ||