I think you are worrying too much about names of things.
Of course it is important that names are sort of self-documenting, but if you want the names to be documentative of every possible aspect related to the things they name (semantics of the content is typically an important one, specification of the "logical" structure, if any, is often another important one, specification of the "physical" approach is often also a useful one), then they will typically become way too long. CustomerListRestrictedToProvinceOrderedByStreetThenHousenum and the like.
I also have the impression you are already mixing the three too much.
E.g. "KeyValue" refers to a "logical" organization in which information is organized in key-value pairs. "CSV" invokes notions a reference to the physical way of storing. "SQLStatement" is at the same level (sibling) as "CSV", but an SQL statement is clearly a whole different kind of beast than "CSV", seeing as an SQL statement is most certainly not also a physical way of storing things ...
Received on Fri Mar 21 2014 - 08:18:20 CET
