Andreas Hartmann 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.
sorry, i was in a hurry. the "Glossary" reflects the current state as i understood it. the proposal i mean is: http://wiki.apache.org/lenya/GlossaryStructure <quote> - - - Document (an abstract container for all assets) contains: - - - - Assets (text assets (in several languages), images, media files, pdfs, etc) Assets have revision control information. Documents have a revision control information summary (the collection of all current revisions of their assets). Whenever one asset changes, the Document revision number is bumped. </quote> one thing that's missing is that all assets can have a language attribute. > asset:: An atomic piece of information, handled as a single unit by the > API. > An asset consists of multiple translations (language versions). "can consist"? > > document:: A dynamically assembled piece of information, based on an asset. ok, i realize that not all assets are created equal. one is the starting point which references the others. but the starting asset should not be special. the document should know which is the starting asset of a particular language version. > 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. hmm. for components such as navigation, how about "dynamic asset"? i'd like the document to be the final piece of content that is created to answer a user request. -- "Án nýrra verka, án nútimans, hættir fortíðin að vekja áhuga." "Without new works, without the present the past will cease to be of interest." - Ásmundur Sveinsson (1893-1982) -- Jörn Nettingsmeier, EDV-Administrator Institut für Politikwissenschaft Universität Duisburg-Essen, Standort Duisburg Mail: [EMAIL PROTECTED], Telefon: 0203/379-2736 --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
