Here's my rough criteria when selecting applicants for technology roles: 1) What have you done lately that is like what I want you to do? 2) What is your attitude like? (past references very important here) 3) Have you taken some test or certification (or can we give you one) that demonstrates skills in areas we might be concerned about? From there, perhaps you can start learning , that is, it might be worthwhile to…
I freely admit that we apprenticeship supporters wave our hands around a lot while yelling "apprenticeships! apprenticeships!" without providing necessary detail. A lot of those details could be worked out along the way. I'd be more excited to see the supporters provide actual apprentice programs than details on how everyone should operate such a program.
The last thing we need is folks going to their dictionaries and starting to create or use formal definitions for all of this. That kind of rigidity is what got us here in the first place.
Much better to adopt a general definition consisting of "in situ" and "rapid feedback" and then try a million experiments to see what gains traction. Theory is easy. Application is difficult. We need much more application and much less theory.