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."

58 of 234 comments (clear)

  1. 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 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
  2. 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 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.
    3. 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.

    4. 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."
    5. 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"!!!
    6. 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."
    7. 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.

  3. 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 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. 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 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
  5. 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 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;
  6. 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.

  7. 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?

  8. 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!

  9. 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.

  10. 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 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).

  11. 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!"

  12. 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.

  13. 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).

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

    "But didn't Lotus Notes suck?"

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

  15. 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".

  16. Re:Just say No by Ohreally_factor · · Score: 4, Funny

    Or to coin a phrase, bastandardizations.

    --
    It's not offtopic, dumbass. It's orthogonal.
  17. 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
  18. response to the proposal by ChipMonk · · Score: 4, Funny

    Dear Microsoft,

    No.

    Signed,
    Everyone On The Internet

    1. 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

  19. 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?

  20. 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
  21. 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!
  22. 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 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
    2. 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.
    3. 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!

  23. 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.

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

    I smell IPX.

  25. 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.

  26. 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.
  27. 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.

  28. 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
  29. 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
  30. 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)
  31. 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).

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


    Microsoft's RSS Checklist:

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