05.25.21

Gemini version available ♊︎

USPTO Promotes Microsoft Monopoly and Proprietary Software (Updatedx2)

Posted in Microsoft, Open XML, Patents at 11:59 am by Dr. Roy Schestowitz

Related: USPTO Rewards Microsoft for Corruption at ISO by Teaching People Proprietary OOXML and Promoting Its Use | USPTO Craziness: Changing Rules to Punish PTAB Petitioners and Reward Microsoft for Corruption at ISO | Conflict of Interest: Microsoft and IBM Controlling the USPTO and Leaving GNU/Linux Users Shut Out (in the Cold) | Why Wouldn’t an Office That Grants Monopolies Support Microsoft Monopoly?

Director's Forum: A Blog from USPTO's Leadership
“Modernizing” as in adding vendor lock-in and pushing proprietary dependencies

Summary: Classic example of vendor capture; Microsoft engaged in endless and well-documented corruption to push OOXML and now the U.S. Patent and Trademark Office (USPTO) participates in this marketing propaganda; moreover it financially penalises people who don’t use Microsoft’s proprietary formats; this is certainly what Microsoft lobbied for. “Just got this from the USPTO,” a reader told us about this new E-mail and Web page (promoted via E-mail). “I’m not too savvy on this DOCX stuff, but I notice the word “surcharge,” and I guess they’ve figured out another way to scam fees from Linux users.” Similarly, the EPO was illegally outsourced to Microsoft. They infiltrate and take over patent offices, just like that.

Update: Someone has written a summary about this:

There are still a few months to fix this, but for now the US Patent and Trademark Office’s (USPTO) Acting Commissioner for Patents, Andrew Faile, and Chief Information Officer, Jamie Holcombe, have announced that starting January 1st, 2022, the USPTO will institute a surcharge for applicants that are not locked into Microsoft products via the proprietary DOCX format. From that date onwards, the USPTO will move away from PDF and require all filers to use that proprietary format or face an arbitrary surcharge when filing.

First, we delayed the effective date for the non-DOCX surcharge fee to January 1, 2022, to provide more time for applicants to transition to this new process, and for the USPTO to continue our outreach efforts and address customer concerns. We’ve also made office actions available in DOCX and XML formats and further enhanced DOCX features, including accepting DOCX for drawings in addition to the specification, claims, and abstract for certain applications.

One out of several major problems with the plans is that DOCX is a proprietary format. There are several variants of DOCX and each of them are really only supported by a single company’s products. Some other products have had progress in beginning to reverse engineering it, but are hindered by the lack of documentation. DOCX is a competitor to the fully-documented, open standard OpenDocument Format, also known as ISO/IEC 26300.

DOCX is not to be confused with OOXML, though it often is. While OOXML, also known as ISO/IEC 29500, is technically standardized, it is incompletely documented and only vaguely related to DOCX. The DOCX format itself is neither fully documented nor standard. So the USPTO is also engaged in spreading disinformation by asserting that it is.

Previously:
(2015) Microsoft Threatened the UK Over Open Standards


Original Submission

Update #2: This controversy has reached more mainstream media. E.g.:

  • US Patent Office to take only DOCX in future – or PDFs if you pay extra

    Documents submitted to the US Patent and Trademark Office should be in .DOCX format starting from next year – and if you want to stick to PDFs, that will cost extra.

    “At the USPTO, we are continuously working to modernize and streamline our patent application systems,” the agency announced this week. “To improve application quality and efficiency, the USPTO will be transitioning to DOCX for all filers on January 1, 2022.”

    The office said it decided to make the change years ago in an attempt to streamline the patent examining process. DOCX, otherwise known as Office Open XML, is standardized as ECMA-376 and ISO/IEC 29500. Though it was created by Microsoft for its own products, such as Word, the file format is supported by LibreOffice, OpenOffice, Google Docs, and others. And though the Windows giant has sworn it won’t sue over licensing and patents regarding DOCX, there are some caveats.

