<?xml version="1.0" encoding="utf-8"?>
<!--
Copyright TEI Consortium. 
Dual-licensed under CC-by and BSD2 licences 
See the file COPYING.txt for details
$Date$
$Id$
-->
<?xml-model href="http://tei.oucs.ox.ac.uk/jenkins/job/TEIP5/lastSuccessfulBuild/artifact/P5/release/xml/tei/odd/p5.nvdl" type="application/xml" schematypens="http://purl.oclc.org/dsdl/nvdl/ns/structure/1.0"?>

<macroSpec xmlns="http://www.tei-c.org/ns/1.0" xmlns:rng="http://relaxng.org/ns/structure/1.0" module="tei" type="dt" ident="data.temporal.iso">
  <desc versionDate="2007-04-08" xml:lang="en">defines the range of attribute values expressing a temporal expression such as a date, a
    time, or a combination of them, that conform to the international standard <title>Data elements
      and interchange formats – Information interchange – Representation of dates and times</title>.</desc>
  <desc versionDate="2007-12-20" xml:lang="ko">날짜, 시간, 또는 이들의 조합과 같은 시간 표현의 속성 값 범위를 정의하며, 이는 국제 표준
      <title>Data elements and interchange formats – Information interchange – Representation of
      dates and times</title>을 따른다.</desc>
  <desc versionDate="2007-05-02" xml:lang="zh-TW">定義該系列表示時間的屬性值，例如日期、時間或兩者的組合，需符合國際標準 Data elements and
    interchange formats – Information interchange – Representation of dates and times</desc>
  <desc versionDate="2008-04-05" xml:lang="ja">日付や時間などの時間表現をとる属性値の範囲を定義する．これは，国際標 準である<title>Data
      elements and interchange formats - Information interchange - Representation of dates and
    times</title>に準拠したも のになる．</desc>
  <desc versionDate="2007-06-12" xml:lang="fr">définit la gamme des valeurs d'attribut qui sont capables
    d''exprimer une valeur temporelle comme une date, une période, ou une combinaison des deux qui
    se conforment au standard international <title>Data elements and interchange formats –
      Information interchange – Representation of dates and times</title>
   </desc>
  <desc versionDate="2007-05-04" xml:lang="es">define la gama de valores de atributos que expresan una
    expresión temporal como una fecha, una hora, o una combinación de estas, de acuerdo a un
    estándard internacional <title>Elementos de datos y formatos de intercambio - Intercambio de
      información – Representación de fechas y horas</title>.</desc>
  <content>
    <rng:choice>
      <!-- W3C -->
      <rng:data type="date"/>
      <rng:data type="gYear"/>
      <rng:data type="gMonth"/>
      <rng:data type="gDay"/>
      <rng:data type="gYearMonth"/>
      <rng:data type="gMonthDay"/>
      <rng:data type="time"/>
      <rng:data type="dateTime"/>
      <!-- time w/ reduced precision
      <rng:data type="token">
	<rng:param name="pattern">(-?[0-9]{4}-(0[1-9]|1[0-2])-(0[1-9]|[12][0-9]|3[01])T)?([01][0-9]|2[0-3])(:[0-5][0-9])?(Z|[+\-]((0[0-9]|1[0-3]):[0-5][0-9]|14:00))?</rng:param>
      </rng:data> -->
      <!-- week date 
      <rng:data type="token">
	<rng:param name="pattern">[0-9]{4}-W[0-9][0-9]?(-[1-7])?</rng:param>
      </rng:data> -->
      <!-- any ISO 8601 format (and a lot more) -->
      <rng:data type="token">
        <?tei winita
	My expectation is to replace this catch-all pattern with a series
	of patterns to match the various extended formats of 8601. The two
	commented-out patterns above are a helpful start. Either that,
	or if someone comes up with a real RELAX NG datatype, use it.
	:-) -- sb ?>
        <rng:param name="pattern">[0-9.,DHMPRSTWYZ/:+\-]+</rng:param>
      </rng:data>
    </rng:choice>
  </content>
  <remarks versionDate="2007-04-13" xml:lang="en">
    <p>If it is likely that the value used is to be compared with another, then a time zone
      indicator should always be included, and only the dateTime representation should be used.</p>
    <p>For all representations for which ISO 8601 describes both a <term>basic</term> and an
        <term>extended</term> format, these Guidelines recommend use of the extended format.</p>
    <p>While ISO 8601 permits the use of both <code>00:00</code> and <code>24:00</code> to represent
      midnight, these Guidelines strongly recommend against the use of <code>24:00</code>.
      <!-- As
    there are only 24 hours in a day, numbered "00" through "23", use
    of "24:00" implies a 25th hour, and some software may be confused.
    Note that when there is a leap second, it should be indicated with
    23:59:60. --></p>
  </remarks>
  <remarks xml:lang="ja" versionDate="2008-04-05">
    <p> 当該属性値が他の値と比較される場合，時間帯は必ず示されるべきである． またはdateTimeを使うべきである(訳注：この文は修正されるかもしれな い)． </p>
    <p> ISO 8601には<term>基本形式</term>と<term>拡張形式</term>がある． 本ガイドラインでは拡張形式を使うことを推奨する． </p>
    <p> ISO 8601では，深夜の12時を示す方法として， <code>00:00</code>と<code>24:00</code>の両方を認めているが，
        本ガイドラインでは，<code>24:00</code>とは表記しないことを強く推奨 している．
      <!-- As there are only 24 hours in a day, numbered "00" through "23",
    use of "24:00" implies a 25th hour, and some software may be
    confused. Note that when there is a leap second, it should be
    indicated with 23:59:60. -->
    </p>
  </remarks>
  <remarks xml:lang="fr" versionDate="2007-06-12">
    <p> S'il est vraisemblable que la valeur utilisée soit destinée à être comparer à d’autres
      valeurs, alors une indication du fuseau horaire devrait toujours être incluse, et seule la
      représentation <term>dateTime</term> devrait être employée.</p>
    <p>Pour toutes les représentations pour lesquelles l’ISO 8601 décrit à la fois un format
        <term>basique</term> et un format<term> étendu </term>, ce guide d’encodage recommandande
      l’emploi du format <term> étendu </term>.</p>
    <p> Même si l’ ISO 8601 permet d’écrire à la fois <code>00:00</code> et <code>24:00</code> pour
      minuit, ce guide d’encodage déconseille vivement d’écrire <code>24:00</code>.
      <!-- As
        there are only 24 hours in a day, numbered "00" through "23", use
        of "24:00" implies a 25th hour, and some software may be confused.
        Note that when there is a leap second, it should be indicated with
        23:59:60. --></p>
  </remarks>
</macroSpec>
