You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
"the UTYPEs all begin with the prefix "Spectrum.".
And illustrate with an example:
"UTYPEs such as 'Curation.Contact.Email' should be instantiated as 'Spectrum.Curation.Contact.Email'.
There are 2 example VOTables in Section 8.
The first appears to have completely ignored this requirement so that basically all of the UTYPEs in that example are invalid.
The second (SSA) example is much better, there are a couple GROUPs without the 'Spectrum.'. However, this model does not define UTYPEs for the objects, only leaves.. so this may be valid per the SSAP specification.
A sweep should be made to correct the example.
The text was updated successfully, but these errors were encountered:
* separate doc and diagrams
* rename main tex file, clean up Makefile
* step toward ivoatex Makefile
* rename files; step toward ivoatex. no content change
* Update README.md
* rename and relocate schema
* switch to pdflatex; update diagrams to UML
* Create preview.xml
* Update README.md
* Rename preview.xml to preview.yml
* Update preview.yml
* Update preview.yml
* Update preview.yml
* Update preview.yml
* Update preview.yml
* Update preview.yml
* Update preview.yml
* add overview diagram; individual, not in doc
* add spectral order elements
* add spectral order elements
* add upper/lower limit elements
* correct case of order and relorder attributes
* fix document date
* Update README.md
add link to PDF-preview
* Update README.md
fix URL (oy!)
* Fix for Issue #6: bad utypes in example1
* Fix for Issue #5: ucd assigment for upper/lower limits
* Migrate to PR status
* Update to REC
---------
Co-authored-by: Laurent MICHEL <[email protected]>
Section 3.5 of the document states that
And illustrate with an example:
There are 2 example VOTables in Section 8.
A sweep should be made to correct the example.
The text was updated successfully, but these errors were encountered: