Presentation separation idiom

From CSSEMediaWiki
(Difference between revisions)
Jump to: navigation, search
(add presentation separation idiom)
 
m
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 distinct concept. 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.  
+
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]]
 
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]]

Revision as of 05:22, 6 October 2008

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

See also

Personal tools