<?xml version="1.0"?>
<!DOCTYPE webpage PUBLIC "-//Norman Walsh//DTD Website V2.1b1//EN" "../../../dtd/website.dtd" [
  <!ENTITY application SYSTEM "applications.xml" NDATA XML>
  <!ENTITY base SYSTEM "bases.xml" NDATA XML>
  <!ENTITY entrepot SYSTEM "entrepots.xml" NDATA XML>
  <!ENTITY index SYSTEM "../index.xml" NDATA XML>
  <!ENTITY serveur SYSTEM "serveur.xml" NDATA XML>
]>

<webpage id="entrepots"> 

  <head>
	 <title>Repositories</title>
	 <titleabbrev>Repository</titleabbrev>
	 <author>
		<firstname>Martin</firstname>
		<surname>Sévigny</surname>
		<affiliation>
		  <orgname>AJLSM</orgname> 
		</affiliation>
	 </author>
	 <author>
		<firstname>Frédéric</firstname>
		<surname> Glorieux</surname>
		<affiliation>
		  <orgname>AJLSM</orgname> 
		</affiliation>
	 </author>
	 <revhistory>
		<revision>
		  <revnumber>1.0</revnumber> 
		  <date>2003-06-03</date> 
		</revision>
	 </revhistory>
  </head>

  <para>SDX is a search tool for XML documents, but it also is an interesting platform for displaying those XML documents or other types of documents. Thus, it must be able to retrieve the document, in the same format as it has been submitted for indexing, the repository performs this operation.</para>
  <section> 
	 <title>Definition</title>
	 <para>The repostory can either stock indexed documents, or only record their address. Various types of repositories have one of those options while demonstrating flexibility when being configured. Repositories can stock all types of documents, not only XML documents.</para>
  </section> 
  <section> 
	 <title>Types</title>
	 <para>An SDX-2 application may contain various repositories. It is difficult to provide precise rules for the use of one or more repositories, we will only suggest possible ways:</para>
	 <variablelist> 
		<varlistentry> 
		  <term>documents which are copied or referenced</term> 
		  <listitem>
			 <para>It it is desirable that SDX takes a copy of the document and manages it by itself, specific types of repositories will have to be used. On the contrary, if it is not desirable that SDX takes a copy of the document but rather keep it address for future use, other ttypes of repositories will have to be used. If in a single application, both solutions appear, at least two repositories will have to be used since no repository can have both features simultaneaously.</para>
		  </listitem>
		</varlistentry> 
		<varlistentry> 
		  <term>responsability for digital documents maintenance</term> 
		  <listitem>
			 <para>Particularly when SDX does not take copy of documents, it is important to consider the responsability for maintaining documents when selectiong the repository(ies). If document collections have distinct maintenance responsability, distinct repositories may be preferred, even though it is not absolutely required. </para>
		  </listitem>
		</varlistentry> 
		<varlistentry> 
		  <term>back-up</term> 
		  <listitem>
			 <para>When SDX takes document copies, especially when no copy exists, back-up mechanisms may have to be considered to choose between one or more repository(ies). </para>
		  </listitem>
		</varlistentry> 
	 </variablelist> 
  </section> 

</webpage> 
