947 research outputs found

    Practical Reasoning for Very Expressive Description Logics

    Full text link
    Description Logics (DLs) are a family of knowledge representation formalisms mainly characterised by constructors to build complex concepts and roles from atomic ones. Expressive role constructors are important in many applications, but can be computationally problematical. We present an algorithm that decides satisfiability of the DL ALC extended with transitive and inverse roles and functional restrictions with respect to general concept inclusion axioms and role hierarchies; early experiments indicate that this algorithm is well-suited for implementation. Additionally, we show that ALC extended with just transitive and inverse roles is still in PSPACE. We investigate the limits of decidability for this family of DLs, showing that relaxing the constraints placed on the kinds of roles used in number restrictions leads to the undecidability of all inference problems. Finally, we describe a number of optimisation techniques that are crucial in obtaining implementations of the decision procedures, which, despite the worst-case complexity of the problem, exhibit good performance with real-life problems

    iFAct Recoding

    Get PDF
    Estágio realizado na Critical Software, S. ATese de mestrado integrado. Engenharia Informática e Computação. Faculdade de Engenharia. Universidade do Porto. 200

    ZFITTER: a semi-analytical program for fermion pair production in e+e- annihilation, from version 6.21 to version 6.42

    Full text link
    ZFITTER is a Fortran program for the calculation of fermion pair production and radiative corrections at high energy e+e- colliders; it is also suitable for other applications where electroweak radiative corrections appear. ZFITTER is based on a semi-analytical approach to the calculation of radiative corrections in the Standard Model. We present a summary of new features of the ZFITTER program version 6.42 compared to version 6.21. The most important additions are: (i) some higher-order QED corrections to fermion pair production, (ii) electroweak one-loop corrections to atomic parity violation, (iii) electroweak one-loop corrections to nu-e nu-e-bar production, (iv) electroweak two-loop corrections to the W boson mass and the effective weak mixing angle.Comment: 60 pages, latex, 3 table

    Electronic institutions with normative environments for agent-based E-contracting

    Get PDF
    Tese de doutoramento. Engenharia Informática. Faculdade de Engenharia. Universidade do Porto. 201

    Monitoring cooperative business contracts in an institutional environment

    Get PDF
    The automation of B2B processes is currently a hot research topic. In particular, multi-agent systems have been used to address this arena, where agents can represent enterprises in an interaction environment, automating tasks such as contract negotiation and enactment. Contract monitoring tools are becoming more important as the level of automation of business relationships increase. When business is seen as a joint activity that aims at pursuing a common goal, the successful execution of the contract benefits all involved parties, and thus each of them should try to facilitate the compliance of their partners. Taking into account these concerns and inspecting international legislation over trade procedures, in this paper we present an approach to model contractual obligations: obligations are directed from bearers to counterparties and have flexible deadlines. We formalize the semantics of such obligations using temporal logic, and we provide rules that allow for monitoring them. The proposed implementation is based on a rule-based forward chaining production system

    A data storage, retrieval and analysis system for endocrine research

    Get PDF
    This retrieval system builds, updates, retrieves, and performs basic statistical analyses on blood, urine, and diet parameters for the M071 and M073 Skylab and Apollo experiments. This system permits data entry from cards to build an indexed sequential file. Programs are easily modified for specialized analyses

    The onset of churn flow in vertical tubes : effects of temperature and tube radius

    Get PDF

    Letters to the Editor

    Get PDF
    Letter to the Editor, Jefferson Journal of Psychiatry, Volume 10, Number 1, 1992

    Software packager user's guide

    Get PDF
    Software integration is a growing area of concern for many programmers and software managers because the need to build new programs quickly from existing components is greater than ever. This includes building versions of software products for multiple hardware platforms and operating systems, building programs from components written in different languages, and building systems from components that must execute on different machines in a distributed network. The goal of software integration is to make building new programs from existing components more seamless -- programmers should pay minimal attention to the underlying configuration issues involved. Libraries of reusable components and classes are important tools but only partial solutions to software development problems. Even though software components may have compatible interfaces, there may be other reasons, such as differences between execution environments, why they cannot be integrated. Often, components must be adapted or reimplemented to fit into another application because of implementation differences -- they are implemented in different programming languages, dependent on different operating system resources, or must execute on different physical machines. The software packager is a tool that allows programmers to deal with interfaces between software components and ignore complex integration details. The packager takes modular descriptions of the structure of a software system written in the package specification language and produces an integration program in the form of a makefile. If complex integration tools are needed to integrate a set of components, such as remote procedure call stubs, their use is implied by the packager automatically and stub generation tools are invoked in the corresponding makefile. The programmer deals only with the components themselves and not the details of how to build the system on any given platform
    corecore