Update issue templates

I modified this to facility new term proposal submissions. It clarifies several aspects of what is requested of a submitter.
This commit is contained in:
John Wieczorek 2021-04-30 14:34:38 -03:00 committed by GitHub
parent 13ccfd10bf
commit 08a8facddb
1 changed files with 12 additions and 11 deletions

View File

@ -10,17 +10,18 @@ assignees: ''
## New term ## New term
* Submitter: * Submitter:
* Justification (why is this term necessary?): * Efficacy Justification (why is this term necessary?):
* Proponents (at least two independent parties who need this term): * Demand Justification (name at least two organizations that independently need this term):
* Stability Justification (what concerns are there that this might affect existing emplementations?):
Proposed attributes of the new term: Proposed attributes of the new term:
* Term name (in lowerCamelCase): * Term name (in lowerCamelCase for properties, UpperCamelCase for classes):
* Organized in Class (e.g. Location, Taxon): * Organized in Class (e.g., Occurrence, Event, Location, Taxon):
* Definition of the term: * Definition of the term (normative):
* Usage comments (recommendations regarding content, etc.): * Usage comments (recommendations regarding content, etc., not normative):
* Examples: * Examples (not normative):
* Refines (identifier of the broader term this term refines, if applicable): * Refines (identifier of the broader term this term refines; normative):
* Replaces (identifier of the existing term that would be deprecated and replaced by this term, if applicable): * Replaces (identifier of the existing term that would be deprecated and replaced by this term; normative):
* ABCD 2.06 (XPATH of the equivalent term in ABCD or EFG, if applicable): * ABCD 2.06 (XPATH of the equivalent term in ABCD or EFG; not normative):