Matchmaking Implementation Sample Clauses

Matchmaking Implementation. The Federated Search is developed as a Spring Boot microservice. It consists of the Matchmaking Ontology and an API for accessing the indexed data. It hides the complexity using a full featured search engine (Apache SOLR3) and provides simplified access to the indexed data, supporting full text search and faceted search over the indexed data collections. Apache Solr is a scalable and fault tolerant search platform that provides distributed indexing, replication and load-balanced querying, automated failover and recovery, centralized configuration and more. The Matchmaking Ontology in EFPF is the foundation of the SOLR data model and is inspired by the SKOS4 (Simple Knowledge Organization System) Ontology. SKOS is a common data model for sharing and linking knowledge systems using the Semantic Web technologies. In short, SKOS specifies the notion of concepts which might be connected by means of broader and narrower relationships. Concepts might be grouped together in concept schemes and allow for multilingual naming with preferred, (multiple) alternate and hidden names. Apache SOLR allows for storing arbitrary documents with flexible data models. However, to support the matchmaking and federated search processes, the EFPF Matchmaking Ontology has been defined (see Figure 22 below). Figure 22 — Matchmaking Ontology (simplified view) Every data item of interest is categorized using arbitrary concepts or treated as an instance of a certain class. The Concept class specifies dedicated attributes which are commonly present. This is reflected in the Matchmaking Ontology with the Class/Category and the Property collections. As outlined in Figure 22, each indexed product (Item) might be annotated as an instance of a predefined Class/Category. The Class/Category however will then provide the relevant attributes which are expected to be present with the indexed product. These relationships (Item is instance of Class/Category; Class/Category has Properties) is important for providing search interfaces since the data items need to be presented in a human readable way. The Matchmaking Service is based on the Matchmaking Ontology that defines the internal data structure and format of the indexed data. This data structure must be adhered when using the services for storing and retrieving the data. 3 xxxxx://xxxx.xxxxxx.xxx/ 4 xxxxx://xxx.x0.xxx/TR/swbp-skos-core-spec/ In the indexing workflow (see Figure 21), the base platform’s data stores provide their data to the Match...
Sample 1
AutoNDA by SimpleDocs

Related to Matchmaking Implementation

  • Project Implementation 2. The Borrower shall:

  • Implementation Plan The Authority shall cause to be prepared an Implementation Plan meeting the requirements of Public Utilities Code Section 366.2 and any applicable Public Utilities Commission regulations as soon after the Effective Date as reasonably practicable. The Implementation Plan shall not be filed with the Public Utilities Commission until it is approved by the Board in the manner provided by Section 4.9.

  • Implementation Program 1. The Borrower shall:

  • Implementation Schedule TIME IS OF THE ESSENCE with regard to all dates and time periods set forth and/or incorporated herein. Any material modification or deviation from an approved schedule described in this Agreement shall occur only upon approval of the City and RDA, with any such approvals required to be in writing as an amendment to this Agreement, and which approvals shall not be unreasonably withheld. City shall cooperate and act promptly with respect to any and all permits or approvals necessary for completion of the Project. Notwithstanding the above, this Agreement shall not limit the discretion of the City, or any of its duly appointed and authorized governing bodies, boards or entities, in approving or rejecting any aspect of the Project or improvements contemplated on or about the Property.

  • Project Implementation Manual The Recipient, through the PCU, shall: (i) take all action required to carry out Parts 1.1, 1.3, 1.4, 2, 3.1(b), 3.2, 3.3 and 4 (ii) of the Project in accordance with the provisions and requirements set forth or referred to in the Project Implementation Manual; (ii) submit recommendations to the Association for its consideration for changes and updates of the Project Implementation Manual as they may become necessary or advisable during Project implementation in order to achieve the objective of Parts 1.1, 1.3, 1.4, 2, 3.1(b), 3.2, 3.3 and 4(ii) of the Project; and (iii) not assign, amend, abrogate or waive the Project Implementation Manual or any of its provisions without the Association’s prior agreement. Notwithstanding the foregoing, if any of the provisions of the Project Implementation Manual is inconsistent with the provisions of this Agreement, the provisions of this Agreement shall prevail and govern.

  • Joint Network Implementation and Grooming Process Upon request of either Party, the Parties shall jointly develop an implementation and grooming process (the “Joint Grooming Process” or “Joint Process”) which may define and detail, inter alia:

  • Implementation Services The Company and the Client have developed a plan for implementing the services to be provided hereunder, including with respect to the transition of responsibility for such services from the Client and its current administrator to the Company, which plan attached hereto as Schedule I (the “Implementation Plan”). The Company shall perform the services required to complete the Implementation Plan, as set forth therein (the “Implementation Services”). The Company and the Client shall comply with any applicable requirements agreed in the Implementation Plan.

  • Implementation Specifications 1. The accounting shall contain the date, nature, and purpose of such disclosures, and the name and address of the person or agency to whom the disclosure is made.

  • Implementation and Review The Parties shall consult annually, or as otherwise agreed, to review the implementation of this Chapter and consider other matters of mutual interest affecting trade in services. (10) 10 Such consultations will be addressed under Article 170 (Free Trade Commission) of Chapter 14 (Administration of the Agreement).

  • Implementation Report Within 150 days after the Effective Date, Extendicare shall submit a written report to OIG summarizing the status of its implementation of the requirements of this CIA (Implementation Report). The Implementation Report shall, at a minimum, include:

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