Close Links Sample Clauses

Close Links. Holborn is a group of several organisations each of which is a separate legal entity registered in the relevant jurisdictions in which they operate. The advice provided to you in the respective jurisdictions will be in accordance with the scope of Holborn’s regulatory authorizations in that jurisdiction where applicable. When providing advice on a cross border basis multiple entities may be involved in the advice process. Close Links as referred to in the Markets in Financial Instruments Directive 2014/65/EU (MiFID II) has the following meaning:
Sample 1Sample 2
AutoNDA by SimpleDocs
Close Links. An operating license shall not be granted if the close links of a financial undertaking [cf. Point 1 of Art. 1 a]1) with individuals or legal entities impede supervision of the undertaking by the Financial Supervisory Authority. The same applies if Acts or Regulations which apply to such connected parties impede supervision.
Sample 1Sample 2
Close Links. Close links are considered to exist when:
Sample 1
Close Links the Fund Manager's relationships with any legal or natural person as described in Chapter 1. § 2, of the Swedish UCITS Act (2004:46). Related party: natural or legal person with which the Fund Manager has a Close link, the Fund Manager's Representative, Partner and its Representative, External Investment Manager and its Representative.‌ Relevant Person: (a) a member of the board, shareholder, managing director or other manager at the Fund Manager; (b) one of the Fund Managers employees as well as any other natural person who not only performs services for the Fund Manager but is also under the Fund Manager's control and participates in the operation of the fund operations on behalf of the Fund Manager, and (c) a natural person who, in the context of a contract of assignment, carries out part of the fund operations on behalf of the Fund Manager. Partner: natural or legal person that the Fund Manager engages or cooperates with, for example for fund administration, financial advice to customers, marketing, information and sales of fund units or other financial products or services to pension savers within the premium pension sector.
Sample 1

Related to Close Links

  • Opening an Account Stripe may use information that you provide to Stripe and its Affiliates about a Connected Account to (a) determine the Connected Account’s eligibility to be a Stripe Issuing Accountholder; (b) administer the Stripe Issuing Program; and (c) monitor each Stripe Issuing Accountholder’s Principal Owners, Stripe Issuing Administrators, Card Authorised Users, representatives, and individuals with significant responsibility for management, including executives and senior managers, for the purpose of meeting Stripe’s obligations under Law. Stripe may reject any Connected Account application for, and terminate any Stripe Issuing Accountholder’s access to, the Stripe Issuing Services immediately if any Connected Account, Stripe Issuing Accountholder, Principal Owner, Stripe Issuing Administrator, Card Authorised User, representative, or individual with significant responsibility for management is or becomes a High-Risk Person or uses the Stripe Issuing Program for a Card Unauthorised Purpose.

  • Posting Period Vacancies that the University intends to fill shall be posted for a period of at least seven (7) full working days before the deadline for applications for the position.

  • Service Activation Date Billing for the Service Component will begin on the Service Activation Date, as specified below, for the specific Service type. The Service Activation Date is the date (i) Equipment is installed and tested at the Customer’s locations, and (ii) IP connectivity to LightEdge has been established.

  • Direct Trunked Transport 7.3.2.1 Either Party may elect to purchase direct trunked transport from the other Party.

  • Measured Internet Traffic Dial-up, switched Internet Traffic originated by a Customer of one Party on that Party’s network at a point in a Verizon local calling area, and delivered to a Customer or an Internet Service Provider served by the other Party, on that other Party’s network at a point in the same Verizon local calling area. Verizon local calling areas shall be as defined by Verizon. For the purposes of this definition, a Verizon local calling area includes a Verizon non-optional Extended Local Calling Scope Arrangement, but does not include a Verizon optional Extended Local Calling Scope Arrangement. Calls originated on a 1+ presubscription basis, or on a casual dialed (10XXX/101XXXX) basis, are not considered Measured Internet Traffic. For the avoidance of any doubt, Virtual Foreign Exchange Traffic (i.e., V/FX Traffic) (as defined in the Interconnection Attachment) does not constitute Measured Internet Traffic.

  • 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: Field # Field Name Description 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

Time is Money Join Law Insider Premium to draft better contracts faster.