Use and exploitation of Background Sample Clauses

Open Split View

Download

Share

Cite

Use and exploitation of Background. Information and/or Sideground Information and/or Project Sideground Information and/or Improvements.

Sample 1Sample 2

Save

Copy

Related to Use and exploitation of Background

• Allocation of Registration Opportunities In any circumstance in which all of the Registrable Securities and other shares of the Company with registration rights (the “Other Shares”) requested to be included in a registration contemplated by Section 2(a) cannot be so included as a result of limitations of the aggregate number of shares of Registrable Securities and Other Shares that may be so included, the number of shares of Registrable Securities and Other Shares that may be so included shall be allocated among the Holders and Other Shareholders requesting inclusion of shares pro rata on the basis of the number of shares of Registrable Securities and Other Shares held by such Holders and Other Shareholders; provided, however, that such allocation shall not operate to reduce the aggregate number of Registrable Securities and Other Shares to be included in such registration, if any Holder or Other Shareholder does not request inclusion of the maximum number of shares of Registrable Securities and Other Shares allocated to such Holder or Other Shareholder pursuant to the above-described procedure, then the remaining portion of such allocation shall be reallocated among those requesting Holders and Other Shareholders whose allocations did not satisfy their requests pro rata on the basis of the number of shares of Registrable Securities and Other Shares which would be held by such Holders and Other Shareholders, assuming conversion, and this procedure shall be repeated until all of the shares of Registrable Securities and Other Shares which may be included in the registration on behalf of the Holders and Other Shareholders have been so allocated.

• Background Screening VENDOR shall comply with all requirements of Sections 1012.32 and 1012.465, Florida Statutes, and all of its personnel who (1) are to be permitted access to school grounds when students are present, (2) will have direct contact with students, or (3) have access or control of school funds, will successfully complete the background screening required by the referenced statutes and meet the standards established by the statutes. This background screening will be conducted by SBBC in advance of VENDOR or its personnel providing any services under the conditions described in the previous sentence. VENDOR shall bear the cost of acquiring the background screening required by Section 1012.32, Florida Statutes, and any fee imposed by the Florida Department of Law Enforcement to maintain the fingerprints provided with respect to VENDOR and its personnel. The parties agree that the failure of VENDOR to perform any of the duties described in this section shall constitute a material breach of this Agreement entitling SBBC to terminate immediately with no further responsibilities or duties to perform under this Agreement. VENDOR agrees to indemnify and hold harmless SBBC, its officers and employees from any liability in the form of physical or mental injury, death or property damage resulting from VENDOR’s failure to comply with the requirements of this section or with Sections 1012.32 and 1012.465, Florida Statutes.

• Use of Technology Participants are subject to all existing laws (federal and state) and University regulations and policies on use of technology, including not only those laws and regulations that are specific to computers and networks, but also those that may apply generally to personal conduct such as: • UC Electronic Communications Policy: xxxx://xxx.xxxx.xxx/ucophome/policies/ec/ • UCLA E-mail Policy and Guidelines: xxxx://xxx.xxxxxxxxxxxxx.xxxx.xxx/app/Default.aspx?&id=455 • IT Services Acceptable Use Policy: xxxx://xxx.xxx.xxxx.xxx/policies/aupdetail.html • The UC Policy on Copyright Ownership: xxxx://xxxxxxxxx.xxxxxxxxxxxxxxxxxxxxxx.xxx/resources/copyright-ownership.html • Bruin OnLine Service Level Agreement: xxxx://xxx.xxx.xxxx.xxx/policies/BOL_SLA.pdf Any violation may result in technology related privileges being restricted or revoked and may also result in The University undertaking disciplinary action. If the violation constitutes a criminal offense, appropriate legal action may be taken.

• General Background (Brief description of the national, sector-specific or other relevant context in which the individual contractor will operate)

• Project Background 6.1.1. Brief description of Contracting Agency’s project background and/or situation leading to this Project

• Ownership and Publication of Materials All reports, information, data, and other materials prepared by the Consultant pursuant to this agreement are the property of the City. The City has the exclusive and unrestricted authority to release, publish or otherwise use, in whole or part, information relating thereto. Any re-use without written verification or adaptation by the Consultant for the specific purpose intended will be at the City’s sole risk and without liability or legal exposure to the Consultant. No material produced in whole or in part under this agreement may be copyrighted or patented in the United States or in any other country without the prior written approval of the City.

• Certification Regarding Prohibition of Certain Terrorist Organizations (Tex Gov. Code 2270) Certification Regarding Prohibition of Boycotting Israel (Tex. Gov. Code 2271) 5 Certification Regarding Prohibition of Contracts with Certain Foreign-Owned Companies (Tex. Gov. 5 Code 2274) 5 Certification Regarding Prohibition of Discrimination Against Firearm and Ammunition Industries (Tex.

• 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.

• Transfer or Deletion of Student Data The Provider shall review, on an annual basis, whether the Student Data it has received pursuant to the DPA continues to be needed for the purpose(s) of the Service Agreement and this DPA. If any of the Student Data is no longer needed for purposes of the Service Agreement and this DPA, the Provider will provide written notice to the LEA as to what Student Data is no longer needed. The Provider will delete or transfer Student Data in readable form to the LEA, as directed by the LEA (which may be effectuated through Exhibit D of the DPA), within 30 calendar days if the LEA requests deletion or transfer of the Student Data and shall provide written confirmation to the LEA of such deletion or transfer. Upon termination of the Service Agreement between the Provider and LEA, Provider shall conduct a final review of Student Data within 60 calendar days. If the LEA receives a request from a parent, as that term is defined in 105 ILCS 10/2(g), that Student Data being held by the Provider be deleted, the LEA shall determine whether the requested deletion would violate State and/or federal records laws. In the event such deletion would not violate State or federal records laws, the LEA shall forward the request for deletion to the Provider. The Provider shall comply with the request and delete the Student Data within a reasonable time period after receiving the request. Any provision of Student Data to the LEA from the Provider shall be transmitted in a format readable by the LEA.

• Background and Purpose Executive was employed by the Company. Executive's employment is ending effective __________ under the conditions described in Section 3.1 of the Executive Change of Control Agreement ("Agreement") by and between Executive and the Company dated _____________, 2012. The purpose of this Release is to settle, and the parties hereby settle, fully and finally, any and all claims the Releasing Parties may have against the Released Parties, whether asserted or not, known or unknown, including, but not limited to, claims arising out of or related to Executive's employment, any claim for reemployment, or any other claims whether asserted or not, known or unknown, past or future, that relate to Executive's employment, reemployment, or application for reemployment.