Dear Wiki user, You have subscribed to a wiki page or wiki category on "Lenya Wiki" for change notification.
The following page has been changed by JörnNettingsmeier: http://wiki.apache.org/lenya/GlossaryStructure The comment on the change is: initial draft as per michi's suggestion. New page: This page is meant to give you an overview of key concepts concerning the structure of Lenya publications. ''The terms presented here are currently debated. This page does not reflect or imply consensus. Think of it as a placeholder.'' ---- === ["solprovider"] === {{{ - 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) }}} === JörnNettingsmeier, with ideas from BobHarner === {{{ - Publication contains: - - Site tree (one canonical, optionally others) contains (as nodes): - - - Document (an abstract container for all assets) contains: - - - - Assets (translations [1], 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 review number is bumped. [1] "translation" includes the original language. think of it as "word-centric" XML content. :-D }}} This leaves the ugly words "resource" and "content item" out. They can be used internally for abstract objects if needed. "translations" is sub-optimal outside of the i18n context. how about calling such "word-centric" XML files "text assets" ? === Your 0.02 $CURRENCY here === --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
