Main objectives and goals. The goal of this deliverable is to collect the use cases, list the user requirements, and present the detailed EUMSSI system functionalities. The first step is to gather the use cases related to the two EUMSSI scenarios from the intended target groups. Numerous techniques to achieve this are summarised in Table 2. For this purpose Deutsche Welle conducted guided interviews in order to collect the requirements and wishes in an explorative approach.
Main objectives and goals. The architecture description provided in this document serves several goals, including: Offering a basis for (formal) agreement about the form of the system to be built. The architecture description is the result of various iterations and discussions with consortium partners, either plenary or on a one-to-one basis. This document should serve as a reference point for mutual understanding. Validating assumptions on expected functionality and main priorities, as well as on the responsibilities of each partner with respect to the modules to be developed. Providing management decision points by making important choices and their implications explicit. This deliverable is the result of the activities defined in Task 2.2 of the Description of Work: This task will define the overall architecture of the system based on the requirements as well as the individual components to be developed in WP3 and WP4. The architecture description will comply with ISO/IEC/IEEE 42010 Systems and software engineering — Architecture description standard. The architecture will describe all functional, logical, structural, physical, process, user action and data model of the system (system components, clients, delivery methods, etc.). UML diagrams will be used to specify, visualize, modify, construct and document the components of the system such as: activities, actors, business processes, and database schemas.
Main objectives and goals. The main objectives of this deliverable are to: ● To provide an architectural overview of the search and transformation framework and its constituent parts ● To provide a detailed description of each of the building blocks along with different deployment options ● To provide guidelines for interoperability, collaboration and extension of framework components ● To provide suggestions for further development and continued research and development
Main objectives and goals. As the PHENICX project focuses on digital techniques to make classical music accessible to broader audiences, it is essential that already during the lifetime of the project, potential audiences will actively be able to give feedback on any potential digital technique developed within the project. Some of the academic advances within PHENICX have relevance to multiple use cases at once, while at the same time, techniques from multiple different work packages may cater to a dedicated use case. This is why integrated prototypes – which combine multiple academic advances, but embed them in an integrated experience with some clear use cases connected to them – are considered to be a very suitable means to present advances in the project in an understandable way to potential users, while soliciting the desired user-related feedback from them. In this deliverable, we describe the first efforts towards a tangible integrated prototype. An overview is given of the general planning of prototypes over the timeline of the project, after which we zoom in to the first prototype, describing how the planned features of a desktop/tablet interface are featured in a click model, and a mobile interface is being developed targeted at receiving additional early feedback on several non-trivial use cases. We will also outline how this prototype is planned to be brought to audiences making use of upcoming dissemination possibilities.
Main objectives and goals. ● To provide a combined test and evaluation of the work packages detailed in section 3.4, based on the plan laid out in D8.3 ● To provide further insights into additional testing and evaluation along with further development opportunities.
Main objectives and goals. The main goal of the Audio Commons ontology is to make the Web service orchestration possible by providing necessary knowledge about entities in that process. The previous deliverable related to the ontology, D 2.2 presented the first draft of the Audio Commons ontology. The aim of that deliverable was to explore how an ontology could coordinate the multiple requirements and desiderata related to the Audio Commons ecosystem. The design of the draft ontology and related deliverable was deliberately broader in scope, proposing generic classes and properties to cover multiple aspects, while leaving the detailed practical specification to be defined after a series of trials completed within the context of other work packages that refine the requirements and experiences gained from them This deliverable aims instead at publishing a coherent and complete ontology that deal with the most stringent requirement of the Audio Commons ecosystem, that is having a common data model to search and interact with audio resources. A model to be used in the Audio Commons Web API. The scope of this deliverable is thus in some aspects narrower than D 2.2, in order to focus on the specification of a complete and usable. In this sense, this deliverable is complementary to D 2.2. The broader analysis of actions and provenance that was described there remains still valid as input for potential future extensions of the model presented here. It should be stressed that, while the role of this deliverable in the project is to present the final version of the ontology, this does not mean that the ontology will not possibly evolve later on. Used ontologies necessarily evolve over time, especially if, as in the Audio Commons project, a lot of the use cases still have to be fully analysed. This deliverable features four main chapters. Chapter 2 briefly describes the existing music and audio related ontologies and comments about the potential usefulness of each ontology for the Audio Commons ontology and within the Audio Commons Ecosystem (ACE). Chapter 3 presents the main entities of Audio Commons ontology explaining the rationale behind his design. Chapter 4 shows examples of an important feature of the Audio Commons ontology, that it how sounds may be classified using multiple sound/music taxonomies. Chapter 5 shows how the ontology can be used in the context of the Audio Commons API.
Main objectives and goals. ● The overarching goal of PRESENT is to provide a digital agent that has visual photorealism, believable animation, and reactive communication in the resulting virtual human. ● Photorealistic computer generated digital human rendered in real-time ● to demonstrate progress on the creation of the digital human and what are the areas to focus on for the final asset. ● to design the base topology of Xxxxxx so that it can be subdivided according to the desired resolution for compatibility to all use-cases in PRESENT ● to create a test environment inside Unreal Engine that matches the standard Framestore’s look development environment inside Unreal Engine
Main objectives and goals. Description of the main objectives and goals of the framework are as follows. ● To provide a uniform method by which 3rd party asset managements systems can publish data to the search framework for ingestion, classification, transformation and search ● To provide a framework and data architecture which is extensible and interoperable with 3rd party VFX ontologies and domains, and supports tagging, classification and reasoning across those domains. ● To provide a framework by which 3rd parties can write smart classifiers and enrichers that execute at ingestion time to enrich data from asset management systems and extend and expand upon the aforementioned domains and ontologies. ● To provide programmatic data API’s to update, search and query asset data ● To provide a proof of concept graphical user interface and user experience architecture that demonstrates the entire search and transformation experience from end to end and can be extended over time.
Main objectives and goals. The main objective of this Deliverable is to demonstrate and promote the SAUCE concepts and prototypes to the Media Industry and its users. The target is to reach 1,000 sessions with over 300 unique visitors throughout the Project duration, with 200 sessions in the first Year only.
Main objectives and goals. This deliverable describes concepts and a demonstrator for the utilization of smart assets in virtual production scenarios. The main objective is to explain how and why a virtual production can benefit from smart assets. Along with this, a functional demonstrator is developed, implementing these aspects.
