On 2/9/06, Andreas Hartmann <[EMAIL PROTECTED]> wrote: > Bob Harner wrote: > 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 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.) I'll try to stay out of this, as I have already made my opinions very well known.
"A piece of information, regardless of its nature, which is handled as a single unit by Lenya" I vote for Resource as the parent class which is subclassed: - Document (XML stored in Content and Modules) - Asset (uploaded file stored in Content and Modules) - Program (CSS, XMAP, XSLT, and XSP stored in Modules) We have not discussed a name for "programming resource" yet, but it should be unnecessary because each type will have its own class/Module. XMAP, XSLT, and XSP will inherit from Document since they are XML. CSS will need its own, but Thorsten suggested Forrest has something usable. 'Nuff, solprovider --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
