On Mon, 2006-02-06 at 10:59 +0100, Andreas Hartmann wrote: [...] > 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]
Do I understand correctly that such a document is rather an abstract concept, like e.g. the result of a pipeline? I mean, there would be no Document.java? Would the term "document" actually be used in the code? About the references from one asset to another, would they be handled in a centralized way by the java core, or would the assets do that themselves (by xinclude, or by generating a link, ...)? I'm just trying to understand your idea... Josias > > 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 > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
