Shared Directory Data Sample Clauses

Shared Directory Data. When you order an Online Service using an email address with a domain provided by an organization you are affiliated with (e.g. an employer or school), the Online Service adds you to a directory of users that share the same email domain. Your directory data (name, date of signup, and email address) may be visible to other users of Online Services within your organization’s email domain.
AutoNDA by SimpleDocs
Shared Directory Data. When you order an Software Services using an email address with a domain provided by an organization you are affiliated with, the Software Services adds you to a directory of users that

Related to Shared Directory Data

  • 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

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

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

  • Shareholder Account Maintenance (a) Maintain all shareholder records for each account in the Company. (b) Issue customer statements on scheduled cycle, providing duplicate second and third party copies if required. (c) Record shareholder account information changes. (d) Maintain account documentation files for each shareholder.

  • The Web Services E-Verify Employer Agent agrees to, consistent with applicable laws, regulations, and policies, commit sufficient personnel and resources to meet the requirements of this MOU.

  • 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

  • Third Party Proprietary Data The Disclosing Party's Third Party Proprietary Data, if any, will be identified in a separate technical document.

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

  • EPP query-­‐command RTT Refers to the RTT of the sequence of packets that includes the sending of a query command plus the reception of the EPP response for only one EPP query command. It does not include packets needed for the start or close of either the EPP or the TCP session. EPP query commands are those described in section 2.9.2 of EPP RFC 5730. If the RTT is 5-­‐times or more the corresponding SLR, the RTT will be considered undefined.

  • Optical Plan The Board will provide employees with a program of vision care with the Board paying 100% of the insurance premium. A family plan will be made available at the option of the employee with the Board paying 75% of the cost of the premium. Effective January 1, 2001, the plan shall provide an exam and lenses every calendar year. Frames are an eligible expense every other calendar year. Contact lenses are covered at the same frequency as lenses.

Draft better contracts in just 5 minutes Get the weekly Law Insider newsletter packed with expert videos, webinars, ebooks, and more!