Specifiction discussion
Posted on:I’ve posted a “Browser Sync API” post on Specifiction, in order to stimulate some discussion there. If you prefer to discuss this topic there, please head on over and leave your thoughts in the thread.
The major browsers provide users with a means of synchronizing their data across browser instances, but the services behind that synchronization process are not controlled by users, and users don't have the ability to sync the data of their choice, or sync with other browsers.
Our goal is to create a specification for a browser sync process that gives users more control over their data, gives developers the ability to sync specific data for their web applications, and allows for a diverse marketplace of sync backend providers.
Note: Community Groups are proposed and run by the community. Although W3C hosts these conversations, the groups do not necessarily represent the views of the W3C Membership or staff.
I’ve posted a “Browser Sync API” post on Specifiction, in order to stimulate some discussion there. If you prefer to discuss this topic there, please head on over and leave your thoughts in the thread.
Good morning! I’ve written a call to action explaining why I think this community group is important, and some of the problems that we should be trying to solve in our discussions here. Please read and share: Open Sync: Your Browser Data in Your Hands.
One of our first goals should be to make sure the existence and mission of this community group is known to as many potentially interested parties as possible. I know a handful of people at Mozilla whom I’ve reached out to, but if any of you know people working on Chrome, Safari, Opera, or other browsers, or anyone at Dropbox, Sync, Box, or at Google working on Drive, please let them know that we would greatly appreciate their participation.
Thanks!
As far as “next-generation bookmarking”, the OpenAnnotation W3C Community Draft spec solves for many things. [1]
JSON-LD may be a bit more likely to gain support from browsers and services than RDF/XML. [2]
The Browser Sync Community Group has been launched:
The major browsers provide users with a means of synchronizing their data across browser instances, but the services behind that synchronization process are not controlled by users, and users don’t have the ability to sync the data of their choice, or sync with other browsers.
Our goal is to create a specification for a browser sync process that gives users more control over their data, gives developers the ability to sync specific data for their web applications, and allows for a diverse marketplace of sync backend providers.
In order to join the group, you will need a W3C account.
This is a community initiative. This group was originally proposed on 2014-05-23 by Ryan Freebern. The following people supported its creation: Ryan Freebern, Theodore Mielczarek, Robin Berjon, Ethan Dagner, robin garner. W3C’s hosting of this group does not imply endorsement of its activities.
The group now has access to W3C-hosted services for email, blog, wikis, irc, tracking tools, and more. Read more about tools and services available by default and upon request.
If you believe that there is an issue with this group that requires the attention of the W3C staff, please send us email on site-comments@w3.org
Thank you,
W3C Community Development Team
Welcome to Community noemi Groups. This is your first post. Edit or delete it, then start blogging!