Two years ago someone warned about it:

  • The problem with USPTO’s proposed non-DOCX penalty

    Until now, it has been optional for a practitioner to file a US patent application in DOCX format rather than in PDF format. But USPTO now proposes to charge a $400 penalty for filing a patent application in non-DOCX format. This is a very bad idea, for reasons that I will discuss in detail. Only if USPTO were to make fundamental changes in its way of receiving DOCX files would it be acceptable for USPTO to impose a penalty for filing in a non-DOCX format.

    USPTO needs to follow WIPO’s example, permitting the practitioner to file a “pre-conversion format” version of a patent application along with the DOCX file. In the event of some later problem with USPTO’s rendering of the DOCX file, the practitioner would be permitted to point to the pre-conversion format, which would control in the event of any discrepancy.

    The normal way to file US patent applications is in PDF format. With PDF format, the applicant has complete control over the appearance of characters and symbols.

    Some years ago, the USPTO began beta-testing a system that would permit a practitioner to file a patent application in DOCX format instead of in PDF format. Yours truly was among the very first of the beta-testers of USPTO’s system for DOCX filings. As implemented by the USPTO, the practitioner would upload a DOCX file, and USPTO would render the DOCX file in a human-readable PDF image format. As part of the e-filing process, the practitioner was expected to proofread the rendered image as provided by the USPTO’s e-filing system. The notion was that the practitioner would be obliged to catch any instances of USPTO’s system rendering the DOCX file differently from the way the practitioner’s word processor had rendered that same DOCX file. If, for example, some math equation or chemical formula had gotten corrupted in USPTO’s system, the practitioner would expected to catch this prior to clicking “submit”.

This ‘Microsoft tax’ was discussed months ago by litigation giants:

microsoft-tax

Share in other sites/networks: These icons link to social bookmarking sites where readers can share and discover new web pages.
  • Reddit
  • email

Decor ᶃ Gemini Space

Below is a Web proxy. We recommend getting a Gemini client/browser.

Black/white/grey bullet button This post is also available in Gemini over at this address (requires a Gemini client/browser to open).

Decor ✐ Cross-references

Black/white/grey bullet button Pages that cross-reference this one, if any exist, are listed below or will be listed below over time.

Decor ▢ Respond and Discuss

Black/white/grey bullet button If you liked this post, consider subscribing to the RSS feed or join us now at the IRC channels.

