Extensibility. As much as possible, the system should be built to adapt to varying needs, diverse audiences, changing requirements based on the users’ profile. This will be particularly important for the customizations of the software products, as one should aim at developing reusable and adaptable features rather than one-time development for a specific project. Capacity for internationalization and multi-language support are essential to the success of the solution. In this regard, the Grantee acknowledges and understands that the Fund’s intention is for the software to be deployed in various countries. The Grantee will have due regard to this goal in providing the Programme Deliverables and will, wherever possible and feasible, ensure that customization of any software is transferable and can be applied in other country contexts. In this regard, the Grantee 3 DRAFTING NOTE: Delete those which are not relevant/applicable. will continuously consult with the Fund regarding the possibility and feasibility of transferability of different functions of the customization.
Extensibility. The CFI specification supports extensibility for future device characteristics through the vendor-specific extended Query table(s). Anything not defined in the common CFI Query database is to be defined in the vendor extended tables, with the detailed structure of such tables defined by the major and minor vendor revision numbers and the associated vendor-supplied Command Set and Control Interface specification.
Extensibility. micro-ROS should be extensible with new packages in similar fashion as ROS2 does. Users should be able to add new topic types.
Extensibility. Later iterations of the XXX must allow more complicated use cases (for example to implement WFR.03.19 – Semantic data enrichment) and must perform the actual data publication via Push to and/or Pull from Europeana and other aggregators. While these further requirements will not be implemented at this stage it is important that they are considered in the overall architecture, design and implementation so that other parts of the system are not implemented in such a way that they prevent their implementation.
Extensibility. The architecture of the XXX is designed to be extensible to accommodate both changes to the requirements of Europeana and also to allow the code base to be used to supply data to other services.
Extensibility. With the increase of device, data, transaction and user status, management and storage requirements of related human factors are also increasing. Therefore, the enterprise information security needs a safe and extensible method to ensure the success of block- chain in the next few years. Although the block chain may benefit from its scalability in the future, it is still CHAPTER 6
Extensibility. The standards development process should ensure extensibility of the standards, of the tools for implementations, and of the implementations themselves. Extensibility is a necessity for all system components in order to cater for new and/or more efficient business processes and for the expanding user community.
Extensibility. The data format should be extensible so that if the monitoring metrics evolve over time or new metrics are added, the data formats do not need to be re-designed. This motivates the need for a template-based data format, where the meta-data dictionary is decoupled from the data encoding and data transmission primitives.
Extensibility. Pre-built integrations: dynamics • • Pre-built integrations: xxxxxxxxxx.Xxx • • Pre-built integrations: zendesk • • IVR Studio tool (note: access must be granted) • • Slack integration • • Callflow-driven integration into Xxxxxxxxxx.xxx • •
Extensibility. The field of predictive toxicology is rapidly developing and broadening in many areas including the use of biomarkers, systems biology, epigenetics, toxicokinetics, in vitro assays, stem cell technology, computational biology etc. Hence, OpenTox needs to be extensible to a broad range of future predictive toxicology applications. In such applications, contributing and diverse experimental data and models need to be combined as evidence supporting integrated testing, safety assessment and regulatory reporting as stipulated under REACH. As the OpenTox framework has been designed with these requirements in mind, it not only provides a generic solution for (Q)SAR model development and application, but is also applicable to additional areas of scientific enquiry in the predictive toxicology field and could be extended further as part of its evolutionary development beyond the end of the OpenTox FP7 project.
