| ||||||||
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. | |||||||
> > | Note: VEPs are proposed in a draft of version 2.0 of Vocabularies. This currently is in the state of a proof of concept. | |||||||
Changed: | ||||||||
< < | The next VEP will have the running number 0003. Please update this after uploading a new VEP. | |||||||
> > | The next VEP will have the running number 0003. Please update this after uploading a new VEP. | |||||||
VEPs"> Current VEPs | ||||||||
Changed: | ||||||||
< < | DataLink vocabulary enhancement proposal: Associated-DataSet branch | |||||||
> > | VEP-001: DataLink: Associated-DataSet branch | |||||||
Changed: | ||||||||
< < | DataLink vocabulary enhancement proposal: DataDocumentation term | |||||||
> > | VEP-002: DataLink: DataDocumentation | |||||||
Deleted: | ||||||||
< < | ||||||||
VEPs"> Accepted VEPs(None so far)Vocabulary Enhancement Requests (VEPs) | ||||||||
Changed: | ||||||||
< < | See Vocabularies in the VO version 2 [TODO: add a link once it's updated] for how to write VEPs and how they are processed. | |||||||
> > | See Vocabularies in the VO version 2 for how to write VEPs and how they are processed. | |||||||
<--
| ||||||||
Changed: | ||||||||
< < |
| |||||||
> > |
| |||||||