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

["Paul Donohoe pmdonohoe@xxxxxxxxxxx" <jats-list-service@xxxxxxxxxxxxxxxxxxxxxx>]

Hi all,  OASIS said this was due to their new website, they forced https on
all links. They've now allowed http for the DTDs. Can someone please confirm
that has fixed the problem?

Thanks,
Paul

________________________________
From: Chandi Perera cperera@xxxxxxxxxx
<jats-list-service@xxxxxxxxxxxxxxxxxxxxxx>
Sent: Wednesday, November 11, 2020 9:59 PM
To: jats-list@xxxxxxxxxxxxxxxxxxxxxx <jats-list@xxxxxxxxxxxxxxxxxxxxxx>
Cc: Beck, Jeff (NIH/NLM/NCBI) [E] <beck@xxxxxxxxxxxxxxxx>; Randall, Laura
(NIH/NLM/NCBI) [E] <laura.randall@xxxxxxx>
Subject: Re: [jats-list] Re: Trouble accessing JATS DTD URLs


Hi all

  We first noticed this issue Tuesday morning Australian time.  We had the
resolver failing to resolve catalogs across multiple customers on multiple
installations.



We traced the problem to the DOCTYPE declaration on our catalogs and some DTDs
like NISO STS.

<!DOCTYPE catalog PUBLIC

"-//OASIS//DTD Entity Resolution XML Catalog V3.0//EN"

"http://www.oasis-open.org/committees/entity/release/1.0/catalog.dtd";>



It seems we missed include a local version of the DTD for the builds  and were
pulling the file from OASIS.



According to the catalog.dtd on the OASIS website this file was updated around
the same time as our failures.



It seems the file as of Tuesday had an issue with the nextCatalog tag as well
though we have not investigated this further, but our engineers have informed
me that the catalog DTD on the OASIS website was updated again overnight and
the nextCatalog tag is now ok.  This issue is to be confirmed.



Lesson for us here was to ensure we always maintain a local version of all the
DTDs and use catalogs to ensure we use local copies.



Irony of the resolver failing due to the catalog.dtd was not lost on any of
us.



Chandi







From: Paul Donohoe pmdonohoe@xxxxxxxxxxx<mailto:pmdonohoe@xxxxxxxxxxx>
<jats-list-service@xxxxxxxxxxxxxxxxxxxxxx<mailto:jats-list-service@xxxxxxxxxx
errytech.com>>
Sent: Thursday, 12 November 2020 7:20 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] Re: Trouble accessing JATS DTD URLs



It might be related to the fact that OASIS just launched a new version of
their website. I am a member, but had trouble logging in to their new site. I
will try to pass on the issue to them.



Cheers,

Paul



________________________________

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 7:44 PM
To: jats-list@xxxxxxxxxxxxxxxxxxxxxx<mailto:jats-list@xxxxxxxxxxxxxxxxxxxxxx>
<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] Re: Trouble accessing JATS DTD URLs



Thanks for the quick replies Julie and Liam!



I saw an error at the stage of parsing the XML Catalog file which didnt 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 files
SYSTEM ID pointing to the local catalog.dtd using a file path relative to the
projects 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<mailto:julie.blair@xxxxxxxxxxx>
<jats-list-service@xxxxxxxxxxxxxxxxxxxxxx<mailto:jats-list-service@xxxxxxxxxx
errytech.com>>
Sent: Wednesday, November 11, 2020 12:35 PM
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] 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 its 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





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 Ive 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<http://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">



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 Im 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)

JATS-List info and archive<http://www.mulberrytech.com/JATS/JATS-List/>

EasyUnsubscribe<http://lists.mulberrytech.com/unsub/jats-list/3389464> (by
email)

JATS-List info and archive<http://www.mulberrytech.com/JATS/JATS-List/>

EasyUnsubscribe<http://lists.mulberrytech.com/unsub/jats-list/2690815> (by
email)

JATS-List info and archive<http://www.mulberrytech.com/JATS/JATS-List/>
EasyUnsubscribe<http://lists.mulberrytech.com/unsub/jats-list/3389464> (by
email<>)