DCT Gdańsk S Sample Clauses

DCT Gdańsk S. A. with its registered office in Gdańsk, address: xx. Xxxxxxxxxxx 0, 80- 601 Gdańsk, recorded in the business register kept by the District Court for Gdańsk- Północ in Gdańsk, Commercial Division VII of the National Court Register under number KRS 31077, share capital: PLN 65,500,000; NIP 2040000183; Regon 192967316, represented by: and
AutoNDA by SimpleDocs
DCT Gdańsk S. A. z siedzibą w Gdańsku; adres: xx. Xxxxxxxxxxx 0, 80- 601 Gdańsk, wpisaną do rejestru przedsiębiorców prowadzonego przez Sąd Rejonowy Gdańsk-Północ w Gdańsku, VII Wydział Gospodarczy Krajowego Rejestru Sądowego xxx xx XXX 00000, xxxxxxx xxxxxxxxx 65.500.000 zł.; NIP 2040000183; Regon 192967316, reprezentowaną przez: 1. DCT Gdańsk S.A. with its registered office in Gdańsk, address: xx. Xxxxxxxxxxx 0, 00-000 Xxxxxx, recorded in the business register kept by the District Court for Gdańsk-Północ in Gdańsk, Commercial Division VII of the National Court Register under number KRS 31077, share capital: PLN 65,500,000; NIP 2040000183; Regon 192967316, represented by: [●] - [●] [●] - [●] zwaną dalej "Zamawiającym"; hereinafter referred to as the "Client"; a and

