the Tamino-collection notion and your “collection of documents” may be slightly at odds.
Tamino collections are merely organizational units inside a Tamino database. Think of them as folders in the database or partitions. I use them to distinguish different applications’ data inside one database, e.g.
Then, all doctypes specific to the application bbs go inside collection bbs, e.g.
Then, these Tamino Doctypes hold the “collection of documents” you’re (most likely) talking about, all the posting XML documents, all the user XML documents and so on.
Referencing this and across the fence to another Tamino-collection is always possible, since all access methods support this addressing scheme:
If you’re using the Java API, notice how the Accessor classes need these two information items for initialization: URL to the database (http://servername/tamino/ino31) and the collection (bbs). Then all commands like queries are executed against the given collection. That’s why X-Queries usually start with the Tamino-doctype name, that being the root-element of your schema, e.g. user .
So, in our example, if bbs and portal are to have both a user doctype, there’s no problem of correctly identifying the one or the other, since you always have to give database name AND Tamino-collection.
Let me wrap it up by saying:
When you design your doctype (DTD or schema), you don’t need to care about anything in regard to Tamino. Yes, you should be able to use about any existing DTD / schema, load it into the Schema Editor and have it placed in a Tamino collection of your choice.
Documents adhering to this schema are loaded into the thus prepared storage structure, when - and only when - you send them to the right Tamino-collection. In Interactive Interface you’d set the database name and right next to it the collection name of bbs, go to the “process” entry field and give the path to a user instance (adhering to the User-DTD defined in collection bbs). Tamino goes forth and loads the instance right there.
Then you set the collection entry to portal, set “process” to another file containing a User document adhering to the schema you defined in the portal Tamino-collection and Tamino goes forth and loads it just there.
So you could have two totally different User-dtd/schemas fenced off each other by the different Tamino collections.
When query-ing the one or the other you need to specify the collection, so nothing gets messed up during any operation.
Best regards, Andreas