changed to JATS 1.1

1.1d3 is completely backward compatible to 1.1 and will be so PMC suggest we move back to 1.1. The only difference is that for the xmlns:ali="http://www.niso.org/schemas/ali/1.0 namespace a / needs to be added to the end to make this work: xmlns:ali="http://www.niso.org/schemas/ali/1.0/

elife-00666.xml

@@ -1,5 +1,5 @@
 <?xml version="1.0" encoding="UTF-8"?>
-<!DOCTYPE article PUBLIC "-//NLM//DTD JATS (Z39.96) Journal Archiving and Interchange DTD v1.1d3 20150301//EN" "JATS-archivearticle1.dtd">
+<!DOCTYPE article PUBLIC "-//NLM//DTD JATS (Z39.96) Journal Archiving and Interchange DTD v1.1 20150301//EN" "JATS-archivearticle1.dtd">
 <!--eLife uses the JATS suggested @article-types from the given attribute list. This is the location where we match our content names to known terms, 
     we use subj-groups to use-eLife specific terms. The @article-type on article drives the template used on the html version of the article and is also used for PubMed deposits
 The @article-types currently used are:
@@ -9,7 +9,7 @@ discussion - Feature 1/Feature 2
 editorial - Editorial
 research-article - all research content (ie non-feature content)
 -->
-<article article-type="research-article" dtd-version="1.1d3" xmlns:ali="http://www.niso.org/schemas/ali/1.0"
+<article article-type="research-article" dtd-version="1.1" xmlns:ali="http://www.niso.org/schemas/ali/1.0/"
     xmlns:mml="http://www.w3.org/1998/Math/MathML" xmlns:xlink="http://www.w3.org/1999/xlink">
     <front>
         <!--journal-meta is standard for all articles published by eLife. Can be boilerplate text as this will not change.