Comment Details - National Information Standards Organization

#00239 Comment Details - RP-15-201x Suppl_TWG_draft_for_comments_final-rev.pdf (revision #1)

Document Information
Title	NISO RP-15-201x, Recommended Practices for Online Supplemental Journal Article Materials, Part B: Technical Recommendations
File Name	RP-15-201x Suppl_TWG_draft_for_comments_final-rev.pdf	State	Draft
Date Added	2012-08-06 11:10:25	Revision Number	1
Submitter Name	Cynthia Hodgson	Size	256K

Comment Information
Summary	Suggestions from ACS	State (Disposition)	New (Unresolved)
Date Added	2012-09-15 10:25:43	Last Updated	2012-09-15 10:25:43
Submitter Name	David Martinsen	Assigned To	Unassigned
Company Name	American Chemical Society	Response	None
Interest Category		Category	N/A
Origin	Public Review	Section, Page, Line
Item	N/A	Item Description

Submitter Comment
At a high level, a designation of the format might not be specific enough. For example, a movie might be in mp3 format, but could be stored with a variety of different CODECs. The detailed specification of the format should be included. Please check the sample DTD tagging in Table 1 for the following: ◦ Make the use of underscore vs. hyphen more consistent, e.g., <article_metadata> vs. @supp-mat-type ◦ The prefix "supp_mat_" (or "sup-mat-") is used some places but not in others. Consider using this prefix for the top level elements only, including the root element and the primary “supplement material object metadata” container element. ◦ <supp_mat_physical> - it might be nice to include “metadata” in the element name. ◦ The NLM DTD (a.k.a. JATS) uses hyphens; it would be nice to be synchronous with that tagset at least in the format of tag names, in anticipation of them being used together or even merged someday as you suggested. ◦ Overall, it would be great to align the element/attribute names and design principals to that of JATS since there is a high degree of likely overlap between the two sets of implementers/users. On page 11, Consider PDF-A be explicitly mentioned as a recommended archival format. On page 12, consider that "encoded as plain ASCII text" be changed to UTF-8. Plain ASCII might be too limiting for handling file names from non-English authors.

Submitter Comment

At a high level, a designation of the format might not be specific enough. For example, a movie might be in mp3 format, but could be stored with a variety of different CODECs. The detailed specification of the format should be included.

Please check the sample DTD tagging in Table 1 for the following:
◦ Make the use of underscore vs. hyphen more consistent, e.g., <article_metadata> vs. @supp-mat-type
◦ The prefix "supp_mat_" (or "sup-mat-") is used some places but not in others. Consider using this prefix for the top level elements only, including the root element and the primary “supplement material object metadata” container element.
◦ <supp_mat_physical> - it might be nice to include “metadata” in the element name.
◦ The NLM DTD (a.k.a. JATS) uses hyphens; it would be nice to be synchronous with that tagset at least in the format of tag names, in anticipation of them being used together or even merged someday as you suggested.
◦ Overall, it would be great to align the element/attribute names and design principals to that of JATS since there is a high degree of likely overlap between the two sets of implementers/users.

On page 11, Consider PDF-A be explicitly mentioned as a recommended archival format.

On page 12, consider that "encoded as plain ASCII text" be changed to UTF-8. Plain ASCII might be too limiting for handling file names from non-English authors.