On 2/6/06, Andreas Hartmann <[EMAIL PROTECTED]> wrote: > Jörn Nettingsmeier wrote: > > Andreas Hartmann wrote: > >> Jörn Nettingsmeier wrote: > >> > >> [...] > >> > >>>> One thing, though: It isn't clear to me whether Jörn and Solprovider > >>>> really agree on what a Document is. Jörn seems to be using Document > >>>> as the aggregate/container term for both the editable text and the > >>>> assets of a page. But Solprovider seems to be suggesting the words > >>>> Resource or Content for that purpose. > >>> > >>> now that you say it, you are right. i had read solprovider's remark > >>> the way i wanted it to read :( > >> > >> A little off topic, but I'd like to state my opinion once more: > >> The concept of "the editable text and the assets of a page" should be > >> dropped. Textual documents and (binary) assets should be equally handled > >> items in a flat storage. > > > > ++votes. > > > > how do you like my terminology proposal in the wiki? > > i'm suggesting to use "document" as the thing that is composed of > > assets, where assets are "text assets" (can be in different languages), > > and image or other media assets (with the same properties). > > > Actually I'm not quite pleased with that. > IMO "set of =>language versions and other =>assets" is a mixture of concepts. > Assets consist of language versions (translations). > > > How about this: > > > asset:: An atomic piece of information, handled as a single unit by the API. > An asset consists of multiple translations (language versions). > > document:: A dynamically assembled piece of information, based on an asset. > The document isgenerated by resolving references to other assets > and external resources. [1] > > page:: The aggregation of 1..n documents + presentation. > > > [1] Using this definition, navigation widgets can be implemented as documents, > based on an asset which references the resource which generates the navigation > widget. This means, according to this definition, a page can contain > navigation > widgets as well. > > > -- Andreas >
I like Andreas' definitions, except I'm a little uneasy about saying that a page consists of one or more documents. That's the converse of the real-world definition in which a "document" consists of one or more pages (which in HTML terms would mean next page & prev page links). Also, let's please consider the possibility that a document could be simply a PDF file (linked directly from the navigation). I'm not sure how to work that in, but it would seem to be an important need. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
