Yep. There are shortcomings on Poser's side. They should make it a open source project for Poser 8. :tt2:

Back to filenames or product naming. I don't know why someone want his name in the filepath or visible in the application (i.e. Poser) if the ReadMe contains it already.
At first, when I had very few products, I used to keep the files in the order they came from marketplaces.
E.g.: ":Poser nRuntimeLibrariesCharacter"

That was not a big problem because there were 1) few products and 2) few vendors at all. Now there are products of hundreds of vendors and this system is confusing. A good solution would have both, the new Poser user and the long time Poser user, in mind.

Example of the structure of some of the products I have installed:
"..ReadMe's"
"..RuntimeGeometries"
"..RuntimeLibrariesV3Body"
"..RuntimeLibrariesCharacter"
"..RuntimeLibrariesPose"
"..RuntimeTexturesCharacter"
"..RuntimeTexturesCloths"
"..RuntimeTexturesClothsTemplates"

If there are let's say 20+ products of one single vendor then it makes sense to place them in one folder with the vendor name.
But that is rarely the case. Reality is that there are many many folders with vendor names and very few peoducts in them.
Often it's only 1 product.

"..RuntimeLibrariesV3Body"
That makes not much sense for example. There are only some .pz2 files in that folder.
The reason for the "!" and the reason for the location of this folder I can not see.

"..RuntimeLibrariesPose"
Sure, I expect poses in "..Pose" and not in "..Geometry" or "..Python". Needless to name the folder and needless to place that ! there. The word "Poses" I won't even see in Poser's library palette because the product name is so long already.

"..RuntimeTexturesCloths"
"..RuntimeTexturesClothsTemplates"
This is good. In the texture folder it makes sense to gather all textures per vendor.
The templates however can be located in one templates folder.
"..RuntimeTexturesTemplatesCloths" looks better and makes finding templates easier because if one looks for templates, he will look for some folder called "Templates" and for the vendor maybe after this.

"..RuntimeLibrariesCharacter"
This one is good too. If one installs a single product it's quickly to reorganize this structure.

In the case of "..RuntimeLibrariesCharacter" one quartal later the user won't know anymore what the single vendor-named folders contain.

For giving credit it can be helpful if there's a dummy file with the vendor name along with the pose files. Hair colors for example or any other stuff. It's more useful than placing the vendor name in the file path because it is visible if the library palette is opened to load the mat pose or the mesh.

For the hierarchy is to add: Below "Geometry" comes the geometry. - Similar to the case of "Template".
A geometry could be clothes, hair, props. These are broken down logically.
Clothes can be
"..GeometryClothesMenShoes"
"..GeometryClothesWomenShoes"

And so on.
Fantasy clothing also belongs to some real world category. Plate, leather, chain, scale armors belong to Armor etc...
Some magic wand belong to primitives --> cylindrical --> staves --> wands. - Or whatever. Have a look at what gaming industry does.

Real world industry gives some good example patterns for clothes and other stuff like houses, furniture, vehicles.
Hair can be sorted by it's default style, props can be sorted by their function.
A house would be somewhere around "..GeometryPropsdwellings"

From elementary particles up to stars and galaxy clusters everything can be classified and sorted.
If one creates a whole new universe the real world may fail to serve with some sorting pattern. In this special case it's ok to place the universe in whatever folder you want. As long as it sticks to Poser's file system.