Service Registry Sample Clauses

Service Registry a database for raw measures The Service Registry contains all the information about the network performance. The raw measures produced by the SLA Observer can’t be stored in the WSN nodes, that are memory-constrained (they can only keep the current local information). Moreover, the raw measures must be consulted by the other enti- ties of the architecture (SLA Manager, SLA Admit- ter), without occupying the WSN resource. Hence, the Service Registry must be centralized (e.g. a database in the WSN operator core network). We keep the raw measures all along the SLA du- ration. Thus, if the WSN operator changes the algo- rithms of the SLA Manager and SLA Admitter, new policies can be applied taking into account the whole history of the WSN. Given that we monitor various sensor nodes, dur- ing long periods, the measures have to be accurately identified and classified. We propose the following log format for the raw measures: • timestamp: the time of the measure; • measurer (id): the producer of the measure; • entity (ids): which entities have been measured;
AutoNDA by SimpleDocs
Service Registry. This defines the components that enable discovery and execution of different backend services in the platform through the frontend.
Service Registry. This is a repository where service providers register their services. We assume that the providers would also supply details of the QoS metrics and that they will not publish false QoS values for one reason or the other.
Service Registry a database for raw measures • timestamp: the time of the measure; • measurer (id): the producer of the measure; • entity (ids): which entities have been measured;
Service Registry. In an interconnected platform ecosystem such as EFPFInterop, the services of different platforms need to be composed together to achieve common objectives. For this purpose, the service consumers should be able to discover the available services, retrieve their API metadata, and consume them without the active involvement of the service providers. The Data Spine Service Registry provides the following mechanisms to fulfil these requirements: • Registration and lifecycle management of service/API metadata for synchronous (Request- Response) as well as asynchronous (Pub/Sub) services in a uniform manner • Discovery, lookup, and filtering of services • Use of standard API specifications (specs) to capture service metadata to ensure the completeness of and uniformity across the API descriptions. Figure 8 shows the abstract class diagram for the Service Registry that illustrates composition relationship between its classes. The notation ‘0..*’ in the diagram denotes ‘zero or more instances’ of the concerned entity. As illustrated in the diagram, the Catalog of the Service Registry can have zero or more services. Each Service has zero or more APIs, and each API has exactly one API specification (Spec). <.. image(Diagram Description automatically generated) removed ..>
Service Registry. LinkSmart Service Catalog can be used to realise the Service Registry component of Data Spine. Service Catalog is the entry point for web services. Its functionality mainly covers the lifecycle management of services i.e., the registration, viewing, updating and deregistration of services’ metadata. In addition, it supports browsing of the registered service entries and provides a service filtering functionality that can be used by service consumers to search services by known capabilities. The schema of Service Catalog supports storing metadata for both synchronous (Request-Response) as well as asynchronous (Pub/Sub) type of services. Moreover, the Service Catalog provides an MQTT API for announcing the service registration/deregistration events over predefined MQTT topics.

