Taxonomy of Directory Service for Netscape Channels Sample Clauses

Taxonomy of Directory Service for Netscape Channels. Excite will provide the capability for Netscape to deliver a subject based directory service that would be presented to the user outside the context of a Channel. Excite will also provide the capability for Netscape to deliver an alphabetically-based directory service. To the extent that Excite develops a time-based or location-based directory service for its own purposes, Excite will provide the capability for Netscape to deliver these directories as well. Excite will provide "cuts" of the directory to be integrated into the Netscape channels. The technical teams will work in good faith to assure timely updates to the Netscape Directory Service. Netscape may, with the assistance of Excite, determine the taxonomy contained in any Directory Service to be included by Netscape in a Channel (other than Co-Branded Channels). At Netscape's request from time to time, upon reasonable advance notice to Excite, Excite shall modify and enhance the taxonomy of any Directory Service included by Netscape in a Channel (other than Co-Branded Channels). Netscape and Excite will cooperate in good ------------ * Confidential Treatment has been requested with respect to certain portions of this exhibit. Confidential portions have been omitted from the public filing and filed separately with the Securities and Exchange Commission. faith to establish a schedule to promptly implement changes to the Directory Service necessary to comply with Netscape's revisions.
AutoNDA by SimpleDocs

Related to Taxonomy of Directory Service for Netscape Channels

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

  • 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

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

  • Technical and Organizational Measures The following sections define SAP’s current technical and organizational measures. SAP may change these at any time without notice so long as it maintains a comparable or better level of security. Individual measures may be replaced by new measures that serve the same purpose without diminishing the security level protecting Personal Data.

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

  • COMMERCIAL REUSE OF SERVICES The member or user herein agrees not to replicate, duplicate, copy, trade, sell, resell nor exploit for any commercial reason any part, use of, or access to 's sites.

  • DEVELOPMENT OR ASSISTANCE IN DEVELOPMENT OF SPECIFICATIONS REQUIREMENTS/ STATEMENTS OF WORK

  • Surgery Services This plan covers surgery services to treat a disease or injury when: • the operation is not experimental or investigational, or cosmetic in nature; • the operation is being performed at the appropriate place of service; and • the physician is licensed to perform the surgery. This plan covers reconstructive surgery and procedures when the services are performed to relieve pain, or to correct or improve bodily function that is impaired as a result of: • a birth defect; • an accidental injury; • a disease; or • a previous covered surgical procedure. Functional indications for surgical correction do not include psychological, psychiatric or emotional reasons. This plan covers the procedures listed below to treat functional impairments. • abdominal wall surgery including panniculectomy (other than an abdominoplasty); • blepharoplasty and ptosis repair; • gastric bypass or gastric banding; • nasal reconstruction and septorhinoplasty; • orthognathic surgery including mandibular and maxillary osteotomy; • reduction mammoplasty; • removal of breast implants; • removal or treatment of proliferative vascular lesions and hemangiomas; • treatment of varicose veins; or • gynecomastia.

  • Please see the current Washtenaw Community College catalog for up-to-date program requirements Conditions & Requirements

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

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