Answers.Body: <p>This happens because at least two parts of EPUBCheck dislike the ISO8601 timezone format in different ways. In the dc:date context, EPUBCheck is OK with &quot;2020-12-09T14:06:40-07:00&quot; but not with &quot;2020-12-09T14:06:40-0700&quot;. The only difference is a colon in the timezone offset of 0700 hours. I learned about this oddity from a <a href="https://www.php.net/manual/en/class.datetime.php#111532" rel="nofollow noreferrer">PHP manual page comment</a>. The author pointed out that the format method of the DateTime class yields different results for the format specifiers 'c' and ISO8601. The former includes the colon in the offset and the latter does not.</p>
  <p>When I applied that correction to my code, the dc:date warning went away because EPUBCheck accepted &quot;2020-12-09T14:06:40-07:00&quot; as a valid date-time. However, the error persisted.</p>
  <p>Reading the W3 specs for date-time and the IDPF specs for dcterms:modified, I eventually figured it out. Where I went wrong was in reading the error message. It said it was expecting a date-time of the form &quot;CCYY-MM-DDThh:mm:ssZ&quot;. I already knew that the &quot;T&quot; in the middle was a literal character to separate the date from the time. My mistake was in thinking that the &quot;Z&quot; at the end was a symbolic character like all the others. I figured it was a placeholder for the timezone offset.</p>
  <p>I was wrong. The &quot;Z&quot; is another literal character that means the time is in UTC, or Coordinated Universal Time, or Greenwich Mean Time, or Zulu Time or whatever other moniker you give to the time zone surrounding zero longitude.</p>
  <p>If you read the <a href="https://www.w3.org/TR/NOTE-datetime" rel="nofollow noreferrer">W3 standard</a> carefully you'll find a slightly ambiguous statement about the meaning of the letter &quot;Z&quot; at the end of the date-time string. Then look up the <a href="http://idpf.org/epub/30/spec/epub30-publications.html" rel="nofollow noreferrer">IDPF standard</a> and search the page for both dc:time and dcterms:modified. All the examples show a literal &quot;Z&quot; in the date-time strings. Nowhere does this standard say it will accept local times with a timezone offset at the end.</p>
  <p>Thus, we have two takeaways. 1) Always terminate a date-time value with &quot;Z&quot; in EPUB XML, and 2) Always use UTC time for any date-time values. While EPUBCheck will accept a local time for the dc:time item, that is not a guarantee that an e-reader will interpret the offset correctly.</p>
  <p>In the end, I changed the PHP code to use the following. The resulting date-time string validates in EPUBCheck and it looks like all the examples in the IDPF standard. It also generates UTC time.</p>
  <pre><code>$isoDate=gmdate('Y-m-d\TH:i:s').'Z';
  </code></pre>
  <p>DO NOT move the &quot;Z&quot; inside the gmdate() format specifier. That will really munge up the string and probably give you more errors.</p>
  
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2020-12-09T22:07:35.733Z
Answers.LastActivityDate: 2020-12-09T22:07:35.733Z
Answers.UserDisplayName: Ray N. Franklin
Body: <p>While working on a PHP script that builds EPUB 3.0.1 content from external data, I encountered a situation where EPUBCheck complains about a valid ISO8601 date-time string in two places in the container file. The string comes from the following PHP code.</p>
  <pre><code>$isoDate=date(DateTime::ISO8601);
  </code></pre>
  <p>The same date string appears in both places of the container. One yields a warning and the other an error. I am positive that the string is valid per the ISO8601 standard quoted in the warning message. So why does this happen?</p>
  <p>Below is the top portion of my container.opf file and the errors I got from the online validator at <a href="http://validator.idpf.org" rel="nofollow noreferrer">http://validator.idpf.org</a>. The validator used EPUBCheck version 4.1.1.</p>
  <pre><code>&lt;?xml version=&quot;1.0&quot; encoding=&quot;utf-8&quot;?&gt;
  &lt;package xmlns=&quot;http://www.idpf.org/2007/opf&quot; xmlns:opf=&quot;http://www.idpf.org/2007/opf&quot; version=&quot;3.0&quot; unique-identifier=&quot;uuid_id&quot;&gt;
  &lt;metadata xmlns:dc=&quot;http://purl.org/dc/elements/1.1/&quot; xmlns:dcterms=&quot;http://purl.org/dc/terms/&quot; xmlns:opf=&quot;http://www.idpf.org/2007/opf&quot;&gt;
      &lt;dc:identifier id=&quot;uuid_id&quot; opf:scheme=&quot;uuid&quot;&gt;508c6b12-b888-4d7b-9c58-c25d8fba7846&lt;/dc:identifier&gt;
      &lt;dc:title&gt;Franklin's Palindromedary&lt;/dc:title&gt;
      &lt;dc:language&gt;en&lt;/dc:language&gt;
      &lt;dc:creator&gt;Ray N. Franklin&lt;/dc:creator&gt;
      &lt;dc:date&gt;2020-12-09T14:06:40-0700&lt;/dc:date&gt;
      &lt;meta property=&quot;dcterms:modified&quot;&gt;2020-12-09T14:06:40-0700&lt;/meta&gt;
  &lt;/metadata&gt;
  </code></pre>
  <p>The first offending line is #8, declaring the dc:date value. Here's the warning.</p>
  <pre><code>WARNING:  content.opf, line 8, position 45:  Date value '2020-12-09T14:06:40-0700' does not follow recommended syntax as per http://www.w3.org/TR/NOTE-datetime:Missing minute field.
  </code></pre>
  <p>The next line declares the required meta property dcterms:modified using the same date string. It garners an error.</p>
  <pre><code>ERROR:  content.opf, line 9, position 36:  Error while parsing file: dcterms:modified illegal syntax (expecting: 'CCYY-MM-DDThh:mm:ssZ')
  </code></pre>
  <p>Please note that I am posting this question so I can answer it, because I did eventually find a solution. I want to give the full answer here because everywhere else I found only pieces of the puzzle.</p>
  
