Listing Data and Fees Sample Clauses

The "Listing Data and Fees" clause defines the requirements and terms regarding the information to be included in a property listing and the associated fees for listing services. Typically, this clause outlines what data must be provided by the seller or agent, such as property details, photographs, and disclosures, as well as the structure and timing of any fees charged for listing the property on a platform or with an agency. Its core practical function is to ensure transparency and clarity for all parties by specifying what is expected in terms of data submission and payment, thereby reducing misunderstandings and disputes related to listing requirements and costs.
Listing Data and Fees 
View SourceView Similar (5)

Related to Listing Data and Fees

  • Bulk Registration Data Access to Icann Periodic Access to Thin Registration Data. In order to verify and ensure the operational stability of Registry Services as well as to facilitate compliance checks on accredited registrars, Registry Operator will provide ICANN on a weekly basis (the day to be designated by ICANN) with up-to-date Registration Data as specified below. Data will include data committed as of 00:00:00 UTC on the day previous to the one designated for retrieval by ICANN.

  • Registration Data Directory Services Until ICANN requires a different protocol, Registry Operator will operate a WHOIS service available via port 43 in accordance with ▇▇▇ ▇▇▇▇, 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.

  • Exceptional Access to Thick Registration Data In case of a registrar failure, deaccreditation, court order, etc. that prompts the temporary or definitive transfer of its domain names to another registrar, at the request of ICANN, Registry Operator will provide ICANN with up-­‐to-­‐date data for the domain names of the losing registrar. The data will be provided in the format specified in Specification 2 for Data Escrow. The file will only contain data related to the domain names of the losing registrar. Registry Operator will provide the data as soon as commercially practicable, but in no event later than five (5) calendar days following ICANN’s request. Unless otherwise agreed by Registry Operator and ICANN, the file will be made available for download by ICANN in the same manner as the data specified in Section 3.1 of this Specification.

  • Listings 1.3.1 This Attachment sets forth terms and conditions that apply to Resale and Facility-Based CLECs for subscriber listing information provided by AT&T-21STATE.

  • Contract Database Metadata Elements Title: Sayville Union Free School District and Sayville Union Free School Custodial and Maintenance Employees Unit, United Public Service Employees Union (UPSEU), Local 424 (2011) Employer Name: Sayville Union Free School District Union: Sayville Union Free School Custodial and Maintenance Employees Unit, United Public Service Employees Union (UPSEU) Local: 424 Effective Date: 07/01/2011 Expiration Date: 06/30/2015 PERB ID Number: 6131 Unit Size: 55 Number of Pages: 24 For additional research information and assistance, please visit the Research page of the Catherwood website - ▇▇▇▇://▇▇▇.▇▇▇.▇▇▇▇▇▇▇.▇▇▇/library/research/ For additional information on the ILR School - ▇▇▇▇://▇▇▇.▇▇▇.▇▇▇▇▇▇▇.▇▇▇/ 55 People TABLE OF CONTENTS ARTICLE Page XXII ANNUAL LEAVE DAYS 14 XXV BREAKS 18 XXVI CIVIL SERVICE LAW ARTICLE SECTION 75 18 XXVIII DURATION 19 XIV EMERGENCY WORK 11 XXI FOUL WEATHER CLOTHING 14 XI GRIEVANCE PROCEDURE 9 XVI HIGHER JOB CLASSIFICATION 12 XVIII HOLIDAYS 13 XV HOLIDAY AND WEEKEND BUILDING CHECKS 12 V INSURANCE 4 X LAYOFF, DISPLACEMENT AND RECALL ORDER 8 VII MANAGEMENT RIGHTS 7 XXVII MISCELLANEOUS 19 XVII NOTICES OF PROMOTIONS 13 XIII OVERTIME 10 II PAYROLL DEDUCTIONS 1 III PERSONNEL FILES 2 XXIV PHYSICAL EXAMINATIONS 18 XXIII RETIREMENT 16 IX STRIKES AND LOCKOUTS 7 XIX VACATIONS 13 XX VISITATION 14 IV WAGES 3 VI WORKERS' COMPENSATION 6 XII WORKWEEK 10 VIII WRITTEN BOARD POLICY 8 APPENDIX A 20 4/20/2016 AGREEMENT made and entered into this day of November 2013 between the SAYVILLE UNION FREE SCHOOL DISTRICT (hereinafter referred to as the “District”) and United Public Service Employees Union, ▇▇▇▇ ▇▇▇▇▇▇▇▇ ▇▇▇▇▇▇▇▇ ▇▇▇▇▇▇▇, ▇▇▇▇▇▇▇▇▇▇, N.Y. 11779 (hereinafter referred to as the “Union”).