V2.3.01 - 2009 06 30
News
New update of the registry released. | June 30, 2009 |
| see history for details. |
DAS workshop 2009 Registration closed | Feb 5, 2009 |
| Attendees who have already registered can expect to recieve emails with further information about the workshop in the next couple of weeks. |
New RelaxNG validation messages added to the das registry in version 2.2.5 | Dec 11, 2008 |
| Features, types, entry_points, alignments, sequence, structure and interaction validation now have extra more informative error messages if they do not conform to the DAS specification. It is intended that in the new year new DAS sources will need to pass this validation process in order to register.
If you think the validation is incorrect and your source is valid please email Jonathan Warren with the error message and the source you are trying to validate.
|
DAS workshop announced for 9th, 10th, 11th March 2009 | Nov 10, 2008 |
| Please register for the March 2009 workshop. Once registered you can change details at a later date. Registrations will close on the 1st Feb 2009 and places are limited. Presenatations from the previous workshop can be found here. |
New Coordinator for the DAS Registry | Sep 01, 2008 |
| Jonathan Warren is now maintaining the DAS Registry and has now taken over from Andreas Prlic |
About
The
DAS registration service provides a repository
for registry and discovery of
DAS (Distributed Annotation System)
services. DAS servers are described with meta
data like who is providing a server, what DAS commands are being understood by it,
what type of data is being provided, etc.
DAS style XML-http as well as SOAP based web services can be used to
interact with the DAS registry.
This is used by
DAS clients like
EnsEMBL,
SPICE,
or
Dasty
to retrieve the list of available services.
In the future
DAS servers like
Dazzle
or
Proserver
perhaps can automatically connect to the registration service and register or
renew the lease for a DAS service.
Projects
Projects that fund DAS sources can be acknowledged.
We are currently in the process in adding support for this also on the DAS client side.
I.e. next to a DAS track the logo of the funding project should be displayed.
Validation
The registration server contains a
validation
mechanism, to make sure that a DAS source is registered properly. When
registering a new service an accession code (segment id) needs to be
provided. This is used to create a DAS request and validate the
response. A service can only be registered if the provided accession
code returns a DAS response that contains data.
To prevent the registration service from keeping track of old or even
non-functional DAS services, a
lease is assigned to each. If the
lease
is not renewed for a long period, a server might be removed from the
registry, after a warning has been submitted to the administrator of the
DAS service.
Reference
Please cite:
Mailing List
There is an
announce
mailing list at
to keep you informed about the latest news.
Authors:
Andreas Prlic, Thomas Down, Eugene
Kulesha, Andreas Kähäri, Tim Hubbard.
Thanks to Jody Clements, Andy Jenkinson, Tony Cox and the Sanger Web Team, Stefan
Gräf, Brendan Vaugham.
Release history:
see the history of releases
here.
Feedback and suggestions: