[jats-list] Re: Trouble accessing JATS DTD URLs

Subject: [jats-list] Re: Trouble accessing JATS DTD URLs
From: "Julie Blair julie.blair@xxxxxxxxxxx" <jats-list-service@xxxxxxxxxxxxxxxxxxxxxx>
Date: Wed, 11 Nov 2020 17:34:37 -0000

This problem effectively shut down our validation server yesterday. We
were/are scratching our heads to locate the problem, but sounds like it's not
just our problem.

The resolver was rejecting our catalog file, showing errors with catalog.dtd
(SYSTEM identifier
http://www.oasis-open.org/committees/entity/release/1.1/catalog.dtd) and these
errors disappeared when catalog.dtd was stored locally, in same directory as
catalog file, and SYSTEM id changed to "catalog.dtd".


Julie Blair
Global Content Systems Manager
SAGE Publishing
2455 Teller Road
Thousand Oaks, CA 91320

T: 805.410.7326

From: Lizzi, Vincent vincent.lizzi@xxxxxxxxxxxxxxxxxxxx
Sent: Wednesday, November 11, 2020 8:53 AM
To: jats-list@xxxxxxxxxxxxxxxxxxxxxx
Cc: Beck, Jeff (NIH/NLM/NCBI) [E] <beck@xxxxxxxxxxxxxxxx>; Randall, Laura
(NIH/NLM/NCBI) [E] <laura.randall@xxxxxxx>
Subject: [jats-list] Trouble accessing JATS DTD URLs


Is anyone else currently having trouble accessing the site that hosts the
public JATS DTDs? Over the past few days I've seen and been told about
problems and slowdowns parsing XML that references the public JATS DTDs in the
DOCTYPE URL. Here is one of the error messages:

"Unknown host 'jats.nlm.nih.gov'"

This problem is happening intermittently with XML that contains, for

<!DOCTYPE article
  PUBLIC "-//NLM//DTD JATS (Z39.96) Journal Archiving and Interchange DTD with
OASIS Tables with MathML3 v1.2 20190208//EN"

I have XML Catalogs configured to resolve DOCTYPE URLs to a local copy of the
DTD, which have been unchanged and working up until now. Even with the XML
Catalog configuration in place I'm encountering this problem.


Information Classification: General
JATS-List info and archive<http://www.mulberrytech.com/JATS/JATS-List/>
EasyUnsubscribe<http://lists.mulberrytech.com/unsub/jats-list/243121> (by

Current Thread