[
Lists Home |
Date Index |
Thread Index
]
> > Since we're talking of native XML databases, in Tamino
> there is a relationship
> > between the concepts of document type and schema, but it
> doesn't have to be
> > one-to-one; a document type is whatever the user wants it
> to be, the only
> > restriction being that each document has exactly one type.
>
> Please forgive me if I am being obtuse, but the phrasing
> above seems to beg anew
> the very question which I hope we might resolve in this
> thread. Are you saying
> (as I hope) that each document instance committed to Tamino
> may have exactly one
> type because of the inherent limit in this 'type' being a
> purely lexical identifier
>
Yes, more or less. Without wanting to go into the fine detail of the
product, a Tamino server gives access to a number of named databases, each
database contains a number of named document collections, each collection
allows the storage of a number of named document types, and each document
type is associated with a schema (not specifically with a top-level element
type, but you can organize it that way if you wish). Each document instance
when it is loaded is assigned to a document type, a collection, and a
database.
Mike Kay
(Software AG)
|
