Modifications and Updates to the Wire Center List and Subsequent Transition Periods 5.4.6.1 In the event AT&T identifies additional wire centers that meet the criteria set forth in Sections 5.4.2.1 or 5.4.2.2 above, but that were not included in the Master List of Unimpaired Wire Centers or AT&T’s List of Unimpaired Wire Centers, AT&T shall include such additional wire centers in a CNL. Each such list of additional wire centers shall be considered a Subsequent Wire Center List. AT&T will follow any limitations on the frequency with which it may issue such lists and notification procedures set forth in applicable Commission orders. 5.4.6.2 TWTC shall have thirty (30) business days to dispute the additional wire centers listed on AT&T’s CNL. Absent such dispute, effective thirty (30) business days after the date of a AT&T CNL providing a Subsequent Wire Center List, AT&T shall not be required to provide DS1 and DS3 Dedicated Transport, as applicable, in such additional wire center(s), except pursuant to the self-certification process as set forth in Section 1.9.1 of this Attachment. 5.4.6.3 For purposes of Section 5.4.6.1 above, AT&T shall make available DS1 and DS3 Dedicated Transport that were in service for TWTC in a wire center on the Subsequent Wire Center List as of the thirtieth (30th) business day after the date of AT&T’s CNL identifying the Subsequent Wire Center List (Subsequent Embedded Base) until one hundred eighty (180) days after the thirtieth (30th) business day Version: 4Q06 Standard ICA 11/30/06 from the date of AT&T’s CNL identifying the Subsequent Wire Center List (Subsequent Transition Period). 5.4.6.4 The rates set forth in Exhibit B shall apply to the Subsequent Embedded Base during the Subsequent Transition Period. 5.4.6.5 No later than one hundred eighty (180) days from AT&T’s CNL identifying the Subsequent Wire Center List, TWTC shall submit an LSR(s) or spreadsheet(s) as applicable, identifying the Subsequent Embedded Base of circuits to be disconnected or converted to other AT&T services. 5.4.6.5.1 In the case of disconnection, the applicable disconnect charges set forth in this Agreement shall apply. 5.4.6.5.2 If TWTC chooses to convert DS1 and/or DS3 Dedicated Transport to special access circuits in existence as of the Effective Date of this Agreement, AT&T will include such DS1 and/or DS3 Dedicated Transport within TWTC’s total special access circuits, and apply any discounts to which TWTC is entitled from the transition period of 3/11/2006 to the conversion date. Conversions will be subject to the switch-as-is charge set forth in Exhibit A to this Attachment 2. 5.4.6.5.3 AT&T shall not impose disconnect or nonrecurring installation charges when transitioning the Subsequent Embedded Base of DS1 and DS3 Dedicated Transport in existence as of the Effective Date of this Agreement. 5.4.6.6 If TWTC fails to submit the LSR(s) or spreadsheet(s) for all of its Subsequent Embedded Base by one hundred eighty (180) days after the date of AT&T’s CNL identifying the Subsequent Wire Center List, AT&T will identify TWTC’s remaining Subsequent Embedded Base, if any, and will transition such circuits to the equivalent tariffed AT&T service(s), or in the case of Georgia, to the equivalent 271 service(s) set forth in Exhibit 1. In the states of Florida, Kentucky, Mississippi and South Carolina, those circuits identified and transitioned by AT&T shall be subject to the applicable disconnect charges as set forth in this Agreement and the full nonrecurring charges for installation of the equivalent tariffed AT&T service as set forth in AT&T’s tariffs. In the states of Alabama, Georgia, North Carolina and Tennessee, those circuits identified and transitioned by AT&T shall be subject to the applicable switch-as-is rates set forth in Exhibit A of Attachment
Public Posting of Approved Users’ Research Use Statement The PI agrees that information about themselves and the approved research use will be posted publicly on the dbGaP website. The information includes the PI’s name and Requester, project name, Research Use Statement, and a Non-Technical Summary of the Research Use Statement. In addition, and if applicable, this information may include the Cloud Computing Use Statement and name of the CSP or PCS. Citations of publications resulting from the use of controlled-access datasets obtained through this DAR may also be posted on the dbGaP website.
Specific Provisions for Access Rights to Software For the avoidance of doubt, the general provisions for Access Rights provided for in this Section 9 are applicable also to Software. Parties’ Access Rights to Software do not include any right to receive source code or object code ported to a certain hardware platform or any right to receive respective Software documentation in any particular form or detail, but only as available from the Party granting the Access Rights.
Selection of Subcontractors, Procurement of Materials and Leasing of Equipment The contractor shall not discriminate on the grounds of race, color, religion, sex, national origin, age or disability in the selection and retention of subcontractors, including procurement of materials and leases of equipment. The contractor shall take all necessary and reasonable steps to ensure nondiscrimination in the administration of this contract. a. The contractor shall notify all potential subcontractors and suppliers and lessors of their EEO obligations under this contract. b. The contractor will use good faith efforts to ensure subcontractor compliance with their EEO obligations.
Proposed Policies and Procedures Regarding New Online Content and Functionality By October 31, 2017, the School 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 School to provide equally effective alternative access. The Plan for New Content will require the School, 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, alternates 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 School’s 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 School will officially adopt, and fully implement the amended policies and procedures.
Solicitations for Subcontracts, Including Procurements of Materials and Equipment In all solicitations either by competitive bidding or negotiation made by the Engineer for work to be performed under a subcontract, including procurements of materials or leases of equipment, each potential subcontractor or supplier shall be notified by the Engineer of the Engineer's obligations under this contract and the Regulations relative to nondiscrimination on the grounds of race, color, or national origin.
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. 11.2 We may (i) compile statistical and other information related to the performance, operation and use of the Services, and (ii) use data from the Services in aggregated form for security and operations management, to create statistical analyses, and for research and development purposes (clauses i and ii are collectively referred to as “Service Analyses”). We may make Service Analyses publicly available; however, Service Analyses will not incorporate Your Content, Personal Data or Confidential Information in a form that could serve to identify You or any individual. We retain all intellectual property rights in Service Analyses. 11.3 We may provide You with the ability to obtain certain Oracle Software (as defined below) for use with the Services. If we provide Oracle Software to You and do not specify separate terms for such software, then such Oracle Software is provided as part of the Services and You have the non-exclusive, worldwide, limited right to use such Oracle Software, subject to the terms of this Agreement and Your order (except for separately licensed elements of the Oracle Software, which separately licensed elements are governed by the applicable separate terms), solely to facilitate Your use of the Services. You may allow Your Users to use the Oracle Software for this purpose, and You are responsible for their compliance with the license terms. Your right to use any Oracle Software will terminate upon the earlier of our notice (by web posting or otherwise) or the end of the Services associated with the Oracle Software. Notwithstanding the foregoing, if Oracle Software is licensed to You under separate terms, then Your use of such software is governed by the separate terms. Your right to use any part of the Oracle Software that is licensed under the separate terms is not restricted in any way by this Agreement.
Solicitations for Subcontracts, Including Procurement of Materials and Equipment In all solicitations either by competitive bidding or negotiation made by the Local Government for work to be performed under a subcontract, including procurement of materials or leases of equipment, each potential subcontractor or supplier will be notified by the Local Government of the Local Government’s obligations under this Agreement and the Acts and Regulations relative to Nondiscrimination on the grounds of race, color, or national origin.
Operation and Maintenance Manuals Receipts for transmittal of Operation and Maintenance Manuals, Brochures and Data to the Design Professional (or Commissioning Agent) as required by Section 6.1.1.5.
Registration Data Directory Services Until ICANN requires a different protocol, Registry Operator will operate a WHOIS service available via port 43 in accordance with XXX 0000, and a web-‐based Directory Service at <whois.nic.TLD> providing free public query-‐based access to at least the following elements in the following format. ICANN reserves the right to specify alternative formats and protocols, and upon such specification, the Registry Operator will implement such alternative specification as soon as reasonably practicable. Registry Operator shall implement a new standard supporting access to domain name registration data (SAC 051) no later than one hundred thirty-‐five (135) days after it is requested by ICANN if: 1) the IETF produces a standard (i.e., it is published, at least, as a Proposed Standard RFC as specified in RFC 2026); and 2) its implementation is commercially reasonable in the context of the overall operation of the registry. 1.1. The format of responses shall follow a semi-‐free text format outline below, followed by a blank line and a legal disclaimer specifying the rights of Registry Operator, and of the user querying the database. 1.2. Each data object shall be represented as a set of key/value pairs, with lines beginning with keys, followed by a colon and a space as delimiters, followed by the value. 1.3. For fields where more than one value exists, multiple key/value pairs with the same key shall be allowed (for example to list multiple name servers). The first key/value pair after a blank line should be considered the start of a new record, and should be considered as identifying that record, and is used to group data, such as hostnames and IP addresses, or a domain name and registrant information, together. 1.4. The fields specified below set forth the minimum output requirements. Registry Operator may output data fields in addition to those specified below, subject to approval by ICANN, which approval shall not be unreasonably withheld.
