%%% Modif FO
%APN3_PROCEEDINGS_FORM%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% 
%
% TEMPLATE.TEX -- APN3 (2003) ASP Conference Proceedings template.
%
% Derived from ADASS VIII (98) ASP Conference Proceedings template
% Updated by N. Manset for ADASS IX (99), F. Primini for ADASS 2000,
% D.Bohlender for ADASS 2001, and H. Payne for ADASS XII and LaTeX2e.
%
% Use this template to create your proceedings paper in LaTeX format
% by following the instructions given below.  Much of the input will
% be enclosed by braces (i.e., { }).  The percent sign, "%", denotes
% the start of a comment; text after it will be ignored by LaTeX.  
% You might also notice in some of the examples below the use of "\ "
% after a period; this prevents LaTeX from interpreting the period as
% the end of a sentence and putting extra space after it.  
% 
% You should check your paper by processing it with LaTeX.  For
% details about how to run LaTeX as well as how to print out the User
% Guide, consult the README file.  You should also consult the sample
% LaTeX papers, sample1.tex and sample2.tex, for examples of including
% figures, html links, special symbols, and other advanced features.
%
% If you do not have access to the LaTeX software or a laser printer
% at your site, you can still prepare your paper following the
% instructions in the User Guide.  In such cases, the editors will
% process the file and make any necessary editorial adjustments.
% 
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
% 
\documentclass[11pt,twoside]{article}  % Leave intact
\usepackage{adassconf}

% If you have the old LaTeX 2.09, and not the current LaTeX2e, comment
% out the \documentclass and \usepackage lines above and uncomment
% the following:

%\documentstyle[11pt,twoside,adassconf]{article}

\begin{document}   % Leave intact

%-----------------------------------------------------------------------
%			    Paper ID Code
%-----------------------------------------------------------------------
% Enter the proper paper identification code.  The ID code for your
% paper is the session number associated with your presentation as
% published in the official conference proceedings.  You can           
% find this number locating your abstract in the printed proceedings
% that you received at the meeting or on-line at the conference web
% site; the ID code is the letter/number sequence proceeding the title 
% of your presentation. 
%
% This will not appear in your paper; however, it allows different
% papers in the proceedings to cross-reference each other.  Note that
% you should only have one \paperID, and it should not include a
% trailing period.
%
% EXAMPLE: \paperID{O4-1}
% EXAMPLE: \paperID{P7-7}
%

\paperID{P2-31}
%%%% ID=P2-31

%-----------------------------------------------------------------------
%		            Paper Title 
%-----------------------------------------------------------------------
% Enter the title of the paper.
%
% EXAMPLE: \title{A Breakthrough in Astronomical Software Development}
% 
% If your title is so long as to fill the page header when you print it,
% then please supply a short form as a \titlemark.
%
% EXAMPLE: 
%  \title{Rapid Development for Distributed Computing, with Implications
%         for the Virtual Observatory}
%  \titlemark{Rapid Development for Distributed Computing}
%

\title{BDB - a database for all types of double stars }
%\titlemark{ }

%-----------------------------------------------------------------------
%		          Authors of Paper
%-----------------------------------------------------------------------
% Enter the authors followed by their affiliations.  The \author and
% \affil commands may appear multiple times as necessary (see example
% below).  List each author by giving the first name or initials first
% followed by the last name.  Authors with the same affiliations
% should grouped together. 
%
% EXAMPLE: \author{Raymond Plante, Doug Roberts, 
%                  R.\ M.\ Crutcher\altaffilmark{1}}
%          \affil{National Center for Supercomputing Applications, 
%                 University of Illinois Urbana-Champaign, Urbana, IL
%                 61801}
%          \author{Tom Troland}
%          \affil{University of Kentucky}
%
%          \altaffiltext{1}{Astronomy Department, UIUC}
%
% In this example, the first three authors, "Plante", "Roberts", and
% "Crutcher" are affiliated with "NCSA".  "Crutcher" has an alternate 
% affiliation with the "Astronomy Department".  The fourth author,
% "Troland", is affiliated with "University of Kentucky"

