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

["Lizzi, Vincent vincent.lizzi@xxxxxxxxxxxxxxxxxxxx" <jats-list-service@xxxxxxxxxxxxxxxxxxxxxx>]

Thanks for the quick replies Julie and Liam!

I saw an error at the stage of parsing the XML Catalog file which didn't make
sense until your message, Julie. The solution that you described is working.
In the example in front of me now, it is working with the catalog file's
SYSTEM ID pointing to the local catalog.dtd using a file path relative to the
project's root.

It is amusing that this a problem that XML Catalogs are designed to solve and
the solution is almost recursive.

Thank you!

Vincent

_____________________________________________
Vincent M. Lizzi
Head of Information Standards | Taylor & Francis Group
vincent.lizzi@xxxxxxxxxxxxxxxxxxxx<mailto:vincent.lizzi@xxxxxxxxxxxxxxxxxxxx>




Information Classification: General
From: Julie Blair julie.blair@xxxxxxxxxxx
<jats-list-service@xxxxxxxxxxxxxxxxxxxxxx>
Sent: Wednesday, November 11, 2020 12:35 PM
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] Re: Trouble accessing JATS DTD URLs

Yes!

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<http://ww
w.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


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

T: 805.410.7326
www.sagepublishing.com<http://www.sagepublishing.com/>

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


[ EXTERNAL ]
Hello,

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
instance:

<!DOCTYPE article
  PUBLIC "-//NLM//DTD JATS (Z39.96) Journal Archiving and Interchange DTD with
OASIS Tables with MathML3 v1.2 20190208//EN"
"https://jats.nlm.nih.gov/archiving/1.2/JATS-archive-oasis-article1-mathml3.d
td<https://jats.nlm.nih.gov/archiving/1.2/JATS-archive-oasis-article1-mathml3
.dtd>">

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.

Thanks,
Vincent


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
email)
JATS-List info and archive<http://www.mulberrytech.com/JATS/JATS-List/>
EasyUnsubscribe<http://lists.mulberrytech.com/unsub/jats-list/194671> (by
email<>)