Amos Latteier wrote:
I agree to renaming DTML Methods, but I think a different approach should be taken to Documents. I think we should think more generally in terms of a Content object that can have different encodings like XML, plain text, structured text, XML, HTML, and did I mention XML. That way we don't need a separate type of Object for each separate type of content.
What makes Content object different from a DTML document? Is it just a content-type property? I would expect XML objects to have much more structure than, say, plain text or even HTML. For example, I imagine XML objects providing a navigation interface of some kind.
As a bonus if Content objects work well, Products like Confera could hold their content in standard Content objects, and so it would be much easier for different types of Products to exchange data.
But this implies that Content objects have structure. Do you imagine that Content objects have sub-objects? Are they foldoids? Would they provide a mechanism for setting limitations on what kinds of objects could be sub-objects? I think that a driving need that alot of people have expressed is a *simple* mechanism for handling textual content with properties and DTML markup. I'd like to meet that basic need. Jim -- Jim Fulton mailto:jim@digicool.com Technical Director (540) 371-6909 Python Powered! Digital Creations http://www.digicool.com http://www.python.org Under US Code Title 47, Sec.227(b)(1)(C), Sec.227(a)(2)(B) This email address may not be added to any commercial mail list with out my permission. Violation of my privacy with advertising or SPAM will result in a suit for a MINIMUM of $500 damages/incident, $1500 for repeats.