Home | Public Area

Comment #00516 - Allow string-date in more places - z39.96-2012.pdf

Comment 516
Addressed (Unresolved)
ANSI/NISO Z39.96-2012, JATS: Journal Article Tag Suite (version 1.0) (Revision 0)
Comment Submitted by
Vincent Lizzi
2014-07-01 13:49:43

This suggestion is to allow the string-date element to appear in more places to support tagging dates that appear in text. The string-date element could be used to capture an actual date value in places where the text may have a written out date or even a partial date. However, places where string-date may be used are currently limited.



In this usage of string-date, the text to display is captured as the text content of the element and the iso-8601-date attribute holds an ISO 8601 formatted date or date and time. The content-type attribute may be used to further identify the date.   



The following example shows a date range in text tagged using string-date. The content-type attribute values dtstart and dtend are borrowed from hCalendar.  



<bold><string-date iso-8601-date="2013-03-15" content-type="dtstart">March 15</string-date>–<string-date iso-8601-date="2013-03-17" content-type="dtend">17</string-date></bold>

Submitter Proposed Solution

Allow string-date to appear in more places, possibly everywhere that named-content is allowed to appear by adding string-date to parameter entity %phrase.class.



If string-date is added to %phrase.class this may necessitate changes in turn. In the Publishing and Archiving DTDs, remove parameter entity %citation-additions.class. In the Archiving DTD change parameter entity %history-elements to contain the date element instead of parameter entity %date.class.

Ms. B. Tommie Usdin
2015-07-09 11:25:02

The Standing Committee considered this request and decided to take no action. While there may be circumstances where this change alone would be useful the Standing Committee felt that in most cases this would not be enough to be useful.