Table 3. The bullet points in the table are a concise summary of the practical implications based on the lessons learned during the development process of the ENVRI-KMS.

Practical Implications
Software engineers with broad knowledge and software engineering principles are essential for successful software development projects.
Software architecture, encompassing base structure and subsystems, significantly impacts the success or failure of a software system.
Design decisions in software architecture should meet both functional and quality requirements, considering the application domain and other aspects.
Selecting the appropriate database system(s) (DBMS) is a crucial design decision that affects data storage and retrieval in the ENVRI- KMS.
Evaluating and selecting the right programming language ecosystem is crucial for developing a knowledge base system like the ENVRI-KMS.
Cross-referencing statements between knowledge bases (named graphs) requires careful consideration, with separate graphs for static and dynamic data.
Ontowiki can serve as an RDF-based middleware, supporting high- level user applications and services in the ENVRI-KMS.
Versioning and backup strategies are crucial for managing RDF data in the ENVRI-KMS, including exporting RDF dumps and using external means.
Continuous development and growth of the ENVRI-KMS depend on the efforts and contributions of the ENVRI subdomains and research infrastructures.
Interaction and collaboration with other subdomain developers and semantic search workgroups provide valuable input for the ENVRI- KMS.
Future development efforts will focus on continuous content ingestion and curation, improvement based on community feedback, DevOps practices, and community involvement in content maintenance.