-
Notifications
You must be signed in to change notification settings - Fork 2
Open
Description
Extra metadata fields would be useful for generating documentation:
descriptionfor all elementsreferenceorcitationfor documenting which standard defined the keyword/column (HDUs already have HDUCLASS/HDUDOC)unitorphysical_typefor cards (for docs, and maybe validation by string conversion). Note that the FITS standard suggests having the unit in square brackets in the comment string, i.e.EMAX = 1.2 / [TeV] The maximum energy, though it is not enforced. However, for VODF we could check for the existence of the correct unit in the doc and warn if not.ivoa_keyreference/citation of where this key/column/hdu was defineducdfor definingColumnUCDs (maybe also for Headers, only for documentation as there is no way to store it?)exampleslike in JSONSchema for headers at least (a list of example strings)
Metadata
Metadata
Assignees
Labels
No labels