SwePub
Sök i SwePub databas

  Extended search

Träfflista för sökning "WFRF:(Thane H.) "

Search: WFRF:(Thane H.)

  • Result 1-2 of 2
Sort/group result
   
EnumerationReferenceCoverFind
1.
  • Murray, Alison E., et al. (author)
  • Roadmap for naming uncultivated Archaea and Bacteria
  • 2020
  • In: Nature Microbiology. - : NATURE PUBLISHING GROUP. - 2058-5276. ; 5:8, s. 987-994
  • Journal article (peer-reviewed)abstract
    • The assembly of single-amplified genomes (SAGs) and metagenome-assembled genomes (MAGs) has led to a surge in genome-based discoveries of members affiliated with Archaea and Bacteria, bringing with it a need to develop guidelines for nomenclature of uncultivated microorganisms. The International Code of Nomenclature of Prokaryotes (ICNP) only recognizes cultures as 'type material', thereby preventing the naming of uncultivated organisms. In this Consensus Statement, we propose two potential paths to solve this nomenclatural conundrum. One option is the adoption of previously proposed modifications to the ICNP to recognize DNA sequences as acceptable type material; the other option creates a nomenclatural code for uncultivated Archaea and Bacteria that could eventually be merged with the ICNP in the future. Regardless of the path taken, we believe that action is needed now within the scientific community to develop consistent rules for nomenclature of uncultivated taxa in order to provide clarity and stability, and to effectively communicate microbial diversity. In this Consensus Statement, the authors discuss the issue of naming uncultivated prokaryotic microorganisms, which currently do not have a formal nomenclature system due to a lack of type material or cultured representatives, and propose two recommendations including the recognition of DNA sequences as type material.
  •  
2.
  • Ekman, M., et al. (author)
  • Tool qualification for safety related systems
  • 2014
  • In: Ada User Journal. - 1381-6551. ; 35, s. 47-54
  • Journal article (peer-reviewed)abstract
    • Tools used in the development of safety related software applications need to be qualified as safe. That is, the tools cannot be allowed to introduce hazardous faults into the application, e.g., a compiler shall not generate dangerous code due to failure of the compiler. In many cases laws and regulations require the product development of safety related applications to comply with industry sector specific safety standards. Examples of such standards include EN50129/50128 for railway applications, ISO/EN13849 for machines with moving parts, DO-178B/C for avionics, or IS026262 for cars. These standards require the use of a rigorous development and maintenance process. The standards are also mainly intended to be used when developing systems from scratch. However, most development and test tools are not developed from scratch according to the rigorous processes of these standards. In order to address this issue, some of the standards provide means for qualifying existing tools as a more lightweight and pragmatic alternative to a regular certification process. In this paper we analyze the concept of these qualification approaches. The result of the analysis in our contribution includes a set of approaches that can be applied individually or as a combination in order to reduce the effort needed for qualifying tools. As a running example we use one of the most flexible but at the same time dangerous, even prohibited, maintenance techniques available: dynamic instrumentation of executing code. With this example, we describe how exceptions in these standards can be utilized in order to qualify a dynamic instrumentation tool with a minimal effort, without following the process of tool certification as defined by the standards.
  •  
Skapa referenser, mejla, bekava och länka
  • Result 1-2 of 2

Kungliga biblioteket hanterar dina personuppgifter i enlighet med EU:s dataskyddsförordning (2018), GDPR. Läs mer om hur det funkar här.
Så här hanterar KB dina uppgifter vid användning av denna tjänst.

 
pil uppåt Close

Copy and save the link in order to return to this view