Hey,
You cannot put all the stuff in one namespace; how would you then know what
it actually is? For example properties show a list of pages on which they
are used (plus the value they have there). This information would need to be
represented in another way if it all was in a single namespace. The current
approach makes it very obvious what the thing is, a property, type or
something else. Also, it avoids naming conflicts. I honestly don't see why
you'd put everything in a single ns, it seems it'd only cause issues and not
provide any benefits.
Cheers
--
Jeroen De Dauw
http://www.bn2vs.com
Don't panic. Don't be evil.
--
------------------------------------------------------------------------------
Benefiting from Server Virtualization: Beyond Initial Workload
Consolidation -- Increasing the use of server virtualization is a top
priority.Virtualization can reduce costs, simplify management, and improve
application availability and disaster protection. Learn more about boosting
the value of server virtualization. http://p.sf.net/sfu/vmware-sfdev2dev
_______________________________________________
Semediawiki-devel mailing list
Semediawiki-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/semediawiki-devel
