Standards/Consortia: OpenDocument Format (ODF), HTTP, EU's New Radio Equipment Directive, and More

posted by Roy Schestowitz on Aug 09, 2025

• Document Foundation ☛ Best practices for creating and editing OpenDocument Format (ODF) files

  Adhering to these guidelines can enhance productivity and guarantee that documents remain consistent, robust and accessible over time, irrespective of the platform. Firstly, use an editor such as LibreOffice that natively supports the format without conversion.

• Daniel Stenberg ☛ HTTP is not simple

  I don’t believe anyone has tried to claim that HTTP/2 or HTTP/3 are simple. In order to properly implement version two or three, you pretty much have to also implement version one so in that regard they are accumulating complexity and bring quite a lot of extra challenges in their own respective specifications.

  Let me elaborate on some aspects of the HTTP/1 protocol that make me say it is not simple.

• Raspberry Pi ☛ Navigating the EU's new Radio Equipment Directive: how Raspberry Pi provides an industrial advantage

  The EU Radio Equipment Directive (2014/53/EU) ensures that all radio-enabled equipment sold in Europe meets essential requirements for safety, electromagnetic compatibility (EMC), and spectrum usage, and its provisions will be familiar to many manufacturers. However, a recent Delegated Act (2022/30/EU) expands this framework. It includes three new essential cybersecurity requirements for all internet-connected radio equipment, including industrial devices: [...]

• The Record ☛ CISA pledges to continue backing CVE Program after April funding fiasco

  At the Black Hat cybersecurity conference in Las Vegas, two leaders from the Cybersecurity and Infrastructure Security Agency (CISA) were asked about the CVE Program’s future — which was thrown into doubt amid a flurry of high-profile cybersecurity contract cancellations following President Donald Trump’s inauguration.

• University of Toronto ☛ Abuse systems should handle email reports that use MIME message/rfc822 parts

  I think it's perfectly fine and maybe even praiseworthy when email abuse handling systems (and people) are willing to accept these literal plaintext format forwarded spam messages. The more formats you accept abuse reports in, the better. But every abuse handling system should accept MIME message/rfc822 format messages too, as a minimum thing. Not just because it's a standard, but also because it's what a certain amount of mail clients will produce by default if you ask them to forward a message. If you refuse to accept these messages, you're reducing the amount of abuse reports you'll accept, for arbitrary (but of course ostensibly convenient for you) reasons.