Presentation separation idiom
From CSSEMediaWiki
(Difference between revisions)
(add presentation separation idiom) |
m (Reverted edits by Ebybymic (Talk); changed back to last version by Linda Pettigrew) |
||
| (5 intermediate revisions by 3 users not shown) | |||
| Line 1: | Line 1: | ||
| − | Presentation separation (also known as ''separation of presentation and content'') is a design idiom in which semantic and aesthetic are separated as to aim for a loose coupling between the two | + | Presentation separation (also known as ''separation of presentation and content'') is a design idiom in which semantic and aesthetic are separated as to aim for a loose coupling between the two. Semantic implies "content, logic, information, ontology, semantic, data, model" while aesthetic implies "presentation, graphics, design, layout, style, visualization, view". This design idiom has been applied in many publishing field, such as web publishing or web design among many others. |
| − | The greater, more general idea of this idiom is [[Separation of concerns]]. In software engineering, this idiom has been developed into an architectural pattern of [[Model | + | The greater, more general idea of this idiom is [[Separation of concerns]]. In software engineering, this idiom has been developed into an architectural pattern of [[Model View Controller]]. |
== See also == | == See also == | ||
* [[Separation of concerns]] | * [[Separation of concerns]] | ||
| − | * [[Model | + | * [[Model View Controller]] |
Latest revision as of 03:08, 25 November 2010
Presentation separation (also known as separation of presentation and content) is a design idiom in which semantic and aesthetic are separated as to aim for a loose coupling between the two. Semantic implies "content, logic, information, ontology, semantic, data, model" while aesthetic implies "presentation, graphics, design, layout, style, visualization, view". This design idiom has been applied in many publishing field, such as web publishing or web design among many others.
The greater, more general idea of this idiom is Separation of concerns. In software engineering, this idiom has been developed into an architectural pattern of Model View Controller.
