Slashdot Mirror


Microsoft Proposes RSS Extension

An anonymous reader writes "Microsoft Chief Technical Officer Ray Ozzie said this week that his company is working on a new extension to RSS that would help users with different contact and calendar software and services synchronize each other's information." From the article: "If this sounds familiar to those using IBM's Lotus Notes, it should. SSE was conceived after Microsoft's recently recruited chief technology officer Ray Ozzie brainstormed with members of the Exchange, Outlook, MSN, Windows Mobile and Messenger Communicator product teams shortly after he joined."

234 comments

  1. Yea by nxaccount · · Score: 0

    Because they've already done so much for SPF.

    1. Re:Yea by WraithRealm · · Score: 1

      What, did they change the specs on sunscreen again!? And I was just getting used to them!

      --
      I aim to misbehave.
  2. Yay! by dduardo · · Score: 4, Funny

    Embrace and Extend!!

    1. Re:Yay! by Utopia · · Score: 4, Interesting

      The RSS standard itself allows for extensions.
      The extensions themselves can be standardized.

    2. Re:Yay! by greenskyx · · Score: 1

      "Embrace and Extend!!" Step 3. Extinguish Step 4. Profit

    3. Re:Yay! by bersl2 · · Score: 1

      Are the standardized extensions allowed to be patented into oblivion? I mean, think about who we're talking about.

    4. Re:Yay! by Anonymous Coward · · Score: 0

      Microsoft has once again missed the bandwagon, so their only solution is to ruin it.

      Why do they have to use RSS to do all this stuff? Can't they come up with something which is similar to RSS but call it a different name like RCS (Really Complicated Syndication), that way they get they want and everyone else on the planet remains happy.

    5. Re:Yay! by amliebsch · · Score: 1
      I already posted this much further down, but you might want to actually read the spec, which says at the bottom:
      As to software implementations, Microsoft is not aware of any patent claims it owns or controls that would be necessarily infringed by a software implementation that conforms to the specification's extensions. If Microsoft later becomes aware of any such necessary patent claims, Microsoft also agrees to offer a royalty-free patent license on reasonable and non-discriminatory terms and conditions to any such patent claims for the purpose of publishing and consuming the extensions set out in the specification.

      So, it seems to me that the answer to your query is "no."

      --
      If you don't know where you are going, you will wind up somewhere else.
    6. Re:Yay! by Anonymous Coward · · Score: 0

      But will they be standarized? And will they be designed well, or will this be another ActiveX, Cold-Fusion, IIS-4.0?

    7. Re:Yay! by cofaboy · · Score: 2, Insightful

      As to software implementations, Microsoft is not aware of any patent claims it owns or controls that would be necessarily infringed by a software implementation that conforms to the specification's extensions. If Microsoft later becomes aware of any such necessary patent claims, Microsoft also agrees to offer a royalty-free patent license on reasonable and non-discriminatory terms and conditions to any such patent claims for the purpose of publishing and consuming the extensions set out in the specification.

      Is this the same reasonable and non-discriminatory terms that exclude open source from other MS extentions etc?

      --
      In the end, It's all bovine dung you know
    8. Re:Yay! by MarsLander · · Score: 1

      Except on most previous occasions their "reasonable and non-discriminatory terms and conditions" have prevented implementations in free software. Completely coincidental, I'm sure.

    9. Re:Yay! by Anonymous Coward · · Score: 0

      As someone said (I wish I could remember who), RSS 2.0 and ATOM are an awesome way to transfer structured data. Like html, and unlike soap, rss is very simple. Anyone can pick it up and use it with very little code, and everyone does. RSS can easily become the default structured data transmission stadard for the web. It already is its specialised way.

    10. Re:Yay! by MaunaLoa · · Score: 1

      Is that a sequel to "Command & Conquer"?

      --
      Reality is that which, when you stop believing in it, doesn't go away. - Philip K. Dick
    11. Re:Yay! by lee7guy · · Score: 1

      Ceterum censeo Microsoftum esse delendam

      --
      Ceterum censeo Microsoftem esse delendam
    12. Re:Yay! by Anonymous Coward · · Score: 0

      You made a grammatical error there. If Microsoft were Microsoftum in Latin, delendam would be delendum. The adjective (ok, it's gerundive) has to be congruent with the noun.

      Also, I believe it is praetera, not ceterum.

    13. Re:Yay! by Mr.+Ghost · · Score: 1

      Why can't the call it RSS.Net or RSS++ or RSS#

    14. Re:Yay! by amliebsch · · Score: 1
      Is this the same reasonable and non-discriminatory terms that exclude open source from other MS extentions etc?

      I reject the conflation between "GPL" and "open source," and in any case, the question is moot until Microsoft actually asserts a patent right on this, which they haven't.

      --
      If you don't know where you are going, you will wind up somewhere else.
    15. Re:Yay! by hachete · · Score: 1

      as we all know, "Open Source" isn't reasonable to The Man

      --
      Patriotism is a virtue of the vicious
    16. Re:Yay! by sumdumass · · Score: 1

      Reasonable and non-discriminatory would be a reletive term. You are probably corect in that somethign completley opensource might interfere with the license provided by microsoft. I guess a true test would be if they actualy released somethign GPLed (compaitble) implementing this extension that we could all build from. I'm not aware that they could exert or exclude uses after doing this.

      In either way, It sounds like they have somethign that will make use of this extension and once it is a standard you cannot live without, Licenses might change. Thats why i think a GPL compaitble release with source code might squash your fears. It could be that thier intent is to have as many other programs as possible use this extention as part of some service they plan to offer. This way they could sell the service or create a need to the service technoligy and profit just by the existance of it. Maybe the service would have the patten restriction. It would be alot easier to sell product X that uses microsofts free extentions if every program capable of using RSS cna easily support it. Then they don'/t have to wait for a upgrade cycle before they instal the ability ot use it by default on every MS OS computer.

    17. Re:Yay! by Anonymous Coward · · Score: 0

      I can just imagine the tech boffins at Microsoft sitting around the boardroom table saying... "Now, how can we add exploits into RSS?"

    18. Re:Yay! by lee7guy · · Score: 1
      --
      Ceterum censeo Microsoftem esse delendam
  3. Embrace and extend by ThatGeek · · Score: 4, Funny

    Microsoft's motto is embrace and extend.

    It embraces like a boa constrictor, and then extends like a medieval torture rack.

    Microsoft, sit down, and let's hear from someone else.

    --
    What are you eating? isItVeg?.
    1. Re:Embrace and extend by aussie_a · · Score: 4, Insightful

      Right. So anytime Microsoft looks to add to an open-standard (you know, the thing open standards are meant to enable) they shouldn't be allowed? Wow, talk about openness. It's open for everyone, except those we dislike.

      Yes, Microsoft does have a habit of destroying standards by extending them. But they're going to do this regardless. They might as well work through a standards committee, and there isn't any indication that this will result in a proprietry product becoming part of the standard. Is there any reason other then "Cause Microsoft is evil" to not consider adding this extension to the standard?

    2. Re:Embrace and extend by pnatural · · Score: 1, Insightful

      So anytime Microsoft looks to add to an open-standard (you know, the thing open standards are meant to enable) they shouldn't be allowed?

      Correct.

      Wow, talk about openness. It's open for everyone, except those we dislike.

      It's open for everyone, except those whom have repeatedly shown their distain for standards and for those whom have repeatedly and purposefully corrupted the standards process with the expressed intent of extinguishing said standards.

    3. Re:Embrace and extend by bergeron76 · · Score: 2, Funny

      Microsoft has equal rights to any US Citizen and they should have their voice heard.
      US Corporations have to fight like hell these days to get their voices heard by Congress, and it's just unfair to not grant them equal rights! You progressives are all about "civil liberties, blah blah", so why don't you unite this country and [wait] Hey look! - There's a WAR over there...! I'm pulling for the guys in the grey outfits!

      w00t - Go Longhorn Devils!

      --
      Don't think that a small group of dedicated individuals can't change the world. It's the only thing that ever has.
    4. Re:Embrace and extend by Cylix · · Score: 1

      Yeah,

      While they could feasibly pull an exchange like variant with RSS their new tactic is a little more effective. I full expect to see their lovely new patent axe brought out on this one.

      Sure, you can touch it, taste it and even change it a bit... just be careful because the axe can fall at any time.

      At this point in the game, anytime anyone hears Microsoft talking about standards and services it is quite normal to watch everyone worry just like Oliver asking for more porage. (You notice he didn't ask a second time)-

      --
      "You should always go to other people's funerals; otherwise, they won't come to yours." -- Yogi Berra
    5. Re:Embrace and extend by HiThere · · Score: 1

      If standards are patented, then the patent has been dedicated to the public. Specifications can be patented, I suppose, but standards are supposed to be the way we agree to do things...and if someone holds an official government approved and enforced monopoly (i.e., patent) on the "standard", then it can't be the way that we agree to do things.

      So, no, I don't trust any "standard" that MS proposes. I'll wait a few years before I think about using it...long enough that I believe the doctrine of latches and estoppel will protect me.

      --

      I think we've pushed this "anyone can grow up to be president" thing too far.
    6. Re:Embrace and extend by koko775 · · Score: 1

      More accurately, ignore, deny, then embrace and extend. I talked to a Microsoft employee & Caltech graduate at Anime Expo 2005, who said that Microsoft's attitude towards RSS was that it was extremely flawed and would hurt the internet to promote.

      But if I recall, he also said that Microsoft was watching RSS, and that its popularity might force MS's hand. It seems that after noticing and disliking RSS, it's finally getting around to using it -- but, of course, with no love for standards.

      It's not really so evil as it is sinister -- Microsoft defines the standards because it is big, and Microsoft is big because it defines the standards. With the increasing usage of Firefox I hope we can break away from this vicious cycle. Besides, Microsoft "channels" (in IE 4 or 5 I think) were never any good, anyway.

    7. Re:Embrace and extend by node+3 · · Score: 4, Interesting

      It's just one of those things where you have to defer to reality.

      Yes, theoretically, Microsoft could act responsibly and cooperatively with regards to a public standard. However, given MS's past (ie: the reality of Microsoft), it makes sense to be extraordinarily skeptical of the outcome here.

      It's like this, you have this public well in the center of town, and anyone can come and take a drink, and can volunteer to help maintain and operate the well. There's one guy in town, Prince William the Third, who is known for taking free, public services and corrupting them, selling them, and otherwise claiming such things are immoral because they don't make anyone any money. He's gone into the public park, cordoned it off and charged people to play in his area. He's set vermin free in the communal corn fields. And at the local mercantile, he always takes a penny, but never leaves a penny.

      So you see him heading to the well with a large bucket and a drill... Do you think he's going to:

      A. Drill holes into his large bucket to loop the rope through, giving to the town a larger bucket making it easier for them to bring up water.

      or

      B. Fill up his big bucket, then drill a hole into the current bucket about halfway up to make using the public bucket a bit more difficult, and oh, btw, you can buy some water from his huge bucket.

      Yeah, maybe this time MS will play fair. I wouldn't bet on it. In fact, I'd say it's extremely foolish to think they'll do anything other than subvert the standard in a way that's designed to most benefit them. That's just what they do. Every single action MS makes is designed to give them the most competitive advantage they can get. There's nothing terribly wrong with this, just don't be so naive as to pretend they're even remotely likely to do otherwise.

      It's not that we hate MS, so we don't trust them, it's that they've lost our trust, so we hate them. They could easily earn it back. IBM did it, Apple did it. Hopefully, some day MS will do it, too.

      Hopefully this will all work out for the best, but skepticism is definitely called for.

    8. Re:Embrace and extend by Precambrian-C · · Score: 1

      Somebody PLEASE mod the parent Funny. It's scaring me to think it might not be intended to be funny.

    9. Re:Embrace and extend by jcr · · Score: 1

      So anytime Microsoft looks to add to an open-standard (you know, the thing open standards are meant to enable) they shouldn't be allowed?

      "Allowed" isn't really in question here. MS can of course ship any extension to any standard they feel like, except where limited by contract, as in the case of how they buggered Java. The question at hand is whether anyone else should play along.

      My immediate reaction to any "standards" proposed by MS is "eat flaming death, you pack of incompetent marketroids", but I'm open to being convinced that this time will be different. YMMV, but so far, I havent seen an instance where they meant well and delivered.

      -jcr

      --
      The only title of honor that a tyrant can grant is "Enemy of the State."
    10. Re:Embrace and extend by jcr · · Score: 2, Insightful

      Microsoft is big because it defines the standards.

      No, Microsfot is big because they picked up IBM's fumble and used that advantage to bugger the third-party apps developers, and hold the hardware companies hostage.

      -jcr

      --
      The only title of honor that a tyrant can grant is "Enemy of the State."
    11. Re:Embrace and extend by Lifewish · · Score: 2, Insightful

      I'm perfectly happy for them to add to an open standard. Just as long as their additions are kept as open as the standard was. Otherwise (for example if they patent their extensions) they're just leeching off the hard work of others, and historically such actions have mostly been anticompetitive too.

      I await the licensing of these extensions. Do you think they'll be GPL compatible?

      --
      For the love of God, please learn to spell "ridiculous"!!!
    12. Re:Embrace and extend by aussie_a · · Score: 1

      MS can of course ship any extension to any standard they feel like, except where limited by contract, as in the case of how they buggered Java.

      And then get accused of not following standards. They try to work through a standards body this time and everyone says "But Microsoft's extensions can never ever become a standard. Why? Well, simply because we don't like Microsoft."

    13. Re:Embrace and extend by jcr · · Score: 4, Insightful

      Why? Well, simply because we don't like Microsoft."

      More like, we don't trust Microsoft. Keep in mind that this animosity is not undeserved.

      -jcr

      --
      The only title of honor that a tyrant can grant is "Enemy of the State."
    14. Re:Embrace and extend by jacksonj04 · · Score: 1

      Sorry, open is open. There is no licence which specifically excludes Microsoft.

      --
      How many people can read hex if only you and dead people can read hex?
    15. Re:Embrace and extend by zapadoo · · Score: 1

      Let it not go unsaid (sorry if others have brought this up) that RSS is a crappy standard to build upon, but then, Micrsoft liked SOAP enough to mangle it. RSS is a defacto standard thanks to the wide userbase; but it was ill-conceived from the start. What kind of 'standard' needs an extension just to be able to account for more than one author of a piece of content?

      Atom would have been a far better building block...

    16. Re:Embrace and extend by Dryth · · Score: 1

      In fact, I'd say it's extremely foolish to think they'll do anything other than subvert the standard in a way that's designed to most benefit them.

      "Anything but subvert" seems a bit harsh. Every day I work with at least one standard that Microsoft took a role in the development of. One with the apparent intent of specifically avoiding lock-in in several respects. The (arguably) best implementations isn't Microsoft's own, and in most cases they communicate with each other quite happily. And, similar to this latest proposal, it's based upon existing standards which might help in curbing abuse.

    17. Re:Embrace and extend by aussie_a · · Score: 1

      Except that most people don't use Atom. I don't blame Microsoft for going for the de facto standard to try to build upon.

    18. Re:Embrace and extend by Anonymous Coward · · Score: 0

      Well, they have extended open standards before, and then patented the extensions.
      So, you can put on your history-blinkers if you like, but I'm not going to trust them.

    19. Re:Embrace and extend by Jesus_666 · · Score: 1

      Actually, I don't think it's possible for Microsoft to make the situation with RSS much worse. We have how many mutually incompatible RSSes? Seven? I know that at least two of them are called "RSS 3" - does any software support either of them? I have no idea. Just because a website offers an RSS feed and you have an RSS reader doesn't mean that you can read the feed. Ugh.

      Seriously, the only way they could screw up RSS even more would be by dropping all support for it (do they even support RSS?) and using their own patented format instead.

      They should offer this stuff as an extension to Atom, at least then we'd be able to use a standard that deserves the name.

      --
      USE HOT GRITS WITH STATUE OF NATALIE PORTMAN (NAKED AND PETRIFIED)
    20. Re:Embrace and extend by bheer · · Score: 1

      RSS is licensed under the Creative Commons. Microsoft's extension (SSE) is licensed under the Creative Commons. Then there is Microsoft's history on XML standards -- good interop even with competitors. This does not prove MS == angels, but it does indicate they're prepared to do the right thing.

      Maybe you should lay aside the tinfoil hat and actually RTFA sometime.

    21. Re:Embrace and extend by Anonymous Coward · · Score: 0

      > So anytime Microsoft looks to add to an open-standard

      I dont' recall MS ever 'adding' an 'open-standard' to anything in the context your putting it in. I'm sure they've added plenty of Microsoft standards to their products, but calling them 'open' is a fairy-tale.

      >Yes, Microsoft does have a habit of destroying standards by extending them.

      It's not a habit, it's their design. Marketing design. Microsoft is a very succesful marketing behemoth. They have proven they get what they want through marketing or monetary means. It seems you have bought the package hook, line and sinker.

      > Is there any reason other then "Cause Microsoft is evil" to not consider adding this extension to the standard?

      The same reasons they keep a gorrilla behind a cage at the zoo.

    22. Re:Embrace and extend by node+3 · · Score: 2, Insightful

      And, similar to this latest proposal, it's based upon existing standards which might help in curbing abuse.

      Like kerberos? Like CSS?

      I agree that the damage MS can do here is limited due to the nature of the proposed standard, but with MS, anything they promote as "open" (either open source or open standard) needs to be presumed guilty until proven innocent. This is based on their past behavior. I don't mean to say that seeking gain is wrong, just that with some corporations, you need to be more careful (from an open source/open standards point of view) than with others.

    23. Re:Embrace and extend by node+3 · · Score: 1

      Maybe you should lay aside the tinfoil hat and actually RTFA sometime.

      Care to explain the "tinfoil hat" comment? I'm not saying anything that isn't true. Every action MS takes is meant to help MS. If it helps others, that's a byproduct. MS supports tons of open standards, but only when it serves them.

      I'm not saying there's anything wrong with that. I'm not saying MS is out to get me. I'm just saying that MS does whatever MS thinks will best help them, and that it's important to keep that in mind when dealing with MS.

      MS still hasn't learned to be a good corporate citizen in the open source and open standards realms. I hope that some day they do (I use many of their products, and even like a lot of them). I just hold no illusions about MS's motives or honesty when dealing with the open (source/standards) world.

      Are you saying my skepticism is misguided? That I should accept MS's open source and open standards submissions on face value? How many times does MS have to be shown to misrepresent themselves before it's logical to more carefully scrutinize their actions before accepting their words?

      For MS customers (which I am one), this proposal is most likely going to be a good thing. But that doesn't mean they'll play nice with others (which I am also one). I'm not saying that MS is supposed to play nice with others (business is business, right?), just that, from the point of view of the "others", you've always got to keep one eye open with MS. It's just the rule when dealing with MS.

    24. Re:Embrace and extend by Dryth · · Score: 1

      Like kerberos? Like CSS?

      And these cases reflect the current situation how? Kerberos came out of MIT (and damn if Microsoft's extension didn't come with an RFC specifically declaring their modifications as non-standard), and CSS from academics who would subsequently join the W3C. Microsoft had majority involvement in neither, and as with all corporations, they're more likely to respect their own standards (which they cna distort from the very beginning in defining it, rather than down the road) than to respect standards put forth by others. They also weren't bedded entirely in existing standards, either, as with this SSE proposal, and as with SOAP.

      I don't doubt the abundance of other examples of Microsoft outlining a specifications than violating them, but there are certain restraints that limit the damage they can do in this case, and it's most similar other standards that have been hurt more by complexity than any nefarious distortion on Microsoft's part. If Microsoft were interested solely in locking down a standard in this case, why attempt a standard at all? From the evil point of view it makes sense to simply throw the XML into the wild without clear specification, leaving it more open to the introduction of backward compability and proprietary extension.

  4. Cha? by Anonymous Coward · · Score: 1, Insightful

    Why must they add their own custom extension to everything? It seems their behaviour (almost) always ends up leaving security holes in people's machines.

    1. Re:Cha? by Trigun · · Score: 4, Interesting

      You have to realize that Microsoft attracts the best and the brightest. That's not the best and the brightest programmers, but the best and the brightest managers, and the best and the brightest lawyers. Even if the programmers come out with the digital version of sliced bread, the managers will do what they do best and departmentalize the task, impose deadlines, and micro-manage. The Accountants will decide how to best make a profit off of this work. And the lawyers will implement it to ensure that there is nothing free or open about it.

      It's not just Microsoft, it's business. The sad fact is that Microsoft is even better at business than it is at programming.

    2. Re:Cha? by Anonymous Coward · · Score: 0

      Cha. Spot on, except that MS doesn't seem to be very good at programming with security in mind.

  5. RSS Stuff by jimmyhat3939 · · Score: 5, Interesting
    I can't stand it when they reuse acronyms. As every coder knows, SSE stands for Intel's follow-on to MMX ("streaming simd instruction set"), not "simple sharing extensions". Agh.

    Personally I think this is an example of a good technology (RSS) that Microsoft is trying to co-opt by coming out with something marginally "better" -- mostly just more complex -- so they can attain some elements of control over it.

    Oh and one other thing - they're basing it on the ideas underlying Exchange and Lotus Notes? I can't wait to see this one.

    --
    Free Conference Call -- No Spam, High Quality
    1. Re:RSS Stuff by Anonymous Coward · · Score: 0
      No way man. SSE stands for "Southern Connecticut Bankcorp", which has been around since 1881. So there!

      --

      Free 411! 1-800-411-SAVE

    2. Re:RSS Stuff by Jules+Mercuri · · Score: 1

      I would think that that would be S(treaming)S(IMD)I(nstruction set), but I guess that was taken by "server-side includes"? Argh, the acronym wars never end!

    3. Re:RSS Stuff by ergo98 · · Score: 4, Interesting

      Personally I think this is an example of a good technology (RSS) that Microsoft is trying to co-opt by coming out with something marginally "better" -- mostly just more complex -- so they can attain some elements of control over it.

      RSS is the absolutely height of simplicity. While that simplicity works for getting it out there and initially adopted, it does toss a wrench in it being a sustainable, growing technology. RSS is definitely showing signs of weakness (and the "next geners" are already chomping at the bit to switch to ATOM. I believe Google already tried to kill RSS), but thankfully it was built to support extensions (primarily just by supporting XML namespaces, but extensions were a part of the initial design).

      I rashly proposed my own simplistic extension to RSS to great improve the mechanical interpretation of RSS entries in certain domains.

    4. Re:RSS Stuff by Anonymous Coward · · Score: 0

      According to TFA, Microsoft is releasing it under Creative Commons. I think that this is the most important part of the article, which slashdot seemed to completely miss.

  6. dugg this one up last night by xoip · · Score: 0, Offtopic

    Someone else Found it on the digg_

    1. Re:dugg this one up last night by thenetbox · · Score: 4, Funny

      and by "someone else" you mean someone with the digg username xoip which happens to be your slashdot username? Not only did he beat slashdot but he also stole your nickname.

      gasp! that dastardly fellow!

    2. Re:dugg this one up last night by Anonymous Coward · · Score: 0

      He reads Digg.com, you can't expect him to be intelligent.

  7. Small but important correction... by Darth+Maul · · Score: 2, Insightful

    ...would help users with different contact and calendar software and services synchronize each other's information.

    Here, let me help you with that. I think what you really meant was this: ...would help users with different Miscrosoft contact and calendar software and services synchronize each other's information.

    --
    --- witty signature
    1. Re:Small but important correction... by xoip · · Score: 1

      I thought they were going to let all applications play nice and syncronize Just give them enough time and they will screw this one up too.

    2. Re:Small but important correction... by spideyct · · Score: 1

      The parent is a typical Slashbot kneejerk post, that adds nothing that we haven't heard for the last decade.

      It is especially juvenile considering the original statement from Ozzie specifically called out that a goal was to work with non-Microsoft products.

      "We brainstormed about this "meshed world" and how we might best serve it - a world where each of these products and others' products could both manage these objects and synchronize each others' changes"
      http://spaces.msn.com/members/rayozzie/Blog/cns!1p yct_cYtbBtOBPDVAumMEdw!175.entry

      MS: "I like oranges"
      You: "I think what you really mean was.. you don't like oranges!" bwahahaha, high five guys!
      Slashdot: Burn! Man, that was insightful! High five!

    3. Re:Small but important correction... by Anonymous Coward · · Score: 0

      MS: "I like oranges"
      You: "I think what you really mean was.. you don't like oranges!" bwahahaha, high five guys!
      Slashdot: Burn! Man, that was insightful! High five!


      Now that was fruity.

    4. Re:Small but important correction... by bit01 · · Score: 1

      The parent is a typical Slashbot kneejerk post, that adds nothing that we haven't heard for the last decade.

      Well, since M$ hasn't changed their attitude to open standards in more than a decade, in fact since they were established, it's entirely appropriate to repeat it. The fact that a M$ engineering representative said they want to interroperate is almost completely irrelevant. M$ has a long history of talking the talk but not walking the walk.

      M$ might one day reform but it will take a huge effort to cancel out their history, not just a few minor marketing ploys. IBM was able to do it; I'm hopeful M$ can too.

      I've no doubt the technical people behind this proposal mean well, but what M$ does with standards is driven by their lawyers, marketing 'droids and managers, not their engineers.

    5. Re:Small but important correction... by killjoe · · Score: 2, Insightful

      "MS: "I like oranges"
      You: "I think what you really mean was.. you don't like oranges!" bwahahaha, high five guys!"

      No it's more like this.

      MS: "I like oranges"
      me: "for the last five years you have done nothing but lie to me I don't believe you for one second. Please take your hands out of your pockets so I can see if you are holding a knife. The last fifty times you knifed me it hurt like hell and cost me lots of money"

      See how that works?

      --
      evil is as evil does
    6. Re:Small but important correction... by spideyct · · Score: 1

      They're using a Creative Commons license. They're creating an RSS extension, instead of coming up with an entirely new format. They worked with the RSS community to get feedback and fine tune. They're following the processes as defined for open source software.
      Are those processes and licenses so fragile and irrelevant/impotent that they can be co-opted/corrupted so easily? If so, should any business in their right mind use any software based on such licenses?

    7. Re:Small but important correction... by towsonu2003 · · Score: 1

      mod this correction up so that people reading the news can also see the correction...

    8. Re:Small but important correction... by killjoe · · Score: 1

      "Are those processes and licenses so fragile and irrelevant/impotent that they can be co-opted/corrupted so easily? If so, should any business in their right mind use any software based on such licenses?"

      1) MS could have used groupdav or an already existing standard.
      2) Why would anybody trust MS to do right thing, ever? How many times does someone need to stab you in the back before you treat them with caution?

      --
      evil is as evil does
  8. Awesome! by Eightyford · · Score: 2, Funny

    I hope they do as good a job with RSS as they did with HTML! Actually, to be fair, Netscape was just as bad with that. But I did like the scrolling better than the blinking.

    1. Re:Awesome! by Myen · · Score: 1

      Err, I'm not sure if RSS needs any help screwing up. See here (Google cache because the guy's site seems to be down).

    2. Re:Awesome! by Eightyford · · Score: 1

      9 versions! No wonder I can never get RSS to work properly.

    3. Re:Awesome! by ToasterofDOOM · · Score: 1

      Here's some good reading that you'd take some benefit from.

      --
      I am Spartacus
    4. Re:Awesome! by Eightyford · · Score: 1

      Heh, I think you misunderstood me. I don't actually use blinking or scrolling text. Maybe you clicked on my cannedgames.com link. Sure it's ugly, but I don't mind at all!

    5. Re:Awesome! by HeroreV · · Score: 1

      Why choose? Firefox can give you both!

    6. Re:Awesome! by Phroggy · · Score: 2, Informative

      Please keep in mind that Microsoft invented AJAX, without which things like Google Maps and GMail wouldn't be possible.

      Personally, I'm glad Microsoft is proposing a standard extension to RSS, instead of using their own proprietary format or protocol for this sort of thing. If you were trying to make a piece of third-party software interoperate with Exchange or Outlook, wouldn't you be glad too? Instead of trying to reverse-engineer some weird proprietary format, somebody will just extend the RSS libraries already available for your language of choice and you'll be able to use those (I expect XML::RSS::MSExtThingie will show up on CPAN within about 15 minutes of this new standard being published, and you'll be able to compile it into the next version of PHP).

      --
      $x='S24;r)>63/* h@<5+oZ)32"5cz';$me='phroggy'x$];
      $x=~y+ -xz+\0-Tx+;print$_^chop$me for split'',$x;
    7. Re:Awesome! by jferris · · Score: 1
      Please keep in mind that Microsoft invented AJAX, without which things like Google Maps and GMail wouldn't be possible.

      Not quite. Microsoft implemented XMLHTTP in the MSXML library. It was forward thinking developers who started using it from web clients in the fashion that is now known as AJAX. XMLHTTP, at the time, was primarily intended to facilitate SOAP messaging as a replacement to traditional client server applications. Once people started using it as the TNYKAA (Technology Not Yet Known As Ajax), Microsoft quickly changed direction in the emphasis of its usage.

      Not only did the shop that I previously worked at implement AJAX before it had an acronym, a lot of other people that I have talked to have done so, as well. And these projects predate Google Maps and GMail by a fair shake, too.

      --
      You are in a maze of little twisting passages, all different.
    8. Re:Awesome! by Phroggy · · Score: 1

      Not only did the shop that I previously worked at implement AJAX before it had an acronym, a lot of other people that I have talked to have done so, as well. And these projects predate Google Maps and GMail by a fair shake, too.

      Of course I didn't mean to imply that Microsoft called it AJAX; that's a recent buzzword applied by somebody else. Nor did I mean that Google Maps and GMail were the first webapps to use it. Microsoft created it so they could get Outlook Web Access (OWA) to work without sucking ass, and of course what others have done with it since then has been really cool.

      --
      $x='S24;r)>63/* h@<5+oZ)32"5cz';$me='phroggy'x$];
      $x=~y+ -xz+\0-Tx+;print$_^chop$me for split'',$x;
    9. Re:Awesome! by elemental23 · · Score: 1

      I had forgotten how annoying and full of himself ESR is. Thanks for the reminder.

      --
      I like my women like my coffee... pale and bitter.
    10. Re:Awesome! by ToasterofDOOM · · Score: 1

      Very true, but sometimes he does have a point.

      --
      I am Spartacus
  9. Pointless by Kickboy12 · · Score: 3, Interesting

    If this software/service follows the same trends as the rest of their products, Microsoft will once again be punted by somebody who takes the same concept one step further. Futher more, Microsoft will some how find a way to make this peice of software so insecure that sombody from India will be able to edit your RSS files. Then Microsoft will claim blasphemy and be yelled at by screaming Linux geeks.

    Erego; pointless.

    1. Re:Pointless by ggvaidya · · Score: 1

      Microsoft will some how find a way to make this peice of software so insecure that sombody from India will be able to edit your RSS files

      That's not too bad; we only really need to worry once it gets easy enough for an American to do it ... :P

  10. Improvements by WookieinHeat · · Score: 2, Funny

    MS will make this better the same way they make everything else better, by adding stuff on top.

    I think their moto should be "if its broke, pour some paint on it so you don't see that part!"

    Bloat...? Whats that?

    1. Re:Improvements by black+mariah · · Score: 0
      Bloat...? Whats that?
      I can see you haven't run KDE in a while.
      --
      'Standards' in computing only impress those who are impressed by things like 'standards'.
    2. Re:Improvements by kfg · · Score: 1

      The proper form of the motto is:

      Putty and paint makes up for what a carpenter ain't.

      KFG

    3. Re:Improvements by AndroidCat · · Score: 1

      I thought their motto was "Beautiful plumage!"

      --
      One line blog. I hear that they're called Twitters now.
  11. Microsoft extensions? by saskboy · · Score: 2, Insightful

    May I point out that when IE extended the abilities of the WWW, we ended up with worms and exploits up the wazoo. Is RSS relatively safe as it is now, and if so, why muck with it? Just what we'd need is a worm that can exploit a technology designed to deliver new information to everyone at once.

    --
    Saskboy's blog is good. 9 out of 10 dentists agree.
    1. Re:Microsoft extensions? by Nebu · · Score: 2, Insightful

      It's not inordinately difficult to make an extension safe. I mean, CSS has also extended the abilities of the WWW without introducing any new exploits.

      I don't think Microsoft is planning on turning RSS into a Turing Complete language or anything.

    2. Re:Microsoft extensions? by saskboy · · Score: 3, Interesting

      We all thought JPG, PNG, and MP3 were safe file types, but that turned out to not be the case when you used a vulnerable standard viewer. Adding more stuff introduces more risk. We have to ask is the added usability worth the mild risk?

      --
      Saskboy's blog is good. 9 out of 10 dentists agree.
    3. Re:Microsoft extensions? by Nebu · · Score: 5, Insightful

      The vulnerabilities that you are referring to are called "Buffer Overflow Attacks", and it has nothing to do with the format. The problem lies with the viewers. Even TXTs can have buffer overflow attacks injected to them, though no TXT viewer is known to be supceptible yet.

    4. Re:Microsoft extensions? by shinghei · · Score: 2, Insightful

      It's probably not the standard itself that is vulnerable. It's the IMPLEMENTATION of the standard.

    5. Re:Microsoft extensions? by Yhippa · · Score: 1

      Hopefully this will be a little different as RSS readers seem to be fragmented. That is, there doesn't appear to be "One Reader to Rule Them All." We actually have a choice in this matter. Microsoft had IE automatically installed on the majority of the world's computers, so developers created their code to work with that.

    6. Re:Microsoft extensions? by jrockway · · Score: 1

      > no TXT viewer is known to be supceptible yet

      You've obviously never used finger. I think finger was the original buffer overflow :)

      --
      My other car is first.
  12. Kerberos by Anonymous Coward · · Score: 4, Interesting

    Any bets this extension to RSS will be like what they did to Kerberos? It will be incompatible will existing RSS implementations. Any details will have to be reverse engineered or require immense community pressure to have disclosed.

    And sombody better cross reference this to Microsoft's patent filings.

    1. Re:Kerberos by thparker · · Score: 2, Informative
      Any details will have to be reverse engineered or require immense community pressure to have disclosed.

      You mean the sooper sekrit details posted here under a Creative Commons license, which was linked in TFA?

      Listen, I'm not prepared to take everything they say at face value, but this is probably a step in the right direction. We have an instance where they've proposed this extension and published it, for anyone to use.

      Now, someone more technical than me will have to review what they've published and comment on what, if anything, it screws up.

    2. Re:Kerberos by buckhead_buddy · · Score: 1
      Anonymous Coward wrote:
      Any bets this extension to RSS will be like what they did to Kerberos?
      It's probably related to security. It'll allow users to "subscribe" to the latest set of exploits automatically. Users won't have to depend on infected emails or auto-run programs on CD's.
    3. Re:Kerberos by Dr.+Sp0ng · · Score: 2, Insightful

      Heh. there are so many incompatible and somewhat-compatible versions and implementations of RSS out there that they can't make the situation worse (actually, they're actively trying to clean up the RSS scene by making IE7 reject malformed XML... that'll make a whole lot of people fix their shit real quick).

    4. Re:Kerberos by killjoe · · Score: 0

      Is it patented? Does the creative commons license protect me from MS patents.

      --
      evil is as evil does
    5. Re:Kerberos by hachete · · Score: 1

      The *specification* is under the CC licence. So you're talking bollocks :) The kicker:

      "As to software implementations, Microsoft is not aware of any patent claims it owns or controls that would be necessarily infringed by a software implementation that conforms to the specification's extensions."

      I think this means that it's already patented the implementations it already has. Nice.

      h

      --
      Patriotism is a virtue of the vicious
    6. Re:Kerberos by thparker · · Score: 1

      I'm not certain if this is a requirement of the Creative Commons license or not, but there is a disclosure on the Microsoft page at the bottom where it discusses the licensing. It states that the material in the document does not infringe on any MS patents.

    7. Re:Kerberos by thparker · · Score: 1
      The *specification* is under the CC licence. So you're talking bollocks :)

      That's the first step. The specification needs to be open and published, and freely available. This is the opposite of the MS Word document format, and is not a bad thing.

      "As to software implementations, Microsoft is not aware of any patent claims it owns or controls that would be necessarily infringed by a software implementation that conforms to the specification's extensions." I think this means that it's already patented the implementations it already has. Nice.

      IANAL, but I read this as exactly the opposite. I really don't see anything in that sentence to support your reading of it. It doesn't say anything about Microsoft's implementation or affirms a patent. They're saying that MS has no patent that you would be infringing if you created an implementation that conforms to the spec.

      To be more picky -- it says "necessarily infringed". Just creating something that interoperable using the spec would be fine. Someone else will have to speak to patents related to Outlook data format, which is the whole point of this. But again, if you just publish your data to interoperate with Outlook, you wouldn't be infringing. As I read it. Could be wrong. :-)

    8. Re:Kerberos by hachete · · Score: 1

      I don't see anything in that statement to support your construction. The deciding test is to see if there are patents on RSS SSE.

      h

      --
      Patriotism is a virtue of the vicious
    9. Re:Kerberos by Phil06 · · Score: 1

      If original web browsers had stubbornly rejected malformed HTML, the web would not have taken off like it did. Stodgy perfectionists would have been happy though.

      --
      "...and yet, I blame society" Duke - Repo Man
    10. Re:Kerberos by Dr.+Sp0ng · · Score: 1

      That's true, but RSS and HTML are 2 different things - while a lot of people hand-write their HTML, especially in the early days of the web, RSS is rarely (if ever) hand-written. It's generated by software and read by software, and therefore there's no excuse or reason for malformed XML, especially when it makes parsing that much more difficult.

    11. Re:Kerberos by killjoe · · Score: 1

      It doesn't say that. It says they don't think that it does and if one is found it will be available under RAND licensing.

      MS is probably lying about the patents, (they lie pretty much all the time) there probably is a patent and they will make it available under RAND which is not compatible with open source licenses.

      --
      evil is as evil does
    12. Re:Kerberos by thparker · · Score: 1
      It doesn't say that. It says they don't think that it does and if one is found it will be available under RAND licensing.

      You're absolutely correct. I completely missed the additional language the first time through. I apologize for my imprecision. And yeah, they could be lying.

      I still think putting this out there under a CC license is more good than bad. In the past, I think they would have just incorporated any extensions into their software and then promoted FUD about everyone else's software being broken. So if one accepts the premise that this is a positive move on Microsoft's part, then I think the more interesting question is, why have they done it?

      I'm optimistic, and hoping that it's because the ol' monopoly-engine isn't what it used to be.

    13. Re:Kerberos by killjoe · · Score: 1

      Ms has always tried to paint a patina of openness on their closed procotols and file formats. They just want to be able to say that they support open formats so the CIOs can be fooled.

      At it's core I don't think anybody at Ms believes in open formats or supporting open standards. It seems to me that they would have supported at least one or two popular open standards like HTML, Kerberos, LDAP, or something. The fact is everytime they had a choice as to follow a standard or break one they have chosen to break one. Even if the standard was proposed by them (see c#).

      --
      evil is as evil does
  13. Translation! by jav1231 · · Score: 4, Funny

    Bill: "Basically, RSS is a technology we have little marketshare in and we'd like to alter to give us a chance to catch up. Eventually, of course, we will monopolise the technology bastardizing it until only our RSS reader, Internet Extreme Explorer, is the only tool that will correctly read it. What? Not a good idea? I thought it was fresh!"

    1. Re:Translation! by Anonymous Coward · · Score: 0

      Replace RSS with OpenGL and DirectX with IXE (Xtreme, because X is more popular than E)and I'm hearing deja vu - oh how horrible a world it will be when MS bastardizes every new technology like they did OpenGL.

  14. we can predict that... by penguin-collective · · Score: 4, Insightful

    Microsoft's "new" RSS format will be XML based, it will turn out in six months that they have filed a patent on it, they will offer a RAND license, they'll submit it as an ECMA standard, and they'll proclaim that it's open. Microsoft will recruit Apple and Oracle to sign up for "free" licenses of their "standard" and proudly announce their adoption of it.

    And then Microsoft will try to create FUD (through strategically placed speakers) within the open source community whether it is really possible for open source software to implement their "open" standard. They'll do this in an effort to scare away commercial users from adopting open source software based on the "open standard".

    That way, they'll try to achieve the appearance and widespread adoption of an "open" standard while still interfering with its open source implementation.

    1. Re:we can predict that... by pclminion · · Score: 1
      Microsoft's "new" RSS format will be XML based

      Uhh... RSS is already XML based.

    2. Re:we can predict that... by penguin-collective · · Score: 1

      Just because the RSS part is XML-based doesn't mean the information it carries needs to be--Microsoft has already demonstrated that.

    3. Re:we can predict that... by Jesus_666 · · Score: 1

      Most of the time. Some RSSes are RDF based. We can't tell whether Microsoft will use RSS 0.90, 0.91, 0.91, 0.92, 0.93, 0.94, 1.0, 2.0, 2.01, 2.01, 3.0 or 3.0. The repetitions are intentional, as some versions have been implemented more than once (0.91: Netscape vs. Userland; 2.01: Two incompatible revisions by Userland. All 2.01 RSSes use the official version number 2.0; 3.0: Two implementations that have nothing to do with all other RSSes at all). IIRC, 0.90, 1.0 and one of the 3.0s are RDF-based.

      --
      USE HOT GRITS WITH STATUE OF NATALIE PORTMAN (NAKED AND PETRIFIED)
    4. Re:we can predict that... by 75bhp · · Score: 1

      QUICK!!!

      Somebody apply for a patent on the steps outlined!! That way Microsoft will prevented from following through and will be dancing for us.

      nyaahh!

  15. why? by soapdog · · Score: 5, Interesting

    Why use RSS for that when vCard and iCalendar specs already cover that and are implemented by many groupware suites out there. The RFCs cover from HTTP transport of calendar and contact data as well as other MIME enclosures... And it's a simple and elegant format, it's not XML based but it works! Why reinvent the well this time? more info on vCard and iCalendar at http://www.imc.org/pdi/

    --
    -- Por mais que eu ande no vale das trevas e da morte, meu PowerMac G4 Não Travará!!!
    1. Re:why? by Thundersnatch · · Score: 2, Interesting

      Outlook & Exchange Server already support vCard and iCal. I think there must be something more to this RSS stuff. Group calendaring is specifically mentioned (which iCal does not support AFAIK).

    2. Re:why? by Zapd · · Score: 1

      This spec doesn't reinvent calendar or contact-list wheels.

      If you bothered to read the specs, this extension adds simple synchronisation logic for two or more feeds with OPML / RSS items, no more, no less. It does not define a transport protocol, it doesn't have to do anything with the content enclosed in the RSS items.

      The only re-inventors of the wheel are people that use this extention to create aplications that use this specification to SSE-sync embedded vCard or iCalendal-like items.

      --
      The imp hits!
    3. Re:why? by Ilgaz · · Score: 1

      They theoretically support IMAP 4 and POP3 too but for some reason I really don't know, people on Exchange servers either uses Outlook, Entourage or licensed (?) stuff like Apple OS X Mail to get their mail from Exchange servers.

      There is a trick somewhere. I am totally clueless about the corporate networks but I can easily see from outside.

    4. Re:why? by metamatic · · Score: 1
      This spec doesn't reinvent calendar or contact-list wheels.

      If you bothered to read the specs, this extension adds simple synchronisation logic for two or more feeds with OPML / RSS items, no more, no less.


      In other words, it reinvents the SyncML wheel?
      --
      GCHQ Quantum Insert installed. If only our tongues were made of glass, how much more careful we would be when we speak
    5. Re:why? by Mr.+No+Skills · · Score: 1

      Partially support them. Outlook does not let you import an iCal file with multiple records in it.

      --
      Sleep is for the Weak
    6. Re:why? by Thundersnatch · · Score: 1
      They theoretically support IMAP 4 and POP3 too but for some reason I really don't know, people on Exchange servers either uses Outlook, Entourage or licensed (?) stuff like Apple OS X Mail to get their mail from Exchange servers.

      POP3 and IMAP4 work just fine on Exchange server; I used Thunderbird as my mail client for a time there just to see what all the hype was about. But most organizations use the other clients with Exchange because they offer features not available with IMAP4 and POP3. Like public folders, group scheduling, delegation for administrtive assistants, folder-level permissions, server-side rule creation, etc.

      Group scheduling is the killer app for Exchange in my company: conference rooms, projectors, laptops, lunch service and the like are all reserved by the users themselves. We would have to build a separate app to handle the scheduling all that stuff, and it wouldn't be integrated with the mail client and calendaring application that people use every day. With Exchange, all the users have to do is invite a conference room to a meeting along with other people, and it accepts automatically if it is available.

  16. woohoo! by ndruw1 · · Score: 1

    now ill have super slashdot feeds...powered by supreme M$ technology! fantastic

  17. profit ??? by Anonymous Coward · · Score: 0

    1. Extend RSS

    2. ...

    3. profit??

  18. Just say No by rodgster · · Score: 1

    to proprietary, close, non-standards based bastardizations.

    --
    Who will guard the guards?
    1. Re:Just say No by Ohreally_factor · · Score: 4, Funny

      Or to coin a phrase, bastandardizations.

      --
      It's not offtopic, dumbass. It's orthogonal.
    2. Re:Just say No by jbrader · · Score: 1

      Nice. I move that we declare bastandardizations a new word.

      --
      You are so boring that when I see you my feet go to sleep.
    3. Re:Just say No by Anonymous Coward · · Score: 0

      Looks like we misunderestimated your language skills after all.

    4. Re:Just say No by Anonymous Coward · · Score: 0

      Easy for most of the people partcipating on this site to say NO to Microsoft but for the general computer using population, they'll use whatever Microsoft includes with their OS. Microsoft certainly has a right to participate but hopefully they'll approach it with the proper spirit rather than finding a way to lock it down.

  19. But didn't Lotus Notes suck? by OsirisX11 · · Score: 3, Funny

    "But didn't Lotus Notes suck?"

    Yeah..but....look where they are now. :)

    1. Re:But didn't Lotus Notes suck? by calculadoru · · Score: 1

      Flash news: Lotus Notes still sucks. The big ones.

      --
      The power of accurate observation is commonly called cynicism by those who have not got it. -- G.B. Shaw
    2. Re:But didn't Lotus Notes suck? by Anonymous Coward · · Score: 0

      And now, still sucking in last place... Lotus Notes.

      Domino: the quasi-web server poorly hacked into the middle of a non-relational quasi-database. All proprietary. Yummy.

    3. Re:But didn't Lotus Notes suck? by EMacAonghusa · · Score: 1

      It still sucks! I'm forced to use it and it pains me!

  20. RDF by SWroclawski · · Score: 3, Interesting

    RSS is a form of RDF, and so this idea of an "extension" is a little both misleading and confusing.

    Part of the point of RDF is that you can embed lots of vocabularies in a single document. You can say, for example, that a RSS publisher has an attribute FoaF document, or even arbitrary FoaF properies. Or you could use an RDF version of vCard, or RDF iCal...

    That's all been part of the Semantic Web for a long time.

    It seems that instead of the standards, the proposal is for yet another complete extension from Microsoft.

    I think RDF needs help getting the full adoption it needs, but based on what Microsoft has done to other standards (Kerberos, SPF, HTML, etc.) I don't think that this will end up being the right approach to fix any problems RSS has.

    1. Re:RDF by Jerf · · Score: 2, Informative

      "RSS" is not a form of RDF. Only "RSS 1.0" is a form of RDF, and it is, by far, not the commonly-used version. SSE is built on RSS 2.0 which is not RDF at all.

      RSS 2.0 supports XML namespaces. This defines such a namespace. RDF is not involved.

    2. Re:RDF by SWroclawski · · Score: 2, Informative

      Fair enough. I was't aware that RSS 2 isn't RDF based.

      But even XML namespaces makes any extension like this pretty much unecessary.

      It's a shame that RSS couldn't still be RDF... RDF needs more "killer apps".

    3. Re:RDF by Jerf · · Score: 1

      But even XML namespaces makes any extension like this pretty much unecessary.

      Uh, no. What XML namespaces means is that Microsoft can declare this extension without any revision of the core RSS spec.

      It doesn't mean that they don't need to declare what namespace they are using and explain what it means to other people if they expect other people to be using it and building on it, which is exactly what they've done.

      XML namespaces isn't some sort of magic that eliminates the need to explain specifications, or whatever other thing it is you think Microsoft doesn't need to have done, since they done pretty much exactly what they needed to do.

    4. Re:RDF by Anonymous Coward · · Score: 1, Funny

      There were lots of killer RDF apps, but it turned out that they were all friends of friends with each other so they were easy to hunt down and neutralize.

    5. Re:RDF by Anonymous Coward · · Score: 0

      Uh, no

      All I needed to know that the rest of the comment would be something extremely arrogant and not worth reading further. Thanks!
    6. Re:RDF by osi79 · · Score: 1

      > It's a shame that RSS couldn't still > be RDF... RDF needs more "killer > apps". First of all, RDF needs a better XML representation. In it's current form, RDF/XML is confusing and hardly human- (or: programmer-)readable. For the average programmer who wants to write a little RSS-processing app and doesn't care about semantic web and the like, RSS2 or Atom are just more clear and less obfuscated. Of course, having 1000 formats and variants is a problem, too. But the basic XML representation of these formats makes simple things simple, RDF does not. I like the RDF model (somewhat, if Reification wasn't that complicated, I would like it even more), but the XML representation sucks for simple purposes like syndication.

  21. Oh great, just great by ewe2 · · Score: 2, Insightful

    So let me guess: they'll stick binary data in RSS.

    Then we have remote execution via RSS, system automation via RSS, a rootkit you never realized was there via RSS. FFS, use the tool for what it was intended, not a hacked-up stealth technology for taking over blogs and putting pretty pictures all over it.

    --
    insecurity asks the wrong question irritation gives the wrong answer
    1. Re:Oh great, just great by tomstdenis · · Score: 1

      But text is soooo boring.

      I mean why use text emails when you can use 100s of colourful and usually non-portable fonts to liven up your communication :-)

      Tom

      --
      Someday, I'll have a real sig.
    2. Re:Oh great, just great by Anonymous Coward · · Score: 0

      not having binary does not give you any protection from exploiting a poorly written RSS reader, if you are of the believe that you can't be exploited through a non binary RSS feed then I have a bridge I would like to sell you :-)

    3. Re:Oh great, just great by Keichann · · Score: 1

      The parent is insightful? Read the spec and find a use of binary data.

      This will neither break existing (well-designed) readers, nor be 'evil'. In fact, it seems like a good idea. I'll only use it in the workplace, where it belongs, mind.

    4. Re:Oh great, just great by Zapd · · Score: 1

      This will neither break existing (well-designed) readers, nor be 'evil'. In fact, it seems like a good idea. I'll only use it in the workplace, where it belongs, mind.

      Seems to me that if you want to mutually sync your RSS items, you should do that only with trusted feeds over a trusted channel anyway.

      --
      The imp hits!
    5. Re:Oh great, just great by Anonymous Coward · · Score: 0

      So let me guess

      FFS, use the tool for what it was intended, not a hacked-up stealth technology for taking over blogs and putting pretty pictures all over it.

      rofl, you got angry over your guess huh? :)

  22. Any patents yet? by One+Louder · · Score: 1

    Any takers on whether or not they'll attempt to patent these extensions, and make sure that they cannot be licensed in a manner compatible with the GPL?

    1. Re:Any patents yet? by CrazedWalrus · · Score: 1

      Read the MSDN SSE Spec (as linked above by another poster I'm too lazy to search for).

      In particular, check out Licensing Information at the bottom. They don't seem to want to patent this -- at least at the moment. They've got a very clear statement there that would be difficult to reneg on.

      Also, for those suspecting that MS will embed binaries, I didn't see anything to support this suspicion in the spec.

  23. response to the proposal by ChipMonk · · Score: 4, Funny

    Dear Microsoft,

    No.

    Signed,
    Everyone On The Internet

    1. Re:response to the proposal by superpulpsicle · · Score: 1

      ROFLMAO. This should be the standard automated first post response for all M$ related articles.

    2. Re:response to the proposal by unbeatable73 · · Score: 0
    3. Re:response to the proposal by Otter · · Score: 4, Funny
      Actually, my reaction was more:

      Dear Guy Who Invented Lotus Notes,

      If I have to use a second piece of software written by you, I swear I'll chew my fingers off.

      Signed,

      Everyone Who Has To Use That Nightmarish Piece Of Crap

    4. Re:response to the proposal by bheer · · Score: 1

      As a Notes user (not developer) I have to disagree. Notes has major suckage, but mostly in client UI. Notes' UI makes complete sense if you get your head around the Notes 'model'. If you try treating it like a simple MUA you'll get a lot of grief (sort of like treating emacs like just another editor).

      However, a lot of Notes' ideas were WAY ahead of their time and work well (as long as you aren't worried about scaling, which is more involved). Replication, unstructured data storage, workflow, forms-based development ... there's a reason for the oft-heard Notes developers' saying "it was in Notes for years".

    5. Re:response to the proposal by dxminxs · · Score: 0

      The single most secure/robust/reliable messaging/calendaring/collaboration platform ever, in use by 40,000 + employees at my workplace, for close to 10 years. Thank you man who invented Lotus Notes, thank you indeed, for saving me *thousands* of virus calls should we have used exchange/outlook.

    6. Re:response to the proposal by Otter · · Score: 1
      If you try treating it like a simple MUA you'll get a lot of grief (sort of like treating emacs like just another editor).

      Actually, emacs is the analogy I always use against this defense of Notes. Yes, emacs has all sorts of great features despite being a lousy email client -- but that doesn't make it a good idea to standardize on emacs as a corporate email client! Similarly, Notes may be a fantastic everything-but-an-email-client, but it's my email client!

    7. Re:response to the proposal by ChipMonk · · Score: 1

      Why isn't that a top-level post? Microsoft could learn a lot from it.

    8. Re:response to the proposal by bheer · · Score: 1

      But what if emacs' lisp environment was useful to IT departments to roll out internal apps?

      Lots of companies (including (most of?) GE) use Notes as a standard not because it's the greatest email client ever, but because they can get lots of internal workflow apps quickly written and deployed, even to a countrywide scale. However, because of late a lot of these apps have been converted to Domino web apps, many users don't even know their intranet apps run on Domino!

      Thankfully, IBM's current strategy is to phase out the Notes client in favor of multiple rich clients (Workplace for one), so I'm guessing your pain will go away in a few years :-)

  24. Embrace, extend, and ejaculate by Anonymous Coward · · Score: 0

    Just like a rapist.

  25. Rambus, anyone? by Urusai · · Score: 4, Interesting

    Didn't they work on an open JEDEC standard, only to turn around and patent it before finalization? Perhaps Microsoft will have an RSS patent ere long?

    1. Re:Rambus, anyone? by FuzzyBad-Mofo · · Score: 1

      Are you sure you're not thinking of Rambus, and the SDRAM DDR fiasco?

  26. The real question is why not something else by Anonymous Coward · · Score: 0

    Why use RSS for that when vCard and iCalendar specs already cover that and are implemented by many groupware suites out there. The RFCs cover from HTTP transport of calendar and contact data as well as other MIME enclosures...

    You may not be that familiar with MS' tactics in the past. If you want to get your name in everything you have to act like you "contributed" to it. For them to add to an open standard they want to make it look like they proposed new features directly as opposed to a behind-the-scenes addition (open source itself isn't in it for the glory, though it comes naturally) that wouldn't help them out in publicity. I propose Microsoft does an upgrade to Internet Explorer (either 7 and/or more version 6 fixes) in light of the many recent exploits instead of trying to get their hands into more technologies...or perhaps IE 7 will be based on their implementation of RSS? Oh wait maybe I saw this on MSDN recently...

    I am down to about 60/35 (Safari for the other 5%) usage with IE barely being used more than FF . Looking forward to seeing integrated RSS in IE7 (I'm sure this will be just one of many features) Quote

    Or perhaps, The aggregator allows users to subscribe to feeds in both RSS and Atom formats; suggests and organizes popular feeds; and connects directly to MSN Search, saving a user's search history. No word yet on how or when MSN plans to commercialize the aggregator. The MSN RSS Aggregator .

    It seems so much clearer now that the rain is gone! Definitely makes me think MS has something up that they aren't telling people

    1. Re:The real question is why not something else by soapdog · · Score: 1

      I just looked on the spec for iCalendar... and a Microsoft Engineer is one of the authors... So this is not a case of "not invented here". Heck, I just can't understand this kind of move, but it does not surprises me

      --
      -- Por mais que eu ande no vale das trevas e da morte, meu PowerMac G4 Não Travará!!!
  27. They just have to be different. CalDAV? by Kunta+Kinte · · Score: 3, Informative
    CalDAV is an IETF draft is is actively being worked on by a large community. Already there are interoperating implementations ( http://ietfreport.isoc.org/idref/draft-dusseault-c aldav/ and http://ietf.webdav.org/caldav/home.html )

    Why not join in and support the effort?

    --
    Based on upvotes, Ageism is the only "-ism" Slashdotters care about and think isn't SJW
  28. Can't They Use XML in RSS? by 6e7a · · Score: 1

    It seems to me that MS could just come up with some useful XML schema(s) that RSS carries, just like it carries HTML markup right now. Why do they have to extend the RSS (family of) standard(s)?

  29. Bottom line.... by Stupor+Man · · Score: 0

    IF they extend it, we won't come.

  30. Sharpen and poke. by Anonymous Coward · · Score: 0

    "It's open for everyone, except those whom have repeatedly shown their distain for standards and for those whom have repeatedly and purposefully corrupted the standards process with the expressed intent of extinguishing said standards."

    C#

  31. Already been done. by IGnatius+T+Foobar · · Score: 3, Informative

    Sounds like Microsoft is trying to re-invent GroupDAV, which is an open standard developed for precisely this purpose. Microsoft just has to be a childish brat and do things its own way.

    --
    Tired of FB/Google censorship? Visit UNCENSORED!
    1. Re:Already been done. by AndroidCat · · Score: 1

      And after a year of existance, how much universal acceptance does GroupDAV have? Have they had their first faction fights and version number wars like RSS? If not, I don't know if I can take them seriously.

      --
      One line blog. I hear that they're called Twitters now.
  32. Creative Commons by mikeboone · · Score: 4, Interesting

    Microsoft is releasing this spec under a Creative Commons license. So perhaps it's not evil, or at least they're doing a better job of hiding the evil part!

    1. Re:Creative Commons by mbaciarello · · Score: 1, Informative

      Too bad I don't have mod points for you, man, and too bad your comment is buried at the bottom. To all the wankers already going off about MS patenting the specs:

      Take a look at the licensing information - get to the source.

      Ok, if you really are that lazy, it's a Creative Commons Attribution-ShareAlike 2.5, which means you only have to credit MS for this stuff, and release your own stuff (plugin/library?) under the same license.

    2. Re:Creative Commons by Raul654 · · Score: 2, Informative

      IANAL, so someone please correct me if I'm wrong here, but: Even if they release the spec under a creative commons license, that doesn't stop them from patenting the ideas expressed in 'said spec, does it?

      --


      To make laws that man cannot, and will not obey, serves to bring all law into contempt.
      --E.C. Stanton
    3. Re:Creative Commons by amliebsch · · Score: 1
      Amen. This really is pathetic. Here we have a technical proposal perfectly free for anyone to examine, and all that is here is lame "I bet is suckz d00d l0l!!!" posts and IGNORANT tin-foil-hattery. Those of you who are bashing without having even looked at the source - you ought to be ashamed of yourselves.

      But, you aren't. Pity.

      --
      If you don't know where you are going, you will wind up somewhere else.
    4. Re:Creative Commons by amliebsch · · Score: 4, Informative
      From the bottom of the linked page:
      As to software implementations, Microsoft is not aware of any patent claims it owns or controls that would be necessarily infringed by a software implementation that conforms to the specification's extensions. If Microsoft later becomes aware of any such necessary patent claims, Microsoft also agrees to offer a royalty-free patent license on reasonable and non-discriminatory terms and conditions to any such patent claims for the purpose of publishing and consuming the extensions set out in the specification.
      So they don't think they have any patents, and even if it turns out they do, licenses are granted under RAND terms.
      --
      If you don't know where you are going, you will wind up somewhere else.
    5. Re:Creative Commons by advocate_one · · Score: 1

      I think you'll find that that CC license is not GPL compatible.

      --
      Donald 'Duck' Dunn: We had a band powerful enough to turn goat piss into gasoline.
    6. Re:Creative Commons by bit01 · · Score: 2, Insightful

      So they don't think they have any patents,

      You're being somewhat naive; what M$ says and does are often completely different. It's a large organisation, different people have different opinions and given the mess that is the current patent system a submarine patent could easily turn up.

      and even if it turns out they do, licenses are granted under RAND terms.

      RAND terms to M$ often means "(except GPL)" and "with lots of arbitrary restrictions and sufficient legal roadblocks to make fair competition impossible."

      They could've published a patent license as an addendum to the specification license, even though they claim they know of no relevant patents. The fact that they didn't is telling. I could be generous and say it's an oversight or bureaucratic inertia or a small risk that M$ does not want to take but given M$' history I'm not going to be generous and will assume until proven otherwise it's M$ playing their cards close to their chest as usual.

      If M$ published a patent license with the final spec, and make legally clear that there are no possible legal and commercial roadblocks to others implementing and interroperating with the spec then that would be worth something.

      ---

      Keep your options open!

    7. Re:Creative Commons by killjoe · · Score: 1

      RAND means it's not compatible with the GPL. That's why MS is doing this, because the competing protocols liek groupdav, ical etc are all GPL compatible.

      MS wants to destroy the GPL more then anything else in the world.

      --
      evil is as evil does
    8. Re:Creative Commons by mbaciarello · · Score: 1

      So what, is it the only license possible?

      Furthermore, notice how I wrote "library/plugin" instead of application. And finally, my main point is that with a CC license they can't just go and patent their concept.

    9. Re:Creative Commons by hachete · · Score: 1

      "Microsoft is not aware of any patent claims it owns or controls that would be necessarily infringed by a software implementation that conforms to the specification's extensions"

      Yes they do have patents on their RSS SSE implementation. It's just they don't know of any similiar patents held by others which might infringe their patents. In other words, this is catch-all phrase. I have patents; somebody else might have similar patents but we're unaware of them, therefore we will cross-licence if it turns out that there are patents.

      Of course they have patents. I'm afraid it's a bit premature for peace breaking out. The sharing stops at the MS borders. No, hang on. The sharing ends at MSs hand in my wallet. That's the only sharing they know. Has nobody learnt anything? It appears not.

      --
      Patriotism is a virtue of the vicious
  33. Yay! Another way to get a virus! by Anonymous Coward · · Score: 0

    I can't wait for somebody to find out how to exploit this (and you know somebody will), prompting MS to issue a security patch (but only on the second tuesday of the month) that disables it.

  34. Er... by Fishbulb · · Score: 2, Insightful

    I smell IPX.

    1. Re:Er... by natd · · Score: 1

      I'll forgo my mod points to ask 'where?' What's the relevance?

      --
      Only big ligs use sigs.
    2. Re:Er... by mk_is_here · · Score: 1

      I smell svk.

  35. Microsoft forfeited their "rights". by Saeed+al-Sahaf · · Score: 1
    Well, it may be a valid question: Are there behaviors that would qualify for reason that Microsoft had forfeited their "rights"? Microsoft is not and will never be a friend of anything "open", so are we obligated to play with them at all? If someone hurts you over and over again, maybe they no longer have equal rights? Equal rights to continue hurting you, perhaps?

    Let the fox in the hen house because to keep them out would be "discrimination"? Get real.

    --
    "Who are in control, they are not in control of anything - they don't even control themselves!" - Glen Beck
    1. Re:Microsoft forfeited their "rights". by evershade · · Score: 1

      Perhaps a karma clause could be add to GPL 3...

      Mod -1.....

  36. Why wait? by spideyct · · Score: 5, Insightful

    >I can't wait to see this one.

    You don't have to wait, it is already published. Instead of just spouting off, go read the spec and judge it on its technical merits, instead of adding another needless me too "MS sucks so this must suck" post.

    http://msdn.microsoft.com/xml/rss/sse/

    Then come back and give a reasoned opinion about the flaws in the proposed extension.

    1. Re:Why wait? by CrazedWalrus · · Score: 2, Insightful

      Interesting bits from the MS page you linked:

      The objective of Simple Sharing Extensions (SSE) is to define the minimum extensions necessary to enable loosely-cooperating apps

      [snip]

      Microsoft's copyrights in this specification are licensed under the Creative Commons Attribution-ShareAlike License (version 2.5). To view a copy of this license, please visit http://creativecommons.org/licenses/by-sa/2.5/. As to software implementations, Microsoft is not aware of any patent claims it owns or controls that would be necessarily infringed by a software implementation that conforms to the specification's extensions. If Microsoft later becomes aware of any such necessary patent claims, Microsoft also agrees to offer a royalty-free patent license on reasonable and non-discriminatory terms and conditions to any such patent claims for the purpose of publishing and consuming the extensions set out in the specification.

      I'm as suspicious of MS as the next guy, but it looks like, at least in this case and at this moment, they're trying to play nice. Give 'em a chance. They don't seem to be trying to crowd anybody out, and aren't trying to extend the standard beyond recognition ("minimum necessary").

      I think if everyone just takes a deep breath and realizes that the OSS Spaghetti Monster doesn't mind fair contributions from other camps, maybe everyone can benefit by a modernized and more functional RSS standard.

      MS gets their app interoperability, OSS gets some good ideas and even gets to use them without fear of patent infringement (per last paragraph). Everybody wins.

    2. Re:Why wait? by Ponyegg · · Score: 1

      I'd agree. I'm reminded of the Boy who cried wolf here. Over the coming years MS will HAVE to accommodate greater openess in the products it writes and develops, we're seeing this already. Each small step it tries to make is invariably met with a torrent of 'yahboosucks' from the ./ brigade. Take heed, those who fail to see and act upon such changes invaribaly end up a casualty of it. Constant derision of a company that is obviosuly trying to change just becomes borish, whilst there's a way to go yet I always think that by encouraging them to change we'll eventually get what WE want.

  37. Some kind of sport... by marko123 · · Score: 1

    Some people (people make nasty hurtful decisions, not companies, folks, people) take great joy in fscking nice people in the ear through deceit, and then apologising to them again and again until they forgive them so that they can fsck them in the ear again.

    Some nasty people get a huge kick out of this and laugh until they cry if they can get the nice person to bend their heads over three or more times because they can't help forgiving and trusting. It really really annoys me, because I like to give people a second (and third) chance and I get a sore head sometimes.

    --
    http://pcblues.com - Digits and Wood
  38. Oh no, not again! by AndroidCat · · Score: 1

    Isn't there RSS stuff that already does this? Like RSSCalendar for the last while or so? (Mind you, I don't see any links to technical information or protocols, so if they were hoping to keep people locked into their own little "capture eyeballs" business model .. oh well.)

    --
    One line blog. I hear that they're called Twitters now.
    1. Re:Oh no, not again! by sveinhal · · Score: 1

      RTFA. The draft is published under a Creative Commons licence (by-sa 2.5), and is available here: http://msdn.microsoft.com/xml/rss/sse/

    2. Re:Oh no, not again! by AndroidCat · · Score: 1

      RMFP. No, I meant that RSSCalendar didn't seem to say which standards they were using.

      --
      One line blog. I hear that they're called Twitters now.
  39. Obligatory by Anonymous Coward · · Score: 1, Funny

    That's no extension. IT'S A TRAP!

  40. Give 'em a piece of their own medicine by alfrin · · Score: 1

    How about we just stop excepting their ideas, much like they do to us (or take it as their own). Stop having Linux just play "catch up" with them.

  41. XMLHttpRequest by snowwrestler · · Score: 4, Insightful

    May I point out that when IE extended the abilities of the WWW, we ended up with worms and exploits up the wazoo.

    XMLHttpRequest was one of those extensions and it's given us Gmail and other "AJAX" interfaces. Not all extension is bad; if it was how the heck would the industry progress?

    --
    Build a man a fire, he's warm for one night. Set him on fire, and he's warm for the rest of his life.
  42. Any GPL black-holes yet? by Anonymous Coward · · Score: 0

    "Any takers on whether or not they'll attempt to patent these extensions, and make sure that they cannot be licensed in a manner compatible with the GPL?"

    You mean like GPL code is licensed to be compatible with everyone else?

  43. Imminent Death Of The Net Predicted! by jerryasher · · Score: 1

    In 2030, as mankind pulls itself out of the ashes caused by the great net meltdown of 2006, observers will point to Microsoft's extension of RSS as the straw that broke the camel's back.

  44. I wanna play too! by GMFTatsujin · · Score: 2, Insightful

    Hey! I've got a great new extension for our Microsoft friends. I call it "TTF", or "The Third Finger." And it's so efficient it only requires one-fifth the bandwidth of that needed for an entire spanking.

    Please guys. Stop breaking things.

  45. Just like... by consolidatedbord · · Score: 2, Insightful

    The WONDERFUL extensions to LDAP, DNS, DHCP, and many more? UGH

    --
    while true ; do echo this is my sig; done
  46. For the last time... by Dirtside · · Score: 2, Funny

    *sigh* No, Microsoft, you may not add the evil bit to RSS!

    --
    "Destroy science and religion. Science would re-emerge exactly the same; but not religion." - Penn Jillette, paraphrased
  47. Already been done-KDE,Gnome,GNUstep,Alsa,OSS. by Anonymous Coward · · Score: 0

    "Microsoft just has to be a childish brat and do things its own way."

    As opposed to Linux and it's three different incompatible windowing environments, and two* different sound servers.

    *Three if you include Gstreamer.

  48. Then I propose... by biovoid · · Score: 1

    ..they change the acronym to RCS.

  49. No, it was just ahead of it's time by Belial6 · · Score: 1

    No, Notes is a stable secure environment that allows extreamly rapid development, with very simple yet powerful administration. It's biggest problem was that while MS added eye candy to Exchange, Lotus worked on security and features.

    MS was also allowed to pervert the term "Groupware" into meaning email and calandering. Back around '87 or '88 MS was out touring Exchange and promising that it would be a Notes killer, but every time they were asked if it could do tasks that was simple in Notes, the answer was "Not, yet but it's planned for the next version." Well it didn't take long before MS just gave up and started telling people that "Groupware" was email and calandering. Now you see dozens of applications that claim to be groupware. Most would have been laughed at for that claim in the '80s.

    Being a Notes/Domino fan, let me tell you what IS wrong with Notes.

    1) Poor control of the front end classes. It is problimatic to dynamically create objects in the client.
    2) No native Linux client. They do have a native Linux server. (as well as many other OSs) 3) The JVM is built in, and is often a version behind what is in broad use. 4) Printing is a bit weak. That's about it.

    1. Re:No, it was just ahead of it's time by gauauu · · Score: 1

      Ok, you being a notes fan, I would like to know what is right about notes. Not trolling, I'm serious. I see that you say it allows rapid development. Development of what?

      I tend to think Lotus notes sucks, but that's probably because the only time I used it was at a company that only used it for email. As a pure email client, it was rather bad. But it always seemed like there was a lot more that could be done with it. I just never understood WHAT those things were (other than calendar sharing type things).

      And whenever I looked for information about it, the answers were always marketing babble that didn't really mean anything.

      So, you being a fan, what does "groupware" REALLY mean, and what do YOU use Lotus Notes for?

    2. Re:No, it was just ahead of it's time by kbg · · Score: 1

      It allows rapid development of groupware applications. Notes is basically a complete platform for developing and running groupware applications. Comparing it to Outlook is just plain silly since Outlook is just mail/calendar application, in notes the mail/calendar is just one of the applications that comes with notes and there is nothing stopping you from modifying or creating your own mail application and using that instead if you don't like the default mail from Lotus. Modifying and extending the applications is easy since they have the source open, try doing that in Outlook.

      The security access in notes was created from the ground up, so it is very powerful, you can have very flexible access control down to the field level.

      Comparing Outlook to Notes is like comparing a bicycle to a Boeing 747, sure you can use both to get across the country, but using the plane is much much easier :)

    3. Re:No, it was just ahead of it's time by cygnusx · · Score: 1

      Comparing Outlook to Notes is like comparing a bicycle to a Boeing 747, sure you can use both to get across the country, but using the plane is much much easier :)

      Actually you do your argument a disservice there: if *all* you want to do is read your email, Outlook would probably be easier. The Notes' client always reminds me of emacs somehow -- its very extensible and powerful, but not very approachable for beginners.

      Good example: up to version 6 (which is what I use) you couldn't create a rule that'd stop further rule processing if a condition matched. This meant that if you had rules that scanned for 'foo' and 'bar' in the subject and put them in different folders, a message titled 'foobar' would end up in _both_ folders. I ended up hacking my mail template to add this feature, but how many people have the rights/skill to do that? (And it's no coincidence most corporate Notes users let all their mail come into their inbox and use manual filing.) This is a core MUA feature, and it's a shame Lotus/IBM couldn't be bothered to add it.

    4. Re:No, it was just ahead of it's time by kbg · · Score: 1

      Yes I agree if all you want to do is read email then Outlook is probably simpler since that is what it was designed for exclusively. But as you said it was still possible for you to add that feature into to the mail template, I seriously doubt that you could do that in Outlook at all, it just shows how flexible notes is.

      Unfortunately it seems that since IBM bought Lotus it has been trying to kill of notes (IMHO) and doesn't fix obvious usability issues with the mail application and stops any killer features from being implemented, like JSP, Java UI classes, Servlets, XML parsing, Web Services, DHTML views etc.

  50. Response to the response. by erveek · · Score: 1

    Dear Everyone On The Internet,

    What an odd word.

    Signed,

    Microsoft
     

    --
    -- This void intentionally left null.
  51. This isn't the meme you are looking for by srpatterson · · Score: 1

    Well that post took a while to appear.

    --
    -- The Heineken Uncertainty Principle: You can never be sure how many bears you had last night.
  52. As Mr Jefferson would say by DrSkwid · · Score: 1

    Don't say that about Microsoft, that's just ignorance, you're being ignorant.

    --
    There are places where the networks are not touching,and there are places where they are-Boeing's Lori Gunter
  53. SyncML by barbazoo · · Score: 1

    ...we mobile users have been able to synchronize PIM data for years using this great, free (as in beer) service

  54. Seriously by Anonymous Coward · · Score: 0

    You need to go talk to Netscape and the WC3. Then you will realize that Microsoft comes by their reputation honestly. Dude, these are people you really don't want showing up at your party and your all for sending out invitations. You must be young.

  55. Re:They just have to be different. CalDAV? by Jesus_666 · · Score: 2, Insightful

    Because supporting a standard is nothing you can brag to potential customers about. Extending $BUZZWORD so that it does things that are extremely necessary ever since We Said So gives the company the image of someone who gets the things done that other people couldn't.

    I say it's at least 70% marketing.

    --
    USE HOT GRITS WITH STATUE OF NATALIE PORTMAN (NAKED AND PETRIFIED)
  56. Exactly what are you worried about? by brunes69 · · Score: 2, Insightful

    I fail to see how Microsoft can take an open, XML-based, plain text format that is ratified in numerous RFCs, and somehow "corrupt it" amd make it unuseable by adding some extra extentions.

    Hell, these extentions would not even break existing clients, the parser would just not do anything with the new nodes and attributes!

    But on the other hand, you are Evolution and want to sync with Outlook, this would be *great*.

    Honestly, with you guys Microsoft is damned if they to (try to create an open standard for synching datebooks via RSS) and damned if they don't (keep their systems proprietary and incompatable).

  57. More of the same by Sir+Holo · · Score: 3, Insightful


    Microsoft's RSS Checklist:

    1) Embrace ... done
    2) Extend ... in progress
    3) Extinguish ...

  58. This extension can NOT "break" RSS 2.0 in any way. by acroyear · · Score: 1

    RSS 2.0 has one simple rule for extensions: put it in its own damn namespace; any RSS 2.0 tag remains in the default namespace and no new attributes or tags can be used that are in the default namespace unless specified by the standard. OPML (also written by Winer) is the same way.

    As such, this spec does not break RSS 2.0 or require any RSS 2.0 feed reader to change if it simply wants to ignore the extension (the way most RSS readers just ignore extensions). Winer wrote the spec that way specifically so extensions are just that, extensions, not ways to break the file.

    My only gripe is that it looks as though it has introduced yet another date format to parse. Dates are different for RSS 0.91/2.0 and 1.0 and it's really obnoxious to deal with.

    --
    "But remember, most lynch mobs aren't this nice." (H.Simpson)
    -- Joe
  59. Re:They just have to be different. CalDAV? by AndroidCat · · Score: 1

    Are you sure that they haven't joined in? Since they are major players in WebDAV (even if their implementation can be squirrelly), I'd be surprised if they didn't have someone involved in a big way. (I tried to find a membership list to check, but first must have coffeeee...)

    --
    One line blog. I hear that they're called Twitters now.
  60. Right... by Anonymous Coward · · Score: 0

    How about they start by implementing current standards first?

  61. Hey, it's related with my idea: by Inyu · · Score: 1

    http://tinyurl.com/72rs5 I think it's good, and the extension is necessary, but the standard should be well-designed.

  62. Been there, done that - ExRss by glenmark · · Score: 1

    A collegue of mine posted some ASP.NET code on SourceForge back in July for providing Exchange mailbox data (Not just Calendar items -- Inbox, Calendar, Tasks, everything) via RSS feed:

    http://sourceforge.net/projects/exrss/

    --
    *** Quantum Mechanics: The Dreams of Which Stuff is Made ***
  63. Bloat by The+Monster · · Score: 1
    I fail to see how Microsoft can take an open, XML-based, plain text format that is ratified in numerous RFCs, and somehow "corrupt it" amd make it unuseable by adding some extra extentions.
    Maybe not unuseable, but bloated for damnsure. Here's an example:
    <sx:history when="Sat, 21 May 2005 09:43:33 GMT" by="REO1750"/>
    With a proper IS0-8601-compliant date format, that can be done as:
    <sx:history when="20050521T094333" by="REO1750"/>
    Yes, it omits the day of week, but that can always be derived from the full 8-digit date, so it need not be transmitted. Similarly, the timezone is extraneous because the spec says that all times must be in GMT. Since there are going to be a lot of these fields, they'll add up. I can also change 'when' to 'at', and save two more bytes, but at least 'when' is unambiguously time rather than place, so it's defensible.

    The second form is not only smaller, but easier to process, because a ASCII sort of the 'when' values is sufficient to determine which represents an earlier moment in time.

    --

    [100% ISO 646 Compliant]
    SVM, ERGO MONSTRO.

    1. Re:Bloat by brunes69 · · Score: 1

      So you're saving like 8 bytes, which would be totally irrelevant if the stream is compressed for transmission (which it usually is) at the expense of making it non-human readable, which is one of the whole reasons XML is plain-text based in the first place. If all you care about is data efficiency, then why the hell are you even useing XML?

  64. The better of two evils by b4k3d+b34nz · · Score: 1

    I know this is slightly off-topic, but I'm not sure why anyone would want to use Lotus Notes. Outlook, for all its problems, is certainly better than anything IBM/Lotus has come out with. We use Notes 5 at work, which means we're behind by about 8 years or so. Anyway, the folks in my group here at work use a connector so we can use Outlook. I think the better solution for the problem that Microsoft is trying to solve is to buy out Lotus Notes and destroy it. Forget RSS extensions.

    Download the connector here: http://www.microsoft.com/downloads/details.aspx?Fa milyID=8EBBBA59-5F17-4E52-8980-C4F0DFA92D65&displa ylang=en

    --
    Grammar Lesson: you're is a contraction of "you are"; your means you possess something; yore means days gone by.
  65. anti-rss by towsonu2003 · · Score: 1

    okay, now how can i find a anti-RSSvirus engine?? would norton work??!! someone has to let clamAV know about this...

  66. Another pointless "standard" by jfanning · · Score: 1

    Why does everyone have to keep reinventing the wheel. Or is it just another case of NIH?

    SyncML has been a standard syncronisation protocol now for several years, and it is even XML based. But MS has consistantly ignored it from what I can see.

    http://www.openmobilealliance.org/tech/affiliates/ syncml/syncmlindex.html

  67. Finally! by fabioaquotte · · Score: 1

    Finally we can get VoIP and such other nice things on our RSS !!!
    Thanks Microsoft!

    --
    Fabio Aquotte
  68. The good things... by Belial6 · · Score: 1

    The list is long, but here are some.

    * An simple yet complete Access Control List. It starts at the connection to the server and works it way all the way down to the specific fields you want to give access to.
    * A simply yet complete Execution Control List.
    * Replication. No one does it better or easier
    * Extreamly simple to set up and maintain load balancing.
    * Simple clustering.
    * Multiplatform. Many for the server, fewer for the client.
    * Write once run anywhere development.
    * The ability to have multiple people that are not currently connected to each other to work in the same database at the same time. Notes understands the difference between a 'copy' and a 'replica'. If you and I are running from the same copy with different replicas, we can make changes at different unconnected places, and it will not break the application.
    * A simple API that gives access almost all aspects of the environment. Depending on where the code is going, you have the choice between 'Simple Actions' (Simple wizard), @Formula (like original 1-2-3 or excel macros), LotusScript (Basic), Java, or Javascript.
    * HTML rendering inside of the client
    * Runtime on the fly native application auto-conversion to HTML/Javascript. Not 100%, but it gets you 80% of the way there. This allows mixed client/browser applications.
    * Secure
    * No rip and replace. Notes v1 apps still run in v6.5, and I have no reason to believe they won't run in v7 to be released in January.
    * A commitment to interop with standards. Many features in Notes were not standardized, or even existant when Notes was created, but as standards have emerged, Lotus has interface to them. i.e. SMTP, POP3, IMAP, LDAP, SQL, Java, XML, HTML, URLs...
    * Stable.
    * Simple administration. I have seen receptionists trained to be administrators in a week, and successfully perform the job. I'm not talking about shining stars that just never got the chance, but people that were topping out on skill sets as receptionists.
    * The ability to keep using your HTML based applications even disconnected from the server. i.e. on an airplane.
    * I could keep going on...


    One of the reasons Notes has such a bad reputation is that the barier to entry is so low that companies will often assign whoever is the first person to use it as the adminstrators and developers. If you are going to just use Notes as an email server, that might be ok, but the people soon end up out of their scope when asked to develop applications that require an actual developer to do the work.

    As for what I do with it, here are some of the applications I have developed:

    * Multiple help desk systems
    * Injury tracking
    * Root Cause Analysis
    * Repair assignemnt and tracking
    * Various simple calendering apps link vacation tracking and such...
    * Medical testing scheduling
    * Time card applications
    * Resource tracking
    * Training compliance and tracking
    * Applicant tracking
    * Intern tracking
    * Sales Management
    * Various discussion applications
    * Employee Appraisal
    * Order Inquiry
    * Various web based questionairs
    * Photo Hosting
    * Recipie book

    Anything else I can't think of off the top of my head.

    These were not slapped together, just make it work applications, but full end user apps that notify users (nag when it warrents) via email, escalate when necessary, and implement the various business logic that is necessary to keep data in a consistant state. Some use a browser as a client, some use Notes as the client, and many use both, determined by the task and user.

    So, yes, if you work at a company that has Notes/Domino, and your only using it for email, your company is missing out on a very good application platform.

    The company that I do the bulk of my work for has one employee that works with me. She was an admin type that fell into the position. She is now a very low end developer. She handles testing, form/view design, and can edit some code to fix some errors. Between her and I, we crank out 3 to 4 full end user application a year, while she also supports all existing applications that are in production.

  69. Oh the irony.... by rdean400 · · Score: 1

    If you'll notice the licensing on the specification, it's the Creative Commons Share-alike license. For a corporation that hates the GPL, this seems odd.