tdwg/hc

New Term - areNonTargetTaxaFullyReported

Closed this issue · 1 comments

tucotuco commented

New term

  • Submitter: Humboldt Extension Task Group

  • Efficacy Justification (why is this term necessary?): Part of a package of terms in support of biological inventory data.

  • Demand Justification (name at least two organizations that independently need this term): The Humboldt Extension Task Group proposing this term consists of numerous organizations.

  • Stability Justification (what concerns are there that this might affect existing implementations?): None

  • Implications for dwciri: namespace (does this change affect a dwciri term version)?: Needs ecoiri: equivalent.
    Proposed attributes of the new term:

  • Term name (in lowerCamelCase for properties, UpperCamelCase for classes): areNonTargetTaxaFullyReported

  • Term label (English, not normative): Are Non-target Taxa Fully Reported

  • Organized in Class (e.g., Occurrence, Event, Location, Taxon): Event

  • Definition of the term (normative): Every dwc:Organism that was outside of the target taxonomic scope (the combination of eco:targetTaxonomicScope and eco:excludedTaxonomicScope) and detected during the dwc:Event, and that was detectable using the given protocol (given in eco:protocolDescription and dwc:samplingProtocol), was reported.

  • Usage comments (recommendations regarding content, etc., not normative): This term is meant to inform a user of the data whether there were non-target taxa that were detected, but left unreported. This term is only relevant if the dwc:Event used restricted search or open search methods and if a target taxonomic scope is declared. Taxonomic scope is based on the combination of eco:targetTaxonomicScope and eco:excludedTaxonomicScope. Within dwc:Events that used either a restricted search or an open search method and declared a taxonomic scope, if all dwc:Organisms that are not included within the target taxonomic scope and that were detected during the dwc:Event were reported, the value of this term should be 'true', otherwise the value of this term should be false'.

  • Examples (not normative): true; false

  • Refines (identifier of the broader term this term refines; normative): None

  • Replaces (identifier of the existing term that would be deprecated and replaced by this term; normative): None

  • ABCD 2.06 (XPATH of the equivalent term in ABCD or EFG; not normative): not in ABCD

tucotuco commented

In the Technical Architecture Group meeting on 2023-09-11 it was recommended that the comments for boolean terms include a statement such as, "Recommended best practice is to comply with the recommendations provided in the Boolean Controlled Vocabulary document (https://tag.tdwg.org/boolean/)."