Context Navigation

MultipleProject

-              v2
+              v3
 The next step is therefore to provide the ability to group different Trac projects inside a single environment, so that the resources from one project become fully addressable from other projects or from a global level.
+The main concept is that of a project identifier being attached to each resource, which provides an additional scope for the resource identifiers, in addition to the realm.
+== The Data Model == #DataModel
+The main idea is to attach a project identifier to each resource.
+This can be achieved either by using an extra `.project` field for each resource or by parenting the resources in a project resource.
+The second way is probably better, as some resources might be project independent (like the Changeset and Source which belong to a given repository - see MultiRepos).
 The empty string `''` could be used to qualify the toplevel project, which is always there. If no other project has been defined, then Trac behaves as usual, one environment is one project. As soon as other projects are defined, the environment becomes a multi-project one.
-== The Data Model ==
 Independently from the GenericTrac specification, the MultiProject changes to the data model are quite simple.