> Part of the reason, I believe, is because those "conventions" are not carved > in stone. There often isn't a hard and fast convention that says when to > make a profile or when to make a module or when to use a classifier to store > a second artifact alongside the primary
And over time these conventions (or philosophies) change as we gain more experience. There is stuff you can do in profiles that is considered exceptionally bad practice. There is some move at apache to get the web sites onto some CMS system. I really don't know the details. I think at the moment it can be backed by SVN. This may make it easier for people to make changes without having to checkout the website first, etc. So the barrier to creating some of this great advice may become lower. I think another reason that the information isn't available is that people don't recognise what is wrong with their mental model and when they have that "aha" moment can no longer articulate how they went from the wrong to correct mental model to explain to other people. And there is less incentive to do so because they "know it now". You only have to look at all the threads on the internet that have a question, answers from other people, and either no response from the original poster to say whether they worked or they reply with "thanks, works now" with no bloody details! I know that in six months time I will eventually be revisiting this piece of knowledge so I try to ensure it gets put back on the internet somewhere for google to find. Because I can guarantee I will be searching for it again at some later point. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
