New Search Logic Sample Clauses

New Search Logic. Registry shall enable the public side website to display the search results based on the additional criteria set forth below.
AutoNDA by SimpleDocs

Related to New Search Logic

  • Alternative Work Schedule An alternate forty (40) hour work schedule (other than five (5) uniform and consecutive eight (8) hour days in a seven (7) day period), or for hospital personnel an eighty (80) hour workweek in a fourteen (14) day period and other mutually agreed upon schedules that comply with applicable federal and state law. Employee work schedules normally include two (2) consecutive days off.

  • Research Plan The Parties recognize that the Research Plan describes the collaborative research and development activities they will undertake and that interim research goals set forth in the Research Plan are good faith guidelines. Should events occur that require modification of these goals, then by mutual agreement the Parties can modify them through an amendment, according to Paragraph 13.6.

  • End User License Agreement This work is licensed under a Creative Commons Attribution-NonCommercial-NoDerivs 3.0 Unported License. xxxx://xxxxxxxxxxxxxxx.xxx/licenses/by-nc-nd/3.0/ You are free to: Share: to copy, distribute and transmit the work Under the following conditions: Attribution: You must attribute the work in the manner specified by the author (but not in any way that suggests that they endorse you or your use of the work).

  • Public Posting of Approved Users’ Research Use Statement The PI agrees that information about themselves and the approved research use will be posted publicly on the dbGaP website. The information includes the PI’s name and Requester, project name, Research Use Statement, and a Non-Technical Summary of the Research Use Statement. In addition, and if applicable, this information may include the Cloud Computing Use Statement and name of the CSP or PCS. Citations of publications resulting from the use of controlled-access datasets obtained through this DAR may also be posted on the dbGaP website.

  • Development Schedule The Project shall substantially comply with the specific timetables and triggers for action set forth in Article 5 of this Agreement. The parties acknowledge that, as provided in G.S. 160A-400.25(b), the failure to meet a commencement or completion date shall not, in and of itself, constitute a material breach of this Agreement pursuant to G.S. 160A-400.27 but must be judged based upon the totality of the circumstances.

  • Registration Data Directory Services Until ICANN requires a different protocol, Registry Operator will operate a WHOIS service available via port 43 in accordance with XXX 0000, and a web-­‐based Directory Service at <whois.nic.TLD> providing free public query-­‐based access to at least the following elements in the following format. ICANN reserves the right to specify alternative formats and protocols, and upon such specification, the Registry Operator will implement such alternative specification as soon as reasonably practicable. Registry Operator shall implement a new standard supporting access to domain name registration data (SAC 051) no later than one hundred thirty-­‐five (135) days after it is requested by ICANN if: 1) the IETF produces a standard (i.e., it is published, at least, as a Proposed Standard RFC as specified in RFC 2026); and 2) its implementation is commercially reasonable in the context of the overall operation of the registry.

  • Project Specific Milestones In addition to the milestones stated in Section 212.5 of the Tariff, as applicable, during the term of this ISA, Interconnection Customer shall ensure that it meets each of the following development milestones:

  • Commercialization Plan On a Product by Product basis, not later than sixty (60) days after the filing of the first application for Regulatory Approval of a Product in the Copromotion Territory, the MSC shall prepare and approve a rolling multiyear (not less than three (3) years) plan for Commercializing such Product in the Copromotion Territory (the "Copromotion Territory Commercialization Plan"), which plan includes a comprehensive market development, marketing, sales, supply and distribution strategy for such Product in the Copromotion Territory. The Copromotion Territory Commercialization Plan shall be updated by the MSC at least once each calendar year such that it addresses no less than the three (3) upcoming years. Not later than thirty (30) days after the filing of the first application for Regulatory Approval of a Product in the Copromotion Territory and thereafter on or before September 30 of each calendar year, the MSC shall prepare an annual commercialization plan and budget (the "Annual Commercialization Plan and Budget"), which plan is based on the then current Copromotion Territory Commercialization Plan and includes a comprehensive market development, marketing, sales, supply and distribution strategy, including an overall budget for anticipated marketing, promotion and sales efforts in the upcoming calendar year (the first such Annual Development Plan and Budget shall cover the remainder of the calendar year in which such Product is anticipated to be approved plus the first full calendar year thereafter). The Annual Commercialization Plan and Budget will specify which Target Markets and distribution channels each Party shall devote its respective Promotion efforts towards, the personnel and other resources to be devoted by each Party to such efforts, the number and positioning of Details to be performed by each Party, as well as market and sales forecasts and related operating expenses, for the Product in each country of the Copromotion Territory, and budgets for projected Pre-Marketing Expenses, Sales and Marketing Expenses and Post-Approval Research and Regulatory Expenses. In preparing and updating the Copromotion Territory Commercialization Plan and each Annual Commercialization Plan and Budget, the MSC will take into consideration factors such as market conditions, regulatory issues and competition.

  • EPP query-­‐command RTT Refers to the RTT of the sequence of packets that includes the sending of a query command plus the reception of the EPP response for only one EPP query command. It does not include packets needed for the start or close of either the EPP or the TCP session. EPP query commands are those described in section 2.9.2 of EPP RFC 5730. If the RTT is 5-­‐times or more the corresponding SLR, the RTT will be considered undefined.

  • Development Plan document specifying the work program, schedule, and relevant investments required for the Development and the Production of a Discovery or set of Discoveries of Oil and Gas in the Contract Area, including its abandonment.

Time is Money Join Law Insider Premium to draft better contracts faster.