CoreLogic Data Sample Clauses

CoreLogic Data. Nothing in this Section 13.2 is intended to limit the obligations of Supplier under Section 13.1 or 13.3 of this Agreement with respect to the Confidential Information addressed in such Sections. To the extent that the provisions pertaining to CoreLogic Data in Section 13.1, this Section 13.2, and Section 13.3, the provisions of Section 13.3 shall control over the provisions of this Section 13.2, which shall control over the provisions of Section 13.1.
AutoNDA by SimpleDocs

Related to CoreLogic Data

  • Customer Materials Subject to Section 4(a), all right, title and interest (including all Intellectual Property Rights) in and to the Customer Materials are owned by Customer or Customer’s suppliers.

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

  • Database The LERG is available through Telcordia. ICONN is available through the Qwest web site.

  • PORTAL At the Closing Time, the Securities shall have been designated for trading on PORTAL.

  • Statistical Information Any third-party statistical and market-related data included in the Registration Statement, the Time of Sale Disclosure Package and the Prospectus are based on or derived from sources that the Company believes to be reliable and accurate in all material respects.

  • Online Payments may be made online from the Money Matters tab in the Licensee’s Cal Poly Portal or at xxxx://xxx.xxx.xxxxxxx.xxx/student_accounts/online_payments.asp. Online payments can be made with either eCheck (with no added convenience fee) or credit card (with an added 2.75% convenience fee). Online payments received after 5:00 pm will be recorded as paid the following business day. If there are any problems making a payment online, contact the University Student Accounts Office at (000) 000-0000 or by email to xxxxxxxxxxxxxxx@xxxxxxx.xxx

  • Computer Files Marked The Seller shall, at its own expense, on or before the Closing Date, indicate in its computer files that the Receivables have been sold to the Purchaser pursuant to this Receivables Purchase Agreement and deliver to the Purchaser the Receivable Schedule, certified by an officer of the Seller to be true, correct and complete.

  • Internet Services Transfer Agent shall make available to Fund and Shareholders, through its web sites, including but not limited to xxx.xxxxxxxxxxxxx.xxx (collectively, “Web Site”), online access to certain Account and Shareholder information and certain transaction capabilities (“Internet Services”), subject to Transfer Agent’s security procedures and the terms and conditions set forth herein and on the Web Site. Transfer Agent provides Internet Services “as is,” on an “as available” basis, and hereby specifically disclaims any and all representations or warranties, express or implied, regarding such Internet Services, including any implied warranty of merchantability or fitness for a particular purpose and implied warranties arising from course of dealing or course of performance. Transfer Agent shall at all times use reasonable care in performing Internet Services under this Agreement.

  • Technical Information The Employer agrees to provide to the Union such information that is available relating to employees in the bargaining unit, as may be required by the Union for collective bargaining purposes.

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

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