Authorised Test Units and Pre-Release Apple Software Sample Clauses

Authorised Test Units and Pre-Release Apple Software. As long as an Authorised Test Unit contains any pre-release versions of the Apple Software or uses pre-release versions of Services, You agree to restrict access to such Authorised Test Unit to Your Authorised Developers and to not disclose, show, rent, lease, lend, sell or otherwise transfer such Authorised Test Unit to any third party. You further agree to take reasonable precautions to safeguard, and to instruct Your Authorised Developers to safeguard, all Authorised Test Units from loss or theft. Further, subject to the terms of this Agreement, You may deploy Your Applications to Your Authorised Developers for use on a limited number of Authorised Test Units for Your own internal testing and development purposes. You acknowledge that by installing any pre-release Apple Software or using any pre- release Services on Your Authorised Test Units, these Units may be “locked” into testing mode and may not be capable of being restored to their original condition. Any use of any pre-release Apple Software or pre-release Services are for evaluation and development purposes only, and You should not use any pre-release Apple Software or pre-release Services in a commercial operating environment or with important data. You should back up any data prior to using the pre-release Apple Software or pre-release Services. Apple shall not be responsible for any costs, expenses or other liabilities You may incur as a result of provisioning Your Authorised Test Units and Registered Devices, Your Covered Product development or the installation or use of this Apple Software or any pre-release Apple Services, including but not limited to any damage to any equipment, or any damage, loss or corruption of any software, information or data.
Sample 1Sample 2
AutoNDA by SimpleDocs

Related to Authorised Test Units and Pre-Release Apple Software

  • Supplemental JBoss Software Conditions Software Access and Software Maintenance for Supplemental JBoss Software is intended and available for Development Purposes only and for up to 25 users for each 16 Core Band Subscription of Red Hat JBoss Middleware Software that you purchased. If you deploy or use the Supplemental JBoss Software for Production Purposes or for more than 25 users, you agree to purchase the appropriate Software Subscriptions for each Unit that you deploy or use. Red Hat’s Open Source Assurance Program applies only to the Red Hat JBoss Middleware Software Subscription that you purchased (such as Red Hat JBoss Enterprise Application Platform in the example above) and does not apply to Supplemental JBoss Software. JBoss xPaaS Subscriptions (defined below) are not considered Supplemental JBoss Software. Each installation and use of JBoss xPaaS Subscriptions Software for either Development Purposes or Production Purposes is a Unit and requires a paid Software Subscription.

  • Loop Provisioning Involving Integrated Digital Loop Carriers 2.6.1 Where InterGlobe has requested an Unbundled Loop and BellSouth uses IDLC systems to provide the local service to the End User and BellSouth has a suitable alternate facility available, BellSouth will make such alternative facilities available to InterGlobe. If a suitable alternative facility is not available, then to the extent it is technically feasible, BellSouth will implement one of the following alternative arrangements for InterGlobe (e.g. hairpinning):

  • EODUF Packing Specifications 7.3.1 The data will be packed using ATIS EMI records. A pack will contain a minimum of one (1) message record or a maximum of ninety-nine thousand nine hundred and ninety-nine (99,999) message records plus a pack header record and a pack trailer record. One transmission can contain a maximum of ninety-nine (99) packs and a minimum of one (1) pack.

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

  • MSAA Indicator Technical Specification Document This Agreement shall be interpreted with reference to the MSAA Indicator Technical Specifications document.

  • Harvest Share Use Section 7.2 is administrative except to the extent that it applies to the 17 Sector managers ability to impose and utilize legal means to recover Liquated damages as 18 authorized in section §10.10 of this agreement, in which case NMFS enforcement procedures 19 may apply.

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

  • PROPRIETARY/RESTRICTIVE SPECIFICATIONS If a prospective bidder considers the specification contained herein to be proprietary or restrictive in nature, thus potentially resulting in reduced competition, they are urged to contact the Procurement Division prior to bid opening. Specifications which are unrelated to performance will be considered for deletion via addendum to this Invitation for Bids.

  • Red Hat Enterprise Linux Desktop Software Subscriptions Software Subscriptions for Red Hat Enterprise Linux Desktops and Workstations are subject to the parameters set forth in Table 6 below. Each Red Hat Enterprise Linux Desktop and Workstation Software Subscription includes one Red Hat Network system entitlement and one Smart Management Module, each to be used solely with a single Red Hat Enterprise Linux Desktop or Workstation System. Production Support for Red Hat Enterprise Linux Desktop subscriptions is limited to web-based support only for your helpdesk support personnel. Red Hat is not obligated to support your end users directly.

  • ODUF Packing Specifications 6.3.1 The data will be packed using ATIS EMI records. A pack will contain a minimum of one (1) message record or a maximum of ninety-nine thousand nine hundred and ninety-nine (99,999) message records plus a pack header record and a pack trailer record. One transmission can contain a maximum of ninety-nine (99) packs and a minimum of one (1) pack.

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