On 2/4/06, Bob Harner <[EMAIL PROTECTED]> wrote: > BTWI think I was unclear earlier in what I meant by "Content Item" and > its relationship to Document. I meant that both a Document and an > Asset are each Content Items. I didn't mean for "Content Item" to > mean the aggregate of a Document and its Assets. > > One thing, though: It isn't clear to me whether Jörn and Solprovider > really agree on what a Document is. Jörn seems to be using Document > as the aggregate/container term for both the editable text and the > assets of a page. But Solprovider seems to be suggesting the words > Resource or Content for that purpose. > > I wonder if we shouldn't promote "Asset" a little like this: A > Document consists of Assets. An Asset can be any of the following: a > German translation of the document, a French translation, a JPEG > image, a PDF file, etc. All are assets. Collectively, they are a > Document. This approach does away with the need for "Content Item" > and helps us in treating assets just like other managed content, which > several people have stated as a goal.
Sorry. I was using Asset in the Lenya 1.2 GUI meaning of anything that is not a Document. I also assumed we were moving Assets from the Document to the Publication. Old: Content/Document/Assets New: Content/Document Content/Asset Each ["Resource | "Content Node" | "Content Item"] is either a Document or Asset. Each Document has Translations which have Revisions. Each Asset has Revisions. Advantages: - Assets have Revisions and Workflow like Documents. - The URL for Assets is based on the Publication. Usage could be as simple as "/mypicture.gif" for the server's default pub, or "/mypub/mypicture.gif" for other pubs. That would require the default "live" Module checks extensions for handling. There are many possible algorithms: - - "live" retrieves the data; - - "live" passes to "assets" which retrieves the data; - - "live" passes to "assets" passes to "images" which retrieves the data. Any of these options are easier than 1.2's Make Link "docid/assetname.ext". solprovider --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
