-
Notifications
You must be signed in to change notification settings - Fork 3
Description
Regarding the MANGO model
I am using a particular commit in my mapping, namely
https://raw.githubusercontent.com/ivoa-std/MANGO/a46441f6fc498a6aeb33ed97e65689fee3d00f6c/vo-dml/mango.vo-dml.xml
Referring only to the "last" commit may break certain mappings if the model changes.
Should do the same with the Cube and the various STC models I suppose.
I ran into some issues there that MCD fixed.
It would be nice if all the mappings that we compare here use exactly the same versions of the models. Can we define such a set? Note that these need to be internally consistent as well when considering model imports.
There are some problems with the VO-DML for that mango model:
The validation in the volute vo-dml folder produces some xsd problems, mainly pattern validation errors caused by leading spaces.
More importantly the following model errors were found:
- Target role of subsets constraint on 'exterrors.MultiParamError1D' with vodml-ref mango:errors.MultiParamError.correlatedErrors can not be found
- Target role of subsets constraint on 'exterrors.MultParamErro2D' with vodml-ref mango:exterrors.MultiParamError.correlatedErrrors can not be found
- datatype mango:extcoords.FlagState of composition extcoords.FlagSys.statusLabels is not an object type but a 'dataType'