Evolution Layer Sample Clauses

Evolution Layer. ‌ The Evolution Layer contains three new workflows: the Situation Change workflow is responsible for monitoring semantic changes in the Active System and to propagate them into the DPS, in order to keep the preserved content understandable; the Setting Change workflow deals with changes in practices, formats and technology in the environment of the preservation (setting); finally, the System Change workflow is responsible for situa- tions, where one of the involved systems changes. The first two workflows are described in more detail below, whereas the last workflow is left to the revised version of the PoF Ref- erence Model which will be reported in deliverable D8.5 [ForgetIT, 2016]. In support of the aforementioned workflows, the Evolution Layer includes additional functionalities: Evolu- tion Monitoring, Context Evolution Management, Content Value Re-assessment and Context-aware Preservation Management. The Situation Change workflow consists of four steps (as depicted in Figure 8): (1) change monitoring, (2) change assessment (assessment of detected changes), (3) change notification (notification of involved components as well as the DPS on rele- vant changes) and (4) change propagation, which performs different types of actions depending on the observed change and the chosen change propagation strategy. For monitoring, assessing the changes and deciding about the consequences, in support to the Situation Change workflow, the functionalities Evolution Monitoring (mainly part of Active System), Context Evolution Management and Content Value Re-assessment have been introduced in the Evolution Layer: Figure 8: Situation Change Workflow in the Evolution Layer Evolution Monitoring The Evolution Monitoring functionality is required for the change monitoring step in the Situation Change workflow. This is mainly performed in the Active System (extension), because this is the main place, where evolution in the conceptual model of the application become visible. Such changes might, for ex- ample, be changes in the ontology (implicitly) underlying the organization of the information triggered e.g. by a major re-organization. Evolution Monitoring has to observe changes in the explicit representations of the conceptual model (such as taxonomies, information structures) in the Active System as well as more implicit signals of context evolution (e.g. newly upcoming topics, tags getting out of use, department sites no longer updated). Context Evolution Management The C...
AutoNDA by SimpleDocs
Evolution Layer. ‌ A preservation framework per definition exists in a long-lived environment aimed to sur- vive at least decades. Clearly, most of the involved parts widely ranging from formats, technology and systems to semantics, and relevant real world situations (represented by the application) will not remain stable (i.e. unchanged) over such long period of times. This implies that adequately dealing with changes is a core property that is required from such a framework. The purpose of the Evolution Layer is to adequately deal with the upcoming changes, such that the preserved content remains accessible and understandable. Clearly this means different things for different types of changes. Other types of actions are, for example, required in case a media format gets out of use as compared to the situation that an organization is re-organized. The Evolution Layer, therefore, groups the changes considered in three classes, each handled by its own type of change workflow. Thus, the Evolution Layer contains three new workflows: the Situation Change workflow is responsible for monitoring semantic changes in the Active System and propagating them into the DPS, in order to keep the preserved content understandable; the Setting Change workflow deals with changes in practices, formats and technology in the environment of the preservation (setting); finally, the System Change workflow is responsible for situations, where one of the involved systems changes. In support of the aforementioned workflows, the Evolution Layer includes additional func- tionalities: Content Value Re-assessment, Evolution Monitoring, Context Evolution Management and Context-aware Preservation Management.

Related to Evolution Layer

  • Provisioning of High Frequency Spectrum and Splitter Space 3.2.1 BellSouth will provide <<customer_name>> with access to the High Frequency Spectrum as follows:

  • Access Toll Connecting Trunk Group Architecture 9.2.1 If CBB chooses to subtend a Verizon access Tandem, CBB’s NPA/NXX must be assigned by CBB to subtend the same Verizon access Tandem that a Verizon NPA/NXX serving the same Rate Center Area subtends as identified in the LERG.

  • OVATIONS FOOD SERVICES, L.P. dba SPECTRA All food and beverage service must be discussed with and approved by Spectra, the OCFEC Master Concessionaire. FORM F-31 AGREEMENT NO. R-026-18 DATE May 16, 2018 REVIEWED APPROVED RENTAL AGREEMENT FAIRTIME INTERIM XX THIS AGREEMENT by and between the 32nd District Agricultural Association dba OC Fair & Event Center, hereinafter called the Association, and B & L Productions, Inc. hereinafter, called the Rentor

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

  • Infrastructure Improvements The design, redevelopment and construction and completion of certain infrastructure improvements, including sewer, stormwater, electrical and water main improvements, along with other similar improvements.

  • Information Technology Enterprise Architecture Requirements If this Contract involves information technology-related products or services, the Contractor agrees that all such products or services are compatible with any of the technology standards found at xxxxx://xxx.xx.xxx/iot/2394.htm that are applicable, including the assistive technology standard. The State may terminate this Contract for default if the terms of this paragraph are breached.

  • Network Interconnection Architecture Each Party will plan, design, construct and maintain the facilities within their respective systems as are necessary and proper for the provision of traffic covered by this Agreement. These facilities include but are not limited to, a sufficient number of trunks to the point of interconnection with the tandem company, and sufficient interoffice and interexchange facilities and trunks between its own central offices to adequately handle traffic between all central offices within the service areas at P.01 grade of service or better. The provisioning and engineering of such services and facilities will comply with generally accepted industry methods and practices, and will observe the rules and regulations of the lawfully established tariffs applicable to the services provided.

  • Mastectomy Services Inpatient This plan provides coverage for a minimum of forty-eight (48) hours in a hospital following a mastectomy and a minimum of twenty-four (24) hours in a hospital following an axillary node dissection. Any decision to shorten these minimum coverages shall be made by the attending physician in consultation with and upon agreement with you. If you participate in an early discharge, defined as inpatient care following a mastectomy that is less than forty-eight (48) hours and inpatient care following an axillary node dissection that is less than twenty-four (24) hours, coverage shall include a minimum of one (1) home visit conducted by a physician or registered nurse.

  • DEVELOPMENT OR ASSISTANCE IN DEVELOPMENT OF SPECIFICATIONS REQUIREMENTS/ STATEMENTS OF WORK Firms and/or individuals that assisted in the development or drafting of the specifications, requirements, statements of work, or solicitation documents contained herein are excluded from competing for this solicitation. This shall not be applicable to firms and/or individuals providing responses to a publicly posted Request for Information (RFI) associated with a solicitation.

  • Volunteer Firefighting Leave Leave without pay will be granted when an employee who is a volunteer firefighter is called to duty to respond to a fire, natural disaster or medical emergency.

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