Slashdot Mirror


Red Hat Claims Patent On SOAP Over CGI

WMGarrison writes "US Patent 7453593 claims command-line processing by a web server of SOAP requests, resulting in XML responses, from and to a remote client. The HTTP Common Gateway Interface (CGI) operates precisely as described in Claim 1. If you POST a SOAP document and return an XHTML response or a SOAP document, this infringes Claim 2, since both XHTML and SOAP are XML languages. This patent thus claims to own the processing of SOAP documents by CGI programs."

191 comments

  1. frist psot by Anonymous Coward · · Score: 1, Funny

    ...dont drop the SOAP.

    1. Re:frist psot by fictionpuss · · Score: 3, Funny

      You know, I never understood the "don't drop the soap" joke. Surely if someone is physically able to rape you anally, then there is little to no advantage to you bending over initially.

      And if you've ever got a large quantity of soap in your eyes, you'll know that having bent over to get the soap, you've got your hands on quite a good weapon.

      The joke seems to imply an attitude of "Oh jeeze - well, since you've started, you might as well finish", which rather cuts against the whole homophobic thrust. I've read back over these passages a few times, but it still doesn't make sense - is it just going straight over my head?

    2. Re:frist psot by Anonymous Coward · · Score: 0

      Your vastly over thinking it. Just read it, think "Oh those crazy homos" and chuckle uncomfortably like the rest of us.

    3. Re:frist psot by catmistake · · Score: 1

      I always thought SOAP was a common server configuration, like LAMP, but Solaris Oracle Apache Perl.

    4. Re:frist psot by commodore64_love · · Score: 1

      >>>Surely if someone is physically able to rape you anally, then there is little to no advantage to you bending over initially.

      Perhaps bit it's like when you see a woman. You may not be attracted to her at first, but then when she bends over ad display hr fine ass. suddenly wicked thoughts run through your brain & millions of years of instinct take over. In the prison shower room, it's the same deal albeit with two guys.

      So don't bend over.

      --
      "I disapprove of what you say, but I will defend to the death your right to say it." - historian Evelyn Beatrice Hall
    5. Re:frist psot by Anonymous Coward · · Score: 0

      If it's just going straight over your head, your partner's doing it wrong.

    6. Re:frist psot by fictionpuss · · Score: 1

      Huh? What do you mean?

  2. This is a patent I can get behind by haystor · · Score: 5, Insightful

    If this results in the abandonment of SOAP, I'm all for it.

    --
    t
    1. Re:This is a patent I can get behind by Bovius · · Score: 1

      So say we all!

    2. Re:This is a patent I can get behind by Just+Some+Guy · · Score: 1

      If this results in the abandonment of SOAP, I'm all for it.

      No complaints there, but it would be inconvenient if you're no longer allowed to return XML in response to a request. Even a large proportion of HTML documents are valid XML, so hypothetically you might have to include unclosed tags in your pages to be on the safe side.

      --
      Dewey, what part of this looks like authorities should be involved?
    3. Re:This is a patent I can get behind by dkh2 · · Score: 1

      No complaints there, but it would be inconvenient if you're no longer allowed to return XML in response to a request. Even a large proportion of HTML documents are valid XML, so hypothetically you might have to include unclosed tags in your pages to be on the safe side.

      Actually, this would apply to CGI, on-the-fly machine generated XML. Given the close relationship between XML and HTML I can see the possibility of less informed company lawyer types having a panic attack over something like this with respect to things like form landing pages, RSS feeds, and other generated pages on their web sites that do not fall into the SOAP category.

      --
      My office has been taken over by iPod people.
    4. Re:This is a patent I can get behind by Lord+Ender · · Score: 1

      Sure SOAP is complex, but that complexity can be encapsulated away. Really, the alternative is what? Everyone coming up with completely incompatible data transmission formats, reinventing the wheel and making the same mistakes over and over?

      --
      A slashdotter who didn't build his own computer is like a Jedi who didn't build his own lightsaber.
    5. Re:This is a patent I can get behind by Anonymous Coward · · Score: 0

      Free Software are allowed to use any of RedHat patents, so this is not likely to result in the abandonment of SOAP. The goal of this patent is to fight against Microsoft and other companies in the case they attack some free software with patents.

    6. Re:This is a patent I can get behind by haystor · · Score: 2, Insightful

      I'm not sure what SOAP solves. What does that complexity buy me? I've written to API's in XML, fixed width files, serialized objects, url encoded, cgi post, shared memory, named pipes and others.

      All SOAP manages to do is make object instantiation and invocation look nothing like what is going on.

      SOAP is not abstraction it is misdirection.

      COBOL files were typically well defined. Writing a parser and validator for them would take less time than setting up the same for SOAP. I'm not suggesting we go back to COBOL, I'm saying that SOAP doesn't win us anything by making parsing and validating available to something made unnecessarily complex.

      --
      t
    7. Re:This is a patent I can get behind by pthreadunixman · · Score: 1

      It always seemed to me that sole guiding principal behind SOAP was to evade obnoxious outbound firewall policies.

    8. Re:This is a patent I can get behind by bb5ch39t · · Score: 1

      Right! "He brings a knife, you bring a gun."

    9. Re:This is a patent I can get behind by DontBlameCanada · · Score: 1

      Give it a REST, dirty anti-soap troll! Washing with water is non-compliant.

    10. Re:This is a patent I can get behind by i_ate_god · · Score: 1

      Sure SOAP is complex, but that complexity can be encapsulated away. Really, the alternative is what? Everyone coming up with completely incompatible data transmission formats, reinventing the wheel and making the same mistakes over and over?

      Uh... use HTTP for what it was designed for?

      GET /resourceName/resourceId

      PUT /resourceName?param1=val1&param2=val2

      POST /resourceName/resourceId?param1=val1&param2=val2

      DELETE /resourceName/resourceId

      ok, that's not a perfect representation, but HTTP has all your CRUD methods, which is really all you need. You use GET to perform queries, you use PUT and POST to CREATE and UPDATE respectively, and DELETE to... DELETE!

      The HTTP protocol makes a hell of a lot more sense than using SOAP, it's a deeply rooted standard, fits perfectly into the MVC pattern, fits perfectly into load balancing schemes, is application agnostic, and with HTTP Digest over SSL, it's as secure as SOAP.

      So, take a break, and get some REST!

      --
      I'm god, but it's a bit of a drag really...
    11. Re:This is a patent I can get behind by Just+Some+Guy · · Score: 1

      Actually, this would apply to CGI, on-the-fly machine generated XML.

      Literally every page on our web application is generated on-the-fly. Why should lawyer types not care that our application is potentially infringing? And why should choices between things like mod_php and FastCGI be the province of the legal department?

      --
      Dewey, what part of this looks like authorities should be involved?
    12. Re:This is a patent I can get behind by Lord+Ender · · Score: 1

      That is insane. Have you ever actually tried that stuff? Firewalls, cache, all these things don't behave well with GET. Furthermore, there are arbitrary limits to GET string length.

      At the very least, any browser/server communication format must be able to handle arbitrarily complex datastructures of arbitrary length... unless you're writing toy apps.

      --
      A slashdotter who didn't build his own computer is like a Jedi who didn't build his own lightsaber.
    13. Re:This is a patent I can get behind by mini+me · · Score: 1

      Really, the alternative is what?

      HTTP?

      I'm sure you have some edge case waiting to point out where HTTP fails and SOAP does not. But just because SOAP is better suited for one out of every million projects, it does not mean that it is suitable for every project.

      It comes down to using the right tool for the job. SOAP may have it's place, but if you're writing a quick CGI script to expose a web service like the article seems to imply, SOAP is most certainly not the right tool.

    14. Re:This is a patent I can get behind by Just+Some+Guy · · Score: 1

      Really, the alternative is what?

      XMLRPC (which would probably also be covered by this patent)?

      --
      Dewey, what part of this looks like authorities should be involved?
    15. Re:This is a patent I can get behind by mini+me · · Score: 1
      1. If your firewall is broken, fix your firewall.
      2. If your is broken, fix your cache.
      3. What difference does it make if GET has an upper length limit? You're only requesting a short URI. When you are sending data you are using POST or PUT which do not have the same limits imposed on them.

      The web browser is just another web service client. Slashdot is just another web service. The mere fact you were able to post your message shows that the model works just fine. Why add unnecessary complexity?

    16. Re:This is a patent I can get behind by i_ate_god · · Score: 3, Insightful

      That is insane. Have you ever actually tried that stuff? Firewalls, cache, all these things don't behave well with GET. Furthermore, there are arbitrary limits to GET string length.

      At the very least, any browser/server communication format must be able to handle arbitrarily complex datastructures of arbitrary length... unless you're writing toy apps.

      You're so very wrong. The HTTP protocol does not define a max length for the GET query string. Any complex data structure can be represented by XML and you can return 100gb of XML if you want. Simpler structures can even be represented by JSON which might be even easier.

      As for firewall and cache, well... stop setting up idiotic solutions. Your public API is exposed via HTTP. So your firewall and caching solutions need to represent this. If it doesn't, that's because you did something wrong and missed the point. HTTP is highly scalable and that's the point. If your public API are serving massive requests very frequently, throw squid infront of your HTTP server. If you want some obfuscation set your port to something other than 80. Your excuses for firewall and caching don't make a lot of sense.

      --
      I'm god, but it's a bit of a drag really...
    17. Re:This is a patent I can get behind by Fnord · · Score: 1

      The REST model is probably a good thing, but HTTP doesn't type your parameters, doesn't allow datastructures more complex than key value pairs, and doesn't do input validation. In most cases where I've seen people using HTTP as a REST mechanism, they end up needing complex data, and end up sending ... *drumroll* ... blocks of XML! Unspec'd, incompatible, app specific XML layouts. SOAP isn't the answer, but it solved some problems very well that HTTP doesn't even approach.

    18. Re:This is a patent I can get behind by Lord+Ender · · Score: 1

      As to GET and PUT limitations: http://support.microsoft.com/kb/208427

      As to browser cache and proxy behavior: You are assuming app developers have control over their users' browsers and proxy servers. That's a false assumption. You just failed to meet the minim requirements for the project (working on ie6 with ghettoproxy 0.1).

      --
      A slashdotter who didn't build his own computer is like a Jedi who didn't build his own lightsaber.
    19. Re:This is a patent I can get behind by ClosedSource · · Score: 1

      "Uh... use HTTP for what it was designed for?"

      You mean delivering static pages? You can use HTTP for web services, but it certainly wasn't designed for that purpose.

    20. Re:This is a patent I can get behind by Lord+Ender · · Score: 1

      You mistakingly assume I control my users' proxies and browser settings.

      --
      A slashdotter who didn't build his own computer is like a Jedi who didn't build his own lightsaber.
    21. Re:This is a patent I can get behind by i_ate_god · · Score: 4, Insightful

      As to GET and PUT limitations: http://support.microsoft.com/kb/208427

      As to browser cache and proxy behavior: You are assuming app developers have control over their users' browsers and proxy servers. That's a false assumption. You just failed to meet the minim requirements for the project (working on ie6 with ghettoproxy 0.1).

      You don't know what you're talking about. Who mentioned browsers? Since when do browsers make direct SOAP calls to SOAP-based web services? They don't. Applications make SOAP-based requests to web services and then serves up views based on the data models the web service returns. The problem with SOAP is that SOAP reinvented HTTP. HTTP is perfectly geared to handle this notion of a centralized API with many applications using the same API. You can use this setup with ANY KIND OF APPLICATION, whether it be a desktop app, a web app, a command line app. You don't even need the internet.

      • User makes request
      • Application receives request, fetches data from RESTful webservice over HTTP
      • Centralized API fetches data, returns it to application
      • Application displays top ten favorite movies to user

      If you somehow see a problem with this, then you're working in the wrong job.

      --
      I'm god, but it's a bit of a drag really...
    22. Re:This is a patent I can get behind by Lord+Ender · · Score: 1

      SOAP via xmlhttprequest: http://support.microsoft.com/kb/208427

      More browser-based soapiness: http://livedocs.adobe.com/flex/2/langref/mx/rpc/soap/mxml/WebService.html

      So... I'm wondering who's in the wrong job at this point. But good luck with that attitude, buddy!

      --
      A slashdotter who didn't build his own computer is like a Jedi who didn't build his own lightsaber.
    23. Re:This is a patent I can get behind by Lord+Ender · · Score: 1

      Posted the wrong link.

      SOAP via xmlhttprequest: http://www.ibm.com/developerworks/webservices/library/ws-wsajax/

      --
      A slashdotter who didn't build his own computer is like a Jedi who didn't build his own lightsaber.
    24. Re:This is a patent I can get behind by i_ate_god · · Score: 1

      SOAP via xmlhttprequest: http://support.microsoft.com/kb/208427

      More browser-based soapiness: http://livedocs.adobe.com/flex/2/langref/mx/rpc/soap/mxml/WebService.html

      So... I'm wondering who's in the wrong job at this point. But good luck with that attitude, buddy!

      This is all made pointless with what I described above. Your application should be serving up content, not your centralized API. The only views your centralized API should have is logic on how to serialize models for digest by your applications.

      And another thing, SOAP is an utterly pointless technology. It reinvents HTTP for no real reason at all. If you're still using SOAP, then you obviously miss the point of what HTTP is and what it represents.

      Try harder next time :P

      --
      I'm god, but it's a bit of a drag really...
    25. Re:This is a patent I can get behind by blueskies · · Score: 1

      That's not a GET and PUT limitation. That is a IE 6 limitation. That's a huge difference.

      All you need to do is force upgrade people using IE6. Use one of the various browser exploits that exist for IE6, and upgrade their computer for them. In fact, don't bother sniffing for IE6, if they have IE6 your code will exploit them, upgrade their computer and reboot. You'll slowly be patching the entire internet.

    26. Re:This is a patent I can get behind by RightSaidFred99 · · Score: 1

      Guh? SOAP solves the problem of "how can I move the discussion of RPC communications to what's important - the contract." If you need high performance and SOAP doesn't cut it, by all means use something else.

      You don't have to do anything to "set up" SOAP. I can make a SOAP service based in Java or .NET that can use secure communications using SSL, Kerberos, Certificates, or other mechanisms in a matter of minutes.

      It can get extremely complicated, but so can any complex RPC implementation.

      SOAP isn't going anywhere. Really the best thing about it is the tooling - most of the IDEs have good support for easily managing some of the complexities of a SOAP based web service.

    27. Re:This is a patent I can get behind by pmarini · · Score: 1

      that a large proportion of documents are in HTML format I agree, that most of them are returned by SOAP calls I'm not so sure...
      can't we just use ORB instead ?

      --
      Can I put a spell on those who can't spell?
      Your wheels are loose and they're losing their grip, good you're there.
    28. Re:This is a patent I can get behind by sjames · · Score: 1

      Encapsulation doesn't remove complexity, it just hides it away so it can cause hard to find bugs.

      A good scheme would make simple things easy and hard things possible. SOAP violates that by making practically anything moderately hard (or at least complex).

      If your encapsulation is going to have THAT much overhead, it needs to provide a lot more benefit than SOAP does over simpler and more compact representations.

    29. Re:This is a patent I can get behind by atraintocry · · Score: 1

      They came first for SOAP, and I didn't speak up because SOAP is hella lame.

      Then they came for XML, and I didn't speak up because I'm always stuck debugging some terrible custom XML parser at work.

      Then they came for HTTP, and by that time, no one was left to speak up...except for the people on IRC, and nobody cares what those dudes have to say.

    30. Re:This is a patent I can get behind by javabsp · · Score: 1

      HTTP is just one of the possible transports for SOAP, so saying SOAP reinvented HTTP would be like... I think I will spare you from a bad analogy this time.

  3. Fix the patent laws with anti cancer drugs by unlametheweak · · Score: 5, Insightful

    OK, to save companies time and money (except for the Trolls and parasites), just get rid of software patents already. It's not good for buyers or sellers. It's not good for employees. It only benefits lawyers and patent troll parasites. Patent reform shouldn't take years, it should take days. I don't want to see another story like this ever again.

    1. Re:Fix the patent laws with anti cancer drugs by Anonymous Coward · · Score: 0

      I have always wondered the reason for patents in the first place. Patents are designed to prevent competition which, (unless I am mistaken) is exactly what is suppost to help balance out this capitalistic society.

      In two words:No Patents!

    2. Re:Fix the patent laws with anti cancer drugs by Repossessed · · Score: 1

      The point is to encourage companies to reveal how they make things, in exchange for a limited monopoly (basically you ensure the monopoly is x years, not 5 or 500, which used to be a real issue in medieval times)

      --
      Liberte, Egalite, Fraternite (TM)
  4. !AHAH by neo · · Score: 1

    Since returning HTML would not be covered, AHAH requests would not be covered.

    You should be using AHAH anyway.

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

      AHAHAH, you didn't say the magic word.
      -- Dennis

  5. Patent for "Talking" by olddotter · · Score: 3, Insightful

    Perhaps I should patent Talking. A means of transferring information between people. If you submit audible sounds to a individual and get audible sounds back, then you are infringing. :-) For a follow up I'll patent political speeches.

    When will the madness end?

    1. Re:Patent for "Talking" by Anonymous Coward · · Score: 1, Funny

      Political speeches transfer no information and are thus not covered under your patent.

    2. Re:Patent for "Talking" by Anonymous Coward · · Score: 0

      But you'd inadvertently patent group farting too, and so-called contagious yawning.

    3. Re:Patent for "Talking" by pmarini · · Score: 1

      you'd better aim to patent the "bit", that'll give you:
      - control over electronic information (obvious)
      - control over human communications (a bit of this, bits and pieces, ...)
      - control over life (heartbits, well this was a bit (!) streched...)

      anyway, it was funny :0

      --
      Can I put a spell on those who can't spell?
      Your wheels are loose and they're losing their grip, good you're there.
  6. On the server side, it would be the same... by tjstork · · Score: 1

    AHAH on the server is just another request...that's the whole point

    --
    This is my sig.
    1. Re:On the server side, it would be the same... by neo · · Score: 1

      But it's not XML.

  7. Umm... by gandhi_2 · · Score: 1

    Ok so who patented POSTing a JSON and returning an XML? Or GETing a key/value pair and returning JSON? Or POSTing XML and returning porn?

    And why only over CGI? Why not patent the use of server text preprocessors as well?

    1. Re:Umm... by Anonymous Coward · · Score: 0

      The patent claims any UNIX shell processing of SOAP documents inside a web server. Read the claims: #1 is for a UNIX shell, #2 is for web services that process SOAP and return *any* XML. CGI just happens to be the majority case of this.

      God knows how Red Hat thought they could get away with this. It seems amazingly stupid. And greedy. And stupid.

      Maybe they've been hiring Microsoft patent lawyers.

    2. Re:Umm... by ultrabot · · Score: 1

      God knows how Red Hat thought they could get away with this. It seems amazingly stupid. And greedy. And stupid.

      Maybe being stupid and obvious is the purpose of the whole maneuver.

      --
      Save your wrists today - switch to Dvorak
  8. So what? by BadAnalogyGuy · · Score: 1

    What's the impact of this? If this is such big news, perhaps you could spell that out in the summary.

    1. Re:So what? by zarthrag · · Score: 4, Insightful

      Therein lies the problem. I'm a one-developer shop. Even if a claim is 100% bunk, I can't afford to defend myself from a legion of lawyers who would simply drag out a court case forever - SCO style. Since I'd like to actually work instead of spend my life in court, I'd be forced to settle - giving said patent a bit of legitimacy. It's not a protection now, it's a business model equivalent to a protection racket.

      --
      Why can't all fpga/microcontroller manufacturers just release free optimizing compilers???
    2. Re:So what? by Anonymous Coward · · Score: 0

      Slashdotters seem to think the Patent system is some kind booby-trapped chess game.

      Coincidentally we think the same thing about talking to girls.

    3. Re:So what? by Anonymous Coward · · Score: 0

      If you are a one-developer shop, what's to be gained by suing you? WHERE are these many-many small shops that are being bullied?

      Secondly if you HAD to defend yourself in court and you are a one-developer shop you would defend it yourself. You could just get a para-legal at a small price or get legal-aid for free. I've been legally bullied before (not patent related) and I stood up myself in front of the Judge and he threw the case out with my spending a cent.

      This whole "Slashdotified/Stallmanified" patent paranoia is all a straw man.

      I can totally see through the psychology of these arguments. It began with disenfranchise teenagers who did not like the fact they had to pay for their favorite game or DVD and developed into a hatred for those that protect any kind of IP.

    4. Re:So what? by pieterh · · Score: 1

      Uhm, so anyone who is against software patents is by definition a copyright-infringing teenager?

    5. Re:So what? by Zerth · · Score: 2, Insightful

      You hit a small shop first to gain that legitmacy. The next place you sue(slightly larger), you show that you've succeeded in court before, and that either gets them to settle or influences the judge in deciding for you. You continue up the chain until you get smacked or start making serious money. If you get any resistance, you drop it as soon as possible and go on the next company. While you may have had success as an individual, most of these cases would either avoid you initially after you pushed back or smack you into the ground later through accumulated successes.

      As for you reducing this discussion to teenagers stealing games, that is quite bizarre. Many of us are reliant on IP laws, whether to using hacks to get around the limitations(GPL, BSD, Creative Commons) or working in the system(standard copyright, extra rights/limits through contracts, etc).

      I don't hate IP wholesale, I need it as a backdrop to the extra rights I grant those who use my software. Otherwise everything uses the WTFPL without the name change requirement. What I hate are those who take advantage of a system that is sorely out-of-date for purposes that contradict what the system was supposed to do.

  9. Not a problem for most Web appliactions by pcjunky · · Score: 1

    The claim would only come into play if a CLI application was used. Use a Non-cli application and viola no infringement.

    1. Re:Not a problem for most Web appliactions by MadKeithV · · Score: 1

      I don't see what a baritone violin has to do with the infringement.

    2. Re:Not a problem for most Web appliactions by VGPowerlord · · Score: 1

      That's how CGI works: It launches a CLI application, passing data to it through a series of defined environment variables and STDIN (POST only).

      --
      GLaDOS for President 2016! "Well here we are again. It's always such a pleasure." -- GLaDOS, 2011
    3. Re:Not a problem for most Web appliactions by pmarini · · Score: 1

      so as long as I don't use .NET languages then I'm safe ?

      (ironic, watch out for those acronyms...)

      --
      Can I put a spell on those who can't spell?
      Your wheels are loose and they're losing their grip, good you're there.
  10. I Thought This Would be Coming by segedunum · · Score: 1

    1. Red Hat are now employing too many lawyers and they need something to do.

    2. Red Hat have started to become the target of a lot of patent trolls themselves and this is what the said lawyers recommend as a defense mechanism.

  11. Thanks for the spam link by Dachannien · · Score: 4, Informative

    All of the various "free patents" sites are pure spam. The USPTO, like many other patent offices around the world, lets you view patents online for free - including free from ads.

    In this particular case, you can read the patent here, straight from the horse's mouth.

    1. Re:Thanks for the spam link by pieterh · · Score: 3, Interesting

      Actually, I think you're wrong and overmoderated. I've been trying freepatentsonline.com and it is pretty neat.

      Negative points: adverts, and these go away when you sign in.

      Positive points: extensive search functions (e.g. search on all different fields), ability to save searches, ability to download search results as spreadsheets (not figured out how yet).

      Of course you can read the patent without ads on the USPTO site. But the hard part is searching patents.

      Maybe you want to actually try the site before making blanket statements about "all free patent sites being pure spam". I think Google patent search is also pretty neat, and it's free.

      And the USPTO site is also free.

    2. Re:Thanks for the spam link by jank1887 · · Score: 1

      does USPTO give you PDF download of the full document? I go to see images, and I'm told I need a TIF plugin. a quick registration at freepatentsonline, and I can download the full PDF. Google patents, I can download a registration free PDF download. Both are 'image pdf' files with non selectable text. wikipatents is interesting, but doesn't quite do it for me.

      USPTO is behind the times. But that's to be expected.

    3. Re:Thanks for the spam link by Dachannien · · Score: 1

      Positive points: extensive search functions (e.g. search on all different fields), ability to save searches, ability to download search results as spreadsheets (not figured out how yet).

      I must be jaded by the search functionality we have at work. The big thing that Google and various other search sites lack is proximity operators.

      While the USPTO external website doesn't provide proximity operators, it does let you search on all fields in the advanced search. You can use the same search tools that examiners use if you visit the public search room at the USPTO headquarters in Alexandria, Virginia, and I think at least some of the examiner search tools are also available at the various Patent and Trademark Depository Library locations around the country.

    4. Re:Thanks for the spam link by saleenS281 · · Score: 1

      Why not just use google?
      http://www.google.com/patents?hl=en

    5. Re:Thanks for the spam link by Builder · · Score: 1

      The USPTO don't even use their own tools for searching / working with their patent database, so why should we ?

      AFAIK, they use products from what was Thomson Scientific (then Thomson Reuters, and now sold to someone else) for their own internal searches, etc.

  12. A new hope by Lalakis · · Score: 1

    RedHat seems to have a firm understanding of how the current patent system works. I salute them and hope in the future for them to own a lot of stupid patents like this one.

  13. Defensive patents by Richard+W.M.+Jones · · Score: 5, Insightful

    These are defensive patents. You have to file them if you're in the US software business, or else risk getting sued for $billions. Read how Red Hat licenses their patent portfolio to all open source projects.

    1. Re:Defensive patents by Obfuscant · · Score: 2, Insightful
      If software patents are bad, then they are bad. You can't claim you are doing a Good Thing by patenting something simple and obvious and then prohibiting some people from using it.

      That's what they are doing by promising not to sue Open Source projects for using THEIR patented intellectual property. It's still THEIR patented intellectual property, and they'll sue closed source projects for using it.

      What's even worse is they renig on their promise if an Open Source project tries to challenge Red Hat's claim to the IP. "Our Promise does not extend to any party who institutes patent litigation against Red Hat with respect to a patent applicable to software (including a cross-claim or counterclaim to a lawsuit)."

      That means that any project that wants to use any of Red Hat's licensed IP can't challenge ANY of Red Hat's patents for any reason, even patents that they shouldn't have because that open source project has provable, existing prior art in the area.

      Red Hat isn't defending anyone but themselves.

    2. Re:Defensive patents by gandhi_2 · · Score: 2, Funny

      Oh...so like a litigious Boondock Saints?

    3. Re:Defensive patents by geekoid · · Score: 0

      If they were serious, they would be spending money on lobbyists to make it so software isn't patentable.

      --
      The Kruger Dunning explains most post on /. http://en.wikipedia.org/wiki/Dunning%E2%80%93Kruger_effect
    4. Re:Defensive patents by ryran · · Score: 2, Insightful

      Thanks for posting the link! It should've been posted along with the article. .... Although I had never read it before, I already knew what it [much more explicitly] states: Red Hat cares about the community -- they owe everything to the community; they're not trying to extort the community. Having a firm grasp on the history of things, and having worked with Red Hat employees a lot, it's hard for me to understand how people can't see that.

    5. Re:Defensive patents by pieterh · · Score: 1

      Red Hat is not one thing. It is:

      - a community of engineers
      - a bunch of lawyers and accounts
      - a group of shareholders

      and more. I think the value of this story is not to show that the engineers are bad people. It's to show that the lawyers and accountants have a lot of power and could abuse that.

      It probably goes without saying that Red Hat engineers are generally really smart and ethical people - you don't work for an open source company otherwise.

      A lot of technology firms have tensions between the patent lawyers and engineers. IBM, Nokia, Sony, Microsoft, Red Hat, Sun, SAP... the only firms that don't have this tension are firms that do not file software patents at all.

    6. Re:Defensive patents by dirvine · · Score: 1
      I think what people are missing here is the smaller developers, perhaps not using GPL or OSS license X but instead looking to produce (or in fact just idea) some good product and sell it.

      I often feel pure open source (whatever that is - here comes the bsd vs gpl thing again) and proprietary 800 lbs gorrila companies are at opposite ends of a spectrum. The wee guy always seems to loose.

      Fair enough everybody patent everything - proprietary or the 'use for open source' people then game over the guys in the middle small companies and lone developers trying to get a buck from a great idea loose.

      I 100% agree making money continually from a bit of software is screwed unless your always adding real functionality and innovation (and thats another debate). I also agree there should be limits of some description (I mean after you have a couple of million - how much more do you really need, personally). The main point is always missed, 100% open source is not the answer and 100% proprietary is definitely not. Good developers should get paid for developing not supporting so there must be an answer somewhere in between these two wildly opposing points.

    7. Re:Defensive patents by Obfuscant · · Score: 1
      It probably goes without saying that Red Hat engineers are generally really smart and ethical people - you don't work for an open source company otherwise.

      Then it is the Red Hat lawyers prodded by the shareholders who file for patents on software, which the engineers think are bad, and expect closed-source software companies to license the IP.

      If Red Hat objected to software patents in general, they'd file for the patent and then let ANYONE use it. That's what would happen if there were no software patents -- everyone can use the ideas. By limiting the users of Red Hat's IP they are making the clear statement that software patents DO have a purpose and are valuable enough to spend money getting and defending.

    8. Re:Defensive patents by Anonymous Coward · · Score: 2, Informative

      Oh how adorable!

      Is your mommie a lawyer? You should ask her to read their patent promise to you one night before bed.

      In particular, she could explain to you the difference between "patent litigation" and a patent re-examination. They are not the same thing (yes, I'm ignoring ex parte vs. inter partes).

      The phrase you refer to means that the license for a third party to use the patents is terminated if that third party attempts to sue the holder over any other software patent.

      Ps. it's "renege".

    9. Re:Defensive patents by Obfuscant · · Score: 1
      I 100% agree making money continually from a bit of software is screwed unless your always adding real functionality and innovation (and thats another debate).

      Why shouldn't someone who buys my software in 2009 pay the same amount as someone who bought it in 2007? It does the same job, and it probably runs on less expensive hardware since it hasn't bloated beyond all reasonable size. A piece of software that does one thing and does it well doesn't need constant additions of "real functionality and innovation". That's the Microsoft "always upgrade" mindset.

      I also agree there should be limits of some description (I mean after you have a couple of million - how much more do you really need, personally).

      I employ ten people. I pay them well. They don't stop needing money to buy food after a year, or after the first two million in sales. Just who gives you the right to decide how much money is enough for someone else?

      Good developers should get paid for developing not supporting ...

      So I should just sell my program and never answer the phone or emails about how to use it or whatever bugs people find? Yes, I guess so, since "a couple of million" is enough money for me, I can't afford to spend it on phone lines or network connections to provide easy access for users to ask questions.

    10. Re:Defensive patents by dirvine · · Score: 1
      I think you miss the point here, good developers who produce good products are not necessarily good support personnel, in many cases the opposite (as with scientists and breakthrough drugs etc.). This is my issue with a lot of Open Source models

      On the other hand anti competitive behavior in any area of business (software, biotechnology, healthcare etc.) is plain wrong. There has to be a way to get rewarded, sure I agree and some more than others, but anti competitive behavior through ill thought out legal protectionism of this is daft.

      Also I have no rights (and would want none) to decide on whats enough money for you or anyone but it is a principle I think we have wrong, money is a barter commodity (could be seashells) and if something or somebody soaks up too much there less to go around an pay the next innovator. Thats the last point there has to be a better way. Mankind depends on innovation and anything that stops this is wrong in my opinion, but the converse is true innovators must get a chance to capitalise (and hopefully innovate more).

      Congratulations on employing 10 well paid staff this is a good thing and always should be, I would just ask you read everything in context.

    11. Re:Defensive patents by Obfuscant · · Score: 1

      Oh, how precious. A spelling flame. How novel.

    12. Re:Defensive patents by pembo13 · · Score: 1

      > You can't claim you are doing a Good Thing

      RedHat never claimed it was doing a good thing. Just doing something for survival _while_ they try to get patent reform.

      --
      "Thanks for all the money you paid to us. We've used it to buy off ISO among other things" -Microsoft
    13. Re:Defensive patents by RingDev · · Score: 1

      These are defensive patents. You have to file them if you're in the US software business, or else risk getting sued for $billions.

      I disagree.

      If their only concern were defense, then the solution is obvious! PUBLISH. The only difference between publishing your invention and patenting your invention is that you can sue someone for violating your IP rights associated with the patent.

      If they publish their invention, it is out there in the wild acting as prior art. If anyone else were to come along and try to sue them over a patent that the plaintiff had been issued after the defendant had published, all they have to do is point to the published article and show the prior art.

      -Rick

      --
      "Most people in the U.S. wouldn't know they live in a tyrannical state if it walked up and grabbed their junk." - MyFirs
    14. Re:Defensive patents by domatic · · Score: 1

      If their only concern were defense, then the solution is obvious! PUBLISH. The only difference between publishing your invention and patenting your invention is that you can sue someone for violating your IP rights associated with the patent.

      If they publish their invention, it is out there in the wild acting as prior art. If anyone else were to come along and try to sue them over a patent that the plaintiff had been issued after the defendant had published, all they have to do is point to the published article and show the prior art.

      Prior art can help disable a patent but it isn't necessarily a slam dunk; prior art may take care of some but not all claims in an enemy patent. And you might have a West Texas jury on your hands. Patents of your own tell potential litigants that you can hit back. Now you can argue that hitting back isn't nice and I would agree but that is the kind of legal system that we have. As Mel on Alice would put it "Sometimes the best defense is a good offense."

    15. Re:Defensive patents by Anonymous Coward · · Score: 0

      Bet you ten bucks that was PJ from Groklaw. :)

    16. Re:Defensive patents by RingDev · · Score: 1

      37 CFR 1.321

      A patentee owning the whole or any sectional interest in a patent may disclaim any complete claim or claims in a patent. In like manner any patentee may disclaim or dedicate to the public the entire term, or any terminal part of the term, of the patent granted. Such disclaimer is binding upon the grantee and its successors or assigns.

      Again, the only reason to hold on to the patent is for offensive reasons. There is nothing stopping them from publishing or dedicating the patent to the public. The prior protecting them in 49 1/2 states, the later protecting them in that 1/2 a remaining state of ethically challenged judges.

      -Rick

      --
      "Most people in the U.S. wouldn't know they live in a tyrannical state if it walked up and grabbed their junk." - MyFirs
    17. Re:Defensive patents by Ant+P. · · Score: 1

      If (strawman) then {meaningless conclusion}.

      Replace "software patents" with "handguns", "bittorrent clients" or "$minor_feature_in_desktop_environment_X" to suit the invalid point being pushed.

    18. Re:Defensive patents by lutter · · Score: 1

      Software patents are bad, yet they still exist, and you have to live with that reality. Red Hat is not just filing for defensive patents, it is also pouring resources into patent reform. In an ideal world, software patents would be a non-issue, and Red Hat is at the forefront of making that a reality.

      In the current reality, it's impossible for OSS to infringe on Red Hat's patents because of the patent promise which is legally binding and irrevocable. I have no idea what Red Hat's strategy for infringement from non-OSS software is, but it sounds like it's a 'live and let live' attitude. As long as you don't attack Red Hat with your patents, Red Hat won't come after you with theirs. Given reality, that seems an entirely sensible and prudent stance.

    19. Re:Defensive patents by Obfuscant · · Score: 1
      Software patents are bad, yet they still exist, and you have to live with that reality. Red Hat is not just filing for defensive patents, it is also pouring resources into patent reform.

      That's nice. Good for Red Hat. I have no problem with Red Hat getting a software patent on whatever it likes while claiming that software patents are bad. That's not the issue. Not at all.

      Let me make this clearer. The problem is that they are claiming the rights associated with those patents, which is the exact Bad Thing that they object to. Software patents without patent rights are meaningless. Software patents are only worth something because of the rights associated with them, and it is use of those rights to keep people from using knowledge that makes them a Bad Thing.

      If Microsoft got a patent on CGI/SOAP and said "you can't use this IP", there would be screams about how bad Microsoft is and that software patents are bad. Red Hat has gotten that patent and has told a certain subset of the software world that they cannot use it. Yet people are coming out of the woodwork to defend Red Hat for using their patent to prevent people from using the IP they've claimed. Why is that?

      Are software patents and the resulting restrictions that can be imposed on people based on them BAD or GOOD? Why is Red Hat a White Hat for imposing restrictions on people under the guise of a software patent, but MS bad for doing the same thing?

      Remember, the "Red Hat Promise" does not allow everyone to use the IP. That, by DEFINITION, means they are putting restrictions on it.

    20. Re:Defensive patents by Anonymous Coward · · Score: 0

      You are so clueless it hurts. Get out and talk to some people in the business. The standard practice with defensively patenting is you have a portfolio of patents that you can use to defend yourself if some unscrupulous patent troll trys to extort you. If you don't have a patent portfolio in 2009, you are a lamb fresh for the killing. Redhat licenses out their patents for free to any OSS project, they position is crystal clear and totally consistent.

    21. Re:Defensive patents by teg · · Score: 1

      If their only concern were defense, then the solution is obvious! PUBLISH. The only difference between publishing your invention and patenting your invention is that you can sue someone for violating your IP rights associated with the patent.

      Publishing would protect against being sued for this particular "invention". What defensive means in this context is to have a portfolio of patents - if another software vendor sues for violating their patents, Red Hat can point at their portfolio and say "you are violating ours!" and use these to negotiate a deal.

    22. Re:Defensive patents by RingDev · · Score: 1

      Publishing would protect against being sued for this particular "invention". What defensive means in this context is to have a portfolio of patents - if another software vendor sues for violating their patents, Red Hat can point at their portfolio and say "you are violating ours!" and use these to negotiate a deal.

      Which leaves us in the position that we should all patent more things, even the most incredibly inane things, just so that if anyone sues us we can sue them back for a negotiating point. Fighting patent trolls by trolling.

      I think you raise a great point for the current climate. But I think we can all concur that the current IP climate is fubared. Of course, if the USPTO and courts don't come around before the companies, any company that tries to do the right thing will likely get eaten alive by trolls and competitors.

      If we agree that bad patents are bad for innovation, economic growth and advances in technology, it's rather poor form to say "Well, it's okay if Redhat does it, because we like them now". Heck, 20 years ago Microsoft was a rocking little tech company fighting off the big dogs. 20 years from now we could be cursing Redhat for their IP abuses and market influence ;)

      -Rick

      --
      "Most people in the U.S. wouldn't know they live in a tyrannical state if it walked up and grabbed their junk." - MyFirs
    23. Re:Defensive patents by jonaskoelker · · Score: 1

      You have to file them if you're in the US software business, or else risk getting sued for $billions.

      I'm not great at perl, but couldn't you just set

      my $billions = 0;

  14. In Re Bilski by cliffiecee · · Score: 1

    The In Re Bilski case invalidates this patent, as it is not tied to a particular machine.

    DISCLAIMER: Not only am I not a lawyer, my sole basis for my statement is knowledge gained from my somewhat-attentive reading of previous /. comments (not articles) regarding the "In Re Bilski" case. I'm not sure if the word "case" applies to In Re Bilski. I'm not sure if "In Re Bilski" should be written with initial caps, as opposed to "in re Bilski", for instance.

    1. Re:In Re Bilski by jerrund · · Score: 2, Informative

      Bilski doesn't apply here, as the In Re Bilski ruling only applies to Process claims. The claims in question are directed to a system.

    2. Re:In Re Bilski by Anonymous Coward · · Score: 0

      Well, that's debatable. No courts have ruled on whether bilski applies to non-process claims. The Board of Patent Appeals and Interferences (BPAI) has used bilski to invalidate software claims that weren't process claims: http://www.patentlyo.com/patent/2009/01/ex-parte-marius.html

  15. In other news ... by Anonymous Coward · · Score: 0

    Proctor & Gamble claims prior art on SOAP.

  16. Re:Patent Troll by jackspenn · · Score: 2, Insightful

    You are aware they aren't patenting things to prevent others from using those concepts or to change a fee to use the process. Instead they are doing it as a defensive measure against the likes of SCOs, M$ and greedy lawyers. They aren't patent trolls, they are protecting themselves and the Linux.

    --
    Respect the Constitution
  17. I should patent by einhverfr · · Score: 2, Informative

    A circular load bearing device where a bent-wood rim is suspended around a hub with wooden segments of equal length. This is useful as a method of facilitating the motion of wagons, chariots and the like. Optionally a metal (bronze or iron) rim can be placed around the wooden rim adding greater durability at the expense of weight.

    --

    LedgerSMB: Open source Accounting/ERP
    1. Re:I should patent by Anonymous Coward · · Score: 0

      No really. Imagine if patent law hadn't been around! We may have never developed something as critical to the development of the human race as the wheel!

    2. Re:I should patent by einhverfr · · Score: 1

      What is a patent an exchange for, really?

      The exchange is not about innovation. We aren't giving people incentive to INNOVATE through patents. We are giving people incentive to disclose innovations through patents. There is a huge difference.

      The argument for patent law is not about innovation but rather that without a patent process, there would be every incentive to keep innovations secret (moving innovations from patents into trade secrets). Given that alternative, I think that patents make a great deal of sense. The bargain is that if you tell everyone what your innovation is, we will give you a time-limited monopoly on it. If you don't, you can protect it using trade secret law indefinitely.

      In some things, however, this is not in society's interest, so we should review certain types of patent protections and exclude them from the process.

      --

      LedgerSMB: Open source Accounting/ERP
    3. Re:I should patent by einhverfr · · Score: 1

      BTW, I think that software patents should be limited to fields like encryption, simply because I would rather have a documented encryption algorythm than I would an undocumented one. This isn't really an argument against patent-free open source algorythms, btw, just an argument against secret ones.

      --

      LedgerSMB: Open source Accounting/ERP
    4. Re:I should patent by Anonymous Coward · · Score: 0

      Huh? The patent system doesn't stop you from innovating and keeping it secret. The fact that people file patents contradicts your argument that greedy people would just hoard their "innovations." They are only filing out of fear that it will be discovered. Giving people additional options cannot hurt them.

    5. Re:I should patent by einhverfr · · Score: 1

      People will innovate anyway. They always have. However, the case is that some things that would ordinarily be kept as trade secrets will go through the patent process and hence be publically documented. Some sorts of innovations are good candidates for patents. Others are not.

      For example, although I tend to be against software patents, I am for allowing patents on encryption algorythms because given the choice between an algorythm being a trade secret and it being patented, the latter is less damaging to everyone involved. However, I think we also need to reduce the time period where patents are honored, maybe to 10 years for most things or half that for software or other short-life-cycle products.

      --

      LedgerSMB: Open source Accounting/ERP
    6. Re:I should patent by Anonymous Coward · · Score: 0

      You are missing the point. Why would someone patent something if you could just "keep it a trade secret forever"? If this was a tenable approach, companies would avoid patents, and instead keep everything as trade secrets.

    7. Re:I should patent by einhverfr · · Score: 1

      Why would someone patent something if you could just "keep it a trade secret forever"?

      Because patents and trade secrets have entirely different protections and the latter is far weaker for functional components of goods sold to the general public?

      THe basic issue is that with a patent, the government grants a monopoly for a number of years on all applications of the innovation in exchange for disclosing it. The idea is that if you DON'T treat it as a trade secret, we will protect your market for a while.

      However for a trade secret, you only have protection against certain forms of disclosure and competition. If I reverse engineer your implementation, you have NO protections under trade secret law. I pretty much only am in trouble if you trusted me with the secret and I betrayed your trust. If I came by it myself through reverse engineering, you have absolutely no protections.

      I am not saying that patents on short-life-cycle goods like software should be the same as on long-life-cycle goods like automobiles. In fact I don't think they should be. I think a 5-year patent on software ought to be sufficient and a 10 year patent on longer-life-cycle goods ought to be sufficient (automobile parts, pharmaceuticals, etc). The key though is we have to stop thinking of patents as matters of "intellectual property" but rather "payment for disclosure." We as the public need to decide what the disclosure is worth in various areas and create a patent law system which addresses those concerns. (Copyright and software is another issue, and I am of the opinion that one should be forced to register the copyright on the source code before you can register the copyright on binary derivative works.)

      The patent regime expires too quickly not if the big biotech companies are complaining but rather if companies are bypassing the patent process frequently and trying to keep things as trade secrets. The goal of a patent system ought to be to have the shortest patent protection schedule which encourages disclosure.

      --

      LedgerSMB: Open source Accounting/ERP
  18. Yes. by krog · · Score: 2, Insightful

    Of course they are. Of course they are. It's not bad when "we" do it.

    1. Re:Yes. by Nick+Ives · · Score: 4, Insightful

      You're post reads as if you're being sarcastic. You are aware that if Red Hat were to prevent other people from using their patents in GPLv2 or later software then they would lose the ability to distribute GPLv2 or later software, right?

      They could go after proprietary vendors I suppose but I find it far more likely that these are defensive patents.

      --
      Nick
    2. Re:Yes. by Anonymous Coward · · Score: 0

      "defensive patents" -- if this was true, then they should just have cemented the 'proof of prior art' (archive their creations in legally-certified manner). should be cheaper and quicker as well (as compared to patents). so all this 'defensive patents' is nonsense -- they just want to get some leverage to 'wrestle' others wrt other companies' patents if/when such "others" will try to go after redhat -- but that is a different story altogether (i.e. abusing current patent portfolio for no other purpose than political wrangling... all under the pretence of 'good guys')...

    3. Re:Yes. by MillionthMonkey · · Score: 2, Insightful

      Let's say some corporation applies for a patent on garbage collection or XML or image editors or something like that. Someone has to prevent them from doing it.

      Who would be in a better position to present prior art? Who has obvious standing in this case at all? And which one has legal parity that would be obvious to any Windows user charged with making a judgment on this? A corporation with a similar patent, or a loosely-knit but idealistic bunch of Slashdot lawyers?

      In principle it goes against everything to be relying on a single private party to shield obvious processes from frivolous patent claims on things we do every day. It places too much trust in one party. But legally and in a pragmatic sense I would be inclined to let Red Hat deal with these people. They have patent lawyers. Otherwise geeks have to keep coming out of the woodwork to make prior art claims.

    4. Re:Yes. by Anonymous Coward · · Score: 0

      That could be true except no one else is doing it. They could take the high ground and try to defend themselves with prior art, but I think that they need to be able to fight if necessary. Fight fire with fire. If they try to go after someone and do anything negative with this then I will pass judgment. Until then I will assume they are playing CYA in a pool of sharks.

    5. Re:Yes. by Nick+Ives · · Score: 2, Insightful

      so all this 'defensive patents' is nonsense -- they just want to get some leverage to 'wrestle' others wrt other companies' patents if/when such "others" will try to go after redhat

      That's the whole point of a defensive patent portfolio. Some other company has patents over stuff you're selling (considering all the software in RHEL, this is certain) so you take out patents on stuff that other companies are likely to be selling.

      Its the same logic as the cold war where you have nukes because everyone else has them - nobody would ever go after anyone with patents because the other guy could just counter-sue. The problem is patent trolls, they are the equivalent to terrorist groups with nuclear bombs: they have nothing to lose.

      --
      Nick
    6. Re:Yes. by tritonman · · Score: 1

      NEWSFLASH! Red Hat isn't looking out for your best interest just because they create a Linux based OS. They are still a for profit company.

    7. Re:Yes. by bb5ch39t · · Score: 1

      Do you feel that any and all "for profit" companies are evil? I admit that many are. Especially the larger ones. But not each and every one. RH is probably better than most, if not exactly "lily white".

    8. Re:Yes. by mweather · · Score: 1

      Any entity legally compelled to maximise profits behaves in a manner indistinguishable from evil. Corporations are sociopaths.

    9. Re:Yes. by spyowl · · Score: 1

      They could go after proprietary vendors I suppose but I find it far more likely that these are defensive patents.

      Sure they are probably not going to use the patents against open source projects themselves. But the possibility to use them against "proprietary vendors" part opens up a whole new can of worms. If there is an [unrelated] disagreement - e.g. licensing, agreements or whatever - between Red Hat and, say, Novell/Cisco/IBM/Oracle/etc. Red Hat lawyers can quickly bring these patents into their countersuit. Red Hat could argue - "you are distributing free software library XYZ which violates our patent 123."

      As far as losing the ability to redistribute GPL software if they do bring up patents against it, that's not so straightforward as you describe. GPL is a licensing agreement between 2 parties. First, as far as I know, courts have yet to have a case claiming that and rule in that direction. Second, you probably would need help from the original author(s) of the library/software in question and a separate lawsuit against Red Hat. This lawsuit would still be unrelated to Red Hat's patent claims and could go on for as long as Red Hat could drag it out, or until the other party runs out of cash/time.

    10. Re:Yes. by Nick+Ives · · Score: 1

      If there is an [unrelated] disagreement - e.g. licensing, agreements or whatever - between Red Hat and, say, Novell/Cisco/IBM/Oracle/etc. Red Hat lawyers can quickly bring these patents into their countersuit. Red Hat could argue - "you are distributing free software library XYZ which violates our patent 123."

      I don't see that as a bad thing considering the current system. All legitimate software companies need software patents for this very reason, it's a form of mutually assured destruction like the cold war.

      The problem is the system of software patents, not necessarily any particular company that holds patents. Companies that use patents aggressively in order to crush competition should attract our ire in the short term but the problem is the system itself.

      --
      Nick
    11. Re:Yes. by Nick+Ives · · Score: 1

      That isn't in any way relevant to what I posted.

      --
      Nick
    12. Re:Yes. by speedtux · · Score: 1

      They could go after proprietary vendors I suppose but I find it far more likely that these are defensive patents.

      RedHat could go after anybody, we just don't know.

      When was the last time Microsoft asserted a patent directly against a FOSS project? Yet, Microsoft is apparently busily using their patent portfolio to try to force business deals from open source vendors. What makes you think RedHat isn't going to do the same?

      If these were "defensive patents", then RedHat could set up a legal structure that would allow them to be used purely for defensive purposes; in fact, they could set up a legal structure that would allow all FOSS projects to use them for defensive purposes. But they haven't done that; they simply maintain these patents as their exclusive property, to be used for whatever business purposes they want.

  19. Acronyms by necro81 · · Score: 2, Funny

    I haven't had to wade through that many acronyms since "Good Morning Vietnam"

  20. prior art by Anonymous Coward · · Score: 1, Insightful

    Scanning the patent briefly I saw the earliest date was 2005.

    In 2003/2004 I wrote a CGI script that greps a csv file pipes it to sed to generate xml and returns that xml to the client.
    Does this count as prior art?

    Actually I am writing a (client side focused) Ajax course now and intend to use a toy cgi service that greps a csv file and returns the data in not XML but JSON. That is not XML pfew I do not infring the patent.

     

    1. Re:prior art by dirvine · · Score: 1

      Only if you published somewhere good enough to be witnessed and picked up by a reasonable search.

    2. Re:prior art by trwww · · Score: 1

      Here is proof positive of prior art:

      http://search.cpan.org/~kulchenko/SOAP-Lite-0.55/

      15 Apr 2002

      SOAPsh.pl - Interactive shell for SOAP calls

  21. Are you Kidding me? by Anonymous Coward · · Score: 0

    this is ridiculous!

  22. Haha Microsoft by Rogu3 · · Score: 2, Funny

    MS Robotics Studio uses Soap to XML. Haha, how like life now.

    --
    Strive for perfection in everything you do. Take the best that exists and make it better. When it does not exist, design
  23. Re:Patent Troll by Jurily · · Score: 1

    against the likes of SCOs, M$ and greedy lawyers.

    And Canonical, the FSF, and everyone else.

  24. How is that not 'blatantly obvious'? by Assmasher · · Score: 1

    I mean, SOAP's entire purpose is to be a messaging mechanism over different mediums, protocols, architectures, and implementations; ergo, if I implement "Handling SOAP over " how on earth could that be patentable? Maybe they're referring to actual soap (like Lava, or Lever 2000, summat...)

    --
    Loading...
  25. Re:Patent Troll by usman_ismail · · Score: 2, Informative

    You are aware they aren't patenting things to prevent others from using those concepts or to change a fee to use the process. Instead they are doing it as a defensive measure against the likes of SCOs, M$ and greedy lawyers. They aren't patent trolls, they are protecting themselves and the Linux.

    You don't need a patent for that just prior art in the wild

  26. So what? by Anonymous Coward · · Score: 0

    Just because there is a patent does not mean RedHat has a practical defensible claim on something. Slashdotters seem to think the Patent system is some kind booby-trapped chess game. Yes, some companies are misguided and sue. But we don't know the real reasons WHY they sue. In some countries there is not even a Patent vetting process - you can register a patent for anything you like and for a fee it gets filed. RedHat has to make a business decision about if there is financial benefit to protect their claim, against whether the Court will think the claim is bogus. If you can see the claim is bogus, why do you think a court will not have the common sense to come to the same conclusion. Judges aren't stupid.

    That fact that a patent is on file does not take precedence over, nor does it bias, the legal process.

  27. Re:Patent Troll by Ultra64 · · Score: 1

    Unless you live in reality, with the rest of us.

  28. And after htey get rid of SOAP by wiredog · · Score: 1, Funny

    they will get rid of SHOWERS.

    1. Re:And after htey get rid of SOAP by bennomatic · · Score: 1

      Wow... clever invocation of Godwin's Law.

      --
      The CB App. What's your 20?
    2. Re:And after htey get rid of SOAP by TheLink · · Score: 1

      No he said: "they will get rid of SHOWERS."

      Doing a Godwin would be: In Nazi Germany, SHOWERS get rid of YOU!

      --
    3. Re:And after htey get rid of SOAP by Anonymous Coward · · Score: 0

      That is a Jewish conspiracy. It never happened despite the overwhelming physical evidence.

  29. The Patent system is SO broken by Anonymous Coward · · Score: 0

    That I have no choice but to ignore it completely. It has brought itself into disrepute, as the legal lingo would put it.

  30. Probably not so broad as to encompass CGI by Anonymous Coward · · Score: 1, Informative

    The claims of a patent aren't completely isolated from the specification of a patent. While multiple cases warn against reading limitations from the specification into the claims, the terms in the claims often only take on meaning in light of what the specification teaches.

    Take a look at figure 1 to get a sense of what Red Hat's inventor claims to have created: a command-line interpreter that can take something like "cat members | http://ws.example.com/ldap-lookup -name | xml://phone > member-phones" and produce meaningful results. That is, making the Unix command line a tool that seamlessly integrates services that are available remotely.

    Does this help in interpreting the terms in the claim: "A system comprising: a command-line interpreter ("CLI") to obtain a text string describing a data processing pipeline ... process-launching logic to launch a plurality of child processes ... and remote service interaction logic to accept delimited data strings from a first of the plurality of child processes on a standard input" (simplified).

    Well...CGI does not really have a command-line interpreter. You can run a CGI script from the command line, but Apache doesn't need to go through sh when it communicates with a CGI script. If you are running a CGI script from the command line, you're running it locally (even if you have remotely logged into another machine, you are still running it locally on that other machine). Thus, running the CGI script from the command line does not involve remote service interaction logic.

    CGI is a poor example to use of something that might anticipate this patent. Perhaps a stronger argument could be made that the claimed invention was obvious in light of combining a command-line interpreter with wget or rsh, but given how long command-line interpreters have required additional programs to access remote services, an argument could be made that integrating the functionality directly into the command-line interpreters is, in fact, non-obvious.

    1. Re:Probably not so broad as to encompass CGI by Anonymous Coward · · Score: 0

      Thanks for at last posting some sanity. The patent in question doesn't require SOAP or any interaction with a CGI.

      The claims involve syntactical additions to a shell which facilitate the interaction with a network service. Those additions revolve around:

      a) the shell being cognizant of a network service such as HTTP and being able to interact with it, and

      b) mapping parameters received from argv or from stdin as XML input to the network interaction (perhaps as SOAP parameters) and

      c) receiving the network response (e.g. HTTP response), extracting relevant content and mapping it back to stdout, so it can be fed into the input pipe of a subsequent command.

      You *might* have built a system which can interact with a webserver with soap and spit out the results on stdout, but did you modify the shell to support it syntactically?

      Regarding the 'non-obvious' point. The test for obviousness is a legal defintion, not what a lay person might expect. However, one defense for obviousness is

      a) is it easy to implement?
      b) if so, then why has nobody done it before?

      If nobody has done it, it can be argued that its non obvious. Of course, that 'argument' happens in court, not on slashdot, which means you pay to play.

  31. Someone had to... by neowolf · · Score: 3, Insightful

    Face it- if Red Hat hadn't done it, M$ probably would have. It's likely a "defensive" patent they are unlikely to use unless provoked. It's all just a game. A big, high-stakes, unfortunate game.

  32. What AHAH? by tepples · · Score: 1

    Since returning HTML would not be covered, AHAH requests would not be covered.

    Even under a typical AJAX environment, switching the encoding from XML to JSON might work around.

    You should be using AHAH anyway.

    What do you mean by AHAH? Are you implying that not using query suggestions or client-side pre-validation creates a better user experience?

  33. In Soviet Australia, wheel patents YOU by tepples · · Score: 2, Funny

    A circular load bearing device where a bent-wood rim is suspended around a hub[...]

    Except in Australia, such a patent was issued.

  34. Bullshit! by MikeRT · · Score: 1
  35. Not a big deal by steveo777 · · Score: 1

    Most of IT support and administration staff weren't fond enough of SHOWERS to use it. SOAP itself wasn't necessarily a child process or deamon for SHOWERS as it also worked with BATH and HANDWASH. Neither of which are popular either. Most of them will just hope that DEODORANT will cover up the problems that SOAP, SHOWERS, or BATH would have fixed but generally everyone can tell if they start sniffing around the network.

    I hear good things about the open source project PTA BATH.

    --
    This sig isn't original enough, it's time to come up with something witty...
    1. Re:Not a big deal by foobsr · · Score: 1

      PTA BATH

      Taking advantage of prior art like the ultrasonic shower (Asimov, robot series IIRC) or the sonovac (2001) would be a good idea. Admittedly, I since I first read about these ultrasonic devices decades ago (when there was no such thing like the 'basement geek culture' (??) I am very fond of the idea.

      CC.

      --
      TaijiQuan (Huang, 5 loosenings)
    2. Re:Not a big deal by steveo777 · · Score: 1

      Actually, I was referring to the 'hooker bath' where she would wash her Pits, Tits, and Ass before the next trick. Old term that my dad used to use when he was in the army.

      --
      This sig isn't original enough, it's time to come up with something witty...
  36. Re:Patent Troll by Anonymous Coward · · Score: 0

    You don't need a patent for that just prior art in the wild

    amen to that -- finally someone with some brains...f!@#$ patents wrt open source -- prior art shall set you free

  37. USPTO.gov images by tepples · · Score: 1

    The USPTO, like many other patent offices around the world, lets you view patents online for free - including free from ads.

    The various "free patents" sites provide the service of translating the images from TIFF in an obscure codec to something more popular, such as JPEG, PNG, or PDF.

  38. Re:Patent Troll by Anonymous Coward · · Score: 0

    By "the Linux" do you mean "the GNU?"

  39. Re:Patent Troll by Java+Pimp · · Score: 2, Insightful

    We have know for a long time that Red Hat is a patent troll. They make IBM look like noobs.

    Ok, c'mon now... Redhat (IBM as well) is part of OIN... Press Release here... How about we wait until they actually do something trollish before throwing around accusations like they were government bailout money...

    --
    Ascalante: Your bride is over 3,000 years old.
    Kull: She told me she was 19!
  40. Distinction without a difference? by tepples · · Score: 1

    the In Re Bilski ruling only applies to Process claims. The claims in question are directed to a system.

    If a system's only novel aspect is a process that happens in the system, in this case XML encoding and decoding at each side of the connection, then what's the difference between a system claim and a process claim?

  41. Pro se? Ha! by tepples · · Score: 1

    If you can see the claim is bogus, why do you think a court will not have the common sense to come to the same conclusion.

    Because the patent holder may have already won by default. If you were sued, would you have the money to defend yourself in court?

    1. Re:Pro se? Ha! by MetalOne · · Score: 1

      IANAL. From what I have read here in the past, it seems courts don't throw out patents. Courts don't make decisions about their validity. They only determine if you are infringing. The courts assume that since the PTO approved it that it is valid. It is up to you to get the patent office to overturn a bad patent. This can take years and may very well not be successful.

  42. Re:Patent Troll by Anonymous Coward · · Score: 0

    YANAL, right?

    If you feel you have prior art you must argue for your case and have a court agree with you.

    Things are a lot more cut-and-dried when you hold a patent.

  43. i just patented the word 'bailout' by Anonymous Coward · · Score: 0

    I just patented the word 'bailout' i'll be rich overnight.... If that doesn't fly, maybe then i'll use my time machine and go back 2 years and patent the term 'Joe the plumber' oh yea, and i also own a patent for any document containing the letter 'e', so you all owe me eleventy billion dollars!!!

  44. Re:Patent Troll by betterunixthanunix · · Score: 1

    "You don't need a patent for that just prior art in the wild"

    Except prior art does not always exist. In cases where no prior art is available, you need to have a large number of patents available for cross-licensing schemes, or in the worst case, counter-suits. A multi-billion dollar software company just cannot survive anymore without patents at the ready (or without enough money to pay for patent licensing).

    --
    Palm trees and 8
  45. Re:frist psot "Dont' drop the SOAP"... especially by davidsyes · · Score: 1

    if there are Psycho-like shower scenes. My first thought was soaping done in CGI/animation, hehehe....

    Lovely or bubbly?

    --
    Previously: "Linux... Toward the Sunrise..." Now: "Linux... Toward the-- No, now, part of Every Sunrise"
  46. Re:Patent Troll by Anonymous Coward · · Score: 0

    You said "M$", nyuck, nyuck.

  47. bric_soap by kwoff · · Score: 2, Informative

    I've been using such a command called bric_soap in Bricolage (Perl-based CMS) for the last six years at least.

    Introduced in 2002: ViewVC

    An example (see the API docs, navigate to bin -> bric_soap ...): "Republish all published stories. This is useful when a template change needs to be reflected across a site. The sort -k2 -t_ -n is a crude way to make sure that newer stories overwrite older ones."

    bric_soap story list_ids --search publish_status=1 | sort -k2 -t_ -n | bric_soap workflow publish -

    1. Re:bric_soap by Anonymous Coward · · Score: 0

      From what you described, bric_soap would not infringe on the RedHat patent, and thus it does not anticipate the claimed invention. bric_soap is used from the command-line, but it does not provide the command-line. This is an huge distinction. Would it have been obvious to incorporate the bric_soap functionality into the shell? Maybe, but that's not what you argued.

  48. More prior art by RingDev · · Score: 1

    In 2004 my capstone project was a TV/DVR remote control software package that ran on a wireless PDA. It worked by sending SOAP requests to a web server that would execute command line instructions on a media service and return XML data based on the result and state of the device.

    Their patent sounds like it is almost an exact duplication of my capstone.

    I'm sure I have the source floating around somewhere, but I still have images from the app up on the web:

    http://ringdev.com/images/BlueSkinListing.bmp
    http://ringdev.com/images/RedLineSkinListing.bmp
    http://ringdev.com/images/RedLineSkinDetail.bmp

    -Rick

    --
    "Most people in the U.S. wouldn't know they live in a tyrannical state if it walked up and grabbed their junk." - MyFirs
  49. Speaking of prior art... by Denny · · Score: 1

    Bricolage had a command-line SOAP utility in 2002:

    http://viewsvn.bricolage.cc/bricolage/trunk/bin/bric_soap?view=log

    --
    Police State UK - news and
  50. RIP by thethibs · · Score: 5, Funny

    With any luck, this will finally put SOAP to REST.

    --
    I'm a Programmer. That's one level above Software Engineer and one level below Engineer.
  51. Confusing the ttol with the job by mcrbids · · Score: 1

    Wrenches can be used to kill people. So can metal broomhandles and tennis rackets. This fact does not make anyone who carries a wrench, a broomhandle, or a tennis racket a bad murderer.

    (My father used to keep a tennis racket in the car to arm himself when he was in a bad neighborhood - works well and you won't be accused of brandishing a weapon)

    There are few (any?) other companies that 'get' OSS more/better than Red Hat. They license their patents to the community at large, effectively subverting the usual use of patents, much as using the copyleft license uses copyrights to flip normal copyright conventions on their ear.

    Red Hat is one of the really, really good guys. With Red Hat patenting CGI/SOAP, they've effectively prevented others from doing so, assuring all of our freedom to use CGI/SOAP. (No, I don't work for RH, though I was once a shareholder)

    Blaming RH for its patents are like calling somebody who uses a shotgun to get mistletoe out of a tree a murderer.

    --
    I have no problem with your religion until you decide it's reason to deprive others of the truth.
    1. Re:Confusing the ttol with the job by Obfuscant · · Score: 1
      Wrenches can be used to kill people. So can metal broomhandles and tennis rackets. This fact does not make anyone who carries a wrench, a broomhandle, or a tennis racket a bad murderer.

      However, when someone buys a wrench (gets the software patent) and then smacks someone over the head with it (denies them the right to use the IP protected by that patent) they are guilty of attempted murder (using software patents to protect their IP.) Only if you buy a wrench (get the patent) and then never hit anyone with it (allow everyone to use the IP) are you not guilty of attempted murder.

      assuring all of our freedom to use CGI/SOAP

      That is not true. If your project is not open source, you have no freedom to use CGI/SOAP now that Red Hat holds the patent. Is there some odd definition of "all" that you use that doesn't include everyone?

      Blaming RH for its patents are like calling somebody who uses a shotgun to get mistletoe out of a tree a murderer.

      A less coherent analogy would be hard to find.

      Either software patents are bad or they aren't. When Red Hat gets the patent on something, they are claiming the sole rights to determine who gets to use that IP. That's not the issue. The issue is they ARE using that right to prevent people from using the IP. And further, they are saying that someone who objects to Red Hat's patent for ONE piece of IP, by litigating that patent, doesn't get to use ANY of the Red Hat IP.

      If you say that software patents should not be issued, that's saying that NOBODY should get to decide who can or can't use some software-based IP. That would be freedom. Red Hat can't say that they exclude some people from using THEIR IP and also be opposing software patents -- the ability to prevent people from using your IP is the REASON for patents, not an argument against them.

  52. What BS - PRIOR ART. by gabrieltss · · Score: 1

    When I was at Cabela's we had built what is now called SOAP. We were doing XML request/responses across HTTP LONG before SOAP was SOAP... That prior art will blow this patent out no matter WHO claims it... We were sending XML to from an AS/400 to/from Apache web servers / Java web servers. We compiled the source for castor on the AS/400 and were marshelling/demarshelling XML on an AS/400.

    --
    The Truth is a Virus!!!
    1. Re:What BS - PRIOR ART. by Anonymous Coward · · Score: 0

      Identifying a few keywords that show up in pre-existing technologies does not invalidate a patent. Read the patent claims. Make sure that you have an understanding of what they could reasonably mean. The article summary is very much misleading and is a bad claim construction.

  53. HAH! by Anonymous Coward · · Score: 0

    Let them have it!

    SOAP is one of the stupidest technologies I've seen in a long, long time.

  54. Their patent policy is worth reading... by Denny · · Score: 3, Informative
    --
    Police State UK - news and
  55. Re:Patent Troll by jackspenn · · Score: 1

    So why did Linus have to copyright the word "Linux"? Exactly the same reason, to protect us from BS lawsuits, by owning patents they can offer protection against lawsuits. You're naive and don't understand the real worl. RH is a good guy.

    --
    Respect the Constitution
  56. Re:Patent Troll by usman_ismail · · Score: 1

    As for as I know Linus trade marked the word linux, he did not copyright it. Anyone can claim a trade mark as long as it has not been trade marked before. There is not requirement to prove no one used the word before just that they did not trademark it.

    And I am not naive just cynical that RH will continue to be a good guy 5 or 10 years from now

  57. ...And after they get rid of SHOWERS by Anonymous Coward · · Score: 0

    They will come for IME, but nobody will say anything because - dude - it needed a SHOWER...

  58. Patent 101.... by twivel · · Score: 2, Informative

    A patent is not infringed upon unless all claims within the patent are infringed upon. The slashdot submission does not take into account the other claims in the patent.

    Of course, that doesn't really matter, because there are numerous prior art implementations of a CLI integrating to SOAP for something like this. For example, IBM WebSphere Portal has an xmlaccess command line utility that does exactly this.

    1. Re:Patent 101.... by Anonymous Coward · · Score: 0

      "A patent is not infringed upon unless all claims within the patent are infringed upon."

      That's not true. Each claim is a further expansion upon the previous in case the examiner thinks the previous it too vague. You claim all instances you think you can get away with and what goes into the final approved patent are all the claims that are allowed.

    2. Re:Patent 101.... by Anonymous Coward · · Score: 0

      The slashdot submission does not take into account the other claims in the patent.

      And neither did you. There's only one other claim, which is a dependent claim.

      A patent is not infringed upon unless all claims within the patent are infringed upon.

      Not true. A device only has to infringe one claim to infringe the patent. Otherwise, dependent claims would be pointless since they are specializations on the independent claims.

      Also, it is not unusual to see patents where some of the claims are mutually exclusive. i.e. it's not possible to create a device that includes elements of all claims.

      For instance, claim 2 might say something like "the XYZ from claim 1 is an FPGA." Then, claim 3 might say something like, "the XYZ from claim 1 is an ASIC."

      Someone would have to bend over backward to build a device that infringed both claims 2 & 3.

    3. Re:Patent 101.... by cbailey64 · · Score: 2, Informative

      A patent is not infringed upon unless all claims within the patent are infringed upon.

      You are wrong. A single patent in the US may have multiple independent claims. Inside the patent there are also dependent claims that refine either an independent claim or a dependent claim. Duplicating any of them is an infringement. Period. Think of it as a venn diagram.

  59. Re:Patent Troll by budgenator · · Score: 1

    Linus didn't trademark it,

    The Linux trademark is owned by Linus Torvalds in the U.S., Germany, the European Community, and Japan. In the U.S., the mark is registered (Serial Number: 74560867)[1] for "Computer operating system software to facilitate computer use and operation." The assignment of the trademark to Torvalds occurred after an attorney, one William R. Della Croce, Jr, in 1996 began sending letters to various Linux distributors claiming to own the Linux trademark and demanding royalties. The distributors rapidly pooled resources, appealed against the original trademark assignment and had it reassigned to Linus Torvalds. Linux Mark Institute

    This was an instance of where the community came together for the communities good; I suspect that the RH patent is another instance.

    --
    Apocalypse Cancelled, Sorry, No Ticket Refunds
  60. Notice of Infringement by Anonymous Coward · · Score: 0

    Dear Slashdot Editors

    It has come to my attention that you have been infringing my patent "Using More Acronyms Than Ordinary Words in an Online Summary". Please remove the infringing material from your site or contact me about the purchase of a license.

    Sincerely

    AC

  61. Re:Patent Troll by budgenator · · Score: 1

    Linus didn't trademark it;

    The Linux trademark is owned by Linus Torvalds in the U.S., Germany, the European Community, and Japan. In the U.S., the mark is registered (Serial Number: 74560867)[1] for "Computer operating system software to facilitate computer use and operation." The assignment of the trademark to Torvalds occurred after an attorney, one William R. Della Croce, Jr, in 1996 began sending letters to various Linux distributors claiming to own the Linux trademark and demanding royalties. The distributors rapidly pooled resources, appealed against the original trademark assignment and had it reassigned to Linus Torvalds. Linux Mark Institute

    it was trademarked by a trademark troll. Fortunately it was wrested from him and given to Linus.

    --
    Apocalypse Cancelled, Sorry, No Ticket Refunds
  62. They came for SOAP... by istartedi · · Score: 0, Redundant

    They came for SOAP and I said nothing, because it was a bloated ugly PoS.

    Then they cam for XML and I said nothing because I prefer JSON.

    Then they came for JSON and I said nothing because they gave me a bonus.

    Then they came for Linux and I said nothing because I was able to retire on that bonus and no longer cared about IT.

    Then I had a mild heart attack and on the way to the hospital Microsoft's MyShock defibrelator control software crashed.

    --
    For all intensive purposes, "whom" is no longer a word. That begs the question, "who cares"?
  63. Re:Patent Troll by pmarini · · Score: 1

    unless a patent troll(er) comes and sniffs the idea as its own... maybe in Texas ?

    --
    Can I put a spell on those who can't spell?
    Your wheels are loose and they're losing their grip, good you're there.
  64. Remoteable powershell pipelines by Anonymous Coward · · Score: 0

    A pipeline of (.NET remoted) powershell services that outputs XML would probably violate this patent. Since that was conceived of years ago, I find it hard to believe this patent it valid.

  65. Re:Patent Troll by Anonymous Coward · · Score: 0

    You don't need a patent for that just prior art in the wild

    With prior art as your defense, the onus is on you to prove that the prior art invalidates the challenged patent. Patents, on the other hand, are presumed valid after they have been granted by the patent office.

    IANAL though.

  66. It's an innovation patent! by reiisi · · Score: 1

    Eight years is still a long time, but much better than twenty. And they say you can require an examination before the patent owner comes after you with it. I didn't know Australia was doing that.

    So, yeah, it was granted, but it could never have been used in adversarial action without an examination first, and it appears it would expire this year.

    --
    Computer memory is just fancy paper, CPUs just fancy pens with fancy erasers; the 'net is just a fancy backyard fence.
  67. I think you're (deliberately?) over-reacting by reiisi · · Score: 1

    It's hard to provide a covenant to protect people who haven't entered into a covenant with you. Only God can do that, and His protection is not what you seem to think protection is.

    Besides, this kind of patent is valuable only as a part of a big bundle of patents to drop on the table in front of Microsoft when they bring their big bundle of the same kind of patents and try to scare you with them. Everybody around the table knows that these patents would disappear in a brief six months or so, if challenged, but the act of challenging invites the challenge. It's for inducing the 800 pound gorilla to think twice before they try abusing the courts.

    --
    Computer memory is just fancy paper, CPUs just fancy pens with fancy erasers; the 'net is just a fancy backyard fence.
  68. misrepresentation by speedtux · · Score: 1

    If RedHat wanted to build a useful patent portfolio to protect open source, this is not the way to do it. Instead, they should create a separate foundation with a charter that would allow its patent portfolio to be used only in case Red Hat (or other open source developers) are being sued.

    The way it is set up right now, if Microsoft or Apple buys Red Hat, all of RedHat's promises go out the window. In fact, RedHat itself can change its mind if it feels wronged by some other open source project.

    RedHat's promise is worthless, and I think it's likely made in bad faith (i.e., RedHat knows that it's wortheless).

  69. big holes by speedtux · · Score: 1

    First of all, that's just a "promise"; they can change that whenever they want and it's not enforceable.

    Second, they don't even list the Apache license as one of their "approved" licenses; under their definition of "open source", Apache is not an open source project.

    If they want to have credibility on this, they need to do a whole lot better.