Bob Harner wrote:
[...] I would suggest as a next step that each interested person summarize his view of how the site, page, module, document, asset, ande site tree all relate to each other, in just one or two paragraphs, similar to the way Andreas and SolProvider did at the beginning of this thread when they wrote "For me, the following text sounds quite good". There are probably only two or three such versions. Then you committers can vote on which paragraph sounds best.
OK, I'll give it another try. If you don't think this whole thing is rubbish, I'd like to ask you to just add your +-1 and use footnotes for comments, so that the structure stays intact. - A *publication* is a collection of related pieces of information and functionality to manipulate these items. Each piece of information can exist in multiple states at the same time. This might be implemented using *areas*, revision history labels, or something else. - The entirety of information pieces of a publication is called the *content* of the publication. - A piece of information, regardless of its nature, which is handled as a single unit by Lenya is called * asset [+0.3] * resource [+0.2] * content item [+0.2] * document [+0.3] * ... (I thought about it again, Josias has a point saying images can be regarded as documents as well. IMO content item is too long, resource is not specific enough.) - A language version of a piece of information is called a *translation*. - A version in the history of a translation is called a *revision*. - The structuring information (there may be several of them) are * indexes [+0.5] * structures [+0.5] - A node in the information structure is called * (structure/index) node Thanks for your participation in this discussion, -- 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]
