<?xml version="1.0" encoding="UTF-8"?>
<rdf:RDF xmlns:community="http://www.bibsonomy.org/ontologies/2008/05/community#" xmlns:foaf="http://xmlns.com/foaf/0.1/" xmlns:owl="http://www.w3.org/2002/07/owl#" xmlns:admin="http://webns.net/mvcb/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:syn="http://purl.org/rss/1.0/modules/syndication/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" xmlns:cc="http://web.resource.org/cc/" xmlns:xsd="http://www.w3.org/2001/XMLSchema#" xmlns:swrc="http://swrc.ontoware.org/ontology#" xmlns:rdfs="http://www.w3.org/2000/01/rdf-schema#" xmlns="http://purl.org/rss/1.0/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xml:base="https://puma.ub.uni-stuttgart.de/user/robingarcia/programming%20code"><owl:Ontology rdf:about=""><rdfs:comment>PUMA publications for /user/robingarcia/programming%20code</rdfs:comment><owl:imports rdf:resource="http://swrc.ontoware.org/ontology/portal"/></owl:Ontology><rdf:Description rdf:about="https://puma.ub.uni-stuttgart.de/bibtex/2b3444488cffac8a5783daba56155426a/robingarcia"><owl:sameAs rdf:resource="/uri/bibtex/2b3444488cffac8a5783daba56155426a/robingarcia"/><rdf:type rdf:resource="http://swrc.ontoware.org/ontology#Article"/><owl:sameAs rdf:resource="https://doi.org/10.1371/journal.pcbi.1005412"/><swrc:date>Mon Apr 24 15:12:05 CEST 2017</swrc:date><swrc:journal>PLOS Computational Biology</swrc:journal><swrc:month>04</swrc:month><swrc:number>4</swrc:number><swrc:pages>1-10</swrc:pages><swrc:publisher><swrc:Organization swrc:name="Public Library of Science"/></swrc:publisher><swrc:title>Ten simple rules for making research software more robust</swrc:title><swrc:volume>13</swrc:volume><swrc:year>2017</swrc:year><swrc:keywords>code matlab programming science structure </swrc:keywords><swrc:abstract>Author summary Many researchers have found out the hard way that there’s a world of difference between “works for me on my machine” and “works for other people on theirs.” Many common challenges can be avoided by following a few simple rules; doing so not only improves reproducibility but can accelerate research.</swrc:abstract><swrc:hasExtraField><swrc:Field swrc:value="10.1371/journal.pcbi.1005412" swrc:key="doi"/></swrc:hasExtraField><swrc:author><rdf:Seq><rdf:_1><swrc:Person swrc:name="Morgan Taschuk"/></rdf:_1><rdf:_2><swrc:Person swrc:name="Greg Wilson"/></rdf:_2></rdf:Seq></swrc:author></rdf:Description></rdf:RDF>