Software Title parity Sample Clauses

Software Title parity. Each Software Title is subject to the following requirements:
Software Title parity. Each Software Title is subject to the following requirements: 9.1. Features and content parity. 9.1.1. [***] 9.1.2. [***] 9.2. Simship with Competitive Platforms. 9.2.1. [***] 9.2.2. [***]
Software Title parity. Section 9 (“Software Title Parity”) shall be replaced in full with the following: Software Title parity. Each Software Title is subject to the following requirements:
Software Title parity. Each FPU and DFU is subject to the following requirements:
Software Title parity. Section 9 of the Xbox One PLA (Software Title parity) shall be deleted in its entirety and replaced with the following:

Related to Software Title parity

  • Loop Provisioning Involving Integrated Digital Loop Carriers 2.6.1 Where Freedom 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 Freedom. 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 Freedom (e.g. hairpinning): 1. Roll the circuit(s) from the IDLC to any spare copper that exists to the customer premises. 2. Roll the circuit(s) from the IDLC to an existing DLC that is not integrated. 3. If capacity exists, provide "side-door" porting through the switch. 4. If capacity exists, provide "Digital Access Cross Connect System (DACS)- door" porting (if the IDLC routes through a DACS prior to integration into the switch). 2.6.2 Arrangements 3 and 4 above require the use of a designed circuit. Therefore, non- designed Loops such as the SL1 voice grade and UCL-ND may not be ordered in these cases. 2.6.3 If no alternate facility is available, and upon request from Freedom, and if agreed to by both Parties, BellSouth may utilize its Special Construction (SC) process to determine the additional costs required to provision facilities. Freedom will then have the option of paying the one-time SC rates to place the Loop.

  • Programming Phase Schematic Design Phase: 2.2.1.3. Design Development Phase:

  • Access Toll Connecting Trunk Group Architecture 9.2.1 If WCS chooses to subtend a Verizon access Tandem, WCS’s NPA/NXX must be assigned by WCS to subtend the same Verizon access Tandem that a Verizon NPA/NXX serving the same Rate Center Area subtends as identified in the LERG. 9.2.2 WCS shall establish Access Toll Connecting Trunks pursuant to applicable access Tariffs by which it will provide Switched Exchange Access Services to Interexchange Carriers to enable such Interexchange Carriers to originate and terminate traffic to and from WCS’s Customers. 9.2.3 The Access Toll Connecting Trunks shall be two-way trunks. Such trunks shall connect the End Office WCS utilizes to provide Telephone Exchange Service and Switched Exchange Access to its Customers in a given LATA to the access Tandem(s) Verizon utilizes to provide Exchange Access in such LATA. 9.2.4 Access Toll Connecting Trunks shall be used solely for the transmission and routing of Exchange Access to allow WCS’s Customers to connect to or be connected to the interexchange trunks of any Interexchange Carrier which is connected to a Verizon access Tandem.

  • Alternative Work Schedule An alternate forty (40) hour work schedule (other than five (5) uniform and consecutive eight (8) hour days in a seven (7) day period), or for hospital personnel an eighty (80) hour workweek in a fourteen (14) day period and other mutually agreed upon schedules that comply with applicable federal and state law. Employee work schedules normally include two (2) consecutive days off.

  • Two-­‐character labels All two-­‐character ASCII labels shall be withheld from registration or allocated to Registry Operator at the second level within the TLD. Such labels may not be activated in the DNS, and may not be released for registration to any person or entity other than Registry Operator, provided that such two-­‐character label strings may be released to the extent that Registry Operator reaches agreement with the related government and country-­‐code manager of the string as specified in the ISO 3166-­‐1 alpha-­‐2 standard. The Registry Operator may also propose the release of these reservations based on its implementation of measures to avoid confusion with the corresponding country codes, subject to approval by ICANN. Upon conclusion of Registry Operator’s designation as operator of the registry for the TLD, all such labels that remain withheld from registration or allocated to Registry Operator shall be transferred as specified by ICANN. Registry Operator may self-­‐allocate and renew such names without use of an ICANN accredited registrar, which will not be considered Transactions for purposes of Section 6.1 of the Agreement.