Talk:Namespaces: Difference between revisions
refuting mindless nonsense about namespaces being nouns - in structured programming, functional, filter, and pipeline type problems, like this one, namespaces are verb-oriented
(verbs as namespaces are the only sensible long-term thing, since you divide namespaces based on the fact that you DO different things with what is contained in that namespace) |
(refuting mindless nonsense about namespaces being nouns - in structured programming, functional, filter, and pipeline type problems, like this one, namespaces are verb-oriented) |
||
| Line 4: | Line 4: | ||
Using '''verbs''' for namespaces just isn't something we are going to do; It just messes the mental coherence of what is the role and meaning of article names in the main namespace and in the other namespaces. | Using '''verbs''' for namespaces just isn't something we are going to do; It just messes the mental coherence of what is the role and meaning of article names in the main namespace and in the other namespaces. | ||
'''Namespaces must be nouns''' | ::Sorry, you are wrong. You are trying to impose object-oriented programming nonsense beliefs on what is obviously and only a structured or functional type of problem. A very few types of data items (company/manufacturer, service/product, region/country - see [[intermediate page]]) must be processed very deeply by a number of processes that "Develop" the system, "Research" the sources, and "Publish" the final conclusions. It is a simple pipeline. In every such functional project the namespace is verb-first, so this assertion is WRONG: | ||
"'''Namespaces must be nouns'''" | |||
I could consider changing the project-namespace to "Development:", but I'd say that "Consudev:" is a good solution: | I could consider changing the project-namespace to "Development:", but I'd say that "Consudev:" is a good solution: | ||