Slashdot Mirror


Microsoft To Extend RSS

Joshua53077 writes "Microsoft announced today a plan to 'extend the RSS standard to better support the publishing of ordered lists of information...' This feature will be included in Longhorn. It appears as though they will be including RSS support in Internet Explorer, which will come over a year and a half after the same technology was introduced in Apple's Safari RSS." From the article: "Gary Schare, director of strategic product management in the Windows division of Microsoft, says that while RSS is a reliable standard for updating information in message form, it currently has no logical way to organize that information in a way that could help subscribers keep track of what is being fed to them."

30 of 375 comments (clear)

  1. Bye, bye RSS .... by Luscious868 · · Score: 4, Insightful

    Repeat after me "embrace and extend" ....

    1. Re:Bye, bye RSS .... by corsec67 · · Score: 1, Insightful

      Heh, that was my first though when I read the brief.

      The problem is, Microsoft's business plan is:
      1. Steal/Copy Idea
      2. Sell
      3. Profit

      --
      If I have nothing to hide, don't search me
    2. Re:Bye, bye RSS .... by CaymanIslandCarpedie · · Score: 2, Insightful

      This isn't meant to defend anyone or deamonize anyone, just an honest question (I realize /. isn't the place for that type of thing ;-)

      MS always gets kicked around (especially here) for doing things like this, so my question is:
      If a company is developing a product (RSS product seems an obvious example), and after exploring and using the standard meant for that type of product they see additional functionality which would be useful but isn't covered by the standards. What SHOULD they do? Just forget about additional functionality and live with the standard? Submit a request to the standard body, hope they agree, and wait for it to become part of the standard?

      I'm honestly curious about this because this type of action by MS is fuzzy in my head. Is it really that bad? What should they do?

      --
      "reality has a well-known liberal bias" - Steven Colbert
    3. Re:Bye, bye RSS .... by Baricom · · Score: 3, Insightful

      I'm honestly curious about this because this type of action by MS is fuzzy in my head. Is it really that bad? What should they do?

      A promise to not patent whatever it is they're doing would be an excellent start.

    4. Re:Bye, bye RSS .... by jpickett · · Score: 4, Insightful

      And if you read how Microsoft is handling their extentions, frankly I don't see what the issue is. So someone thought of a way to make RSS potentially better, and they're sharing it with other people.

      As I see it MS had two options:

      1) Create their own proprietary standard and have everyone bitch at them or;
      2) Use an existing standard, try and OPENLY build on it to do what they want, and only have retards like Slashdot minions bitch about it.

      Sure it's flamebait but I'm sick of this crap. Also wilsone8, I'm not directing this to you, just all the others that don't care to educate themselves first.

  2. How? by Conspiracy_Of_Doves · · Score: 4, Insightful

    So how exactly will they be changing the standard to make it incompatable with non-Microsoft readers?

    1. Re:How? by Decaff · · Score: 4, Insightful

      Special features to interact with Exchange and/or Outlook.

      That won't break the use of RSS with existing software. RSS is a dialect of XML. XML is designed to be extended without breaking existing uses. This is why XML can be so useful as a data format - software that uses an XML dialect will still work after the dialect is extended.

      I'm not defending Microsoft here, but worries about incompatibilities are almost certainly unfounded because of the way XML works.

    2. Re:How? by TedTschopp · · Score: 2, Insightful

      HTML is not XML
      XHTML is XML

      --
      Fantasy remains a human right; we make in our measure and in our derivative mode... -- JRR Tolkien
  3. As it should be. by TheBrownShow · · Score: 5, Insightful

    ...while RSS is a reliable standard for updating information in message form, it currently has no logical way to organize that information in a way that could help subscribers keep track of what is being fed to them.

    Which is exactly the way it SHOULD be done. Keep the management of the data seperate from the transmission of the data. Leave content management up to the APPLICATION.

    1. Re:As it should be. by Winterblink · · Score: 2, Insightful

      (A bit offtopic here) I find it interesting how the internet went from a primarily text-based medium, and suddenly exploded with MEDIA MEDIA MEDIA everywhere. We ended up with horrble frankensites like IGN and CNet, with maybe 1% actual content per page, the rest being graphical and media fluff. And now I hear what you say a LOT, where people are sick of going to sites and being overloaded with junk, and trying to find the buried content. Lots of people are finding the minimalist standpoint to be a valid one (my website for instance is pretty minimalist in that regard).

      Back to RSS, I think we'll see the same thing happen. We'll rejoince at the BROADBAND MEDIA XPERIENCE it will bring us with all these extensions, but it will implode under its own weight. I'm just hoping it will return to its roots intead of fizzling out as another internet neato thing du jour.

      --
      "I'm a leaf on the wind. Watch how I soar."
      -Hoban Washburn
    2. Re:As it should be. by TwistedSpring · · Score: 1, Insightful

      Oh god. This was rated 5? Currently there is no way to organise data in a sensible list format. For example, I'm reading an RSS news feed, but there is no RSS standard on how to date the headlines. RSS readers currently have to cache the old RSS file and look for changes to ascertain when new headlines appear and infer the date based on when the new headline appeared. A sensible ordering/dating system would make RSS a great deal more powerful, and a great deal more sensible.

  4. What will they really do? by ravenspear · · Score: 4, Insightful

    I hope by "extend the standard" they don't mean "basterdize it and then break compatibility with all non-M$ versions" because we've all seen that before.

    1. Re:What will they really do? by TwistedSpring · · Score: 2, Insightful

      Why is this relevant? You think Microsoft would change the standard so that no existing RSS reader on any platform could handle it? That's bullshit. Since RSS is based on XML it's easy to extend and add features to it that will simply be ignored by existing readers.

      Microsoft are big on XML. Their new office format will be completely open and XML compliant. I see no reason to believe that Microsoft will "basterdize" the RSS format, a format that has to be compatible with existing readers for its uptake to be guaranteed (i.e. no RSS publisher will embrace the extensions if they are incompatible with the majority of reader apps). The most Microsoft will do is say "Hey, you get a better RSS experience if you use the reader included in Longhorn since it is compatible with the new RSS extensions introduced by Microsoft".

      I think this is solely to do with improving usability and enhancing user experience, which is what Microsoft desperately need to do if Longhorn is going to beat OS X, and as someone who's written RSS parsers I welcome this addition to the standard, it seems like a really practical and useful idea.

    2. Re:What will they really do? by HishamMuhammad · · Score: 2, Insightful

      Microsoft are big on XML. Their new office format will be completely open and XML compliant. Do you call releasing a file format in a GPL-incompatible way "completely open"?? (Notice I didn't refer to GPL-incompatible code. There's a lot of GPL-incompatible free software out there, and they are still free software. File formats, however, are a different story. To be open, they need to be implementation-independent. Not only in their specification but also on their licensing.)

  5. Microsoft "Breaks" RSS by gbulmash · · Score: 3, Insightful
    Whenever Microsoft "extends" a standard, they always seem to extend it in ways so use of their extensions makes your page/script/applet inoperable with competing products that support the internationally approved standard. So should the title of this article actually be "Microsoft Breaks RSS"?

    - Greg

    1. Re:Microsoft "Breaks" RSS by Utopia · · Score: 5, Insightful

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

      Microsoft is not breaking the standard.




    2. Re:Microsoft "Breaks" RSS by TrappedByMyself · · Score: 2, Insightful

      Whenever Microsoft "extends" a standard, they always seem to extend it in ways so use of their extensions makes your page/script/applet inoperable with competing products that support the internationally approved standard.

      You mean like how they extended JavaScript to include XMLHttpRequest? Yeah, that whole emergence of Ajax has been a disaster.

      --

      Help me take back Slashdot. When did 'News for Nerds' become 'FUD and Conspiracy Theories for Extremist Nutjobs'?
  6. Longhorn? What's that? by oliver+clozoff · · Score: 2, Insightful

    Is there really a concern that they'll embrace and extend when they take so long to embrace? Apple on Intel will likely be out before Microsoft releases the successor to XP, which was released in 2001.

  7. In Longhorn huh? by tktk · · Score: 2, Insightful
    Hopefully by the time Longhorn comes out, we'll have moved onto something better.

    So MSFT has basically taken the better, cooler features out of Longhorn and replaced it with an RSS reader? I haven't been paying too much attention to Longhorn but really, what new things are going to be in there?

  8. Re:Microsoft is The Follower by TripMaster+Monkey · · Score: 2, Insightful


    How long can this be maintained?

    As long as we let them.

    --
    ____

    ~ |rip/\/\aster /\/\onkey

  9. Seen this before by Bronz · · Score: 4, Insightful

    1. Pick an up and coming technology that _you_ didn't see coming (and that your products don't support at all).

    2. Point out a fault in it. Promise to *fix* it by changing the standard so the improved version is only compatible with your software.

    3. Get people to believe the technology isn't ready until you have a chance to support it.

    4. Sell it as a new idea and profit.

    Look, I made an ordered list without extending /.

  10. Gee, that's funny ... by w98 · · Score: 2, Insightful
    no logical way to organize that information in a way [to] keep track of what is being fed to them

    Funny, every RSS feed *I* have ever subscribed to has always been returned in timestamp order, newest article first.

    How *else* would you organize it? I watch my feeds based on timestamp - if something new shows up, it shows up at the top of the list.

    It ain't rocket science ...

  11. Embrace, Extend, Patent by Albanach · · Score: 3, Insightful
    Is't microsoft as usual...
    1. Embrace
    2. Extend
    3. Patent
    4. Profit

    Their Office 2k3 XML format's 'may' have patents prohibiting their use in open source applications. Who's to bet the new RSS 'standard' will similarly be patented.

  12. Re:Other RSS uses by cei · · Score: 2, Insightful

    Yeah, but isn't that really all RSS is? Another format of the RDF that was used for channels?

    --
    This sig intentionally left justified.
  13. Good News! by bheerssen · · Score: 2, Insightful

    Now, I'm no MS apologist (look back at my comments) but this is actually good news because Microsoft has decided to release the specs under a Creative Commons "Attribution, Share-Alike" liscense: one of the more generous liscensing plans released by the Creative Commons.

    Larry Lesig has more at his blog.

    I can't vouch for Microsoft's reasons for doing this, other than speculate that they are trying to respond to the old criticism that "embrace and extend" really means "steal and lock away". If Microsoft really is trying to be more open in it's communiction protocols, I can't help but see that as a good thing. They are free to extend all they want as long as they do not use their dominant market position to force those extensions on their customers to unfairly place burdens on their competitors.

    --
    (Score: -1, Stupid)
  14. RSS Viruses by lullabud · · Score: 3, Insightful

    That get updates every hour on new ways to exploit your system.

  15. Just like Krb5 by jlrobins_uncc · · Score: 3, Insightful

    Which they released a 'legal', but value-added-only-for-microsoft extension, whose documentation was explicitly licensed as to prevent you from making an open-source interoperable equivalent.

    AFAIR, anyway. Does SambaNG or whatever truly smell like an AD with the MS-KRB5 authorization field properly filled-in?

  16. Re:RSS, compatibility, and Safari by Anonymous Coward · · Score: 1, Insightful

    Amen. I use a Mac but frankly the little sneaky comments embarass me. It like Six degrees of Mac with /. comments

  17. Re:Maybe if they froze Longhorn's feature set by Anonymous Coward · · Score: 1, Insightful

    Riiiiiight... because Microsoft's history is replete with instances of giving us exactly what was promised when the shipping date arrived.

    No, what's a very common marketing move for Microsoft is to take existing features and innovation from other companies, rehash them into slightly or not-so-slightly incompatible formats, and then bolt them into the operating system monopoly to make sure that "everyone" has the "enhanced" version that doesn't work right for the standard itself.

    The reason Microsoft has to strip features out of Longhorn but is more than willing to put enhanced RSS into Longhorn is because all those features that Microsoft is pulling haven't been invented by someone else yet for Microsoft to copy, but RSS is right there for the taking and breaking.

  18. Re:Maybe if they froze Longhorn's feature set by ky11x · · Score: 2, Insightful

    Parent is overrated.

    This is not a "common" marketing move because it makes no sense. You cannot "lull" your competitors into slowing down -- your competitors do not react to your announcements, they react to what they perceive the market wants and what they think you are doing, not what you say you are doing. Neither does it help to suddenly pop something onto the market when you have been telling IT managers for months to prepare for a release in 2006/2007. MS makes its living by allowing IT shops to phase and plan for purchases and upgrades. Do you think anyone is going to buy Longhorn in "December," if MS magically released it, when they were planning to upgrade their infrastructure and develop and test for Longhorn in 2007? You can bet that they'll wait until 2007 to purchase Longhorn even if it were released early.

    So, if this scheme were so "common," how about some examples?