regarding ALTTYPE [was RE: vo-dml in votable]

[Laurino, Omar]

Hi Mark,



On Wed, Mar 11, 2015 at 8:39 AM, Mark Taylor <m.b.taylor at bristol.ac.uk>
wrote:

> Regarding Omar's suggestion of a modified 4c
> with multiplicity 0..1, I would argue that this additional
> multiplicity restriction ought not to be written into the VOTable
> schema/standard itself; it would be very annoying to have to
> issue VOTable 1.5 one day just in order to change the value
> of a maxOccurs xs:element qualifier.
>

I agree, I just meant we should start prototyping with a solution that
could easily be turned into the other, before we finalize the new version
of the standard. I expect prototypes to inform more decisions other than
TYPE's multiplicity, and this is actually already happening as we update
the old implementations based on UTYPEs. It was decided to update VOTable,
it would be unwise not to change it with a well-thought solution.

Thanks,

Omar.


>
> Following that reasoning the VOTable (1.4?) standard could just
> define the elements VODML, TYPE and ROLE (multiple TYPEs allowed)
> without too much description of their semantics or usage, and point
> to the VODML mapping document for the details; that mapping document
> could then supply additional requirements or advice about TYPE
> multiplicity.  VOTable could then be somewhat insulated against
> future changes in the requirements or usage patterns of VODML
> metadata.
>
> Mark
>
> --
> Mark Taylor   Astronomical Programmer   Physics, Bristol University, UK
> m.b.taylor at bris.ac.uk +44-117-9288776  http://www.star.bris.ac.uk/~mbt/
>



-- 
Omar Laurino
Smithsonian Astrophysical Observatory
Harvard-Smithsonian Center for Astrophysics
100 Acorn Park Dr. R-377 MS-81
02140 Cambridge, MA
(617) 495-7227
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.ivoa.net/pipermail/apps/attachments/20150311/9e6c2192/attachment.html>