Hi Michael, Understand what you are saying but I see an object name as one data type or field and a tag is another.
I see a tag as a flagging tool. Doesnt need hierarchy but can be set up that way if required with multiple "tags"

Example: users could select 100objects, add tag "assembly item 001" or "assembly item"+ "job001"later these tags could be used to find and put items into a drawing. The idea likely came when I was exploring the customui and I thought those library objects or menu could soon get too busy, personally I dont like using "explorer". Likewise I might consider creating comprehensive parts that should be able to be pulled into a moi design fast and easy - these items are likely 'reusable' or standard.