IUCN Red List Sample Clauses

IUCN Red List. Data on threats to species represent a core part of Red List assessments, and BirdLife International collates and compiles the latest information on threats to species through its ongoing programme to reassess all bird species every four years. The assessment of threats is done at species level via a combination of expert consultation (in collaboration with e.g. the respective IUCN Species Survival Commission (SSC) Specialist Groups) and bibliographic searches for studies reporting threats to each species. AEWA has applied the Red List threat assessment system in its action planning process. Information on major threats to all Globally Threatened and Near Threatened species is required (coded to the lowest level) using a standard hierarchal Threats Classification Scheme developed by the IUCN . This threat classification scheme is based on a hierarchal scheme of three levels, with 11, 31 and 99 nested categories respectively, and was developed to improve information sharing and learning among conservation practitioners (Xxxxxxxx et al. 2008) aiming to help practitioners, managers and/ or decisionmakers to: • Identify threats occurring at a site or affecting species. • Tally the frequency of threats across sites, at various scales. • Link targets, threats, contributing factors and actions, and to be able to share these datasets. An overall Impact score for each threat and species is estimated as the sum of individual scores of timing (when the threat is taking place), scope (extent of the population affected) and severity (rate of reduction of the population). Each of these factors is scored between 0 and 3 (Table 4.1). The overall level of impact for each is assigned as: • High impact (score 8-9) • Medium impact (score 6-7) • Low impact (score 3-5) • Negligible/ no impact (score 0-2) Table 4.1: Scoring of timing, scope and severity for the IUCN Red List14
AutoNDA by SimpleDocs

Related to IUCN Red List

  • RDDS query RTT Refers to the collective of “WHOIS query RTT” and “Web-­‐based-­‐ WHOIS query RTT”.

  • WHOIS query RTT Refers to the RTT of the sequence of packets from the start of the TCP connection to its end, including the reception of the WHOIS response. If the RTT is 5-­‐times or more the corresponding SLR, the RTT will be considered undefined.

  • JOC Pricing of Itemized List of Means Non-Prepriced Items” based on the information herein. This Addendum is only to correct a misstatement on the original optional attachment entitled “PART 2 JOC Pricing of Itemized List of Means Non-Prepriced Items.” The attachment mistakenly provided for and discussed “Attribute 39.” Specifically, any erroneous reference to “Attribute 39” on the specified attachment should be considered immediately replaced with “the Attribute Question asking for Pricing for Markup of Non- Prepriced Items in RS Means Unit Price Book.” Please disregard any reference to Attribute 39 on this optional form and consider it to be referencing the Attribute Question asking for “Pricing for Markup of Non-Prepriced Items in RS Means Unit Price Book” instead.

  • PRIORITY RATING If so identified, this Contract is a "rated order" certified for national defense, emergency preparedness, and energy program use, and SELLER shall follow all the requirements of the Defense Priorities and Allocation System Regulation (15 C.F.R. Part 700).

  • DNS name server availability Refers to the ability of a public-­‐DNS registered “IP address” of a particular name server listed as authoritative for a domain name, to answer DNS queries from an Internet user. All the public DNS-­‐registered “IP address” of all name servers of the domain name being monitored shall be tested individually. If 51% or more of the DNS testing probes get undefined/unanswered results from “DNS tests” to a name server “IP address” during a given time, the name server “IP address” will be considered unavailable.

  • Borrowing Base Report The Agent shall have received from the Borrower the initial Borrowing Base Report dated as of the Closing Date.

  • FORMAT AND CONTENT FOR REGISTRY OPERATOR MONTHLY REPORTING Registry Operator shall provide one set of monthly reports per gTLD, using the API described in draft-­‐xxxxxx-­‐icann-­‐registry-­‐interfaces, see Specification 2, Part A, Section 9, reference 5, with the following content. ICANN may request in the future that the reports be delivered by other means and using other formats. ICANN will use reasonable commercial efforts to preserve the confidentiality of the information reported until three (3) months after the end of the month to which the reports relate. Unless set forth in this Specification 3, any reference to a specific time refers to Coordinated Universal Time (UTC). Monthly reports shall consist of data that reflects the state of the registry at the end of the month (UTC).

  • Schedule of Specific Commitments 1. Each Party shall set out in a schedule the specific commitments it undertakes under Article 106 (National Treatment), Article 000 (Xxxxxx Xxxxxx) and Article 108 (Additional Commitments). With respect to sectors where such commitments are undertaken, each Schedule shall specify: (a) terms, limitations and conditions on market access; (b) conditions and qualifications on national treatment; (c) undertakings relating to additional commitments referred to in Article 108 (Additional Commitments); and (d) where appropriate, the time-frame for implementation of such commitments and the date of entry into force of such commitments. 2. Measures inconsistent with both Articles 106 (National Treatment) and 000 (Xxxxxx Xxxxxx) are inscribed in the column relating to Article 107 (Market Access). In this case, the inscription is considered to provide a condition or qualification to Article 106 (National Treatment) as well. 3. The Parties' Schedules of Specific Commitments are set out in Annex 6 (Schedules of Specific Commitments).

  • Selection Under a Fixed Budget Services for assignments which the Association agrees meet the requirements of paragraph 3.5 of the Consultant Guidelines may be procured under contracts awarded on the basis of a Fixed Budget in accordance with the provisions of paragraphs 3.1 and 3.5 of the Consultant Guidelines.

  • Seniority List The Employer shall maintain a seniority list showing the date upon which each employee's service commenced. An up-to-date seniority list shall be sent to the Union and posted on all bulletin boards in January of each year.

Draft better contracts in just 5 minutes Get the weekly Law Insider newsletter packed with expert videos, webinars, ebooks, and more!