DecorWhat Else is New


  1. 2023 is the Year Taxpayers' Money Goes to War and Energy Subsidies, Not Tech

    Now that a lot of powerful and omnipresent ‘tech’ (spying and policing) companies are rotting away we have golden opportunities to bring about positive change and maybe even recruit technical people for good causes



  2. Getting Back to Productive Computer Systems Would Benefit Public Health and Not Just Boost Productivity

    “Smartphoneshame” (shaming an unhealthy culture of obsession with “apps”) would potentially bring about a better, more sociable society with fewer mental health crises and higher productivity levels



  3. Links 04/02/2023: This Week in KDE and Many More Tech Layoffs

    Links for the day



  4. Dotcom Boom and Bust, Round 2

    The age of technology giants/monopolies devouring everything or military-funded (i.e. taxpayers-subsidised) surveillance/censorship tentacles, in effect privatised eyes of the state, may be ending; the United States can barely sustain that anymore and raising the debt ceiling won't solve that (buying time isn't the solution)



  5. Society Would Benefit From a Smartphoneshame Movement

    In a society plagued by blackmail, surveillance and frivolous lawsuits it is important to reconsider the notion of “smart” phone ownership; these devices give potentially authoritarian companies and governments far too much power over people (in the EU they want to introduce new legislation that would, in effect, ban Free software if it enables true privacy)



  6. IRC Proceedings: Friday, February 03, 2023

    IRC logs for Friday, February 03, 2023



  7. IRC Proceedings: Thursday, February 02, 2023

    IRC logs for Thursday, February 02, 2023



  8. Links 03/02/2023: Proton 7.0-6 Released, ScummVM 2.7 Testing

    Links for the day



  9. Links 03/02/2023: OpenSSH 9.2 and OBS Studio 29.0.1

    Links for the day



  10. Links 03/02/2023: GNU C Library 2.37

    Links for the day



  11. Sirius Finished

    Yesterday I was sent a letter approving my resignation from Sirius ‘Open Source’, two months after I had already announced that I was resigning with immediate effect; they sent an identical letter to my wife (this time, unlike before, they remembered to also change the names!!)



  12. The Collapse of Sirius in a Nutshell: How to Identify the Symptoms and Decide When to Leave

    Sirius is finished, but it's important to share the lessons learned with other people; there might be other "pretenders" out there and they need to be abandoned



  13. Links 03/02/2023: WINE 8.1 and RapidDisk 9.0.0

    Links for the day



  14. Links 02/02/2023: KDE Gear 22.12.2 and LibreOffice 7.5

    Links for the day



  15. Linux News or Marketing Platform?

    Ads everywhere: Phoronix puts them at the top, bottom, navigation bar, left, and right just to read some Microsoft junk (puff pieces about something that nobody other than Microsoft even uses); in addition there are pop-ups asking for consent to send visitors’ data to hundreds of data brokers



  16. Daily Links at Techrights Turn 15, Time to Give Them an Upgrade

    This year we have several 15-year anniversaries; one of them is Daily Links (it turned 15 earlier this week) and we've been working to improve these batches of links, making them a lot more extensive and somewhat better structured/clustered



  17. Back to Focusing on Unified Patent Court (UPC) Crimes and Illegal Patent Agenda, Including the EPO's

    The EPO's (European Patent Office, Europe's second-largest institution) violations of constitutions, laws and so on merit more coverage, seeing that what's left of the "media" not only fails to cover scandalous things but is actively cheering for criminals (in exchange for money)



  18. European Patent Office Staff Votes in Favour of Freedom of Association (97% of Voters in Support)

    The Central Staff Committee (CSC) at the EPO makes a strong case for António Campinos to stop breaking and law and actually start obeying court orders (he’s no better than Benoît Battistelli and he uses worse language already)



  19. Links 02/02/2023: Glibc 2.37 and Go 1.20

    Links for the day



  20. IRC Proceedings: Wednesday, February 01, 2023

    IRC logs for Wednesday, February 01, 2023



  21. Links 01/02/2023: Security Problems, Unrest, and More

    Links for the day



  22. Links 01/02/2023: Stables Kernels and Upcoming COSMIC From System76

    Links for the day



  23. IRC Proceedings: Tuesday, January 31, 2023

    IRC logs for Tuesday, January 31, 2023



  24. Links 31/01/2023: Catchup Again, Wayland in Xfce 4.20

    Links for the day



  25. Links 31/01/2023: elementary OS 7

    Links for the day



  26. Intimidation Against Nitrux Development Team Upsets the Community and Makes the Media Less Trustworthy

    Nitrux is being criticised for being “very unappealing”; but a look behind the scenes reveals an angry reviewer (habitual mouthpiece of the Linux Foundation and Linux foes) trying to intimidate Nitrux developers, who are unpaid volunteers rather than “corporate” developers



  27. Links 31/01/2023: GNOME 44 Wallpapers and Alpha

    Links for the day



  28. Free and Open Source Software Developers' European Meeting (FOSDEM) and KU Leuven Boosting Americans and Cancellers of the Father of Free Software

    The Free Software Foundation (FSF) and its founder, Richard M. Stallman (RMS), along with the SFLC one might add, have been under a siege by the trademark-abusing FSFE and SFC; Belgium helps legitimise the ‘fakes’



  29. Techrights in the Next 5 or 10 Years

    Now that I’m free from the shackles of a company (it deteriorated a lot after grabbing Gates Foundation money under an NDA) the site Techrights can flourish and become more active



  30. 60 Days of Articles About Sirius 'Open Source' and the Long Road Ahead

    The Sirius ‘Open Source’ series ended after 60 days (parts published every day except the day my SSD died completely and very suddenly); the video above explains what’s to come and what lessons can be learned from the 21-year collective experience (my wife and I; work periods combined) in a company that still claims, in vain, to be “Open Source”


RSS 64x64RSS Feed: subscribe to the RSS feed for regular updates

Home iconSite Wiki: You can improve this site by helping the extension of the site's content

Home iconSite Home: Background about the site and some key features in the front page

Chat iconIRC Channel: Come and chat with us in real time

Recent Posts