Please find attached to this page a draft of the document "The IVOA in 2006: Assessment and Future Plans".
After detailed feedback during the Victoria meeting, the Technical Coordination Committee expects to finalize this document.
Comments
(please include your name) ......
Roy,
Of course I don't entirely accept your description of DM...
I think that with our experience developing the spectrum DM
and the SSA DAL, we now have software implementations and
we have what Doug calls 'component data models' that are small
bits which can
be reused in different contexts. The Curation,
DataID,
and soon Characterization/Coverage models are pieces that
are relatively simple and can be reused elsewhere.
The Spectral Line model, which is rapidly heading to 1.0,
is a nice example of a DM which is relatively simple and
on which we have achieved convergence quickly. So I think
we have learned how to do it.
- Jonathan
From your description of the GWS work-packages:
VOStore should be carefully defined so that data store can be indirect, not controlled by VOStore, yet the metadata still well synchronoized with the data store.
If we replace "VOStore" with "VOSpace" (since VOStore being dropped), then I agree with you in general. I think that where we have two interfaces to a data-store, e.g. VOSpace and
SkyNode talking to the same RDBMS, then the ensemble is responsible for keeping coherence, and we should write that into the spec. If you had some other requirement or use case in mind then maybe you could explain in more detail; perhaps a note to the Friday GWS session?
GuyRixon