Related to Service Registry

  • Registry The Borrower hereby designates the Administrative Agent to serve as the Borrower’s agent, solely for purposes of this Section 12.17 to maintain a register (the “Register”) on which it will record the Commitments from time to time of each of the Lenders, the Loans made by each of the Lenders and each repayment in respect of the principal amount of the Loans of each Lender. Failure to make any such recordation, or any error in such recordation shall not affect the Borrower’s obligations in respect of such Loans. With respect to any Lender, the transfer of the Commitments of such Lender and the rights to the principal of, and interest on, any Loan made pursuant to such Commitments shall not be effective until such transfer is recorded on the Register maintained by the Administrative Agent with respect to ownership of such Commitments and Loans and prior to such recordation all amounts owing to the transferor with respect to such Commitments and Loans shall remain owing to the transferor. The registration of assignment or transfer of all or part of any Commitments and Loans shall be recorded by the Administrative Agent on the Register only upon the acceptance by the Administrative Agent of a properly executed and delivered Assignment and Assumption Agreement pursuant to Section 12.8(c). Coincident with the delivery of such an Assignment and Assumption Agreement to the Administrative Agent for acceptance and registration of assignment or transfer of all or part of a Loan, or as soon thereafter as practicable, the assigning or transferor Lender shall surrender the Note evidencing such Loan, and thereupon one or more new Notes in the same aggregate principal amount then owing to such assignor or transferor Lender shall be issued to the assigning or transferor Lender and/or the new Lender. The Borrower agrees to indemnify the Administrative Agent from and against any and all losses, claims, damages and liabilities of whatsoever nature which may be imposed on, asserted against or incurred by the Administrative Agent in performing its duties under this Section 12.17.

  • Registry Services “Registry Services” are, for purposes of the Agreement, defined as the following: (a) those services that are operations of the registry critical to the following tasks: the receipt of data from registrars concerning registrations of domain names and name servers; provision to registrars of status information relating to the zone servers for the TLD; dissemination of TLD zone files; operation of the registry DNS servers; and dissemination of contact and other information concerning domain name server registrations in the TLD as required by this Agreement; (b) other products or services that the Registry Operator is required to provide because of the establishment of a Consensus Policy as defined in Specification 1; (c) any other products or services that only a registry operator is capable of providing, by reason of its designation as the registry operator; and (d) material changes to any Registry Service within the scope of (a), (b) or (c) above.

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

  • Certificate Register 7 Class .......................................................................................7

  • Registered Nurse Level 3 (RN3) An employee at this level may also be known as a Clinical Nurse Consultant, Nurse Manager or Nurse Educator. An employee appointed at this level: Holds any other qualification required for working in the employee’s particular practice setting; and is appointed as such by a selection process or by reclassification from a lower level when that the employee is required to perform the duties detailed in this subclause on a continuing basis. In addition to the duties of an RN2, an employee at this level will perform the following duties in accordance with practice settings and patient or client groups: Duties of a Clinical Nurse Consultant will substantially include, but are not confined to:  Providing leadership and role modelling, in collaboration with others including the Nurse Manager and the Nurse Educator, particularly in the areas of action research and quality assurance programs;  Staff and patient/client education; staff selection, management, development and appraisal; Participating in policy development and implementation;  Acting as a consultant on request in the employee’s own area of proficiency for the purpose of facilitating the provision of quality nursing care;  Delivering direct and comprehensive nursing care to a specific group of patients or clients with complex nursing care needs, in a particular area of nursing practice within a practice setting;  Coordinating, and ensuring the maintenance of standards of the nursing care of a specific group or population of patients or clients within a practice setting; and  Coordinating or managing nursing or multidisciplinary service teams providing acute nursing and community services. Duties of a Nurse Manager will substantially include, but are not confined to:  Providing leadership and role modelling, in collaboration with others Including the Clinical Nurse Consultant and the Nurse Educator, particularly in the areas of action research and quality assurance programs;  Staff selection and education; allocation and rostering of staff;  Occupational health;  Initiation and evaluation of research related to staff and resource management;  Participating in policy development and implementation;  Acting as a consultant on request in the employee’s own area of proficiency (for the purpose of facilitating the provision of quality nursing care);  Being accountable for the management of human and material resources within a specified span of control, including the development and evaluation of staffing methodologies; and  Managing financial matters, budget preparation and cost control in respect of nursing within that span of control. Duties of a Nurse Educator will substantially include, but are not confined to:  Providing leadership and role modelling, in collaboration with others including the Clinical Nurse Consultant and the Nurse Manager, particularly in the areas of action research;  Implementation and evaluation of staff education and development programs;  Staff selection;  Implementation and evaluation of patient or client education programs;

  • Transition of Registry upon Termination of Agreement text for intergovernmental organizations or governmental entities or other special circumstances: “Transition of Registry upon Termination of Agreement. Upon expiration of the Term pursuant to Section 4.1 or Section 4.2 or any termination of this Agreement pursuant to Section 4.3 or Section 4.4, in connection with ICANN’s designation of a successor registry operator for the TLD, Registry Operator and ICANN agree to consult each other and work cooperatively to facilitate and implement the transition of the TLD in accordance with this Section 4.5. After consultation with Registry Operator, ICANN shall determine whether or not to transition operation of the TLD to a successor registry operator in its sole discretion and in conformance with the Registry Transition Process. In the event ICANN determines to transition operation of the TLD to a successor registry operator, upon Registry Operator’s consent (which shall not be unreasonably withheld, conditioned or delayed), Registry Operator shall provide ICANN or such successor registry operator for the TLD with any data regarding operations of the TLD necessary to maintain operations and registry functions that may be reasonably requested by ICANN or such successor registry operator in addition to data escrowed in accordance with Section 2.3 hereof. In the event that Registry Operator does not consent to provide such data, any registry data related to the TLD shall be returned to Registry Operator, unless otherwise agreed upon by the parties. Registry Operator agrees that ICANN may make any changes it deems necessary to the IANA database for DNS and WHOIS records with respect to the TLD in the event of a transition of the TLD pursuant to this Section 4.5. In addition, ICANN or its designee shall retain and may enforce its rights under the Continued Operations Instrument, regardless of the reason for termination or expiration of this Agreement.”]

  • Registered Office; Registered Agent The address of the registered office and the name and address of the registered agent of the Company in the State of Delaware is c/o The Corporation Trust Company, Corporation Trust Center, 0000 Xxxxxx Xxxxxx, Xxxx xx Xxxxxxxxxx, Xxxxxx of Xxx Xxxxxx, Xxxxxxxx 00000.

  • Variable Registry-­‐Level Fee (a) If the ICANN accredited registrars (accounting, in the aggregate, for payment of two-­‐thirds of all registrar-­‐level fees (or such portion of ICANN accredited registrars necessary to approve variable accreditation fees under the then-­‐current registrar accreditation agreement), do not approve, pursuant to the terms of their registrar accreditation agreements with ICANN, the variable accreditation fees established by the ICANN Board of Directors for any ICANN fiscal year, upon delivery of notice from ICANN, Registry Operator shall pay to ICANN a variable registry-­‐level fee, which shall be paid on a fiscal quarter basis, and shall accrue as of the beginning of the first fiscal quarter of such ICANN fiscal year (the “Variable Registry-­‐Level Fee”). The fee will be calculated and invoiced by ICANN on a quarterly basis, and shall be paid by Registry Operator within sixty (60) calendar days with respect to the first quarter of such ICANN fiscal year and within twenty (20) calendar days with respect to each remaining quarter of such ICANN fiscal year, of receipt of the invoiced amount by ICANN. The Registry Operator may invoice and collect the Variable Registry-­‐Level Fees from the registrars that are party to a registry-­‐ registrar agreement with Registry Operator (which agreement may specifically provide for the reimbursement of Variable Registry-­‐Level Fees paid by Registry Operator pursuant to this Section 6.3); provided, that the fees shall be invoiced to all ICANN accredited registrars if invoiced to any. The Variable Registry-­‐Level Fee, if collectible by ICANN, shall be an obligation of Registry Operator and shall be due and payable as provided in this Section 6.3 irrespective of Registry Operator’s ability to seek and obtain reimbursement of such fee from registrars. In the event ICANN later collects variable accreditation fees for which Registry Operator has paid ICANN a Variable Registry-­‐Level Fee, ICANN shall reimburse the Registry Operator an appropriate amount of the Variable Registry-­‐Level Fee, as reasonably determined by ICANN. If the ICANN accredited registrars (as a group) do approve, pursuant to the terms of their registrar accreditation agreements with ICANN, the variable accreditation fees established by the ICANN Board of Directors for a fiscal year, ICANN shall not be entitled to a Variable-­‐Level Fee hereunder for such fiscal year, irrespective of whether the ICANN accredited registrars comply with their payment obligations to ICANN during such fiscal year. (b) The amount of the Variable Registry-­‐Level Fee will be specified for each registrar, and may include both a per-­‐registrar component and a transactional component. The per-­‐registrar component of the Variable Registry-­‐Level Fee shall be specified by ICANN in accordance with the budget adopted by the ICANN Board of Directors for each ICANN fiscal year. The transactional component of the Variable Registry-­‐Level Fee shall be specified by ICANN in accordance with the budget adopted by the ICANN Board of Directors for each ICANN fiscal year but shall not exceed US$0.25 per domain name registration (including renewals associated with transfers from one ICANN accredited registrar to another) per year.

  • Maintenance of Office and Transfer Books by the Registrar Until termination of this Deposit Agreement in accordance with its terms, the Depositary or if a Registrar for the Receipts shall have been appointed, the Registrar shall maintain in the Borough of Manhattan, the City of New York, an office and facilities for the execution and delivery, registration, registration of transfers, combination and split-up of Receipts, the surrender of Receipts and the Delivery and withdrawal of Deposited Securities in accordance with the provisions of this Deposit Agreement. The Depositary or the Registrar as applicable, shall keep books for the registration of Receipts and transfers of Receipts which at all reasonable times shall be open for inspection by the Company and by the Holders of such Receipts, provided that such inspection shall not be, to the Depositary’s or the Registrar’s knowledge, for the purpose of communicating with Holders of such Receipts in the interest of a business or object other than the business of the Company or other than a matter related to this Deposit Agreement or the Receipts. The Depositary or the Registrar, as applicable, may close the transfer books with respect to the Receipts, at any time and from time to time, when deemed necessary or advisable by it in connection with the performance of its duties hereunder, or at the reasonable written request of the Company. If any Receipts or the American Depositary Shares evidenced thereby are listed on one or more stock exchanges or automated quotation systems in the United States, the Depositary shall act as Registrar or appoint a Registrar or one or more co-registrars for registration of Receipts and transfers, combinations and split-ups, and to countersign such Receipts in accordance with any requirements of such exchanges or systems. Such Registrar or co-registrars may be removed and a substitute or substitutes appointed by the Depositary. If any Receipts or the American Depositary Shares evidenced thereby are listed on one or more securities exchanges, markets or automated quotation systems, (i) the Depositary shall be entitled to, and shall, take or refrain from taking such action(s) as it may deem necessary or appropriate to comply with the requirements of such securities exchange(s), market(s) or automated quotation system(s) applicable to it, notwithstanding any other provision of this Deposit Agreement; and (ii) upon the reasonable request of the Depositary, the Company shall provide the Depositary such information and assistance as may be reasonably necessary for the Depositary to comply with such requirements, to the extent that the Company may lawfully do so. Each Registrar and co-registrar appointed under this Section 5.1 shall give notice in writing to the Depositary accepting such appointment and agreeing to be bound by the applicable terms of the Deposit Agreement.

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

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