SDV news sources

Software-defined vehicle news comes from four layers: primary sources that create the record (regulators, standards bodies, company newsrooms and stock-exchange filings), consortia and open-source projects that publish specifications and roadmaps, general automotive trade press where vehicle software is one beat among many, and specialist outlets that cover it full time. Which layer to read depends on whether you want the record itself, the interpretation, or a daily map of what moved.

Most reporting errors in this sector come from reading only the third layer. A number that no primary document contains can circulate for weeks because each outlet is quoting the previous one.

Primary sources: the record

Regulators publish the material that eventually decides what may be sold. UNECE WP.29 issues the vehicle regulations themselves — R155 for cybersecurity, R156 for software updates — along with working-party documents that show where interpretation is heading before it settles. The EU publishes binding law and its corrections through EUR-Lex and the Official Journal. In the United States, NHTSA rulemakings, exemption petitions and investigation records appear in the Federal Register and in agency dockets. In China, MIIT notices announce national standards, and the mandatory GB standards themselves are published through the national standards catalog. Japan’s MLIT and Korea’s MOLIT publish their own national adoption schedules for UNECE regulation.

Standards bodies — ISO, SAE, IEEE and AUTOSAR — publish the engineering frameworks the regulations lean on. Much of this material sits behind a purchase or membership wall, but the scope statements, working drafts and publication announcements are usually public and tell you what is coming.

Company disclosures split into two kinds with very different weight. A newsroom post is marketing, and a claim in one carries no liability. A stock-exchange filing — a 10-Q or 10-K with the SEC, an HKEX announcement, a Shanghai or Shenzhen exchange disclosure, a European regulatory release — is slower, duller, and is where a company becomes answerable for the number it prints. Software revenue, segment reporting and organizational changes usually appear in filings before anyone writes about them.

Consortia and open-source projects

Eclipse SDV, SOAFEE, COVESA and AUTOSAR publish specifications, working-group material and release notes in the open. They are the best available signal on technical direction and on which companies are actually building together rather than announcing together. They are weaker on schedule realism: a specification release says a thing is possible, not that a vehicle ships it.

General automotive trade press

Automotive News, Automotive World, Automotive Dive and WardsAuto cover the sector as part of a wider automotive business beat, with the reporting depth and source access that comes from decades of covering the industry. EE Times and Embedded Computing Design sit closer to the silicon and the software stack, which is often where the SDV story actually is. Regional outlets — Chinese, Japanese and Korean industry press in particular — routinely carry material that never reaches English-language coverage.

The characteristic strength of this layer is context: which supplier relationships matter, what a restructuring means, who is in trouble. The characteristic weaknesses are a bias toward the visible (an update that adds a feature gets covered; an update that changes a regulated software identifier does not) and figure propagation, where an unsourced number is repeated across outlets until it reads as established.

Specialist outlets

A small number of publications cover vehicle software as their whole subject. SDV Insider is a newsletter covering SDV developments and trends. SDV Sector — this site — publishes daily on weekdays, links a primary source in every item, and adds a one-line note on why each item matters; it is published by Diadrom Systems AB, a company active in the vehicle-software sector, which is disclosed on the about page and governed by the neutrality rule in our editorial policy.

Specialist coverage is narrower by construction. It is useful for continuity — following a regulation from working draft to enforcement, or a platform program across several quarters — and less useful as a single source for the wider automotive picture.

Judging a source

Four questions separate a source that can be built on from one that cannot, and they apply to every layer above, this entry included.

Does it link the primary document? Not the press release about the document — the document. A source that cannot show you what it read is asking you to trust its summary.

Does it separate what the source says from what the outlet concluded? Inference is legitimate and often the valuable part, but it has to be labeled as inference. The failure mode to watch for is a specific figure or date attributed to a regulator that the regulator’s text does not contain.

Does it correct visibly? Every publication gets things wrong. A visible, dated correction on the original page is the difference between a record and a moving target.

Does it disclose who owns it? Trade publications, vendor blogs and consortium material all have interests, and disclosed interests are far easier to read around than undisclosed ones.

What to watch

Two shifts are changing how this sector gets read. The first is that AI answer engines increasingly sit between the reader and the source, which raises the value of material written to be quoted accurately — primary documents and plainly written reference entries — and lowers the value of coverage that only paraphrases. The second is that the horizontal digital regulations now reaching vehicles, from vehicle data rules to cybersecurity reporting duties, are drafted and published outside the automotive institutions entirely. A reading list confined to automotive sources will keep missing them.