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 AndreasHartmann:
http://wiki.apache.org/lenya/ProposalContentModel

------------------------------------------------------------------------------
   * Regarding {{{Link}}} and {{{DynamicContent}}}, in the current model these 
categories don't really yet seem useful. Should there be some explicit 
structure in the API regarding what a {{{Link}}} is ? Should there be explicit 
classes for common types of dynamic content, e.g. {{{RSSFeed}}}, 
{{{WebService}}}.
   * do the different categories of content have different structures in the 
repository ? e.g. a link, if it exists as an explicit type, should be 
explicitly structured in the repository, and not a formless XML String, as 
opposed to a piece of XHTML content.
  
+ == Comments by AndreasHartmann ==
+ 
+  * I woudln't model a document as a collection of assets. IMO a document 
should be dynamically assembled, based on an asset. The document is generated 
by resolving references to other assets and external resources.
+ 

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to