-
Notifications
You must be signed in to change notification settings - Fork 3
Mark Cresitello-Dittmar edited this page Mar 2, 2021
·
6 revisions
- [MCD] The models used in these serializations do not map to any existing model/model-in-progress with the possible exception of Dataset.
This makes it difficult to compare annotations since the basis is not the same.
- [MCD] Annotation syntax allows for duplicating content, or referencing PARAM|FIELD if ID is available
- so, I think this syntax has minimal impact on the native content.
- FIELDs, I suppose, MUST have an ID. This is true with all of the annotation schemes?
- [MCD] Relies on clients to use VOTable content to fully resolve model elements.
- use FIELD ucd="phot.flux" or "phot.mag" to identify/destinguish the nature of the axis as Magnitude vs Flux
The UCD value is the ONLY difference. Well, the PhotCal instance includes a reference to the respective columns, but that is not part of the PhotDM model.
- use FIELD ucd="phot.flux" or "phot.mag" to identify/destinguish the nature of the axis as Magnitude vs Flux
Please put your name or initials in the front of your constributions (see the guide)