5 resultados para Collaborative research agreements
em Digital Peer Publishing
Resumo:
Compliance with punctual delivery under the high pressure of costs can be implemented through the optimization of the in-house tool supply. Within the Transfer Project 13 of the Collaborative Research Centre 489 using the example of the forging industry, a mathematical model was developed which determines the minimum inventory of forging tools required for production, considering the tool appropriation delay.
Resumo:
This paper presents our research works in the domain of Collaborative Environments centred on Problem Based Learning (PBL) and taking advantage of existing Electronic Documents. We first present the modelling and engineering problems that we want to address; then we discuss technological issues of such a research particularly the use of OpenUSS and of the Enterprise Java Open Source Architecture (EJOSA) to implement such collaborative PBL environments.
Resumo:
This article outlines some of the issues involved in developing partnerships between service users, practitioners and researchers. It discusses these through some experience in Oslo as part of a national level agreement (HUSK) to improve social services in Norway through research and knowledge development. It begins with a review of the main concepts and debates involved in developing collaborative partnerships for practice-based research, particularly in the social services arena. The HUSK program is then described. The article then traces some specific developments and challenges in negotiating partnership relations as discussed by program participants (users, practitioners and researchers) in a series of workshops designed to elicit the issues directly from their experience.
Resumo:
Practice is subject to increasing pressure to demonstrate its ability to achieve outcomes required by public policy makers. As part of this process social work practice has to engage with issues around advancing knowledge-based learning processes in a close collaboration with education and research based perspectives. This has given rise to approaches seeking to combine research methodology, field research and practical experience. Practice research is connected to both “the science of the concrete” – a field of research oriented towards subjects more than objects and “mode 2 knowledge production” – an application-oriented research where frameworks and findings are discussed by a number of partners. Practice research is defined into two approaches: practice research – collaboration between practice and research – and practitioner research – processes controlled and accomplished by practitioners. The basic stakeholders in practice research are social workers, service users, administrators, management, organisations, politicians and researchers. Accordingly, practice research is necessarily collaborative, involving a meeting point for different views, interests and needs, where complexity and dilemmas are inherent. Instead of attempting to balance or reconcile these differences, it is important to respect the differences if collaboration is to be established. The strength of both practice and research in practice research is to address these difficult challenges. The danger for both fields is to avoid and reject them.
Resumo:
Open source software projects are multi-collaborative works incorporating the contributions of numerous developers who, in spite of publishing their code under a public license such as GPL, Apache or BSD, retain the copyright in their contributions. Having multiple copyright-owners can make the steering of a project difficult, if not impossible, as there is no ultimate authority able to take decisions relating to the maintenance and use of the project. This predicament can be remedied by centring the dispersed copyrights in a single authority via contributor agreements. Whether to introduce contributor agreements, and if so in which form, is a pressing question for many emerging, but also for established projects. The current paper provides an insight into the ethos of different projects and their reason for adopting or rejecting particular contributor agreements. It further examines the exact set-up of the contributor agreements used and concludes that smart drafting can blur the difference between CAAs and CLAs to a considerable extent, manoeuvring them into a legal grey area. To avoid costly litigation to test the legal enforceability of individual clauses, this paper proposes the establishment of an international committee comprised of developers, product managers and lawyers interested in finding a common terminology that may serve as a foundation for every contributor agreement