| ||||||||
Changed: | ||||||||
< < | Note: VEPs are proposed in a draft of version 2.0 of Vocabularies. This currently is in the state of a proof of concept. | |||||||
> > | Vocabulary Enhancement Proposals is how IVOA Vocabularies are evolved as | |||||||
Added: | ||||||||
> > | specified in Vocabularies in the VO 2.0. | |||||||
Changed: | ||||||||
< < | The next VEP will have the running number 011. Please update this after uploading a new VEP. | |||||||
> > | To add a VEP, please write a message to semantics@ivoa.net rather than | |||||||
Added: | ||||||||
> > | changing this page directly. The next VEP will have the running number 011. | |||||||
VEPs"> Current VEPsVEP-006: Definitions of datalink/core#calibration and its descendants. VEP-007: Definition of datalink/core#detached-header. VEP-009: Modification of datalink/core#progenitor VEP-010: Creation of datalink/core#packageVEPs"> 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.<--
|