| ||||||||
Changed: | ||||||||
< < | The next VEP will have the running number 009. Please update this after uploading a new VEP. | |||||||
> > | The next VEP will have the running number 010. Please update this after uploading a new VEP. | |||||||
VEPs"> Current VEPs | ||||||||
Changed: | ||||||||
< < | VEP-006: definitions of datalink/core#calibration | |||||||
> > | VEP-006: definitions of datalink/core#calibration | |||||||
and its descendants. | ||||||||
Changed: | ||||||||
< < | VEP-007: definition of | |||||||
> > | VEP-007: definition of datalink/core#detached-header. | |||||||
Deleted: | ||||||||
< < | datalink/core#detached-header. | |||||||
Added: | ||||||||
> > | VEP-009: Modification of datalink/core#progenitor | |||||||
VEPs"> Accepted VEPsVEP-002: datalink/core#documentation VEP-004: datalink/core#counterpart VEP-005: datalink/core#coderivedVEPs"> Abandoned VEPsVEP-001: DataLink: Associated-DataSet branch VEP-003: datalink/core#sibling VEP-008: definition of product-type#dynamic-spectrum. (was procedurally unnecessary as product-type still was preliminary as a whole at that point).Vocabulary Enhancement Requests (VEPs)See Vocabularies in the VO version 2 for how to write VEPs and how they are processed.<--
|