diff --git a/SoftwareGuide/Examples/CMakeLists.txt b/SoftwareGuide/Examples/CMakeLists.txt
index 089431b567969e07ae475b79417be0c33be2623e..91a095cd60f281dffac101797ef486de686a5409 100644
--- a/SoftwareGuide/Examples/CMakeLists.txt
+++ b/SoftwareGuide/Examples/CMakeLists.txt
@@ -153,6 +153,10 @@ ADD_CUSTOM_TARGET(SoftwareGuideExamples  ALL echo)
 
 SET( OTB_EXAMPLES_SRCS
   ${OTB_SOURCE_DIR}/Examples/Installation/HelloWorld.cxx
+  ${OTB_SOURCE_DIR}/Examples/DataRepresentation/Image/Image1.cxx
+  ${OTB_SOURCE_DIR}/Examples/DataRepresentation/Image/Image2.cxx
+  ${OTB_SOURCE_DIR}/Examples/DataRepresentation/Image/Image3.cxx
+  ${OTB_SOURCE_DIR}/Examples/DataRepresentation/Image/Image4.cxx	
   ${OTB_SOURCE_DIR}/Examples/StartExamples/MeanImageFilter.cxx
   ${OTB_SOURCE_DIR}/Examples/ExtractROI/ExtractROI.cxx
   ${OTB_SOURCE_DIR}/Examples/BasicFilters/LeeImageFilter.cxx
diff --git a/SoftwareGuide/Latex/DataRepresentation.tex b/SoftwareGuide/Latex/DataRepresentation.tex
index 58eff84245495ccd20594c09d026e5f38e852cb3..813b5a2382cc06a162cdbff76cba38c57b89b534 100644
--- a/SoftwareGuide/Latex/DataRepresentation.tex
+++ b/SoftwareGuide/Latex/DataRepresentation.tex
@@ -3,21 +3,22 @@
 
 
 This chapter introduces the basic classes responsible
-for representing data in ITK. The most common classes are the
-\doxygen{Image}, the \doxygen{Mesh} and the \doxygen{PointSet}.
+for representing data in OTB. The most common classes are the
+\doxygen{otb::Image}, the \doxygen{itk::Mesh} and the \doxygen{itk::PointSet}.
 
 \section{Image}
 \label{sec:ImageSection}
 
-The \doxygen{Image} class follows the spirit of 
-\href{http://www.boost.org/more/generic_programming.html}{Generic Programming}, 
-where types are separated from the algorithmic behavior of the class.  ITK supports images
-with any pixel type and any spatial dimension.
+The \doxygen{otb::Image} class follows the spirit of
+\href{http://www.boost.org/more/generic_programming.html}{Generic
+Programming}, where types are separated from the algorithmic behavior
+of the class.  OTB supports images with any pixel type and any spatial
+dimension.
 
 \subsection{Creating an Image}\label{sec:CreatingAnImageSection}
 
-
-%\input{Image1.tex}
+\textbf{FIXME : update with otb::Image}
+\input{Image1.tex}
 
 In practice it is rare to allocate and initialize an image directly.
 Images are typically read from a source, such a file or data acquisition
@@ -30,7 +31,7 @@ a file.
 \subsection{Reading an Image from a File}
 \label{sec:ReadingImageFromFile}
 
-%\input{Image2.tex}
+\input{Image2.tex}
 
 
 
@@ -39,7 +40,7 @@ a file.
 \subsection{Accessing Pixel Data}
 \label{sec:AccessingImagePixelData}
 
-%\input{Image3.tex}
+\input{Image3.tex}
 
 
 
@@ -47,8 +48,11 @@ a file.
 \subsection{Defining Origin and Spacing}
 \label{sec:DefiningImageOriginAndSpacing}
 
-%\input{Image4.tex}
+\input{Image4.tex}
 
+\subsection{Defining Other Image Attributes}
+\label{sec:DefiningOtherImageAttributes}
+%% Geographic projections, etc?
 
 \subsection{RGB Images}