\author{Edouard Oblak, Bernard Debray}
        \affil{Besan\c con Observatory,
            F-25010 Besan\c con Cedex,
            UMR CNRS 6091}
        \author{Tomasz Kundera}
        \affil{Cracow Observatory, PL-30244 Cracow}
%
%-----------------------------------------------------------------------
%			 Contact Information
%-----------------------------------------------------------------------
% This information will not appear in the paper but will be used by
% the editors in case you need to be contacted concerning your
% submission.  Enter your name as the contact along with your email
% address.
% 
% EXAMPLE:  \contact{Dennis Crabtree}
%           \email{crabtree@cfht.hawaii.edu}
%

\contact{Edouard Oblak}
\email{oblak@obs-besancon.fr}

%-----------------------------------------------------------------------
%		      Author Index Specification
%-----------------------------------------------------------------------
% Specify how each author name should appear in the author index.  The 
% \paindex{ } should be used to indicate the primary author, and the
% \aindex for all other co-authors.  You MUST use the following
% syntax: 
%
% SYNTAX:  \aindex{Lastname, F. M.}
% 
% where F is the first initial and M is the second initial (if
% used).  This guarantees that authors that appear in multiple papers
% will appear only once in the author index.  
%
% EXAMPLE: \paindex{Crabtree, D.}
%          \aindex{Manset, N.}        
%          \aindex{Veillet, C.}        
%
% NOTE: this information is also used to build the author list that
% appears in the table of contents.  Authors will be listed in the order
% of the \paindex and \aindex commmands.
%

\paindex{Oblak, E.}
\aindex{Debray, B.}     % Remove this line if there is only one author
\aindex{Kundera, T.}

%-----------------------------------------------------------------------
%		      Author list for page header	
%-----------------------------------------------------------------------
% Please supply a list of author last names for the page header. in
% one of these formats:
%
% EXAMPLES:
% \authormark{Lastname}
% \authormark{Lastname1 \& Lastname2}
% \authormark{Lastname1, Lastname2, ... \& LastnameN}
% \authormark{Lastname et al.}
%
% Use the "et al." form in the case of seven or more authors, or if
% the preferred form is too long to fit in the header.

\authormark{Oblak, Debray, Kundera}