Tags: <epub><epubcheck><opf>
Title: Why does EPUBCheck report warnings and errors for ISO8601 date-time string?
UserDisplayName: Ray N. Franklin
ThreadText: # Why does EPUBCheck report warnings and errors for ISO8601 date-time string?
  
  (Asked by: username_0 on 2020-12-09)
  
  While working on a PHP script that builds EPUB 3.0.1 content from external data, I encountered a situation where EPUBCheck complains about a valid ISO8601 date-time string in two places in the container file. The string comes from the following PHP code.
  $isoDate=date(DateTime::ISO8601);
  
  The same date string appears in both places of the container. One yields a warning and the other an error. I am positive that the string is valid per the ISO8601 standard quoted in the warning message. So why does this happen?
  Below is the top portion of my container.opf file and the errors I got from the online validator at http://validator.idpf.org. The validator used EPUBCheck version 4.1.1.
  
  
  
      508c6b12-b888-4d7b-9c58-c25d8fba7846
      Franklin's Palindromedary
      en
      username_0
      2020-12-09T14:06:40-0700
      2020-12-09T14:06:40-0700
  
  
  The first offending line is #8, declaring the dc:date value. Here's the warning.
  WARNING:  content.opf, line 8, position 45:  Date value '2020-12-09T14:06:40-0700' does not follow recommended syntax as per http://www.w3.org/TR/NOTE-datetime:Missing minute field.
  
  The next line declares the required meta property dcterms:modified using the same date string. It garners an error.
  ERROR:  content.opf, line 9, position 36:  Error while parsing file: dcterms:modified illegal syntax (expecting: 'CCYY-MM-DDThh:mm:ssZ')
  
  Please note that I am posting this question so I can answer it, because I did eventually find a solution. I want to give the full answer here because everywhere else I found only pieces of the puzzle.
  
  **Tags:** epub, epubcheck, opf
  
  
  ---
  
  ## 1 answers
  
  ### Answer by username_0 on 2020-12-09. Score: 1
  
  This happens because at least two parts of EPUBCheck dislike the ISO8601 timezone format in different ways. In the dc:date context, EPUBCheck is OK with "2020-12-09T14:06:40-07:00" but not with "2020-12-09T14:06:40-0700". The only difference is a colon in the timezone offset of 0700 hours. I learned about this oddity from a PHP manual page comment. The author pointed out that the format method of the DateTime class yields different results for the format specifiers 'c' and ISO8601. The former includes the colon in the offset and the latter does not.
  When I applied that correction to my code, the dc:date warning went away because EPUBCheck accepted "2020-12-09T14:06:40-07:00" as a valid date-time. However, the error persisted.
  Reading the W3 specs for date-time and the IDPF specs for dcterms:modified, I eventually figured it out. Where I went wrong was in reading the error message. It said it was expecting a date-time of the form "CCYY-MM-DDThh:mm:ssZ". I already knew that the "T" in the middle was a literal character to separate the date from the time. My mistake was in thinking that the "Z" at the end was a symbolic character like all the others. I figured it was a placeholder for the timezone offset.
  I was wrong. The "Z" is another literal character that means the time is in UTC, or Coordinated Universal Time, or Greenwich Mean Time, or Zulu Time or whatever other moniker you give to the time zone surrounding zero longitude.
  If you read the W3 standard carefully you'll find a slightly ambiguous statement about the meaning of the letter "Z" at the end of the date-time string. Then look up the IDPF standard and search the page for both dc:time and dcterms:modified. All the examples show a literal "Z" in the date-time strings. Nowhere does this standard say it will accept local times with a timezone offset at the end.
  Thus, we have two takeaways. 1) Always terminate a date-time value with "Z" in EPUB XML, and 2) Always use UTC time for any date-time values. While EPUBCheck will accept a local time for the dc:time item, that is not a guarantee that an e-reader will interpret the offset correctly.
  In the end, I changed the PHP code to use the following. The resulting date-time string validates in EPUBCheck and it looks like all the examples in the IDPF standard. It also generates UTC time.
  $isoDate=gmdate('Y-m-d\TH:i:s').'Z';
  
  DO NOT move the "Z" inside the gmdate() format specifier. That will really munge up the string and probably give you more errors.
  
  
  ---
  
  