Time/Target mandatory

[Markus Demleitner]

Hi Mark,

On Wed, Aug 13, 2014 at 12:51:00PM -0400, CresitelloDittmar, Mark wrote:
> > So, I guess the answer to that little riddle is that the Bounds
> > fields are "conditionally mandatory" ("*if* you have a TimeAxis,
> > then..."), right?
> >
> 
> No, a validator should require there to be either:
>   Char.TimeAxis.Coverage.Bounds.Extent
> or
>   Char.TimeAxis.Coverage.Bounds.Start
>   Char.TimeAxis.Coverage.Bounds.Stop

Hm -- so, what do I put there in my theoretical spectra?  Do I just
make up bogus dates?  Use the time of their computation?  A NULL
value?  But if the latter is allowed, what does "mandatory" mean in
the end?

Incidentally, this problem doesn't only arise for me, there are lots
of services serving theoretical spectra active in the VO.

> > Slightly related: If we make Target.Name mandatory (and I'm always
> > for doing away with optional things),
> 
> 
> I'm a little confused on this one.. Target.Name has always been MAN.
> I think that may be an error in the change doc.

Aha -- so, my SDM metadata inherited "mandatoriness" from SSA, where
Target.Name is optional (section 4.2.5.7), so whether or not it was
mandatory in SDM 1, I'm advocating a harmonisation of SSA and SDM.
In either direction -- is it intended to use SDM2 in SSA?

And I just notice I did assign target.name in my theoretical service
although it's optional in SSA.  It's "model star" for all the
different model stars that are in there.  Hm.

Since I feel some mild urge to improve the situation: Are there any
opinions on what should be done in such cases, either from my little
list

> * Assign different names to the outcomes of different computations OR
> > * Assign identical names to the outcomes of computations with the
> >   same physics OR
> > * Have a constant target identifying the code ("Spectrum computed
> >   with Magic 3.23pl1") OR
> > * Just have "Artificial" in there always if there's no physical
> >   object
> >
> 
> Good point.. I'll keep it in mind for the cube model work.

or yet something else -- or maybe drop the requirement for
Target.Name entirely?  What, by the way, is the rationale for having
it mandatory?

Cheers,

      Markus