SSE possibilities
Trying to get my head around the SSE possibilities, I posted some last time from what I understand of it.
The post Microsoft SSE and its Implications for Web 2.0 seems to know what it is talking about…although I don’t follow it very well.
From what I understand if you subscribe to someones SSE feed, anything they change on their site will replicate on your site…so it seems your website URL is subscribing to someones SSE feed.
Since there are no live examples I know of it’s hard to grasp how it works…I wonder how you are notified that a replicated change has been made on your site (I suppose you can subscribe to the RSS feed of the site as well and be notified in your RSS reader)…also is there a way to reject or accept the changes before they happen.
An example from the post above illustrates that User B receives data from User A via the SSE feed…
…how does this notification work…and what if User A didn’t want to send this particular content to User B, is there a way to turn off transmitting your content via SSE, and likewise is there a way for User B to turn off receiving other people’s content via SSE…in comparison you can’t really turn off RSS, you can’t decide, I want this blog post to appear in my blog (HTML), but I don’t want the content to appear in RSS readers (XML).
So with SSE maybe you can choose if you want your content transmitted via SSE at the time of posting, eg. if your partner subscribes to the SSE feed of your calendar, but you don’t want your latest entry to replicate on her calendar, as it isn’t relevant to her, you could say I’ll disable transmitting of this particular content via SSE and then post this new entry on my calendar…or maybe you post the new entry, and then it prompts if you want to send this new content via SSE.
Back to the example…User B can choose to accept or even modify the content before accepting it to be replicated (published) on his/her site, which in turn will be sent (replicated) to whoever subscribes to User B’s SSE feed, so long as User A subscribes to User B’s SSE feed the content will replicate on User A’s site.
…as mentioned before, you must be able to to manually turn on/off the transmittal or receiving of SSE feeds, because in this example if User B didn’t modify the content, User A would receive the exact same content, actually why would User A want even the modified content to appear on his/her site…so being able to accept or reject the SSE content makes sense.
I’m not sure if this is how it works…read the post linked to above to follow the rest of the illustration.
Feed Archive
Apparently SSE allows us to access the feed version of content based on any time/date…at the moment when you subscribe to a feed you usually get the last 10 or so entries, with SSE you can choose what ever range of entries you want…not sure how this works, sounds similar to FeedCatch.
Publish comments from your RSS reader
Reply to a post from within your RSS reader…not sure how this works, sounds similar to the comment API on RSS Bandit.
Collaboration
This is something I’m really interested in…I just don’t understand why you would want several people creating another version of the same document in real-time…isn’t this what DMS workflows avoid, isn’t the idea to create a new version from the previous version, and not several new versions to pick from, isn’t controlling a version a crucial aspect of DMS workflow.
More
When you receive content via SSE, the post says you can modify it and send it back out…where do you modify it, does modifying it mean publishing the content on your site, and sending it back out must mean transmitting an SSE version of your content.
So if you receive content via someone’s SSE feed, and choose to accept it to be replicated on your site, I gather it will be stamped with the original authors name, also does it somehow link back to their site…what if you modfiy the content before accepting it to be replicated on your site, will the content now be stamped with both authors names.
I can see this is going to raise huge copyright concerns, as before we just had remixing and re-syndicating RSS feed content, so it can be presented elswhere (re-syndicated), and/or the content is mixed in with other content (spliced feed), and sometimes there are no links back to the native site (rip off merchants).
This will be an even greater concern with SSE, as we are not just remixing the content with other content, we are actually modifying the content itself, just like sampling in Hop Hop music.
Firstly if you are offering an SSE feed you must be aware this will happen, so you could place a copyright notice that says “only replicating, no modifying.”
[ADDED: What about synchronising your bookmark managers, this would put the Multi-Submit Bookmarklet out of business.]
![email.png](http://services.nexodyne.com/email/icon/GxbiQvgbwBgCnw%3D%3D/oIp%2BJMQ%3D/R01haWw%3D/0/image.png"){kind=icon}
Being a fan of the possibilities of SSE, I’ll try to give my understandings of the specification through a couple of examples.
SSE and Blogs:
I subscribe to your feed through bloglines. This post, like all others, are delivered to my bloglines inbox where I access and read. When a particular post arrises that I’d like to comment on, I click the comment button, am redirected to your site where I’m able to post a comment.
Enter SSE. If you (or your blog software) were to implement SSE and Bloglines was to support it, it’d be possible for me to post my comment directly from the blogline reader. True, this is possible through APIs; but APIs are propriatary. An API written for TypePad is not the same as an API written for WordPress, currently it’s up to the RSS agregator software to support what APIs it desires. With SSE, an aggregator only has to support one specification.
SSE and Calender Apps:
My Wife uses Lotus. I use Outlook, Blackberry, and sometimes Upcoming. There’s never a single moment where all our calenders are sync’ed. To transfer an appointment from me to her I have to physically email her the information and she enteres it into her calender. It’s a hastle.
With SSE, I would set-up a group (say family appointments) and when both of us are subscribed to this group, any appointment she classifies as family will show on my various calenders and vice versa. Also, any changes either of us make to an appointment will automagically be reflected in the others calender.
SSE and Social Apps:
Take groups. I a jeep collector. There’s many groups dedicated to jeeps out there (yahoo, livejournal, google, ifsja, etc.). To stay up on jeeps would be a fulltime job. Say that I could find my favorite “jeep stay-up” software. With SSE (being that it’s supported on all platforms) I could read, post, and comment all from my favorite medium.
All these things are current possible with a lot of toil and coding, but the prospect of a simple standard of two-way data transfer; the possibilities are vast. Think. These are simple possibilites, when a mind far richer than mine captures the concept; some pretty sweet apps may come from this.
Comment by Ken Love — December 21, 2005 @ 7:44 pm