Language Selection

English French German Italian Portuguese Spanish

Devil's Advocate: M$ foolish patent policy

Filed under
Microsoft

Is it really true that Microsoft has patented the transformation of objects into XML? That would certainly be proof, if proof were needed, that so-called intellectual property has little to do with innovation.

Software objects involve ingenious ideas that have had growing attraction. The concepts were always sound, and they were all invented before Microsoft even existed. But their use was limited because applications were restricted in scope and computer power was scarce. As those factors changed, so objects became far more central to computing.

Likewise, although XML itself is a relatively recent phenomenon, it is based on SGML. And SGML was also invented long before the foundation of Microsoft. Again, it was a question of timing, as the tantalising goal of building self-describing data looked to be achievable with rising hardware capabilities.

It is reported that Microsoft has now achieved a patent on the transformation of objects to XML and vice versa. This is a pretty bizarre thing to happen. As an industry analyst, I became aware of XML as soon as it started to make waves. My immediate reaction was that XML documents were objects without the behaviour.

Now that was hardly an astonishing insight. I would never have expected to rush off and patent it, even if I could afford to patent anything. It was an insight that was common to anyone who had at least half an understanding of both objects and XML. I must have discussed the point with numerous people, and most likely spoken about it at public conferences. If it is a patentable idea, then the whole patents system is demonstrably absurd.

If large companies are to be granted patents on ideas that have been commonplace for years and are based on fundamental concepts well understood for decades, they might as well be given taxation powers. The idea that their revenues are hard won in competitive markets will be defunct, if it is not already.

The reality is probably just a little more complex.

Full Article.

More in Tux Machines

Leftovers: OSS

Security Leftovers

  • Security updates for Thursday
  • OpenSSL patches two high-severity flaws
    OpenSSL has released versions 1.0.2h and 1.0.1t of its open source cryptographic library, fixing multiple security vulnerabilities that can lead to traffic being decrypted, denial-of-service attacks, and arbitrary code execution. One of the high-severity vulnerabilities is actually a hybrid of two low-risk bugs and can cause OpenSSL to crash.
  • Linux Foundation Advances Security Efforts via Badging Program
    The Linux Foundation Core Infrastructure Initiative's badging program matures, as the first projects to achieve security badges are announced.
  • Linux Foundation tackles open source security with new badge program
  • WordPress Plugin ‘Ninja Forms’ Security Vulnerability
    FOSS Force has just learned from Wordfence, a security company that focuses on the open source WordPress content management platform, that a popular plugin used by over 500,000 sites, Ninja Forms, contains serious security vulnerabilities.
  • Preparing Your Network for the IoT Revolution
    While there is no denying that IP-based connectivity continues to become more and more pervasive, this is not a fundamentally new thing. What is new is the target audience is changing and connectivity is becoming much more personal. It’s no longer limited to high end technology consumers (watches and drones) but rather, it is showing up in nearly everything from children’s toys to kitchen appliances (yes again) and media devices. The purchasers of these new technology-enabled products are far from security experts, or even security aware. Their primary purchasing requirements are ease of use.
  • regarding embargoes
    Yesterday I jumped the gun committing some patches to LibreSSL. We receive advance copies of the advisory and patches so that when the new OpenSSL ships, we’re ready to ship as well. Between the time we receive advance notice and the public release, we’re supposed to keep this information confidential. This is the embargo. During the embargo time we get patches lined up and a source tree for each cvs branch in a precommit state. Then we wait with our fingers on the trigger. What happened yesterday was I woke up to a couple OpenBSD developers talking about the EBCDIC CVE. Oh, it’s public already? Check the OpenSSL git repo and sure enough, there are a bunch of commits for embargoed issues. Pull the trigger! Pull the trigger! Launch the missiles! Alas, we didn’t look closely enough at the exact issues fixed and had missed the fact that only low severity issues had been made public. The high severity issues were still secret. We were too hasty.
  • Medical Equipment Crashes During Heart Procedure Because of Antivirus Scan [Ed: Windows]
    A critical medical equipment crashed during a heart procedure due to a timely scan triggered by the antivirus software installed on the PC to which the said device was sending data for logging and monitoring.
  • Hotel sector faces cybercrime surge as data breaches start to bite
    Since 2014, things have become a lot more serious with a cross section of mostly US hotels suffering major breaches during Point-of-Sale (POS) terminals. Panda Security lists a string of attacks on big brands including on Trump Hotels, Hilton Worldwide, Hyatt, Starwood, Rosen Hotels & Resorts as well two separate attacks on hotel management outfit White Lodging and another on non-US hotel Mandarin Oriental.

Android Leftovers

today's howtos