SAMP RFC: MType list

[Christophe Arviset]

Mark

Thanks for your answer. Indeed having the MTypes documented in some SAMP 
specific web pages will solve the "visibility" part of the question.

But I may have an other question about the process on how MTypes get 
added / removed / updated to that list?
On one side, we need to have some flexibility for these changes and I do 
NOT advocate to go through the standard REC process.
But on the other side, we also need to have some level of formality to 
control these changes.

What are your views on this ?

Thanks

Christophe


Mark Taylor wrote:
> This message is to address the point made by Jesus, Christophe and Bob
> on the SAMP RFC page that it's not clear from the SAMP document how 
> the list(s) of MTypes are or will be documented.
> This topic is mentioned in section 5.3 of the PR, but, as pointed out by
> the reviewers, not in very concrete terms, and specifically not in
> enough detail that a reader of this document can work out where to look
> to find more information.
>
> We've had some discussion on the apps-samp list in an earlier
> thread, and I made a query to the TCG about the possibilities for
> persistent URLs.  It seems that although this would require
> agreement by the IVOA Exec, it probably would be possible to get a URL 
> like "http://www.ivoa.net/samp/", which could, as a minimum, redirect 
> to an existing page on the IVOA wiki.
>
> Bringing these discussions together, I'd like to suggest the following.
> As far as the SAMP document goes, Section 5.3 will be re-written
> to make it clear that if you want to find out about or contribute
> to the existing list(s) of MTypes, what you should do is go to
> http://www.ivoa.net/samp/.  As a minimum, and in the first instance,
> that URL can redirect to the SampProgress wiki page
> (http://www.ivoa.net/cgi-bin/twiki/bin/view/IVOA/SampProgress).
> Although the content currently there is a bit scrappy, it is as it 
> stands sufficient for application authors to find the things they need 
> to know which are not in the SAMP document itself, including MTypes 
> currently in use.
>
> We might in the (perhaps near) future issue one or more IVOA Notes or 
> institute some other processes for formal or informal MType listings -
> however that works out, it will be documented prominently at that URL.
> We might also put some other things as well at that URL, along the 
> lines of what was on the PLASTIC web site.
> It may or may not be technically feasible for that URL to redirect
> to some other content in the future, but either way it remains the
> permanent public one-stop-shop for SAMP information.
>
> If the the reviewers who commented on this issue agree that this
> addresses their concerns, and if the Exec agree we can have a
> redirect from http://www.ivoa.net/samp/, then there are no
> remaining obstacles to progressing the SAMP document towards REC.
> We can continue to discuss the details of MType procedures and
> maybe other useful content on that site, but in a way that is
> decoupled from the SAMP standard itself.
>
> Jesus, Christophe and Bob: does that sound OK to you?
> Other interested parties: any objection?
>
> Mark
>

-- 
Thanks in advance

Cheers

Christophe


-------------------------------------------------------------------
Christophe ARVISET                       Christophe.Arviset at esa.int

European Space Agency (ESA)
European Space Astronomy Centre (ESAC)
Science Operations Department
Science Archives and Computer Support Engineering Unit

P.O. Box 78
28691 Villanueva de la Canada                 Tel: +34 91 813 12 78
Madrid - SPAIN                                Fax: +34 91 813 13 08
------------------------------------------------------------------- 


================================================================================================
This message and any attachments are intended for the use of the addressee or addressees only. The
unauthorised disclosure, use, dissemination or copying (either in whole or in part) of its content
is prohibited. If you received this message in error, please delete it from your system and notify
the sender. E-mails can be altered and their integrity cannot be guaranteed. ESA shall not be liable
for any e-mail if modified.
=================================================================================================