Registry Functions Activity Report This report shall be compiled in a comma separated-value formatted file as specified in RFC 4180. The file shall be named “gTLD-activity-yyyymm.csv”, where “gTLD” is the gTLD name; in case of an IDN-TLD, the A-label shall be used; “yyyymm” is the year and month being reported. The file shall contain the following fields: 01 operational-registrars number of operational registrars at the end of the reporting period 02 ramp-up-registrars number of registrars that have received a password for access to OT&E at the end of the reporting period 03 pre-ramp-up-registrars number of registrars that have requested access, but have not yet entered the ramp-up period at the end of the reporting period 06 web-whois-queries number of Web-based Whois queries responded during the reporting period, not including searchable Whois 09 dns-udp-queries-responded number of DNS queries received over UDP transport that were responded during the reporting period 10 dns-tcp-queries-received number of DNS queries received over TCP transport during the reporting period 11 dns-tcp-queries-responded number of DNS queries received over TCP transport that were responded during the reporting period 12 srs-dom-check number of SRS (EPP and any other interface) domain name “check” requests responded during the reporting period 13 srs-dom-create number of SRS (EPP and any other interface) domain name “create” requests responded during the reporting period 14 srs-dom-delete number of SRS (EPP and any other interface) domain name “delete” requests responded during the reporting period 15 srs-dom-info number of SRS (EPP and any other interface) domain name “info” requests responded during the reporting period 16 srs-dom-renew number of SRS (EPP and any other interface) domain name “renew” requests responded during the reporting period 17 srs-dom-rgp-restore-report number of SRS (EPP and any other interface) domain name RGP “restore” requests delivering a restore report responded during the reporting period 18 srs-dom-rgp-restore-request number of SRS (EPP and any other interface) domain name RGP “restore” requests responded during the reporting period 19 srs-dom-transfer-approve number of SRS (EPP and any other interface) domain name “transfer” requests to approve transfers responded during the reporting period 20 srs-dom-transfer-cancel number of SRS (EPP and any other interface) domain name “transfer” requests to cancel transfers responded during the reporting period 21 srs-dom-transfer-query number of SRS (EPP and any other interface) domain name “transfer” requests to query about a transfer responded during the reporting period 22 srs-dom-transfer-reject number of SRS (EPP and any other interface) domain name “transfer” requests to reject transfers responded during the reporting period 23 srs-dom-transfer-request number of SRS (EPP and any other interface) domain name “transfer” requests to request transfers responded during the reporting period 24 srs-dom-update number of SRS (EPP and any other interface) domain name “update” requests (not including RGP restore requests) responded during the reporting period 25 srs-host-check number of SRS (EPP and any other interface) host “check” requests responded during the reporting period 26 srs-host-create number of SRS (EPP and any other interface) host “create” requests responded during the reporting period 27 srs-host-delete number of SRS (EPP and any other interface) host “delete” requests responded during the reporting period 28 srs-host-info number of SRS (EPP and any other interface) host “info” requests responded during the reporting period 29 srs-host-update number of SRS (EPP and any other interface) host “update” requests responded during the reporting period 30 srs-cont-check number of SRS (EPP and any other interface) contact “check” requests responded during the reporting period 32 srs-cont-delete number of SRS (EPP and any other interface) contact “delete” requests responded during the reporting period 33 srs-cont-info number of SRS (EPP and any other interface) contact “info” requests responded during the reporting period 34 srs-cont-transfer-approve number of SRS (EPP and any other interface) contact “transfer” requests to approve transfers responded during the reporting period 35 srs-cont-transfer-cancel number of SRS (EPP and any other interface) contact “transfer” requests to cancel transfers responded during the reporting period 36 srs-cont-transfer-query number of SRS (EPP and any other interface) contact “transfer” requests to query about a transfer responded during the reporting period 37 srs-cont-transfer-reject number of SRS (EPP and any other interface) contact “transfer” requests to reject transfers responded during the reporting period 38 srs-cont-transfer-request number of SRS (EPP and any other interface) contact “transfer” requests to request transfers responded during the reporting period 39 srs-cont-update number of SRS (EPP and any other interface) contact “update” requests responded during the reporting period The first line shall include the field names exactly as described in the table above as a “header line” as described in section 2 of RFC 4180. No other lines besides the ones described above shall be included. Line breaks shall be <U+000D, U+000A> as described in RFC 4180. For gTLDs that are part of a single-instance Shared Registry System, the Registry Functions Activity Report may include the total contact or host transactions for all the gTLDs in the system. REGISTRATION DATA PUBLICATION SERVICES
Attachment A, Scope of Services The scope of services is amended as follows:
JOC Pricing of Itemized List of RS Means Non-Prepriced Items No response The Vendor may download the optional Pricing of Itemized List of RS Means Non-Prepriced Items form from the attachment tab, fill in the requested information, and upload the completed spreadsheet. DO NOT UPLOAD encrypted or password protected files. Valid Reference Email addresses are REQUIRED on the spreadsheet. The vendor must download the References spreadsheet from the attachment tab, fill in the requested information and upload the completed spreadsheet. DO NOT UPLOAD encrypted or password protected files.
Change in Scope of Work Any change in the scope of the Work, method of performance, nature of materials or price thereof, or any other matter materially affecting the performance or nature of the Work shall not be paid for or accepted unless such change, addition, or deletion is approved in advance and in writing by a valid change order executed by the District. Contractor specifically understands, acknowledges, and agrees that the District shall have the right to request any alterations, deviations, reductions, or additions to the Project or Work, and the cost thereof shall be added to or deducted from the amount of the Contract Price by fair and reasonable valuations. Contractor also agrees to provide the District with all information requested to substantiate the cost of the change order and to inform the District whether the Work will be done by the Contractor or a subcontractor. In addition to any other information requested, Contractor shall submit, prior to approval of the change order, its request for a time extension (if any), as well as all information necessary to substantiate its belief that such change will delay the completion of the Work. If Contractor fails to submit its request for a time extension or the necessary supporting information, it shall be deemed to have waived its right to request such extension.
Commercially Useful Function A prime consultant can credit expenditures to a DBE subconsultant toward DBE goals only if the DBE performs a Commercially Useful Function (CUF). A DBE performs a CUF when it is responsible for execution of the work of a contract and carries out its responsibilities by actually performing, managing, and supervising the work involved. To perform a commercially useful function, the DBE must also be responsible, with respect to materials and supplies on the contract, for negotiating price, determining quality and quantity, ordering the material, and installing (where applicable) and paying for the material itself that it uses on the project. To determine whether a DBE is performing a commercially useful function, the Department will evaluate the amount of work subcontracted, industry practices, whether the amount the firm is to be paid under the contract is commensurate with the work it is actually performing and the DBE credit claimed for its performance of the work, and other relevant factors. A DBE will not be considered to perform a commercially useful function if its role is limited to that of an extra participant in a transaction, contract, or project through which funds are passed in order to obtain the appearance of DBE participation. In determining whether a DBE is such an extra participant, the Department will examine similar transactions, particularly those in which DBEs do not participate. If a DBE does not perform or exercise responsibility for at least 30 percent of the total cost of its contract with its own work force, or if the DBE subcontracts a greater portion of the work of a contract than would be expected on the basis of normal industry practice for the type of work involved, the Department will presume that the DBE is not performing a commercially useful function. When a DBE is presumed not to be performing a commercially useful function as provided above, the DBE may present evidence to rebut this presumption. The Department will determine if the firm is performing a CUF given the type of work involved and normal industry practices. The Department will notify the consultant, in writing, if it determines that the consultant’s DBE subconsultant is not performing a CUF. The consultant will be notified within seven calendar days of the Department’s decision. Decisions on CUF may be appealed to the ADOT State Engineer. The appeal must be in writing and personally delivered or sent by certified mail, return receipt requested, to the State Engineer. The appeal must be received by the State Engineer no later than seven calendar days after the decision of XXXX. XXXX’s decision remains in place unless and until the State Engineer reverses or modifies BECO’s decision. ADOT State Engineer will promptly consider any appeals under this subsection and notify the consultant of ADOT’s State Engineer findings and decisions. Decisions on CUF matters are not administratively appealable to USDOT. The BECO may conduct project site visits on the contract to confirm that DBEs are performing a CUF. The consultant shall cooperate during the site visits and the BECO’s staff will make every effort not to disrupt work on the project.
Grant and Scope of License 2.1. Subject to Licensee’s compliance with the License Agreement, and except as otherwise stated herein, Licensor hereby grants Licensee a non-exclusive, revocable and non-transferrable license to:
2.1.1. permit Authorized Users to access the Content for the duration and in the manner set forth in the License Agreement;
2.1.2. incorporate links on Licensee’s intranet websites to the Content in full text format on the Platforms;
2.1.3. transmit to a non-commercial library single articles, book chapters or portions thereof only for personal educational, scientific, or research purposes (“Interlibrary Loans”). Such transmission shall be reviewed and fulfilled by Licensee’s staff, and shall be made by hand, post, fax or through any secure document transmission software, so long as, in the case of any electronic transmission, the electronic file retains the relevant copyright notice. The right set out in this clause does not extend to centralized ordering facilities, such as document delivery systems, nor the distribution of copies in such quantities as to substitute for a subscription or purchase of the distributed Content.
2.2. Authorized Users may solely for their personal educational, scientific, or research purposes:
2.2.1. access (including by remote access, with the exception of walk-in-users), browse, view, collate, display, search and retrieve the Content,
0.0.0. xxxxxxxx, store on a hard drive or removable media drive, print and copy in paper and digital form single articles, eBooks and portions thereof, individual database outputs, graphs, reports, or other individual items of the Content,
2.2.3. use single articles, eBooks and portions thereof, individual database outputs, graphs, reports or other individual items of the Content for the preparation of academic course materials with all rights notices duly presented.
2.2.4. use the Springer Nature SharedIt functionality when available, or other means when necessary, to transmit single articles, chapters or other individual items of Content to third-party members of the Authorized Users’ research group(s) for personal, scholarly, educational, or research use, but in no case for commercial purposes, nor in any manner that would serve as a replacement for a subscription to the Content.
INDEX OF EXHIBITS Exhibit Description
Submission of Grievance Information a. Upon appointment of the arbitrator, the appealing party shall, within five (5) days after notice of appointment, forward to the arbitrator, with a copy to the School Board, the submission of the grievance which shall include the following:
1. The issues involved.
2. Statement of the facts.
3. Position of the grievant.
4. The written documents relating to Section 5 of the grievance procedure.
Performance of Government Functions Nothing contained in this contract shall be deemed or construed so as to in any way estop, limit, or impair the City from exercising or performing any regulatory, policing, legislative, governmental, or other powers or functions.
Definition of Grievance A grievance shall be defined as any difference arising out of the interpretation, application, administration, or alleged violation of the Collective Agreement.
