(Created page with " == Abstract == Content management systems support the dissemination and maintenance of documents. In software engineering terms, they separate the concerns of content, appli...") |
|||
| (One intermediate revision by the same user not shown) | |||
| Line 3: | Line 3: | ||
Content management systems support the dissemination and maintenance of documents. In software engineering terms, they separate the concerns of content, application logic and visual styling. Current systems largely maintain this separation of concerns after document deployment. Their runtime processing pipeline is a composition of generators, or document transformations. We exploit commutativity to enable new static evaluations of the composite during document deployment. Unlike traditional caching, we arrive at closed-form composites even for styled, database-driven documents. This eliminates the runtime penalties of a separation of concerns while preserving their software engineering benefits. | Content management systems support the dissemination and maintenance of documents. In software engineering terms, they separate the concerns of content, application logic and visual styling. Current systems largely maintain this separation of concerns after document deployment. Their runtime processing pipeline is a composition of generators, or document transformations. We exploit commutativity to enable new static evaluations of the composite during document deployment. Unlike traditional caching, we arrive at closed-form composites even for styled, database-driven documents. This eliminates the runtime penalties of a separation of concerns while preserving their software engineering benefits. | ||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| Line 15: | Line 10: | ||
* [http://www.info.uni-karlsruhe.de/papers/nk2002-cms.pdf http://www.info.uni-karlsruhe.de/papers/nk2002-cms.pdf] | * [http://www.info.uni-karlsruhe.de/papers/nk2002-cms.pdf http://www.info.uni-karlsruhe.de/papers/nk2002-cms.pdf] | ||
| + | |||
| + | * [http://link.springer.com/content/pdf/10.1007/3-540-45821-2_16 http://link.springer.com/content/pdf/10.1007/3-540-45821-2_16], | ||
| + | : [http://dx.doi.org/10.1007/3-540-45821-2_16 http://dx.doi.org/10.1007/3-540-45821-2_16] | ||
| + | |||
| + | * [https://link.springer.com/chapter/10.1007/3-540-45821-2_16 https://link.springer.com/chapter/10.1007/3-540-45821-2_16], | ||
| + | : [http://core.ac.uk/display/24510307 http://core.ac.uk/display/24510307], | ||
| + | : [https://www.scipedia.com/public/Noga_Kruper_2007a https://www.scipedia.com/public/Noga_Kruper_2007a], | ||
| + | : [http://www.info.uni-karlsruhe.de/papers/nk2002-cms.pdf http://www.info.uni-karlsruhe.de/papers/nk2002-cms.pdf], | ||
| + | : [https://academic.microsoft.com/#/detail/66125926 https://academic.microsoft.com/#/detail/66125926] | ||
Latest revision as of 16:24, 21 January 2021
Abstract
Content management systems support the dissemination and maintenance of documents. In software engineering terms, they separate the concerns of content, application logic and visual styling. Current systems largely maintain this separation of concerns after document deployment. Their runtime processing pipeline is a composition of generators, or document transformations. We exploit commutativity to enable new static evaluations of the composite during document deployment. Unlike traditional caching, we arrive at closed-form composites even for styled, database-driven documents. This eliminates the runtime penalties of a separation of concerns while preserving their software engineering benefits.
Original document
The different versions of the original document can be found in:
Document information
Published on 01/01/2007
Volume 2007, 2007
DOI: 10.1007/3-540-45821-2_16
Licence: CC BY-NC-SA license
Share this document
Keywords
claim authorship
Are you one of the authors of this document?