Josias Thoeny wrote:
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?
Yes.
I mean, there would be no Document.java?
Yes.
Would the term "document" actually be used in the code?
Only in URLs like cocoon://generate-document/...
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, ...)?
That has to be decided. I have the feeling that the latter option
is the way to go, since a common interface might be too restrictive.
I'm just trying to understand your idea...
Thanks for your questions, I agree that these issues need clarification.
-- Andreas
--
Andreas Hartmann
Wyona Inc. - Open Source Content Management - Apache Lenya
http://www.wyona.com http://lenya.apache.org
[EMAIL PROTECTED] [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
