Functions Defeating the HDCP Specification. Licensed Products shall not include:
Functions Defeating the HDCP Specification Sample Clauses
Related to Functions Defeating the HDCP Specification
Contractors Submission Respecting the Agreement The Contractor shall, as part of the Contractor's submission respecting this Contract, complete the attached Schedule B, Identification of Principles; Schedule C, Schedule of Tendered Unit Prices; Schedule D, Schedule of Equipment to be used on the work; and Schedule E, Schedule of Sub-Contractors. The Contract including all appended schedules shall be completed in complete conformity with the instructions to bidders contained in the document entitled "General Provisions and Contract Specification for Highway Construction". In presenting the Contractor’s submission for consideration by the Minister, the Contractor understands that until, and unless, the Contract is endorsed by the Minister, no Contract between the parties shall exist and the Minister shall not be bound to endorse any Contract.
SERVICE MONITORING, ANALYSES AND ORACLE SOFTWARE 11.1 We continuously monitor the Services to facilitate Oracle’s operation of the Services; to help resolve Your service requests; to detect and address threats to the functionality, security, integrity, and availability of the Services as well as any content, data, or applications in the Services; and to detect and address illegal acts or violations of the Acceptable Use Policy. Oracle monitoring tools do not collect or store any of Your Content residing in the Services, except as needed for such purposes. Oracle does not monitor, and does not address issues with, non-Oracle software provided by You or any of Your Users that is stored in, or run on or through, the Services. Information collected by Oracle monitoring tools (excluding Your Content) may also be used to assist in managing Oracle’s product and service portfolio, to help Oracle address deficiencies in its product and service offerings, and for license management purposes.
Escrow Format Specification 3.1. Deposit’s Format. Registry objects, such as domains, contacts, name servers, registrars, etc. will be compiled into a file constructed as described in draft-xxxxx-xxxxxxx-registry-data-escrow, see Part A, Section 9, reference 1 of this Specification and draft-xxxxx-xxxxxxx-dnrd-objects-mapping, see Part A, Section 9, reference 2 of this Specification (collectively, the “DNDE Specification”). The DNDE Specification describes some elements as optional; Registry Operator will include those elements in the Deposits if they are available. If not already an RFC, Registry Operator will use the most recent draft version of the DNDE Specification available at the Effective Date. Registry Operator may at its election use newer versions of the DNDE Specification after the Effective Date. Once the DNDE Specification is published as an RFC, Registry Operator will implement that version of the DNDE Specification, no later than one hundred eighty (180) calendar days after. UTF-8 character encoding will be used.
Access Rights for implementation Access Rights to Results and Background Needed for the performance of the own work of a Party under the Project shall be granted on a royalty-free basis, unless otherwise agreed for Background in Attachment 1.
