Screen-To-Screen Movements Sample Clauses

Open Split View

Download

Share

Cite

Screen-To-Screen Movements. All screen-to-screen movements by users shall be less than one-half of one 0.5 second.

Sample 1Sample 2

Save

Copy

Related to Screen-To-Screen Movements

• AUDIT OF LICENSED PRODUCT USAGE Contractor shall have the right to periodically audit, no more than annually, at Contractor’s expense, use of licensed Product at any site where a copy of the Product resides provided that: (i) Contractor gives Licensee(s) at least thirty (30) days advance written notice, (ii) such audit is conducted during such party’s normal business hours, (iii) the audit is conducted by an independent auditor chosen on mutual agreement of the parties. Contractor shall recommend a minimum of three (3) auditing/accounting firms from which the Licensee will select one (1). In no case shall the Business Software Alliance (BSA), Software Publishers Association (SPA), Software and Industry Information Association (SIIA) or Federation Against Software Theft (FAST) be used directly or indirectly to conduct audits, or be recommended by Contractor; (iv) Contractor and Licensee are each entitled to designate a representative who shall be entitled to participate, and who shall mutually agree on audit format, and simultaneously review all information obtained by the audit. Such representatives also shall be entitled to copies of all reports, data or information obtained from the audit; and (v) if the audit shows that such party is not in compliance, Licensee shall be required to purchase additional licenses or capacities necessary to bring it into compliance and shall pay for the unlicensed capacity at the NYS Net Price in effect at time of audit, or if none, then at the Contractor’s U.S. Commercial list price. Once such additional licenses or capacities are purchased, Licensee shall be deemed to have been in compliance retroactively, and Licensee shall have no further liability of any kind for the unauthorized use of the software.

• Posting licensed content on any Website The following terms and conditions apply as follows: Licensing material from an Elsevier journal: All content posted to the web site must maintain the copyright information line on the bottom of each image; A hyper-text must be included to the Homepage of the journal from which you are licensing at xxxx://xxx.xxxxxxxxxxxxx.xxx/science/journal/xxxxx or the Elsevier homepage for books at xxxx://xxx.xxxxxxxx.xxx; Central Storage: This license does not include permission for a scanned version of the material to be stored in a central repository such as that provided by Heron/XanEdu. Licensing material from an Elsevier book: A hyper-text link must be included to the Elsevier homepage at xxxx://xxx.xxxxxxxx.xxx . All content posted to the web site must maintain the copyright information line on the bottom of each image.

• Market Data Zero Hash may make certain information and research data, including historical market information available to you through the Platform or Zero Hash System, as applicable (“Market Data”). Market Data may be provided through third-party providers and may be updated at different time intervals, and accordingly, quotes, news, research data, market information and the various trade status reports, including intraday updates of balances and positions information and may differ due to the different Market Data and sources and their update intervals. Any such Market Data is provided as-is and for informational purposes only. Zero Hash makes no representation as to the accuracy or completeness of any Market Data. Further, Market Data may represent aggregated data from across multiple third-party trading venues and does not necessarily represent the prices of any asset as made available by Zero Hash or ZH Liquidity. Your reliance on any Market Data is at your sole discretion. The provision of Market Data relating to any asset shall not be considered Zero Hash’s, or its affiliates, endorsement of any such asset. You understand and agree that past performance of any asset is not indicative of future performance. You shall not decompile or redistribute any Market Data.

• Job Postings and Applications ‌ If a vacancy or a new job is created for which union personnel might reasonably be recruited, the following shall apply: (a) If the vacancy or new job has a duration of thirty (30) calendar days or more, the vacancy or new job including salary range, a summary of the job description, the required qualifications, the hours of work, including start and stop times and days off, the work area and the commencement date shall, before being filled, be posted for a minimum of seven (7) calendar days, in a manner which gives all employees access to such information, provided that no employees shall be entitled to relieve other regular employees under this clause on more than two (2) occasions in one calendar year unless the Employer and the Union otherwise agree in good faith. (b) Notwithstanding (a) above, if a temporary absence is one of less than ninety (90) calendar days, the work of the absent employee may be performed by employees working in float pool positions, where float pools exist. (c) Notwithstanding (a) above, if the vacancy is a temporary one of less than ninety (90) calendar days and the work is not being performed by a float employee, the position shall not be posted and instead shall be filled as follows: (i) where practicable by qualified regular employees who have indicated in writing their desire to work in such position consistent with the requirements of Article 14. Should a vacancy under this Article result in backfilling of more than one (1) vacancy (including the initial vacancy) the second (2nd) vacancy may be filled by an employee registered for casual work unless the Employer and the Union agree otherwise in good faith. If the application of this paragraph requires the Employer to pay overtime to the employee pursuant to Article 19, the proposed move shall not be made. An employee who accepts work under this provision is not eligible to work in another Article 16.01(c) assignment that conflicts with the accepted one. Probationary employees and employees undergoing a qualifying period shall not be considered for a 16.01(c) assignment in a different classification. (ii) by employees registered for casual work in accordance with the casual addendum. (iii) in cases of unanticipated or unplanned temporary absences, such temporary absence may first be filled under (c)(ii) for a period of up to seven (7) days. (d) A part-time employee who has accepted a casual assignment which conflicts with a temporary vacancy referred to in paragraph (c)(i) above shall be considered unavailable for such temporary vacancy. A part-time employee who has accepted a temporary vacancy referred to in paragraph (c)(i) above which conflicts with a casual assignment shall be considered unavailable for such casual assignment. Where an employee declines an offer to work under (c)(i) the Employer need not offer the work again to that employee under (c)(ii), if she/he is also registered for casual work. (e) Existing local agreements will be in force and effect (including termination clauses) unless changed by mutual agreement by the parties at the local level. (f) Where the local agreement covering access to work by part-time employees (former “15.01c”) does not contain a termination clause, the agreement may be terminated on giving of six (6) months’ notice by either party. (g) By mutual agreement, the parties may vary the job posting process set out in Article 16.01.