%-----------------------------------------------------------------------
%			Subject Index keywords
%-----------------------------------------------------------------------
% Enter a comma separated list of up to 6 keywords describing your
% paper.  These will NOT be printed as part of your paper; however,
% they will be used to generate the subject index for the proceedings.
% There is no standard list; however, you can consult the indices
% for past proceedings (http://adass.org/adass/proceedings/).
%
% EXAMPLE:  \keywords{visualization, astronomy: radio, parallel
%                     computing, AIPS++, Galactic Center}
%
% In this example, the author noticed that "radio astronomy" appeared
% in the ADASS VII Index as "astronomy" being the major keyword and
% "radio" as the minor keyword.  The colon is used to introduce another
% level into the index.

\keywords{astronomy: double stars}

%-----------------------------------------------------------------------
%			       Abstract
%-----------------------------------------------------------------------
% Type abstract in the space below.  Consult the User Guide and Latex
% Information file for a list of supported macros (e.g. for typesetting 
% special symbols). Do not leave a blank line between \begin{abstract} 
% and the start of your text.

\begin{abstract}          % Leave intact
% Place the text of your abstract here - NO BLANK LINES
We present the general characteristics of a database for binary and multiple stars from all observational categories, specifically designed to address the
awkward topics of the identification of stellar components. BDB is based on a modular architecture to allow the easy integration of data from various
sources. We describe in particular the set up of connections with other double star databases through the Internet. Additional tools are being developped for
the processing of image data. The implementation of standards for the connection of BDB with Virtual Observatory projects is reviewed.
\end{abstract}

%-----------------------------------------------------------------------
%			      Main Body
%-----------------------------------------------------------------------
% Place the text for the main body of the paper here.  You should use
% the \section command to label the various sections; use of
% \subsection is optional.  Significant words in section titles should
% be capitalized.  Sections and subsections will be numbered
% automatically. 
%
% EXAMPLE:  \section{Introduction}
%           ...
%           \subsection{Our View of the World}
%           ...
%           \section{A New Approach}
%
% It is recommended that you look at the sample papers, sample1.tex
% and sample2.tex, for examples for formatting references, footnotes,
% figures, equations, html links, lists, and other special features.  

\section{Introduction}
Why a SIMBAD-like database for double and multiple stars?\\
\begin{itemize}
\item to put together the various data of all types of double stars (Fig. 1),
\item to avoid the well known difficulties specific to binaries:\\
confusions between systems, components, measurements, identifiers, ...
\item to show the multiple belonging of a system to the different types of binaries (Fig. 1),
\item to give an easy and simultaneous access to ALL data relevant to any object.
\item more than 50~\% of the stars in a large neighbourhood of the Sun belong to double or multiple systems.
\end{itemize}

\noindent %%FO
The number and diversity of binary stars support the need for the creation 
of a database that cross-refers and compiles data about the various 
observational categories (Oblak 2001).\\
What is sought through BDB is to set at the disposal of the community of stellar astronomers, the query tools necessary to retrieve numerical or image data over the Internet.\\
BDB has been developed since 1995.
\begin{figure}
\epsscale{.80}
\plotone{P2-31-double-type-ang.eps}
\caption{The categories of double stars in term of angular separation given in arcseconds and astronomical units.} \label{P2-31:T1.10-fig-1}
\end{figure}
\begin{quote}
\begin{figure}[h]
\epsscale{.7}
\plottwo{P2-31-organigramme.ps}{P2-31-organisation2.eps}
\caption{General computing scheme of BDB and the computing organisation of BDB.
 the CROSS field contains the identifiers taken from the various catalogues
 CAT1, CAT2, ...etc.} \label{P2-31:T1.10-fig-2}
\end{figure}
\end{quote}
\section{The Computing Structure of BDB}
BDB is managed through the /rdb relational data base management system. A CROSS files supplies the cross-identification between the different identifiers of a given component of a double star. An internal unique order number, called BID, is also assigned to the star.\\
 A second file MAIN supplies the type of the binary system, the number and the 2000 equatorial coordinates (Fig. 2).\\
 Each local or remote set of data (catalogue, images,~...) is accessed separately by the query scripts  allowing  easy integration of new data, updates, corrections,~...
The MAIN field gives the basic information on the stellar systems : the type of the system or the number of the components.
\section{ Astronomical Content of BDB}
Catalogues of the following observational categories of binary stars are available through the database : visual, spectroscopic, interferometric and photometric.
More detailed informations can be found on the data base web site : {\texttt{http://bdb.obs-besancon.fr/}}.\\
Photometric measurements in the three photometric systems (UBV, Str\"omgren and Geneva : 1995 for the moment) were also integrated in BDB.\\
The BDBJAVA tool has been developed to compare numerical data from several catalogues with the Digitized Sky Survey and CCD images (our own observations of a European Network) of visual binaries (Fig. 3).\\
Thanks to computing links with external databases, BDB gives the possibility to access data from the SIDONIE visual binary database (Observatoire de la C\^ote d'Azur, France), IAU's SB9 spectroscopic database (Brussels, Belgium), Cracow data base of eclipsing binaries (Poland) and the Simbad database (CDS).
\begin{quote}
\begin{figure}[h]
\epsscale{.70}
\plotone{P2-31-capture2.eps}
\caption{Example from BDBjava : comparison between numerical data and 
images from  DSS and CCD.} \label{P2-31:T1.10-fig-3}
\end{figure}
\end{quote}

\section{Development Perspectives}
Besides the continous integration of new data specific to all observational categories, short-term developments focus on two axes:\\
1) interconnections with other databases\\
2) the output of data in XML format, especially for interoperability purposes; a
first experimental implementation was made using the Astrores DTD. The work will
now be turned into the new VOTable scheme (Ochsenbein et al. 2002) which was
defined in the framework of developments for the Virtual Observatory initiative.
Concurrently, other standards will also be considered, especially UCDs - Unified
Column Descriptors - (Derri\`ere et al. 2002).

\section{Conclusions}
Thanks to its structure and to its development scheme, the BDB data base allows
now to raise the ambiguity that is very often met when one has to deal with
binary stars. It could play a useful complementary role to CDS'SIMBAD in
supplying data specific to binary stars.\\ BDB can turn out to be a useful tool
for forthcoming projects such as GAIA.

\begin{references}
\reference Derri\`ere, S., Ochsenbein, F., Ortiz, P.  2002,
   ``UCDs: Metadata for the V.O."
   in ``Toward an International Virtual Observatory, Scientific Motivation, 
   Roadmap for Development and Current Status"
   Springer-Verlag, ESO Astrophysics Symposia, (in press),
   eds.~K.M. Gsrski and P.J.   Quinn
\reference Oblak, E. 2001, ``Quelques bases de donn\'ees d'\'etoiles doubles 
   et multiples", Ecole CNRS de Goutelas ``Etoiles doubles--des \'etoiles \`a grande s\'eparations aux binaires X", 
   353-371, eds.~D.~Egret, J.L.~Halbwachs et J.M.~Hameury
\reference Ochsenbein, F., Williams, R., Davenhall, C., Durand, D., 
   Fernique, P.,
   Giaretta, D., Hanisch, R., McGlynn, T., Szalay, A., Wicenec A.  2002,
  ``VOTable - A Proposed XML Format for Astronomical Tables",
  in ``Toward an International Virtual Observatory, Scientific Motivation, 
  Roadmapfor Development and Current Status", Springer-Verlag, ESO 
  Astrophysics Symposia (in press),
  eds.~K.~Gsrski and P.J.~Quinn
\end{references}
%-----------------------------------------------------------------------
%			      References
%-----------------------------------------------------------------------
% List your references below within the reference environment
% (i.e. between the \begin{references} and \end{references} tags).
% Each new reference should begin with a \reference command which sets
% up the proper indentation.  Observe the following order when listing
% bibliographical information for each reference:  author name(s),
% publication year, journal name, volume, and page number for
% articles.  Note that many journal names are available as macros; see
% the User Guide listing "macro-ized" journals.   
%
% EXAMPLE:  \reference Hagiwara, K., \& Zeppenfeld, D.\  1986, 
%                Nucl.Phys., 274, 1
%           \reference H\'enon, M.\  1961, Ann.d'Ap., 24, 369
%           \reference King, I.\ R.\  1966, \aj, 71, 276
%           \reference King, I.\ R.\  1975, in Dynamics of Stellar 
%                Systems, ed.\ A.\ Hayli (Dordrecht: Reidel), 99
%           \reference Tody, D.\  1998, \adassvii, 146
%           \reference Zacharias, N.\ \& Zacharias, M.\ 2003,
%                \adassxii, \paperref{P7.6}
% 
% Note the following tricks used in the example above:
%
%   o  \& is used to format an ampersand symbol (&).
%   o  \'e puts an accent agu over the letter e.  See the User Guide
%      and the sample files for details on formatting special
%      characters.  
%   o  "\ " after a period prevents LaTeX from interpreting the period 
%      as an end of a sentence.
%   o  \aj is a macro that expands to "Astron. J."  See the User Guide
%      for a full list of journal macros
%   o  \adassvii is a macro that expands to the full title, editor,
%      and publishing information for the ADASS VII conference
%      proceedings.  Such macros are defined for ADASS conferences I
%      through XI.
%   o  When referencing a paper in the current volume, use the
%      \adassxii and \paperref macros.  The argument to \paperref is
%      the paper ID code for the paper you are referencing.  See the 
%      note in the "Paper ID Code" section above for details on how to 
%      determine the paper ID code for the paper you reference.  
%
%\begin{references}
%\end{references}

% Do not place any material after the references section

\end{document}  % Leave intact
