VEPs"> Current VEPs | ||||||||
Deleted: | ||||||||
< < | ||||||||
VEP-016: Addition of date_role#ExportRequested
VEP-009: Modification of datalink/core#progenitor
VEPs"> Accepted VEPsVEP-002: datalink/core#documentation VEP-004: datalink/core#counterpart VEP-005: datalink/core#coderived VEP-006: Definitions of datalink/core#calibration and its descendants. VEP-007: Definition of datalink/core#detached-header. VEP-010: Creation of datalink/core#package VEP-011: Creation of datalink/core#thumbnail VEP-013: date_role#Inspected VEP-014: Addition of product-type#spatial-profile VEP-017: Update of RefFrame#geo-appVEPs"> 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). VEP-012: date_role#Validated VEP-015: Addition of relationship_type#References | ||||||||
Deleted: | ||||||||
< < | VEP-017: Documentation of refframe#geo_app | |||||||
Vocabulary Enhancement Proposals (VEPs)See Vocabularies in the VO version 2 for how to write VEPs and how they are processed.<--
|
VEPs"> Current VEPs | ||||||||
Deleted: | ||||||||
< < | VEP-017: Documentation of refframe#geo_app | |||||||
VEP-016: Addition of date_role#ExportRequested
VEP-009: Modification of datalink/core#progenitor
VEPs"> Accepted VEPsVEP-002: datalink/core#documentation VEP-004: datalink/core#counterpart VEP-005: datalink/core#coderived VEP-006: Definitions of datalink/core#calibration and its descendants. VEP-007: Definition of datalink/core#detached-header. VEP-010: Creation of datalink/core#package VEP-011: Creation of datalink/core#thumbnail VEP-013: date_role#Inspected VEP-014: Addition of product-type#spatial-profile VEP-017: Update of RefFrame#geo-appVEPs"> 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). VEP-012: date_role#Validated VEP-015: Addition of relationship_type#References | ||||||||
Changed: | ||||||||
< < | Vocabulary Enhancement Requests (VEPs) | |||||||
> > | VEP-017: Documentation of refframe#geo_app | |||||||
Added: | ||||||||
> > |
Vocabulary Enhancement Proposals (VEPs) | |||||||
See Vocabularies in the VO version 2 for how to write VEPs and how they are processed.
<--
|
VEPs"> Current VEPs | ||||||||
Added: | ||||||||
> > | VEP-017: Documentation of refframe#geo_app | |||||||
VEP-016: Addition of date_role#ExportRequested
VEP-009: Modification of datalink/core#progenitor
VEPs"> Accepted VEPsVEP-002: datalink/core#documentation VEP-004: datalink/core#counterpart VEP-005: datalink/core#coderived VEP-006: Definitions of datalink/core#calibration and its descendants. VEP-007: Definition of datalink/core#detached-header. VEP-010: Creation of datalink/core#package VEP-011: Creation of datalink/core#thumbnail VEP-013: date_role#Inspected VEP-014: Addition of product-type#spatial-profile VEP-017: Update of RefFrame#geo-appVEPs"> 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). VEP-012: date_role#Validated VEP-015: Addition of relationship_type#ReferencesVocabulary Enhancement Requests (VEPs)See Vocabularies in the VO version 2 for how to write VEPs and how they are processed.<--
|
| ||||||||
Changed: | ||||||||
< < | The next VEP will have the running number 017. | |||||||
> > | The next VEP will have the running number 018. | |||||||
VEPs"> Current VEPsVEP-016: Addition of date_role#ExportRequested | ||||||||
Deleted: | ||||||||
< < | ||||||||
VEP-009: Modification of datalink/core#progenitor
VEPs"> Accepted VEPsVEP-002: datalink/core#documentation VEP-004: datalink/core#counterpart VEP-005: datalink/core#coderived VEP-006: Definitions of datalink/core#calibration and its descendants. VEP-007: Definition of datalink/core#detached-header. VEP-010: Creation of datalink/core#package VEP-011: Creation of datalink/core#thumbnail VEP-013: date_role#Inspected VEP-014: Addition of product-type#spatial-profile | ||||||||
Added: | ||||||||
> > | VEP-017: Update of RefFrame#geo-app | |||||||
VEPs"> 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). VEP-012: date_role#Validated VEP-015: Addition of relationship_type#ReferencesVocabulary Enhancement Requests (VEPs)See Vocabularies in the VO version 2 for how to write VEPs and how they are processed.<--
|
VEPs"> Current VEPsVEP-016: Addition of date_role#ExportRequested | ||||||||
Deleted: | ||||||||
< < | VEP-014: Addition of product-type#spatial-profile | |||||||
VEP-009: Modification of datalink/core#progenitor
VEPs"> Accepted VEPsVEP-002: datalink/core#documentation VEP-004: datalink/core#counterpart VEP-005: datalink/core#coderived VEP-006: Definitions of datalink/core#calibration and its descendants. VEP-007: Definition of datalink/core#detached-header. VEP-010: Creation of datalink/core#package VEP-011: Creation of datalink/core#thumbnail VEP-013: date_role#Inspected | ||||||||
Added: | ||||||||
> > | VEP-014: Addition of product-type#spatial-profile | |||||||
VEPs"> 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). VEP-012: date_role#Validated VEP-015: Addition of relationship_type#ReferencesVocabulary Enhancement Requests (VEPs)See Vocabularies in the VO version 2 for how to write VEPs and how they are processed.<--
|
VEPs"> Current VEPsVEP-016: Addition of date_role#ExportRequested | ||||||||
Deleted: | ||||||||
< < | VEP-015: Addition of relationship_type#References | |||||||
VEP-014: Addition of product-type#spatial-profile
VEP-009: Modification of datalink/core#progenitor
VEPs"> Accepted VEPsVEP-002: datalink/core#documentation VEP-004: datalink/core#counterpart VEP-005: datalink/core#coderived VEP-006: Definitions of datalink/core#calibration and its descendants. VEP-007: Definition of datalink/core#detached-header. VEP-010: Creation of datalink/core#package VEP-011: Creation of datalink/core#thumbnail VEP-013: date_role#InspectedVEPs"> 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). VEP-012: date_role#Validated | ||||||||
Added: | ||||||||
> > | VEP-015: Addition of relationship_type#References | |||||||
Vocabulary Enhancement Requests (VEPs)See Vocabularies in the VO version 2 for how to write VEPs and how they are processed.<--
|
| ||||||||
Changed: | ||||||||
< < | The next VEP will have the running number 014. | |||||||
> > | The next VEP will have the running number 017. | |||||||
VEPs"> Current VEPs | ||||||||
Added: | ||||||||
> > | VEP-016: Addition of date_role#ExportRequested VEP-015: Addition of relationship_type#References VEP-014: Addition of product-type#spatial-profile | |||||||
VEP-009: Modification of datalink/core#progenitor
VEPs"> Accepted VEPsVEP-002: datalink/core#documentation VEP-004: datalink/core#counterpart VEP-005: datalink/core#coderived VEP-006: Definitions of datalink/core#calibration and its descendants. VEP-007: Definition of datalink/core#detached-header. VEP-010: Creation of datalink/core#package VEP-011: Creation of datalink/core#thumbnail VEP-013: date_role#InspectedVEPs"> 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). VEP-012: date_role#ValidatedVocabulary Enhancement Requests (VEPs)See Vocabularies in the VO version 2 for how to write VEPs and how they are processed.<--
|
VEPs"> Current VEPsVEP-009: Modification of datalink/core#progenitor | ||||||||
Deleted: | ||||||||
< < | ||||||||
VEPs"> Accepted VEPsVEP-002: datalink/core#documentation VEP-004: datalink/core#counterpart VEP-005: datalink/core#coderived VEP-006: Definitions of datalink/core#calibration and its descendants. VEP-007: Definition of datalink/core#detached-header. VEP-010: Creation of datalink/core#package VEP-011: Creation of datalink/core#thumbnail VEP-013: date_role#InspectedVEPs"> 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). VEP-012: date_role#ValidatedVocabulary Enhancement Requests (VEPs)See Vocabularies in the VO version 2 for how to write VEPs and how they are processed.<--
|
VEPs"> Current VEPsVEP-009: Modification of datalink/core#progenitor | ||||||||
Deleted: | ||||||||
< < | VEP-013: date_role#Inspected | |||||||
VEPs"> Accepted VEPsVEP-002: datalink/core#documentation VEP-004: datalink/core#counterpart VEP-005: datalink/core#coderived VEP-006: Definitions of datalink/core#calibration and its descendants. VEP-007: Definition of datalink/core#detached-header. VEP-010: Creation of datalink/core#package VEP-011: Creation of datalink/core#thumbnail | ||||||||
Added: | ||||||||
> > | VEP-013: date_role#Inspected | |||||||
VEPs"> 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). VEP-012: date_role#ValidatedVocabulary Enhancement Requests (VEPs)See Vocabularies in the VO version 2 for how to write VEPs and how they are processed.<--
|
| ||||||||
Changed: | ||||||||
< < | The next VEP will have the running number 013. | |||||||
> > | The next VEP will have the running number 014. | |||||||
VEPs"> Current VEPsVEP-009: Modification of datalink/core#progenitor | ||||||||
Changed: | ||||||||
< < | VEP-012: date_role#Validated | |||||||
> > | VEP-013: date_role#Inspected | |||||||
VEPs"> Accepted VEPsVEP-002: datalink/core#documentation VEP-004: datalink/core#counterpart VEP-005: datalink/core#coderived VEP-006: Definitions of datalink/core#calibration and its descendants. VEP-007: Definition of datalink/core#detached-header. VEP-010: Creation of datalink/core#package VEP-011: Creation of datalink/core#thumbnailVEPs"> 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). | ||||||||
Added: | ||||||||
> > | VEP-012: date_role#Validated | |||||||
Vocabulary Enhancement Requests (VEPs)See Vocabularies in the VO version 2 for how to write VEPs and how they are processed.<--
|
| ||||||||
Changed: | ||||||||
< < | The next VEP will have the running number 012. | |||||||
> > | The next VEP will have the running number 013. | |||||||
VEPs"> Current VEPsVEP-009: Modification of datalink/core#progenitor | ||||||||
Added: | ||||||||
> > | VEP-012: date_role#Validated | |||||||
VEPs"> Accepted VEPsVEP-002: datalink/core#documentation VEP-004: datalink/core#counterpart VEP-005: datalink/core#coderived VEP-006: Definitions of datalink/core#calibration and its descendants. VEP-007: Definition of datalink/core#detached-header. VEP-010: Creation of datalink/core#package VEP-011: Creation of datalink/core#thumbnailVEPs"> 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.<--
|
| ||||||||
Changed: | ||||||||
< < | Vocabulary Enhancement Proposals is how IVOA Vocabularies are evolved as | |||||||
> > | Vocabulary Enhancement Proposals is how IVOA Vocabularies are evolved as specified in Vocabularies in the VO 2.0. | |||||||
Deleted: | ||||||||
< < | specified in Vocabularies in the VO 2.0. | |||||||
Changed: | ||||||||
< < | To add a VEP, please write a message to semantics@ivoa.net rather than | |||||||
> > | To add a VEP, please write a message to semantics@ivoa.net rather than changing this page directly. | |||||||
Deleted: | ||||||||
< < | changing this page directly. | |||||||
The next VEP will have the running number 012.
VEPs"> Current VEPs | ||||||||
Changed: | ||||||||
< < | VEP-009: | |||||||
> > | VEP-009: Modification of datalink/core#progenitor | |||||||
Deleted: | ||||||||
< < | Modification of datalink/core#progenitor | |||||||
Deleted: | ||||||||
< < | VEP-010: Creation of datalink/core#package | |||||||
Deleted: | ||||||||
< < | VEP-011: Creation of datalink/core#thumbnail | |||||||
VEPs"> Accepted VEPsVEP-002: datalink/core#documentation VEP-004: datalink/core#counterpart VEP-005: datalink/core#coderived | ||||||||
Changed: | ||||||||
< < | VEP-006: | |||||||
> > | VEP-006: Definitions of datalink/core#calibration and its descendants. | |||||||
Deleted: | ||||||||
< < | Definitions of datalink/core#calibration and its descendants. | |||||||
VEP-007: Definition of datalink/core#detached-header. | ||||||||
Added: | ||||||||
> > | VEP-010: Creation of datalink/core#package | |||||||
Added: | ||||||||
> > | VEP-011: Creation of datalink/core#thumbnail | |||||||
VEPs"> Abandoned VEPsVEP-001: DataLink: Associated-DataSet branch VEP-003: datalink/core#sibling | ||||||||
Changed: | ||||||||
< < | VEP-008: definition of | |||||||
> > | VEP-008: definition of product-type#dynamic-spectrum. (was procedurally unnecessary as product-type still was preliminary as a whole at that point). | |||||||
Deleted: | ||||||||
< < | product-type#dynamic-spectrum. (was procedurally unnecessary as product-type still was preliminary as a whole at that point). | |||||||
Vocabulary Enhancement Requests (VEPs) | ||||||||
Changed: | ||||||||
< < | See Vocabularies in the VO version 2 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. | |||||||
<--
|
VEPs"> Current VEPs | ||||||||
Deleted: | ||||||||
< < | VEP-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#package
VEP-011:
Creation of datalink/core#thumbnail
VEPs"> Accepted VEPsVEP-002: datalink/core#documentation VEP-004: datalink/core#counterpart VEP-005: datalink/core#coderived | ||||||||
Added: | ||||||||
> > | VEP-006: Definitions of datalink/core#calibration and its descendants. VEP-007: Definition of datalink/core#detached-header. | |||||||
VEPs"> 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.<--
|
| ||||||||
Changed: | ||||||||
< < | The next VEP will have the running number 011. | |||||||
> > | The next VEP will have the running number 012. | |||||||
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#package | ||||||||
Added: | ||||||||
> > | VEP-011: Creation of datalink/core#thumbnail | |||||||
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.<--
|
| ||||||||
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.<--
|
| ||||||||
Changed: | ||||||||
< < | The next VEP will have the running number 010. Please update this after uploading a new VEP. | |||||||
> > | The next VEP will have the running number 011. Please update this after uploading a new VEP. | |||||||
VEPs"> Current VEPsVEP-006: | ||||||||
Changed: | ||||||||
< < | definitions of datalink/core#calibration | |||||||
> > | Definitions of datalink/core#calibration | |||||||
and its descendants. | ||||||||
Changed: | ||||||||
< < | VEP-007: definition of datalink/core#detached-header. | |||||||
> > | VEP-007: Definition of datalink/core#detached-header. | |||||||
VEP-009: Modification of datalink/core#progenitor | ||||||||
Added: | ||||||||
> > | VEP-010: Creation of datalink/core#package | |||||||
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.<--
|
| ||||||||
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.<--
|
VEPs"> Current VEPsVEP-006: definitions of datalink/core#calibration and its descendants. VEP-007: definition of datalink/core#detached-header. | ||||||||
Deleted: | ||||||||
< < | VEP-008: definition of product-type#dynamic-spectrum. | |||||||
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 | ||||||||
Added: | ||||||||
> > | 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.<--
|
| ||||||||
Changed: | ||||||||
< < | The next VEP will have the running number 008. Please update this after uploading a new VEP. | |||||||
> > | The next VEP will have the running number 009. Please update this after uploading a new VEP. | |||||||
VEPs"> Current VEPsVEP-006: definitions of datalink/core#calibration and its descendants. | ||||||||
Changed: | ||||||||
< < | VEP-007: definitions of | |||||||
> > | VEP-007: definition of | |||||||
datalink/core#detached-header. | ||||||||
Added: | ||||||||
> > | VEP-008: definition of product-type#dynamic-spectrum. | |||||||
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#siblingVocabulary Enhancement Requests (VEPs)See Vocabularies in the VO version 2 for how to write VEPs and how they are processed.<--
|
| ||||||||
Changed: | ||||||||
< < | The next VEP will have the running number 007. Please update this after uploading a new VEP. | |||||||
> > | The next VEP will have the running number 008. Please update this after uploading a new VEP. | |||||||
VEPs"> Current VEPsVEP-006: definitions of datalink/core#calibration and its descendants. | ||||||||
Added: | ||||||||
> > | VEP-007: definitions of datalink/core#detached-header. | |||||||
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#siblingVocabulary Enhancement Requests (VEPs)See Vocabularies in the VO version 2 for how to write VEPs and how they are processed.<--
|
VEPs"> Current VEPs | ||||||||
Changed: | ||||||||
< < | (None at this point) | |||||||
> > | VEP-006: definitions of | |||||||
Added: | ||||||||
> > | datalink/core#calibration and its descendants. | |||||||
VEPs"> Accepted VEPs | ||||||||
Changed: | ||||||||
< < | VEP-002: DataLink: documentation | |||||||
> > | VEP-002: datalink/core#documentation | |||||||
VEP-004: datalink/core#counterpart
VEP-005: datalink/core#coderived
VEPs"> Abandoned VEPsVEP-001: DataLink: Associated-DataSet branch VEP-003: datalink/core#siblingVocabulary Enhancement Requests (VEPs)See Vocabularies in the VO version 2 for how to write VEPs and how they are processed.<--
|
| ||||||||
Changed: | ||||||||
< < | The next VEP will have the running number 006. Please update this after uploading a new VEP. | |||||||
> > | The next VEP will have the running number 007. Please update this after uploading a new VEP. | |||||||
VEPs"> Current VEPs(None at this point)VEPs"> Accepted VEPsVEP-002: DataLink: documentation VEP-004: datalink/core#counterpart VEP-005: datalink/core#coderived | ||||||||
Deleted: | ||||||||
< < | ||||||||
VEPs"> Abandoned VEPsVEP-001: DataLink: Associated-DataSet branch VEP-003: datalink/core#siblingVocabulary Enhancement Requests (VEPs)See Vocabularies in the VO version 2 for how to write VEPs and how they are processed.<--
|
VEPs"> Current VEPs | ||||||||
Changed: | ||||||||
< < | VEP-004: datalink/core#counterpart | |||||||
> > | (None at this point) | |||||||
Deleted: | ||||||||
< < | VEP-005: datalink/core#coderived | |||||||
VEPs"> Accepted VEPsVEP-002: DataLink: documentation | ||||||||
Added: | ||||||||
> > | VEP-004: datalink/core#counterpart VEP-005: datalink/core#coderived | |||||||
VEPs"> Abandoned VEPsVEP-001: DataLink: Associated-DataSet branch VEP-003: datalink/core#siblingVocabulary Enhancement Requests (VEPs)See Vocabularies in the VO version 2 for how to write VEPs and how they are processed.<--
|
| ||||||||
Changed: | ||||||||
< < | The next VEP will have the running number 005. Please update this after uploading a new VEP. | |||||||
> > | The next VEP will have the running number 006. Please update this after uploading a new VEP. | |||||||
VEPs"> Current VEPs | ||||||||
Deleted: | ||||||||
< < | VEP-003: datalink/core#sibling | |||||||
VEP-004: datalink/core#counterpart | ||||||||
Added: | ||||||||
> > | VEP-005: datalink/core#coderived | |||||||
VEPs"> Accepted VEPsVEP-002: DataLink: documentationVEPs"> Abandoned VEPsVEP-001: DataLink: Associated-DataSet branch | ||||||||
Added: | ||||||||
> > | VEP-003: datalink/core#sibling | |||||||
Vocabulary Enhancement Requests (VEPs)See Vocabularies in the VO version 2 for how to write VEPs and how they are processed.<--
|
| ||||||||
Changed: | ||||||||
< < | The next VEP will have the running number 004. Please update this after uploading a new VEP. | |||||||
> > | The next VEP will have the running number 005. Please update this after uploading a new VEP. | |||||||
VEPs"> Current VEPs | ||||||||
Added: | ||||||||
> > | VEP-003: datalink/core#sibling | |||||||
Changed: | ||||||||
< < | VEP-003: datalink/core#sibling | |||||||
> > | VEP-004: datalink/core#counterpart | |||||||
VEPs"> Accepted VEPsVEP-002: DataLink: documentationVEPs"> Abandoned VEPsVEP-001: DataLink: Associated-DataSet branchVocabulary Enhancement Requests (VEPs)See Vocabularies in the VO version 2 for how to write VEPs and how they are processed.<--
|
VEPs"> Current VEPs | ||||||||
Deleted: | ||||||||
< < | VEP-002: DataLink: documentation | |||||||
VEP-003: datalink/core#sibling
VEPs"> Accepted VEPs | ||||||||
Changed: | ||||||||
< < | (None so far) | |||||||
> > | VEP-002: DataLink: documentation | |||||||
VEPs"> Abandoned VEPsVEP-001: DataLink: Associated-DataSet branchVocabulary Enhancement Requests (VEPs)See Vocabularies in the VO version 2 for how to write VEPs and how they are processed.<--
|
| ||||||||
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 004. Please update this after uploading a new VEP. | |||||||
VEPs"> Current VEPsVEP-002: DataLink: documentation | ||||||||
Changed: | ||||||||
< < | VEP-003: datalink/core#sibling | |||||||
> > | VEP-003: datalink/core#sibling | |||||||
VEPs"> Accepted VEPs(None so far)VEPs"> Abandoned VEPsVEP-001: DataLink: Associated-DataSet branchVocabulary Enhancement Requests (VEPs)See Vocabularies in the VO version 2 for how to write VEPs and how they are processed.<--
|
VEPs"> Current VEPs | ||||||||
Changed: | ||||||||
< < | VEP-001: DataLink: Associated-DataSet branch | |||||||
> > | VEP-002: DataLink: documentation | |||||||
Changed: | ||||||||
< < | VEP-002: DataLink: DataDocumentation | |||||||
> > | VEP-003: datalink/core#sibling | |||||||
VEPs"> Accepted VEPs(None so far) | ||||||||
Added: | ||||||||
> > |
VEPs"> Abandoned VEPsVEP-001: DataLink: Associated-DataSet branch | |||||||
Vocabulary Enhancement Requests (VEPs)See Vocabularies in the VO version 2 for how to write VEPs and how they are processed.<--
|
| ||||||||
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: | ||||||||
< < |
| |||||||
> > |
| |||||||
| ||||||||
Changed: | ||||||||
< < | The next VEP will have the running number 0002. 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 | |||||||
> > | DataLink vocabulary enhancement proposal: Associated-DataSet branch | |||||||
Added: | ||||||||
> > | DataLink vocabulary enhancement proposal: DataDocumentation term | |||||||
VEPs"> Accepted VEPs(None so far)Vocabulary Enhancement Requests (VEPs)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.<--
| ||||||||
Changed: | ||||||||
< < |
| |||||||
> > |
| |||||||
Added: | ||||||||
> > |
| |||||||
| ||||||||
Changed: | ||||||||
< < | The next VEP will have the running number 0001. Please update this after uploading a new VEP. | |||||||
> > | The next VEP will have the running number 0002. Please update this after uploading a new VEP. | |||||||
VEPs"> Current VEPs | ||||||||
Changed: | ||||||||
< < | (None yet) | |||||||
> > | DataLink vocabulary enhancement proposal | |||||||
VEPs"> Accepted VEPs(None so far)Vocabulary Enhancement Requests (VEPs)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.<--
| ||||||||
Added: | ||||||||
> > |
| |||||||
| ||||||||
Changed: | ||||||||
< < | Note: This is a proposal by MarkusDemleitner for how to manage vocabulary evolution in the IVOA at this point. | |||||||
> > | Note: VEPs are proposed in a draft of version 2.0 of Vocabularies. This currently is in the state of a proof of concept. | |||||||
Added: | ||||||||
> > | The next VEP will have the running number 0001. Please update this after uploading a new VEP. | |||||||
VEPs"> Current VEPs | ||||||||
Changed: | ||||||||
< < |
| |||||||
> > | (None yet) | |||||||
Deleted: | ||||||||
< < | (please attach your VEP and put the link into this enumeration) | |||||||
VEPs"> Accepted VEPs(None so far)Vocabulary Enhancement Requests (VEPs) | ||||||||
Changed: | ||||||||
< < | We propose to manage vocabulary evolution in the IVOA through Vocabulary Enhancement Requests. These are small, version controllable, plain text files; the current version of a VEP is maintained on this page, currently in an attachment. | |||||||
> > | 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. | |||||||
Deleted: | ||||||||
< < |
A VEP is semistructured; in a header, it should first give the vocabulary URL and a contact address for the author, as in
Vocabulary: http://www.ivoa.net/rdf/datalink/core Author: msdemlei@ari.uni-heidelberg.deThis is followed by one or more blocks. These can be proposals for new terms, given with a human-readable label, a description, and a rationale for the addition. For instance: New Term: isMetadataFor (child of auxiliary) Label: Metadata Description: additional documentation for this dataset (e.g., observatory logs, provenance information) Rationale: This would annotate material such as observation logs, scanned envelopes of plates, or possibly logs of pipeline runs. The term is a bit different from other datalink terms, but it is taken from the DataCite relationships, and I feel re-using these terms whenever possible makes it easier to re-use datalink annotations later.Alternatively, changes to an existing term can be proposed, including changing its parent: Changed term: proc Label: Processing Description: reference to a server-side processing service Rationale: The old description ("server-side data processing result") just doesn't quite match what this is.No process for the deletion of terms is proposed at this point. A VEP may be replaced during discussions. | |||||||
<--
|
VEPs"> Current VEPs
VEPs"> Accepted VEPs(None so far)Vocabulary Enhancement Requests (VEPs)We propose to manage vocabulary evolution in the IVOA through Vocabulary Enhancement Requests. These are small, version controllable, plain text files; the current version of a VEP is maintained on this page, currently in an attachment. A VEP is semistructured; in a header, it should first give the vocabulary URL and a contact address for the author, as inVocabulary: http://www.ivoa.net/rdf/datalink/core Author: msdemlei@ari.uni-heidelberg.deThis is followed by one or more blocks. These can be proposals for new terms, given with a human-readable label, a description, and a rationale for the addition. For instance: New Term: isMetadataFor (child of auxiliary) Label: Metadata Description: additional documentation for this dataset (e.g., observatory logs, provenance information) Rationale: This would annotate material such as observation logs, scanned envelopes of plates, or possibly logs of pipeline runs. The term is a bit different from other datalink terms, but it is taken from the DataCite relationships, and I feel re-using these terms whenever possible makes it easier to re-use datalink annotations later.Alternatively, changes to an existing term can be proposed, including changing its parent: Changed term: proc Label: Processing Description: reference to a server-side processing service Rationale: The old description ("server-side data processing result") just doesn't quite match what this is.No process for the deletion of terms is proposed at this point. A VEP may be replaced during discussions. <--
|