Context Navigation

Changes between Initial Version and Version 1 of Ticket #924, comment 1

initial	v1
4	4	* Every CROWD member must also be a DeepaMehta member. The Events could stay in the DeepaMehta workspace then.
5	5	* The CROWD module reassigns the Event standard type (as well as Person and Institution) to the CROWD workspace. Created events would land in the CROWD workspace then. I don't like this approach as the CROWD module could rely on other modules which also might want to reassign the types. This could produce a conflict situation.
6		* Melt the DeepaMehta and CROWD workspaces down into one workspace, that is, in the CROWD module would rename the "DeepaMehta" workspace to "CROWD".
	6	* Melt the DeepaMehta and CROWD workspaces down into one workspace, that is, the CROWD module would rename the "DeepaMehta" workspace to "CROWD".
7	7	I don't like this approach for 2 reasons:
8	8	1. in the face of the related (and still to be realized) concept of a "Home" workspace (see #371) the CROWD types (Work, Translation, Event Series, Entrance Fee, ...) must get a "dm4" URI prefix then despite this prefix is reserved for the DM standard types. At the moment "DM standard type" means "part of the DM Standard Distro".