Identification of Design Principles

This report identifies those design principles for a (possibly new) query and transformation language for the Web supporting inference that are considered essential. Based upon these design principles an initial strawman is selected. Scenarios for querying the Semantic Web illustrate the design principles and their reflection in the initial strawman, i.e., a first draft of the query language to be designed and implemented by the REWERSE working group I4

Interface qualification between the research central team and design officices in order to evaluate the knowledge sharing

International audienceThis article presents a case study which was led in an international company dealing with hydraulic power plant machine design. It exposes a diagnosis of the interface set up between the Research central team (R) and Development local team (D). The diagnosis shows how the information and knowledge are shared among R&D communities. It shows that the explicit knowledge formalized by the Research central team, is known and applied by the local development team, thanks to two types of networking; (1) The networking with experts in charge of communicating and explaining technical instructions applied on project, (2) and the networking between local colleagues. These practices reveal local logic that are not aligned with the company globalisation objectives. As a consequence, it is proposed that new collaborative tools resulting from Web 2.0 (wiki, bogs, collaborative platforms, etc...) can be exploited to effectively support the design activity through social networking with colleagues spread geographically. Today, no actual solution is developed and evaluated

Developing information systems with nomis: a model-driven systems development approach proposal

Trabalho apresentado na Seventh International Symposium on Business Modeling and Software Design 3-5 Julho 2017, Barcelona, SpainNOMIS is a human centred information systems modelling approach that is based on human observable actions. It models a business domain through a set of views focusing on human actions, human interactions, context for actions and information. These views are represented by a set of tables and diagrams using the NOMIS graphical notation. The modelling elements depicted in these views are defined in the NOMIS metamodel. NOMIS metamodel and graphical notation are a first step for formalizing and automate the design and implementation of computer applications with NOMIS. In this paper, we propose to develop NOMIS applications using a Model Driven System Engineering approach. The suggested approach will define formally NOMIS models and notation and, using model transformations, will derive a code structure to be used by the computerized information system, and a schema for a relational database supporting business data. Additionally, other components of a specified application middleware will be created.N/

Creating a Discipline-specific Commons for Infectious Disease Epidemiology

Objective: To create a commons for infectious disease (ID) epidemiology in which epidemiologists, public health officers, data producers, and software developers can not only share data and software, but receive assistance in improving their interoperability. Materials and Methods: We represented 586 datasets, 54 software, and 24 data formats in OWL 2 and then used logical queries to infer potentially interoperable combinations of software and datasets, as well as statistics about the FAIRness of the collection. We represented the objects in DATS 2.2 and a software metadata schema of our own design. We used these representations as the basis for the Content, Search, FAIR-o-meter, and Workflow pages that constitute the MIDAS Digital Commons. Results: Interoperability was limited by lack of standardization of input and output formats of software. When formats existed, they were human-readable specifications (22/24; 92%); only 3 formats (13%) had machine-readable specifications. Nevertheless, logical search of a triple store based on named data formats was able to identify scores of potentially interoperable combinations of software and datasets. Discussion: We improved the findability and availability of a sample of software and datasets and developed metrics for assessing interoperability. The barriers to interoperability included poor documentation of software input/output formats and little attention to standardization of most types of data in this field. Conclusion: Centralizing and formalizing the representation of digital objects within a commons promotes FAIRness, enables its measurement over time and the identification of potentially interoperable combinations of data and software.Comment: 12 pages, 6 figure

Graphical Database Architecture For Clinical Trials

The general area of the research is Health Informatics. The research focuses on creating an innovative and novel solution to manage and analyze clinical trials data. It constructs a Graphical Database Architecture (GDA) for Clinical Trials (CT) using New Technology for Java (Neo4j) as a robust, a scalable and a high-performance database. The purpose of the research project is to develop concepts and techniques based on architecture to accelerate the processing time of clinical data navigation at lower cost. The research design uses a positivist approach to empirical research. The research is significant because it proposes a new approach of clinical trials through graph theory and designs a responsive structure of clinical data that can be deployed across all the health informatics landscape. It uniquely contributes to scholarly literature of the phenomena of Not only SQL (NoSQL) graph databases, mainly Neo4j in CT, for future research of clinical informatics. A prototype is created and examined to validate the concepts, taking advantage of Neo4j’s high availability, scalability, and powerful graph query language (Cypher). This research study finds that integration of search methodologies and information retrieval with the graphical database provides a solid starting point to manage, query, and analyze the clinical trials data, furthermore the design and the development of a prototype demonstrate the conceptual model of this study. Likewise the proposed clinical trials ontology (CTO) incorporates all data elements of a standard clinical study which facilitate a heuristic overview of treatments, interventions, and outcome results of these studies

concept paper

In this concept paper, we outline our working plan for the next phase of the Corporate Semantic Web project. The plan covers the period from March 2009 to March 2010. Corporate ontology engineering will improve the facilitation of agile ontology engineering to lessen the costs of ontology development and, especially, maintenance. Corporate semantic collaboration focuses the human- centered aspects of knowledge management in corporate contexts. Corporate semantic search is settled on the highest application level of the three research areas and at that point it is a representative for applications working on and with the appropriately represented and delivered background knowledge. Each of these pillars will yield innovative methods and tools during the project runtime until 2013. We propose a concept draft and a working plan covering the next twelve months for an integrative architecture of a Corporate Semantic Web provided by these three core pillars