component nbt paths require 'minecraft:' prefix on keys

I'm finding that, at least in some cases, nbt paths can require "minecraft:" prefixes inside component entities. Specifically I've run into this with armor trim materials. Given a helmet with trim on an armor stand, the command:

/data get entity 850955d7-2f3a-4185-9a91-7f011003d9d2 ArmorItems[0].components.trim

gives the error

Found no elements matching ArmorItems[0].components.trim

while the command

/data get entity 850955d7-2f3a-4185-9a91-7f011003d9d2 ArmorItems[0].components.minecraft:trim

succeeds, giving the trim material.

No other part of the nbt path requires the prefix, so this seems like a problem.