Market Activities The Company will not, directly or indirectly, (i) take any action designed to cause or result in, or that constitutes or would reasonably be expected to constitute, the stabilization or manipulation of the price of any security of the Company to facilitate the sale or resale of Common Stock or (ii) sell, bid for, or purchase Common Stock in violation of Regulation M, or pay anyone any compensation for soliciting purchases of the Placement Shares other than the Agent.
Clean-Up Period (a) Notwithstanding any other provision of any Finance Document:
Certain Market Activities Neither the Company, nor any of the Subsidiaries, nor any of their respective directors, officers or controlling persons has taken, directly or indirectly, any action designed, or that has constituted or might reasonably be expected to cause or result in, under the Exchange Act or otherwise, the stabilization or manipulation of the price of any security of the Company to facilitate the sale or resale of the Placement Shares.
Actions We May Take if You Engage in Any Restricted Activities If we believe that you’ve engaged in any of these activities, we may take a number of actions to protect PayPal, its customers and others at any time in our sole discretion. The actions we make take include, but are not limited to, the following: • Terminate this user agreement, limit your account, and/or close or suspend your account, immediately and without penalty to us; • Refuse to provide the PayPal services to you in the future; • At any time and without liability, suspend, limit or terminate your access to our websites, software, systems (including any networks and servers used to provide any of the PayPal services) operated by us or on our behalf, your PayPal account or any of the PayPal services, including limiting your ability to pay or send money with any of the payment methods linked to your PayPal account, restricting your ability to send money or make withdrawals; • Hold your money to the extent and for so long as reasonably needed to protect against the risk of liability. You acknowledge that, as a non-exhaustive guide: • PayPal’s risk of liability in respect of card-funded payments that you receive can last until the risk of a chargeback closing in favour of the payer/buyer (as determined by card scheme rules) has passed. This depends on certain factors, including, without limitation:
Permitted Activities The Executive shall devote his entire business time, attention and energies to the Business of the Employer and shall not during the Term be engaged (whether or not during normal business hours) in any other business or professional activity, whether or not such activity is pursued for gain, profit or other pecuniary advantage; but this shall not be construed as preventing the Executive from:
Unbundled Network Element Combinations 4.1 For purposes of this Section, references to “Currently Combined” Network Elements shall mean that the particular Network Elements requested by NewPhone are in fact already combined by BellSouth in the BellSouth network. References to “
Loop Provisioning Involving Integrated Digital Loop Carriers 2.6.1 Where EveryCall has requested an Unbundled Loop and BellSouth uses Integrated Digital Loop Carrier (IDLC) systems to provide the local service to the end user and BellSouth has a suitable alternate facility available, BellSouth will make such alternative facilities available to EveryCall. If a suitable alternative facility is not available, then to the extent it is technically feasible, BellSouth will implement one of the following alternative arrangements for EveryCall (e.g. hairpinning):
In the Event of Forecasted Surpluses If the HSP is forecasting a surplus, the LHIN may adjust the amount of Funding to be paid under Schedule B, require the repayment of excess Funding and/or adjust the amount of any future funding installments accordingly.
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
Particular Methods of Procurement of Consultants’ Services 1. Quality- and Cost-based Selection. Except as otherwise provided in paragraph 2 below, consultants’ services shall be procured under contracts awarded on the basis of Quality and Cost-based Selection.
