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.
Publication of Registration Data Registry Operator shall provide public access to registration data in accordance with Specification 4 attached hereto (“Specification 4”).
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.
USER REGISTRATION You may be required to register with the Site. You agree to keep your password confidential and will be responsible for all use of your account and password. We reserve the right to remove, reclaim, or change a username you select if we determine, in our sole discretion, that such username is inappropriate, obscene, or otherwise objectionable.
NERC Registration The NTO shall register or enter into agreement with a NERC registered entity for all required NERC functions applicable to the NTO, that may include, without limitation, those functions designated by NERC to be: “Transmission Owner” and “Transmission Planner” and “Transmission Operator.” The Parties agree to negotiate in good faith the compliance obligations for the NERC functions applicable to, and to be performed by, each Party with respect to the NTO’s facilities. Notwithstanding the foregoing, the ISO shall register for the “Transmission Operator” function for all NTO Transmission Facilities under ISO Operational Control identified in Appendix A-1 of this Agreement.
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.
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.
Copies of Registration Statement The Company will furnish the Dealer Manager with one signed copy of the Registration Statement, including its exhibits, and such additional copies of the Registration Statement, without exhibits, and the Prospectus and all amendments and supplements thereto, which are finally approved by the Commission, as the Dealer Manager may reasonably request for sale of the Shares.
AGREED FACTS Registration History 7. Since June 2006, the Respondent has been registered in Ontario as a mutual fund salesperson (now known as a dealing representative)1 with WFG Securities Inc. (the “Member”), a Member of the MFDA.
8. At all material times, the Respondent conducted business in the Vaughan, Ontario area.
9. At all material times, the Member’s policies and procedures prohibited Approved Persons from signing a client’s name to a document.
10. Between January 2018 and September 2018, while the Respondent was an Approved Person of the Member, the Respondent signed the initials of clients on 8 trade tickets next to alterations he made to information on the trade tickets, and submitted them to the Member for processing.
11. The alterations made by the Respondent on the trade tickets included alterations to: trade instructions, client signature dates and special instructions.
12. At all material times, the Member’s policies and procedures prohibited Approved Persons from altering information on a signed document without the client initialing the document to show that the changes were approved.
13. In May 2018, while the Respondent was an Approved Person of the Member, he altered 1 account form in respect of 1 client by altering information on a trade ticket without having the client initial the alterations, and used this altered form to process a transaction. 1 In September 2009, the registration category mutual fund salesperson was changed to “dealing representative” when National Instrument 31-103 came into force.
14. The Respondent altered the trading instructions, special instructions and representative commission percentage on the trade ticket without having the client initial these alterations.
15. At all material times, the Member’s policies and procedures prohibited Approved Persons from holding an account form which was signed by a client and was blank or only partially completed.
16. Between January 2015 and October 2018, while the Respondent was an Approved Person of the Member, he obtained, possessed and used to process transactions, 30 pre-signed account forms in respect of 21 clients.
17. The pre-signed account forms consisted of: 25 Trade Tickets, 3 New Account Application Forms and 2 Non Financial Information Update Forms.
Costs of updating of registration statement If provided for in the Prospectus for a Trust, the Trustee shall pay, or reimburse to the Depositor, the expenses related to the updating of the Trust's registration statement, to the extent of legal fees, typesetting fees, electronic filing expenses and regulatory filing fees. Such expenses shall be paid from the Income Account, or to the extent funds are not available in such Account, from the Capital Account, against an invoice or invoices therefor presented to the Trustee by the Depositor. By presenting such invoice or invoices, the Depositor shall be deemed to certify, upon which certification the Trustee is authorized conclusively to rely, that the amounts claimed therein are properly payable pursuant to this paragraph. The Depositor shall provide the Trustee, from time to time as requested, an estimate of the amount of such expenses, which the Trustee shall use for the purpose of estimating the accrual of Trust expenses. The amount paid by the Trust pursuant to this paragraph in each year shall be separately identified in the annual statement provided to Unit holders. The Depositor shall assure that the Prospectus for the Trust contains such disclosure as shall be necessary to permit payment by the Trust of the expenses contemplated by this paragraph under applicable laws and regulations. The provisions of this paragraph shall not limit the authority of the Trustee to pay, or reimburse to the Depositor or others, such other or additional expenses as may be determined to be payable from the Trust as provided in this Section 6.02.
