This document describes how you can contribute to The Chronometric Age vocabulary.
Changes to the standard are subject to section 3 Change Process of the TDWG Vocabulary Maintenance Specification under the Darwin Core Maintenance Interest Group. Here's how you can contribute:
- Want to make a change to the standard? Copy and paste one of the issue templates below and submit a new issue.
- Want to contribute to this repository? Fork the repository, make the changes, and send a pull request.
- Have a question about the Chronometric Age vocabulary? Send it to [email protected] or to the Darwin Core Questions & Answers repository through this form or directly as a new issue.
Copy and paste this template into your new issue if you want to create a term that does not exist yet.
## New term
* Submitter:
* Justification (why is this term necessary?):
* Proponents (at least two independent parties who need this term):
Proposed attributes of the new term:
* Class: ChronometricAge
* Term name (in lowerCamelCase):
* Definition of the term:
* Usage comments (recommendations regarding content, etc.):
* Examples:
* Refines (identifier of the broader term this term refines, if applicable):
* Replaces (identifier of the existing term that would be deprecated and replaced by this term, if applicable):
* ABCD 2.06 (XPATH of the equivalent term in ABCD or EFG, if applicable):
Copy and paste this template into your new issue if you want to make a change to a term.
## Change term
* Term identifier (URL of the term to change):
* Justification (why is this change necessary?):
* Submitter:
I suggest the following changes (leave blank whatever would not change):
* Class: ChronometricAge
* Term name (in lowerCamelCase):
* Definition of the term:
* Usage comments (recommendations regarding content, etc.):
* Examples:
* Refines (identifier of the broader term this term refines, if applicable):
* Replaces (identifier of the existing term that would be deprecated and replaced by this term, if applicable):
* ABCD 2.06 (XPATH of the equivalent term in ABCD or EFG, if applicable):
Copy and paste this template into your new issue if you want to make a change to the documentation. Or, fork the repository, make the changes yourself, and send a pull request.
## Change documentation
* Documentation reference (URL):
* Submitter:
* Justification (why is this change necessary?):
I suggest the following changes: