Other Directory Services 73.10.1 Both parties acknowledge that CenturyLink’s directory publisher is not a party to this Agreement and that the provisions contained in this Agreement are not binding upon CenturyLink’s directory publisher. 73.10.2 CenturyLink agrees to include critical contact information pertaining to CLEC in the “Information Pages” of those of its White Pages directories containing information pages, if CLEC meets criteria established by its directory publisher. Critical contact information includes CLEC’s business office number, repair number, billing information number, and any other information required to comply with applicable regulations, but not advertising or purely promotional material. CLEC will not be charged for inclusion of its critical contact information. The format, content and appearance of CLEC’s critical contact information must conform to applicable directory publisher’s guidelines and will be consistent with the format, content and appearance of critical contact information pertaining to all CLECs in a directory. 73.10.3 The directory publisher shall maintain full authority as publisher over its publishing policies, standards and practices, including decisions regarding directory coverage area, directory issue period, compilation, headings, covers, design, content or format of directories, and directory advertising sales.
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.
Provider Directory a. The Contractor shall make available in electronic form and, upon request, in paper form, the following information about its network providers: i. The provider’s name as well as any group affiliation; ii. Street address(es); iii. Telephone number(s); iv. Website URL, as appropriate; v. Specialty, as appropriate; vi. Whether the provider will accept new beneficiaries; vii. The provider’s cultural and linguistic capabilities, including languages (including American Sign Language) offered by the provider or a skilled medical interpreter at the provider’s office, and whether the provider has completed cultural competence training; and viii. Whether the provider’s office/facility has accommodations for people with physical disabilities, including offices, exam room(s) and equipment. b. The Contractor shall include the following provider types covered under this Agreement in the provider directory: i. Physicians, including specialists ii. Hospitals
Supplier Diversity Seller shall comply with Xxxxx’s Supplier Diversity Program in accordance with Appendix V.
Reporting of Total Compensation of Subrecipient Executives 1. Applicability and what to report. Unless you are exempt as provided in paragraph d. of this award term, for each first-tier subrecipient under this award, you shall report the names and total compensation of each of the subrecipient's five most highly compensated executives for the subrecipient's preceding completed fiscal year, if-- i. in the subrecipient's preceding fiscal year, the subrecipient received-- (A) 80 percent or more of its annual gross revenues from Federal procurement contracts (and subcontracts) and Federal financial assistance subject to the Transparency Act, as defined at 2 CFR 170.320 (and subawards); and (B) $25,000,000 or more in annual gross revenues from Federal procurement contracts (and subcontracts), and Federal financial assistance subject to the Transparency Act (and subawards); and ii. The public does not have access to information about the compensation of the executives through periodic reports filed under section 13(a) or 15(d) of the Securities Exchange Act of 1934 (15 U.S.C. 78m(a), 78o(d)) or section 6104 of the Internal Revenue Code of 1986. (To determine if the public has access to the compensation information, see the U.S. Security and Exchange Commission total compensation filings at xxxx://xxx.xxx.xxx/answers/execomp.htm.) 2. Where and when to report. You must report subrecipient executive total compensation described in paragraph c.1. of this award term: i. To the recipient. ii. By the end of the month following the month during which you make the subaward. For example, if a subaward is obligated on any date during the month of October of a given year (i.e., between October 1 and 31), you must report any required compensation information of the subrecipient by November 30 of that year.
Local Circuit Switching Capability, including Tandem Switching Capability 4.2.1 Local circuit switching capability is defined as: (A) line-side facilities, which include, but are not limited to, the connection between a loop termination at a main distribution frame and a switch line card; (B) trunk-side facilities, which include, but are not limited to, the connection between trunk termination at a trunk-side cross-connect panel and a switch trunk card; (C) switching provided by remote switching modules; and (D) all features, functions, and capabilities of the switch, which include, but are not limited to: (1) the basic switching function of connecting lines to lines, line to trunks, trunks to lines, and trunks to trunks, as well as the same basic capabilities made available to BellSouth’s customers, such as a telephone number, white page listings, and dial tone; and (2) all other features that the switch is capable of providing, including but not limited to customer calling, customer local area signaling service features, and Centrex, as well as any technically feasible customized routing functions provided by the switch. Any features that are not currently available but are technically feasible through the switch can be requested through the BFR/NBR process. 4.2.2 Notwithstanding BellSouth’s general duty to unbundle local circuit switching, BellSouth shall not be required to unbundle local circuit switching for Louisville Telephone when Louisville Telephone serves an end-user with four (4) or more voice-grade (DS-0) equivalents or lines served by BellSouth in one of the following MSAs: Atlanta, GA; Miami, FL; Orlando, FL; Ft. Lauderdale, FL; Charlotte-Gastonia-Rock Hill, NC; Greensboro-Winston Salem-High Point, NC; Nashville, TN; and New Orleans, LA, and BellSouth has provided non- discriminatory cost based access to the Enhanced Extended Link (EEL) throughout Density Zone 1 as determined by NECA Tariff No. 4 as in effect on January 1, 1999. 4.2.3 In the event that Louisville Telephone orders local circuit switching for an end user with four (4) or more DS0 equivalent lines within Density Zone 1 in an MSA listed above, BellSouth shall charge Louisville Telephone the market based rates in Exhibit B for use of the local circuit switching functionality for the affected facilities.
Directory Listings 15.1.1 CBT, as publisher of its White Pages, will include Primary Listings of CLEC’s resale directory customers in its White Pages, and shall cause its publisher to include primary listings of CLEC’s directory customers in its Publisher’s Yellow Pages Directories under the following terms and conditions: 15.1.1.1 CBT will publish the Primary Listing of CLEC Directory Customers located within the geographic scope of its White Pages directory and will recover costs for both resale and facility based Customers in accordance with the Act.
Directory Listing and Directory Distribution 41 5. Voice Information Service Traffic 43 6. Intercept and Referral Announcements 44 7. Originating Line Number Screening (OLNS) 44 8. Operations Support Systems (OSS) Services 44 9. Poles, Ducts, Conduits and Xxxxxx-xx-Xxx 00 00. Telephone Numbers 51 11. Routing for Operator Services and Directory Assistance Traffic 51 12. Unauthorized Carrier Change Charges 52 13. Good Faith Performance 52 INTERCONNECTION ATTACHMENT. 53 1. General 53 2. Points of Interconnection and Trunk Types 53 3. Alternative Interconnection Arrangements 57 4. Initiating Interconnection 58 5. Transmission and Routing of Telephone Exchange Service Traffic 59
Directory Assistance Service 8.3.1 Directory Assistance Service provides local end user telephone number listings with the option to complete the call at the caller's direction separate and distinct from local switching.
Hosting Services NCR Voyix shall furnish facilities, equipment, computer programs and services, as specified from time to time by NCR Voyix, that NCR Voyix deems necessary for operation and maintenance of the System (collectively, the “Hosting Services”).
