deletions | additions       diff --git a/Components.tex b/Components.tex  index 82f562a..1ab49d3 100644  --- a/Components.tex  +++ b/Components.tex 
...
\subsubsection{Importing data}  The SED Builder handles SED I/O. As described in Section~\ref{sec:overview}, Iris accepts data from a variety of sources, and is lenient on the data format. Figure~\ref{fig:data_sources} illustrates that Iris imports data from built-in data archive portals as well as from outside resources like local files, URLs, other VO-enabled applications, and from plugins.  Iris natively supports IVOA-compliant FITS and VOTable formats (described in \cite{2012arXiv1204.3055M}). Files in these formats will automatically be added to SED Builder and the visualizer. The Builder can convert ASCII Tables, CSV, Tab-Seprated-Tables, IPAC tables~\footnote{http://irsa.ipac.caltech.edu/applications/DDGEN/Doc/ipac_tbl.html}, tables\footnote{http://irsa.ipac.caltech.edu/applications/DDGEN/Doc/ipac_tbl.html},  SAMP messages, and non-IVOA-compliant VOTable and FITS files into the native format with user input. We provide two file converted forms: (1) the Import Setup Frame, which handles spectrum-style files (i.e. those with columns for the spectral, flux and flux uncertainties), and (2) the Photometry Catalog Importer, which handles photometry catalogs (i.e. files where each column represents a passband and the values represent the fluxes). Users can save their setup options from the Import Setup Frame to a configuration file and automatically read-in files of the same format to Iris via the command line. The SED Builder also has a hook for adding custom file filters. A user can develop a custom file reader that would convert a non-standard file, e.g. a SExtractor-type file, to an IVOA-compliant format. This kind of plugin would allow the user to automatically read-in non-standard files to Iris, without needing to use the importer tools (See Section~\ref{sec:plugins} for details on developing Iris plugins).