Developing Ontologies withing Decentralized Settings

This chapter addresses two research questions: “How should a well-engineered methodology facilitate the development of ontologies within communities of practice?” and “What methodology should be used?” If ontologies are to be developed by communities then the ontology development life cycle should be better understood within this context. This chapter presents the Melting Point (MP), a proposed new methodology for developing ontologies within decentralised settings. It describes how MP was developed by taking best practices from other methodologies, provides details on recommended steps and recommended processes, and compares MP with alternatives. The methodology presented here is the product of direct first-hand experience and observation of biological communities of practice in which some of the authors have been involved. The Melting Point is a methodology engineered for decentralised communities of practice for which the designers of technology and the users may be the same group. As such, MP provides a potential foundation for the establishment of standard practices for ontology engineering

Epstein-Barr virus: clinical and epidemiological revisits and genetic basis of oncogenesis

Epstein-Barr virus (EBV) is classified as a member in the order herpesvirales, family herpesviridae, subfamily gammaherpesvirinae and the genus lymphocytovirus. The virus is an exclusively human pathogen and thus also termed as human herpesvirus 4 (HHV4). It was the first oncogenic virus recognized and has been incriminated in the causation of tumors of both lymphatic and epithelial nature. It was reported in some previous studies that 95% of the population worldwide are serologically positive to the virus. Clinically, EBV primary infection is almost silent, persisting as a life-long asymptomatic latent infection in B cells although it may be responsible for a transient clinical syndrome called infectious mononucleosis. Following reactivation of the virus from latency due to immunocompromised status, EBV was found to be associated with several tumors. EBV linked to oncogenesis as detected in lymphoid tumors such as Burkitt's lymphoma (BL), Hodgkin's disease (HD), post-transplant lymphoproliferative disorders (PTLD) and T-cell lymphomas (e.g. Peripheral T-cell lymphomas; PTCL and Anaplastic large cell lymphomas; ALCL). It is also linked to epithelial tumors such as nasopharyngeal carcinoma (NPC), gastric carcinomas and oral hairy leukoplakia (OHL). In vitro, EBV many studies have demonstrated its ability to transform B cells into lymphoblastoid cell lines (LCLs). Despite these malignancies showing different clinical and epidemiological patterns when studied, genetic studies have suggested that these EBV- associated transformations were characterized generally by low level of virus gene expression with only the latent virus proteins (LVPs) upregulated in both tumors and LCLs. In this review, we summarize some clinical and epidemiological features of EBV- associated tumors. We also discuss how EBV latent genes may lead to oncogenesis in the different clinical malignancie

A DESIGN PERSPECTIVE ON POLICY IMPLEMENTATION: THE FALLACIES OF MISPLACED PRESCRIPTION

Implementation has been used to try to explain too much, particularly that policy formulation should be oriented around implementation. The concentration on implementation has added little to our theoretical understanding of policymaking. Implementation studies have taken either "The Horrors of War" or "The Search for Theory" views. The latter has four major views, none of which is adequate. The best approach is to treat implementation as only one of a number of conditions which must be fulfilled for successful policymaking. The design perspection, explained in the paper, is the best approach for this. Copyright 1987 by The Policy Studies Organization.

The inevitable pain of software development: Why there is no silver bullet

Abstract. A variety of programming accidents, i.e., models, methods, artifacts, and tools, are examined to determine that each has a step that programmers find painful enough that they habitually avoid or postpone the step. This pain is generally where the programming accident meets requirements, the essence of software, and their relentless volatility. Hence, there is no silver bullet.