SSA 1.1

[Pierre Le Sidaner]

Thanks Doug

That was also my idea of testing errata, that's why I have send the 
first email also to TCG

Regards
Pierre

On 11/18/2014 03:21 PM, Douglas Tody wrote:
> The theoretical spectra example was always pretty rough - it would be
> great if it were updated.  Perhaps (for the TCG) this would qualify as
> an errata?  - Doug
>
>
> On Tue, 18 Nov 2014, Carlos Rodrigo wrote:
>
>> Hi
>>
>> Given that the example for theoretical spectra in the document is 
>> based in one of our services, I
>> think that I should say something here... :)
>>
>> Doug's answer has clarified most of the things that I intended to write
>>
>> In fact, there are several metadata that are mandatory and are not in 
>> the example:
>>
>> Char.SpatialAxis.Coverage.Location.Value
>> Char.SpatialAxis.Coverage.Bounds.Extent
>> Char.TimeAxis.Coverage.Location.Value
>> Char.SpectralAxis.Coverage.Location.Value
>> Char.SpectralAxis.Coverage.Bounds.Extent
>>
>> The first three ones does not (usually) make sense for theoretical 
>> spectra so I think that we can
>> apply what Doug says.
>>
>> The last two ones make sense for theoretical spectra and they are not 
>> in the example, so I think
>> that it would be good to add them. In fact, at first sight, I guess 
>> that the example was writen so
>> much time ago and it does not reflect some changes in the document, 
>> so it would be nice to rewrite
>> it a little. In fact, there are more things that should be changed in 
>> the example. For instance,
>> url's are outdated and they don't work (the domain laeff.inta.es does 
>> not exist anymore)
>>
>> So, if it is ok, I could write an updated version of the example
>>
>> Carlos
>>
>>
>> On 11/18/2014 02:33 PM, Douglas Tody wrote:
>>> Hi Pierre -
>>>
>>> Section 4.1 of the spec addresses the issue of theory data and notes
>>> that some metadata may not have meaning for certain types of data
>>> collections such as theory data.  However the section talks about query
>>> constraints (input parameter semantics) and I agree is not explicit
>>> about what to do with the query response.  The implication though, and
>>> what was intended, is that if metadata such as spatial position is not
>>> meaningful for the data collection, these values should be omitted in
>>> the query response.  Hence your option #2 below applies; metadata is 
>>> not
>>> mandatory (i.e. may be set to null) if not defined for a specific data
>>> collection such as as theory data.
>>>
>>>     - Doug
>>>
>>>
>>> On Tue, 18 Nov 2014, Pierre Le Sidaner wrote:
>>>
>>>> Dear IVOA members
>>>>
>>>> I am facing a little problem with my SSA validator
>>>> following the documentation metadata such as 
>>>> Char.SpatialAxis.Coverage.Location.Value are
>>>> mandatory in the query response
>>>> but example in the text for response of Theory-SSA omit some of them.
>>>>
>>>> My question is :
>>>> Am I badly reading the documentation ?
>>>> should we modify the mandatory fields for non "observational" SSA
>>>> Should we modify the example of Theorical SSA
>>>>
>>>> regards
>>>> Pierre
>>>>
>>>> -- 
>>>> ------------------------------------------------------------------------- 
>>>>
>>>>                           Pierre Le Sidaner
>>>>                        Observatoire de Paris
>>>>
>>>> Division Informatique de l'Observatoire
>>>> Observatoire Virtuel 01 40 51 20 89
>>>> 61, avenue de l'Observatoire 75014 Paris
>>>>
>>>> mailto:pierre.lesidaner at obspm.fr
>>>> http://vo.obspm.fr
>>>>
>>>> -------------------------------------------------------------------------- 
>>>>
>>>>
>>


-- 
-------------------------------------------------------------------------
                            Pierre Le Sidaner
                         Observatoire de Paris

Division Informatique de l'Observatoire
Observatoire Virtuel 01 40 51 20 89
61, avenue de l'Observatoire 75014 Paris

mailto:pierre.lesidaner at obspm.fr
http://vo.obspm.fr

--------------------------------------------------------------------------