◇◆
<date> Date
Container element for the parts of a single calendar date.
Usage/Remarks
A <date> element contains date components such as <day>, <month>, and <year> (which are typically given numeric values), as well as non-numeric elements such
as <season> (which is a text string).
<date>In Citations, Related Articles, and Products
When used within citations (<element-citation> and <mixed-citation>), related articles and objects, and product descriptions, <date> names the publication date of the cited or related source.
<date>In Events and History
Best Practice: Use @iso-8601-date
It is recommended to provide an @iso-8601-date attribute on every <date> element, for better machine processing and interoperability
Best Practice: Use <event> Rather Than <history>
Current publishing best practice is not to use the element <history> and instead, tag all publishing dates as <event>s.
- For retrospective conversion, each <date> element inside <history> can be moved into <event> without change and without addition.
- Going forward, the <event> structure allows the publisher to record additional metadata beyond the bare type values (“accepted”, “preprint”, “rejected”, etc.) that are recorded in the @date-type attribute.
<string-date> Best Practice
In <date>,
individual date elements (such as <year>) must be tagged. However, even inside a
<string-date>, the
named date components such as <year> should be identified. Use <string-date> for the narrative
form of a date when necessary, for example, when a date has no
month or year specified or to change the order of date elements.
This Archiving Tag Set allows <string-date> both inside <date> and at the same level as
<date>. This is the
most flexible for allowing the archive to preserve any
publisher’s structure. The tighter Tag Sets created
from the base Suite may choose to use one or the other
in preference.
Attributes
Models and Context
May be contained in
Description
The following, in order:
- Optionally any one of:
- <year> Year, zero or one
- <era> Era of Time, zero or one
- <string-date> Date as a String, zero or one
Content Model
<!ELEMENT date %date-model; >
Expanded Content Model
(((day?, month?) | season)?, year?, era?, string-date?)
Tagged Samples
Event: Date approved
...<article-meta>
......
<pub-history>
<event><event-desc>Accepted for publication</event-desc>
<date date-type="accepted" iso-8601-date="2012-06-01">
<day>01</day>
<month>06</month>
<year>2012</year>
</date>
</event>
</pub-history>
...
</article-meta>
...
Non-Gregorian calendar
...
<date date-type="received" calendar="Japanese"
iso-8601-date="2013-07-01">
<day>1</day>
<month>7</month>
<year>25</year>
<era>平成</era>
</date>
...
With embedded <string-date>
...
<date date-type="online" specific-use="metadata"
iso-8601-date="2012-05-03T08:47:08">
<string-date>2012-05-03T08:47:08</string-date>
</date>
...
Publication date in citations
Mixed citation
...
<ref id="B14">
<mixed-citation publication-type="book" publication-format="print">
<person-group person-group-type="author">
<name><surname>Hart</surname> <given-names>JT</given-names>
</name></person-group>. <source>A new kind of doctor: the
general practitioner’s part in the health of the
community</source>. <publisher-loc>London</publisher-loc>:
<publisher-name>Merlin Press</publisher-name>,
<date iso-8601-date="1988" date-type="pub"><year>1988</year></date>.
</mixed-citation>
</ref>
...
Element citation
...
<ref id="B14">
<element-citation publication-type="book" publication-format="print">
<person-group person-group-type="author">
<name><surname>Hart</surname>
<given-names>JT</given-names></name>
</person-group>
<source>A new kind of doctor: the general practitioner’s
part in the health of the community</source>
<date iso-8601-date="1988" date-type="pub">
<year>1988</year>
</date>
<publisher-loc>London</publisher-loc>
<publisher-name>Merlin Press</publisher-name>
</element-citation>
</ref>
...
Related Resource
- For a discussion on the use of <date> in bibliographic references, see Dates in Citations.
- See: Hierarchy diagram - Date