Greetings all.
I've just submitted this abstract to ADASS.
Are all the attributions correct?
Norman
--
---------------------------------------------------------------------------
Norman Gray http://www.astro.gla.ac.uk/users/norman/
Physics and Astronomy, University of Glasgow, UK [log in to unmask]
---------- Forwarded message ----------
From: [log in to unmask]
To: [log in to unmask], [log in to unmask]
Date: Fri, 8 Aug 2003 09:53:45 -0700 (MST)
Subject: abstract submission for ADASS
X-spam-score: 1.5 (+)
ADASS 2003 Abstract Submission
------------------------------
You submitted the following abstract. You may update it
by going back on the
http://www.adass.org:8080/meetings/adass2003/instructions/abstracts#access
abstract submission form, typing your e-mail address
and the beginning of the title.
===========================================================
Title:
-----
Data models in the VO: how do they make code better?
Requested Presentation Type:
---------------------------
oral
Authors:
-------
Norman Gray, Starlink/University of Glasgow
David L Giaretta, Starlink/RAL
David Berry, Starlink/University of Central Lancashire
Malcolm Currie, Starlink/RAL
Mark Taylor, Starlink/University of Bristol
Abstract:
--------
Data Models exist in people's heads. Data modelling consists of
making these explicit on paper, so that (a) we can discover if there is
more than one important model, and (b) we can develop using the model
which has the best impedance match with the community being targeted.
Thus modelling is not just about communications -- about bits (or angle
brackets!) on the wire -- but is a software quality and usability issue.
We contend that there is in fact more than one model relevant to the
VO, and that while the VOTable model is an excellent and valuable fit
to the archivists' model of data, it may be a poor match for many users or
(which is much the same thing) for the software written to service the
sort of end-user astronomical applications which the VO targets.
Modelling work in other areas shows the importance of abstraction in
the concrete goal of freeing software design from the particulars of any
single implementation. This is extremely important for the VO because
it allows us, and the software we write, to deal with the essentials of
the data rather than the superficial aspects of a particular format such
as XML or FITS. We discuss the work that we and others have been doing
within this context; with this in mind, we will also review some of the
various modelling languages available, such as XSchemas, UML, OMG MDA,
HUTN, RDF, and Topic Maps.
Special Requests:
----------------
|