"File types"

So, it seems like the only reason to have that attribute *visible* is because you want your directory listing (graphical or otherwise) to be able to differentiate between the N different "Skiing" files that you might have (in that particular container). I.e. so that you could "select" (e.g., "click") the one that you are interested in. Wouldn't, instead, a better (?) scheme be to show/list all "Skiing" files as a single item and, when selected, prompt the user for which *aspect* of "Skiing" he was interested in (i.e. "Do you want to view the photo, see the expense summary or read the invitation?"). Note that this (above) is predicated on the assumption that you would *allow* name collisions (overloading based on the file name) and resolve them some other way. If this isn't allowed, then there would be no ambiguity and the user would be free to pick what he/she wants to call the file without someone imposing an artificial "file type" as part of the namespace.