[EMAIL PROTECTED] wrote: [...]
Summary: - Publication - - Content - - - Document (has Type, DocumentUNID, DocumentID properties) - - - - Translation (has Language and LiveRevision properties) - - - - - Revision (has CreationDate and Editor properties) - - - Asset (has Type, UNID, ID properties) [- - - - Translation (has Language and LiveRevision properties)] - - - - - Revision (has CreationDate and Editor properties)
+1, I really like it. But IMO Document and Asset should have a generalization class / interface. Since "Resource" and "Content Item" don't seem to be generally accepted, what else can we use?
Will Assets have Translations?
+1 (e.g., a Chrysler for the American version, a Mercedes-Benz for the German one)
Can it be optional?
It can be up to the publication if it allows multiple translations of an asset.
How do we handle PDFs in multiple languages?
One Asset per language?
-1
Or one Asset with multiple translations?
+1 (I don't see a need for special handling here) Thanks, Joern and solprovider! -- 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]