Related to DCT Gdańsk S

  • Argentina Caja de Valores S A. Australia Austraclear Limited Reserve Bank Information and Transfer System Austria Öesterreichische Kontrollbank AG (Wertpapiersammelbank Division) Belgium Caisse Interprofessionnelle de Dépôt et de Virement de Titres S.A. Banque Nationale de Belgique Brazil Companhia Brasileira de Liquidaçao e Custodia (CBLC) Bolsa de Valores de Rio de Janeiro All SSB clients presently use CBLC Central de Custodia e de Liquidação Financeira de Titulos Bulgaria Central Depository AD Bulgarian National Bank Canada The Canadian Depository for Securities Limited People’s Republic Shanghai Securities Central Clearing and of China Registration Corporation Shenzhen Securities Central Clearing Co., Ltd. Costa Rica Central de Valores S.A. (CEVAL) Croatia Ministry of Finance National Bank of Croatia Czech Republic Stredisko cenných papírů Czech National Bank Denmark Værdipapircentralen (the Danish Securities Center) Egypt Misr Company for Clearing, Settlement, and Central Depository Estonia Eesti Väärtpaberite Keskdepositoorium Finland The Finnish Central Securities Depository France Société Interprofessionnelle pour la Compensation des Valeurs Mobilières (SICOVAM) Germany Deutsche Börse Clearing AG Greece The Central Securities Depository (Apothetirion Titlon AE) Hong Kong The Central Clearing and Settlement System Central Money Markets Unit Hungary The Central Depository and Clearing House (Budapest) Ltd. (KELER) India The National Securities Depository Limited Indonesia Bank Indonesia Ireland Central Bank of Ireland Securities Settlement Office Israel The Tel Aviv Stock Exchange Clearing House Ltd. Bank of Israel Italy Monte Titoli S.p.A. Banca d’Italia Ivory Coast Depositaire Central – Banque de Règlement Jamaica The Jamaican Central Securities Depository Japan Bank of Japan Net System Kenya Central Bank of Kenya Republic of Korea Korea Securities Depository Corporation Latvia The Latvian Central Depository Lebanon The Custodian and Clearing Center of Financial Instruments for Lebanon and the Middle East (MIDCLEAR) X.X.X. The Central Bank of Lebanon Lithuania The Central Securities Depository of Lithuania Malaysia The Malaysian Central Depository Sdn. Bhd. Bank Negara Malaysia, Scripless Securities Trading and Safekeeping System Mauritius The Central Depository & Settlement Co. Ltd. Mexico S.D. INDEVAL, S.A. de C.V. (Instituto para el Depósito de Valores) Morocco Maroclear The Netherlands Nederlands Centraal Instituut voor Giraal Effectenverkeer B.V. (NECIGEF) De Nederlandsche Bank N.V. New Zealand New Zealand Central Securities Depository Limited Norway Verdipapirsentralen (the Norwegian Registry of Securities) Oman Muscat Securities Market Pakistan Central Depository Company of Pakistan Limited Peru Caja de Valores y Liquidaciones S.A. (CAVALI) Philippines The Philippines Central Depository, Inc. The Registry of Scripless Securities (XXXX) of the Bureau of the Treasury Poland The National Depository of Securities (Krajowy Depozyt Papierów Wartościowych) Central Treasury Bills Registrar Portugal Central de Valores Mobiliários (Central) Romania National Securities Clearing, Settlement and Depository Co. Bucharest Stock Exchange Registry Division Singapore The Central Depository (Pte) Limited Monetary Authority of Singapore Slovak Republic Stredisko Cenných Papierov National Bank of Slovakia Slovenia Klirinsko Depotna Xxxxxx x.x. South Africa The Central Depository Limited Spain Servicio de Compensación y Liquidación de Valores, S.A. Banco de España, Central de Anotaciones en Cuenta Sri Lanka Central Depository System (Pvt) Limited Sweden Värdepapperscentralen AB (the Swedish Central Securities Depository) Switzerland Schweizerische Effekten - Giro AG Taiwan - R.O.C. The Taiwan Securities Central Depository Co., Ltd. Thailand Thailand Securities Depository Company Limited Tunisia Société Tunisienne Interprofessionelle de Compensation et de Dépôt de Valeurs Mobilières Central Bank of Tunisia Tunisian Treasury Turkey Takas ve Saklama Bankasi A.S. (TAKASBANK) Central Bank of Turkey Ukraine The National Bank of Ukraine United Kingdom The Bank of England, The Central Gilts Office and The Central Moneymarkets Office Uruguay Central Bank of Uruguay Venezuela Central Bank of Venezuela Zambia Lusaka Central Depository Limited Bank of Zambia

  • Originating Switched Access Detail Usage Data A category 1101XX record as defined in the EMI Telcordia Practice BR-010-200- 010.

  • FORMAT AND CONTENT FOR REGISTRY OPERATOR MONTHLY REPORTING Registry Operator shall provide one set of monthly reports per gTLD, using the API described in draft-­‐xxxxxx-­‐icann-­‐registry-­‐interfaces, see Specification 2, Part A, Section 9, reference 5, with the following content. ICANN may request in the future that the reports be delivered by other means and using other formats. ICANN will use reasonable commercial efforts to preserve the confidentiality of the information reported until three (3) months after the end of the month to which the reports relate. Unless set forth in this Specification 3, any reference to a specific time refers to Coordinated Universal Time (UTC). Monthly reports shall consist of data that reflects the state of the registry at the end of the month (UTC).

  • Joint Funded Project with the Ohio Department of Transportation In the event that the Recipient does not have contracting authority over project engineering, construction, or right-of-way, the Recipient and the OPWC hereby assign certain responsibilities to the Ohio Department of Transportation, an authorized representative of the State of Ohio. Notwithstanding Sections 4, 6(a), 6(b), 6(c), and 7 of the Project Agreement, Recipient hereby acknowledges that upon notification by the Ohio Department of Transportation, all payments for eligible project costs will be disbursed by the Grantor directly to the Ohio Department of Transportation. A Memorandum of Funds issued by the Ohio Department of Transportation shall be used to certify the estimated project costs. Upon receipt of a Memorandum of Funds from the Ohio Department of Transportation, the OPWC shall transfer funds directly to the Ohio Department of Transportation via an Intra- State Transfer Voucher. The amount or amounts transferred shall be determined by applying the Participation Percentages defined in Appendix D to those eligible project costs within the Memorandum of Funds. In the event that the Project Scope is for right-of-way only, notwithstanding Appendix D, the OPWC shall pay for 100% of the right-of-way costs not to exceed the total financial assistance provided in Appendix C.

  • 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

  • Pricing for Registry Services (a) With respect to initial domain name registrations, Registry Operator shall provide ICANN and each ICANN accredited registrar that has executed the registry-­‐registrar agreement for the TLD advance written notice of any price increase (including as a result of the elimination of any refunds, rebates, discounts, product tying or other programs which had the effect of reducing the price charged to registrars, unless such refunds, rebates, discounts, product tying or other programs are of a limited duration that is clearly and conspicuously disclosed to the registrar when offered) of no less than thirty (30) calendar days. Registry Operator shall offer registrars the option to obtain initial domain name registrations for periods of one (1) to ten (10) years at the discretion of the registrar, but no greater than ten (10) years. (b) With respect to renewal of domain name registrations, Registry Operator shall provide ICANN and each ICANN accredited registrar that has executed the registry-­‐registrar agreement for the TLD advance written notice of any price increase (including as a result of the elimination of any refunds, rebates, discounts, product tying, Qualified Marketing Programs or other programs which had the effect of reducing the price charged to registrars) of no less than one hundred eighty (180) calendar days. Notwithstanding the foregoing sentence, with respect to renewal of domain name registrations: (i) Registry Operator need only provide thirty (30) calendar days notice of any price increase if the resulting price is less than or equal to (A) for the period beginning on the Effective Date and ending twelve (12) months following the Effective Date, the initial price charged for registrations in the TLD, or (B) for subsequent periods, a price for which Registry Operator provided a notice pursuant to the first sentence of this Section 2.10(b) within the twelve (12) month period preceding the effective date of the proposed price increase; and (ii) Registry Operator need not provide notice of any price increase for the imposition of the Variable Registry-­‐Level Fee set forth in Section 6.3. Registry Operator shall offer registrars the option to obtain domain name registration renewals at the current price (i.e., the price in place prior to any noticed increase) for periods of one (1) to ten (10) years at the discretion of the registrar, but no greater than ten (10) years. (c) In addition, Registry Operator must have uniform pricing for renewals of domain name registrations (“Renewal Pricing”). For the purposes of determining Renewal Pricing, the price for each domain registration renewal must be identical to the price of all other domain name registration renewals in place at the time of such renewal, and such price must take into account universal application of any refunds, rebates, discounts, product tying or other programs in place at the time of renewal. The foregoing requirements of this Section 2.10(c) shall not apply for (i) purposes of determining Renewal Pricing if the registrar has provided Registry Operator with documentation that demonstrates that the applicable registrant expressly agreed in its registration agreement with registrar to higher Renewal Pricing at the time of the initial registration of the domain name following clear and conspicuous disclosure of such Renewal Pricing to such registrant, and (ii) discounted Renewal Pricing pursuant to a Qualified Marketing Program (as defined below). The parties acknowledge that the purpose of this Section 2.10(c) is to prohibit abusive and/or discriminatory Renewal Pricing practices imposed by Registry Operator without the written consent of the applicable registrant at the time of the initial registration of the domain and this Section 2.10(c) will be interpreted broadly to prohibit such practices. For purposes of this Section 2.10(c), a “Qualified Marketing Program” is a marketing program pursuant to which Registry Operator offers discounted Renewal Pricing, provided that each of the following criteria is satisfied: (i) the program and related discounts are offered for a period of time not to exceed one hundred eighty (180) calendar days (with consecutive substantially similar programs aggregated for purposes of determining the number of calendar days of the program), (ii) all ICANN accredited registrars are provided the same opportunity to qualify for such discounted Renewal Pricing; and (iii) the intent or effect of the program is not to exclude any particular class(es) of registrations (e.g., registrations held by large corporations) or increase the renewal price of any particular class(es) of registrations. Nothing in this Section 2.10(c) shall limit Registry Operator’s obligations pursuant to Section 2.10(b). (d) Registry Operator shall provide public query-­‐based DNS lookup service for the TLD (that is, operate the Registry TLD zone servers) at its sole expense.

  • List of Operator’s Subprocessors [Box 26] [Box 27] [Box 28] [Box 29]

  • AUDIT OF LICENSED PRODUCT USAGE Contractor shall have the right to periodically audit, no more than annually, at Contractor’s expense, use of licensed Product at any site where a copy of the Product resides provided that: (i) Contractor gives Licensee(s) at least thirty (30) days advance written notice, (ii) such audit is conducted during such party’s normal business hours, (iii) the audit is conducted by an independent auditor chosen on mutual agreement of the parties. Contractor shall recommend a minimum of three (3) auditing/accounting firms from which the Licensee will select one (1). In no case shall the Business Software Alliance (BSA), Software Publishers Association (SPA), Software and Industry Information Association (SIIA) or Federation Against Software Theft (FAST) be used directly or indirectly to conduct audits, or be recommended by Contractor; (iv) Contractor and Licensee are each entitled to designate a representative who shall be entitled to participate, and who shall mutually agree on audit format, and simultaneously review all information obtained by the audit. Such representatives also shall be entitled to copies of all reports, data or information obtained from the audit; and (v) if the audit shows that such party is not in compliance, Licensee shall be required to purchase additional licenses or capacities necessary to bring it into compliance and shall pay for the unlicensed capacity at the NYS Net Price in effect at time of audit, or if none, then at the Contractor’s U.S. Commercial list price. Once such additional licenses or capacities are purchased, Licensee shall be deemed to have been in compliance retroactively, and Licensee shall have no further liability of any kind for the unauthorized use of the software.

  • COVID-19 Vaccine Passports Pursuant to Texas Health and Safety Code, Section 161.0085(c), Contractor certifies that it does not require its customers to provide any documentation certifying the customer’s COVID-19 vaccination or post-transmission recovery on entry to, to gain access to, or to receive service from the Contractor’s business. Contractor acknowledges that such a vaccine or recovery requirement would make Contractor ineligible for a state-funded contract.

  • AIRBUS S A.S., a société par actions simplifiée, created and existing under French law having its registered office at 0 Xxxx‑Xxxxx Xxxxxxx Xxxxxxxx, 31707 Blagnac-Cedex, France and registered with the Toulouse Registre du Commerce under number RCS Toulouse 383 474 814 (the "Seller"), and AIR LEASE CORPORATION, a corporation organised and existing under the laws of the State of Delaware, U.S.A., having its principal place of business at 0000 Xxxxxx xx xxx Xxxxx, Xxxxx 0000X, Los Angeles, California 90067, U.S.A. (the “Buyer”). The Buyer and Seller together are referred to as the “Parties”.

Draft better contracts in just 5 minutes Get the weekly Law Insider newsletter packed with expert videos, webinars, ebooks, and more!