PoF Framework Architecture Sample Clauses

PoF Framework Architecture. ‌ The architecture of the PoF Framework, described in detail in deliverable D8.1, is made up of three layers: Active Systems, Preserve-or-Forget (PoF) Middleware and Digital Preser- vation System (DPS), as depicted in Figure 11. The Active Systems represent user appli- cations, while the PoF Middleware is intended to enable seamless transition from Active Systems to the DPS (and vice versa) for the synergetic preservation, and to provide the necessary functionality for supporting managed forgetting and contextualized remember- ing. The PoF Middleware provides also the integration framework for all components developed in WP3-WP6. The DPS is composed by two sub-systems (Digital Reposi- tory and Preservation-aware Storage, including a Cloud Storage Service) and provides both content management and typical archive functionalities required for the synergetic preservation. The deliverable D8.1 also contained a preliminary discussion about the role of the OAIS Reference Model in the overall architecture: according to the project proposal, since OAIS nowadays is the most recognizable conceptualization of a digital preservation system, it was considered as one of the building blocks of ForgetIT approach. However, the model described in Section 3 complements and supersedes this initial approach towards the OAIS model. We further discuss the relationship with OAIS in Section 6.
AutoNDA by SimpleDocs

Related to PoF Framework Architecture

  • Architecture The Private Improvements shall have architectural features, detailing, and design elements in accordance with the Project Schematic Drawings. All accessory screening walls or fences, if necessary, shall use similar primary material, color, and detailing as on the Private Improvements.

  • Configuration Management The Contractor shall maintain a configuration management program, which shall provide for the administrative and functional systems necessary for configuration identification, control, status accounting and reporting, to ensure configuration identity with the UCEU and associated cables produced by the Contractor. The Contractor shall maintain a Contractor approved Configuration Management Plan that complies with ANSI/EIA-649 2011. Notwithstanding ANSI/EIA-649 2011, the Contractor’s configuration management program shall comply with the VLS Configuration Management Plans, TL130-AD-PLN-010-VLS, and shall comply with the following:

  • Start-Up and Synchronization Consistent with the mutually acceptable procedures of the Developer and Connecting Transmission Owner, the Developer is responsible for the proper synchronization of the Large Generating Facility to the New York State Transmission System in accordance with NYISO and Connecting Transmission Owner procedures and requirements.

  • Synchronization The Licensor hereby grants limited synchronization rights for One (1) music video streamed online (Youtube, Vimeo, etc..) for up to 500,000 non-monetized video streams on all total sites. A separate synchronisation license will need to be purchased for distribution of video to Television, Film or Video game.

  • Construction Phase Services 3.1.1 – Basic Construction Services

  • Interface A defined set of transmission facilities that separate Load Zones and that separate the NYCA from adjacent Control Areas. Investor-Owned Transmission Owners. A Transmission Owner that is owned by private investors. At the present time these include: Central Xxxxxx Gas & Electric Corporation, Consolidated Edison Company of New York, Inc., New York State Electric & Gas Corporation, Niagara Mohawk Power Corporation, Orange and Rockland Utilities, Inc., and Rochester Gas and Electric Corporation.

  • Registry Interoperability and Continuity Registry Operator shall comply with the Registry Interoperability and Continuity Specifications as set forth in Specification 6 attached hereto (“Specification 6”).

  • Configuration The configuration for the Purchase Right Aircraft will be the Detail Specification for Model 767-3S2F aircraft at the revision level in effect at the time of the Supplemental Agreement. Such Detail Specification will be revised to include (i) changes required to obtain required regulatory certificates and (ii) other changes as mutually agreed upon by Boeing and Customer.

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