Evaluation License If You are licensing the Software for evaluation purposes, Your use of the Software is only permitted in a non-production environment and for the period limited by the License Key. Notwithstanding any other provision in this ▇▇▇▇, an Evaluation License of the Software is provided “AS-IS” without indemnification, support or warranty of any kind, expressed or implied.
Subproviders and Suppliers List Pursuant to requirements of 43 Texas Administrative Code §9.350 et seq., the Engineer must provide the State a list (Exhibit H-5/DBE or Exhibit H-6/HUB) of all Subproviders and suppliers that submitted quotes or proposals for subcontracts. This list shall include subproviders and suppliers names, addresses, telephone numbers, and type of work desired.
Evaluation Licenses Access to the Software may be provided to User for beta, demonstration, test, or evaluation purposes, (collectively, “Evaluation Licenses”). For any Evaluation Licenses, the term shall be limited to ninety (90) days (the “Evaluation Period”), unless otherwise agreed to by Honeywell in writing. Evaluation Licenses are limited specifically to use for evaluation or demonstration purposes only, and User agrees not to use such Software in a production or non-test environment. User’s use of the Software under an Evaluation License is provided as-is, without any representations or warranties of any kind, and is at User’s sole risk. Honeywell has no obligation to support, maintain or provide any assistance regarding any Evaluation Licenses. IN NO EVENT WILL HONEYWELL BE LIABLE FOR ANY DAMAGES OF ANY KIND IN RELATION TO ANY EVALUATION LICENSE OR EVALUATION OF THE SOFTWARE BY USER, INCLUDING, WITHOUT LIMITATION, ANY DIRECT, INDIRECT, SPECIAL, INCIDENTAL, EXEMPLARY, STATUTORY, PUNITIVE, OR CONSEQUENTIAL DAMAGES (INCLUDING, WITHOUT LIMITATION, LOST PROFITS, LOST DATA, DAMAGE TO SYSTEMS OR EQUIPMENT, OR BUSINESS INTERRUPTION). NEITHER USER NOR ANY PROVIDER IS ENTITLED TO ANY DEFENSE OR INDEMNIFICATION FOR EVALUATION LICENSES GRANTED PURSUANT TO THIS SECTION.
Proposed Policies and Procedures Regarding New Online Content and Functionality By February 1, 2017, the Division will submit to OCR for its review and approval proposed policies and procedures (“the Plan for New Content”) to ensure that all new, newly-added, or modified online content and functionality will be accessible to people with disabilities as measured by conformance to the Benchmarks for Measuring Accessibility set forth above, except where doing so would impose a fundamental alteration or undue burden. a) When fundamental alteration or undue burden defenses apply, the Plan for New Content will require the Division to provide equally effective alternative access. The Plan for New Content will require the Division, in providing equally effective alternate access, to take any actions that do not result in a fundamental alteration or undue financial and administrative burdens, but nevertheless ensure that, to the maximum extent possible, individuals with disabilities receive the same benefits or services as their nondisabled peers. To provide equally effective alternate access, alternatives are not required to produce the identical result or level of achievement for persons with and without disabilities, but must afford persons with disabilities equal opportunity to obtain the same result, to gain the same benefit, or to reach the same level of achievement, in the most integrated setting appropriate to the person’s needs. b) The Plan for New Content must include sufficient quality assurance procedures, backed by adequate personnel and financial resources, for full implementation. This provision also applies to the Division online content and functionality developed by, maintained by, or offered through a third-party vendor or by using open sources. c) Within thirty (30) days of receiving OCR’s approval of the Plan for New Content, the Division will officially adopt and fully implement the amended policies and procedures.
Technical Feasibility of String While ICANN has encouraged and will continue to encourage universal acceptance of all top-‐level domain strings across the Internet, certain top-‐level domain strings may encounter difficulty in acceptance by ISPs and webhosters and/or validation by web applications. Registry Operator shall be responsible for ensuring to its satisfaction the technical feasibility of the TLD string prior to entering into this Agreement.