Jupyter service implementations and registration Sample Clauses

Jupyter service implementations and registration status Table 1 Jupyter service instances at PaNOSC RIs and their EOSC registration Facility Service Prototype Production URL EOSC registration In progress done ESRF JupyterHub ✔ xxxxx://xxxxxxx-xxxxx.xxxx.xx ✔[1] ILL VISA ✔ xxxxx://xxxx.xxx.xx ✔[2] EuXFEL JupyterHub ✔ xxxxx://xxx-xxxx.xxxx.xx (✔*) ESS Jupyter Hub ✔ xxxxx://x-xxxxxxxx.xxx- xxxxxxxx.xx ✔[3] XXX-XXXX Xxxxxxx Hub ✔ xxxxxxxxx.xxx-laser.eu ✔ CERIC- XXXX Xxxxxxx ✔ xxxxx://xxx.xxxxxxx.xx ✔ EGI Jupyter Hub ✔ xxxxx://xxxxxxxxx.xxx.xx ✔[4] * Registration will be done by XXXX [1] xxxxx://xxxxxxxxxxx.xxxx-xxxxxx.xx/services/jupyter-notebook-can-be-used-to-create-and-share-documents- that-contain-live-code-equations-visualizations-and-text [2] xxxxx://xxxxxxxxxxx.xxxx-xxxxxx.xx/services/visa-virtual-infrastructure-for-scientific-analysis [3] xxxxx://xxxxxxxxxxx.xxxx-xxxxxx.xx/services/pan-learning-org-f68a8ee0-ed50-4eb1-b51a-b28516df7966 [4] xxxxx://xxxxxxxxxxx.xxxx-xxxxxx.xx/services/egi-notebooks Jupyter ecosystem services are present either as stand-alone web-service or as part of a larger service infrastructure:
AutoNDA by SimpleDocs

Related to Jupyter service implementations and registration

  • LICENSING, ACCREDITATION AND REGISTRATION The Contractor shall comply with all applicable local, state, and federal licensing, accreditation and registration requirements or standards necessary for the performance of this Contract.

  • 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.

  • Segregation and Registration Except as otherwise provided herein, and except for securities to be delivered to any subcustodian appointed pursuant to Sections 14.2 or 14.3 hereof, the Bank as custodian will receive and hold pursuant to the provisions hereof, in a separate account or accounts and physically segregated at all times from those of other persons, any and all Portfolio Securities which may now or hereafter be delivered to it by or for the account of the Fund. All such Portfolio Securities will be held or disposed of by the Bank for, and subject at all times to, the instructions of the Fund pursuant to the terms of this Agreement. Subject to the specific provisions herein relating to Portfolio Securities that are not physically held by the Bank, the Bank will register all Portfolio Securities (unless otherwise directed by Proper Instructions or an Officers' Certificate), in the name of a registered nominee of the Bank as defined in the Internal Revenue Code and any Regulations of the Treasury Department issued thereunder, and will execute and deliver all such certificates in connection therewith as may be required by such laws or regulations or under the laws of any state. The Fund will from time to time furnish to the Bank appropriate instruments to enable it to hold or deliver in proper form for transfer, or to register in the name of its registered nominee, any Portfolio Securities which may from time to time be registered in the name of the Fund.

  • Supported Initial and Renewal Registration Periods a. Initial registrations of Registered Names (where available according to functional specifications and other requirements) may be made in the registry for terms of up to ten years.

  • Proposing Integration Activities in the Planning Submission No integration activity described in section 6.3 may be proposed in a CAPS unless the LHIN has consented, in writing, to its inclusion pursuant to the process set out in section 6.3(b).

  • Licenses and Registrations It has all governmental, regulatory, self-regulatory, and exchange licenses, registrations, memberships, and approvals required to act as investment adviser to the Fund and it will obtain and maintain any such required licenses, registrations, memberships, and approvals.

  • Information Systems Acquisition Development and Maintenance Security of System Files. To protect City Information Processing Systems and system files containing information, Service Provider will ensure that access to source code is restricted to authorized users whose specific job function necessitates such access.

  • Shareholder Account Maintenance a. Maintain all shareholder records for each account in the Trust.

  • Allocation of Registration Opportunities In any circumstance in which all of the Registrable Securities and other shares of the Company with registration rights (the “Other Shares”) requested to be included in a registration contemplated by Section 2(a) cannot be so included as a result of limitations of the aggregate number of shares of Registrable Securities and Other Shares that may be so included, the number of shares of Registrable Securities and Other Shares that may be so included shall be allocated among the Holders and Other Shareholders requesting inclusion of shares pro rata on the basis of the number of shares of Registrable Securities and Other Shares held by such Holders and Other Shareholders; provided, however, that such allocation shall not operate to reduce the aggregate number of Registrable Securities and Other Shares to be included in such registration, if any Holder or Other Shareholder does not request inclusion of the maximum number of shares of Registrable Securities and Other Shares allocated to such Holder or Other Shareholder pursuant to the above-described procedure, then the remaining portion of such allocation shall be reallocated among those requesting Holders and Other Shareholders whose allocations did not satisfy their requests pro rata on the basis of the number of shares of Registrable Securities and Other Shares which would be held by such Holders and Other Shareholders, assuming conversion, and this procedure shall be repeated until all of the shares of Registrable Securities and Other Shares which may be included in the registration on behalf of the Holders and Other Shareholders have been so allocated.

  • Registration Compliance; No Stop Order No order suspending the effectiveness of the Registration Statement shall be in effect, and no proceeding for such purpose or pursuant to Section 8A under the Securities Act shall be pending before or threatened by the Commission; the Prospectus and each Issuer Free Writing Prospectus shall have been timely filed with the Commission under the Securities Act (in the case of an Issuer Free Writing Prospectus, to the extent required by Rule 433 under the Securities Act) and in accordance with Section 4(a) hereof; and all requests by the Commission for additional information shall have been complied with to the reasonable satisfaction of the Representatives.

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