• Other Methods of Procurement of Goods and Works The following table specifies the methods of procurement, other than International Competitive Bidding, which may be used for goods and works. The Procurement Plan shall specify the circumstances under which such methods may be used: (a) National Competitive Bidding (b) Shopping (c) Direct Contracting

• Trademark Clearinghouse 4.1 Notwithstanding the requirements of Section 2.8 of the Agreement, Section 1 of Specification 7 to the Agreement and Section 2 of the Trademark Clearinghouse Rights Protection Mechanism Requirements (the “TMCH Requirements”), Registry Operator is not required to provide a Sunrise Period (as defined in the TMCH Requirements) or, except as set forth herein, otherwise comply with the obligations set forth in Section 2 of the TMCH Requirements (collectively, the “Sunrise Requirements”) so long as the TLD continues to be qualified as a .Brand TLD by ICANN. 4.2 Registry Operator must comply with all other provisions of the TMCH Requirements, including completing the Integration Testing required by Section 1 of the TMCH Requirements and providing the Claims Services required by Section 3 of the TMCH Requirements. Registry Operator will provide ICANN (i) confirmation of completion of Integration Testing and (ii) notice of the start date (the “Claims Commencement Date”) and end date for the Claims Period (as defined in the TMCH Requirements) for the TLD, in each case via the customer services portal at xxxx://xxxxxxx.xxxxxx.xxxxx.xxx/. Registry Operator may not Allocate (as defined in the TMCH Requirements) or register a domain name in the TLD (except for “NIC” and self-­‐allocation or registration to itself of domain names pursuant to Section 3.2 of Specification 5) prior to the Claims Commencement Date. 4.3 Registry Operator must comply with the Sunrise Requirements effective as of the Disqualification Date and commence a Sunrise Period within 60 calendar days of the Disqualification Date. If, at the Disqualification Date, the Trademark Clearinghouse or any successor or alternative trademark validation authority appointed by ICANN is not in operation, Registry Operator must implement the Sunrise Requirements through an alternative mechanism developed by Registry Operator that is reasonably acceptable to ICANN. As of the Disqualification Date, Registry Operator may not Allocate or register any additional domain names to third parties prior to the Allocation or registration of all Sunrise Period registrations except as permitted by Section 2.2.4 of the TMCH Requirements. In the event ICANN develops an alternative version of the TMCH Requirements specifically for .Brand TLDs or former .Brand TLDs, Registry Operator agrees to comply with such alternative requirements if such requirements are similar to the TMCH Requirements in effect as of the date hereof as modified by this Specification 13.

• Optional Daily Usage File (ODUF 11.1 The Optional Daily Usage File (ODUF) Agreement with terms and conditions is included in this Attachment as Exhibit D. Rates for ODUF are as set forth in Exhibit F of this Attachment. 11.2 BellSouth will provide ODUF service upon written request to its Account Manager stating a requested activation date.

• Originating Switched Access Detail Usage Data A category 1101XX record as defined in the EMI Telcordia Practice BR-010-200- 010.

• PREVAILING WAGE RATES - PUBLIC WORKS AND BUILDING SERVICES CONTRACTS If any portion of work being Bid is subject to the prevailing wage rate provisions of the Labor Law, the following shall apply:

• Line Information Database LIDB is a transaction-oriented database accessible through Common Channel Signaling (CCS) networks. For access to LIDB, ONS must purchase appropriate signaling links pursuant to Section 10 of this Attachment. LIDB contains records associated with End User Line Numbers and Special Billing Numbers. LIDB accepts queries from other Network Elements and provides appropriate responses. The query originator need not be the owner of LIDB data. LIDB queries include functions such as screening billed numbers that provides the ability to accept Collect or Third Number Billing calls and validation of Telephone Line Number based non-proprietary calling cards. The interface for the LIDB functionality is the interface between BellSouth’s CCS network and other CCS networks. LIDB also interfaces to administrative systems.