Unable to work with modular DTD?

Problem

When editing a file with correct DOCTYPE and available DTD files I get message saying the DTD has 41 errors:

The DTD in question is the JATS (Journal Article Tagging Suite), which is a NISO Z39.96-2019 standard maintained by the NLM (U.S. National Library of Medicine), and it most certainly does not have any errors.

I feel that the server is working, for when I remove the system identifier I get the correct error:

Please, any ideas as to what might be wrong?

DTD library and test file

This DTD is available at ftp://ftp.ncbi.nih.gov/pub/jats/publishing/1.1d3/JATS-Publishing-1-1d3-MathML2-DTD.zip and is composed of the following files, which include a sample test XML file (marked below).

./
├── catalog-jats-v1-1d3-no-base.xml
├── catalog-jats-v1-1d3-with-base.xml
├── iso8879
│   ├── isobox.ent
│   ├── isocyr1.ent
│   ├── isocyr2.ent
│   ├── isodia.ent
│   ├── isolat1.ent
│   ├── isolat2.ent
│   ├── isonum.ent
│   └── isopub.ent
├── iso9573-13
│   ├── isoamsa.ent
│   ├── isoamsb.ent
│   ├── isoamsc.ent
│   ├── isoamsn.ent
│   ├── isoamso.ent
│   ├── isoamsr.ent
│   ├── isogrk3.ent
│   ├── isomfrk.ent
│   ├── isomopf.ent
│   ├── isomscr.ent
│   └── isotech.ent
├── JATS-ali-namespace1.ent
├── JATS-articlemeta1.ent
├── JATS-backmatter1.ent
├── JATS-chars1.ent
├── JATS-common1.ent
├── JATS-common-atts1.ent
├── JATS-default-classes1.ent
├── JATS-default-mixes1.ent
├── JATS-display1.ent
├── JATS-format1.ent
├── JATS-funding1.ent
├── JATS-journalmeta1.ent
├── JATS-journalpubcustom-classes1.ent
├── JATS-journalpubcustom-mixes1.ent
├── JATS-journalpubcustom-models1.ent
├── JATS-journalpubcustom-modules1.ent
├── JATS-journalpublishing1.dtd
├── JATS-link1.ent
├── JATS-list1.ent
├── JATS-math1.ent
├── JATS-mathml3-mathmlsetup1.ent
├── JATS-mathml3-modules1.ent
├── JATS-mathmlsetup1.ent
├── JATS-modules1.ent
├── JATS-nlmcitation1.ent
├── JATS-notat1.ent
├── JATS-oasis-namespace1a.ent
├── JATS-oasis-namespace1.ent
├── JATS-oasis-tablesetup1.ent
├── JATS-para1.ent
├── JATS-phrase1.ent
├── JATS-references1.ent
├── JATS-related-object1.ent
├── JATS-section1.ent
├── JATS-XHTMLtablesetup1.ent
├── JATS-xmlspecchars1.ent
├── mathml
│   ├── mmlalias.ent
│   └── mmlextra.ent
├── mathml2.dtd
├── mathml2-qname-1.mod
├── mathml3.dtd
├── mathml3-qname1.mod
├── oasis-exchange.ent
├── Smallsamples
│   ├── journal.elementa.000011.xml
│   ├── journal.elementa.000012.xml
│   ├── journal.elementa.000017.xml
│   └── samplesmall-pub1.xml                                          # this is the test file
├── xhtml-inlstyle-1.mod
├── xhtml-table-1.mod
└── xmlchars
    ├── isogrk1.ent
    ├── isogrk2.ent
    └── isogrk4.ent

[angelozerr]

Thanks for your feedbacj @lpanebr

Please note that you if you enable codelens, you should see someinformation about binding with DTD,XSD

Here a sample with binding with schemaLocation:

You can click on codelens to open the proper xsd.

[lpanebr]

ok. NOW I’ve REALLY gotten it to work (context aware suggestions) on Windows, with multiple catalogs on Sublime and VS Code!

UPDATE 1:

• I’ve added the configuration file used for the LSP package, and comment.

Here´s what I did to get it working on Windows, after installing the LemMinx package:

1. Instead of specifying multiple catalogs in the settings, I used just a single catalog file.
2. Instead of hand-writing the catalog myself I used multiple <nextCatalog> entries pointing to the DTD-libraries-provided catalog files on the same directory.
3. Corrected a problem in one of the catalog files (see note below).
4. Used only the double \\ slash notation.
5. Enabled the xml.validation.resolveExternalEntities setting.
6. Installed the LSP package. (For Sublime only)
7. Installed Java. (required by the LSP package)

IMPORTANT 1:

• The LemMinx package in Sublime provides only very basic validation.
• Installing the LSP package is what gave Sublime the ability to provide context aware suggestions for elements, attributes and attribute values.
• The Exalt package was not installed as during tests it also provided only basic validation and dumb suggestions.

IMPORTANT 2:

• When I intentionally break one of the <nextCatalog>s files, the validation etc breaks for XML files that use that DTD but it all keeps working for XML files using the DTDs specified by the other <nextCatalog>s files.

---

Below are the specific packages configurations that are currently working on Windows and provide context aware suggestions for elements, attributes and attribute values, both for Sublime Text (version 4) and VS Code.

Sublime LSP-lemminx.sublime-settings

{
	"settings": {
		"xml.catalogs": [
			"C:\\catalogs\\catalog.xml"
		],
		"xml.completion.autoCloseTags": true,
		"xml.validation.resolveExternalEntities": true,
	}
}

Sublime LSP.sublime-settings This setting is very convenient for it always opens the diagnostics panel on save, which either has a motivational message showing no errors, or lists each diagnostics allowing you to just double click to go to it in the document.

{
    "show_diagnostics_panel_on_save": 4,
}

VS Code settings.json

{
    "redhat.telemetry.enabled": false,
    "xml.catalogs": [
        "C:\\catalogs\\catalog.xml"
    ],
    "xml.completion.autoCloseTags": true,
    "xml.validation.resolveExternalEntities": true
}

The main catalog.xml has only <nextCatalog> entries using relative path as pointed by @deathaxe .

Catalog file catalog.xml

<?xml version="1.0"?>
<!DOCTYPE catalog PUBLIC "-//OASIS//DTD Entity Resolution XML Catalog V1.0//EN" "http://www.oasis-open.org/committees/entity/release/1.0/catalog.dtd">
<catalog prefer="public" xmlns="urn:oasis:names:tc:entity:xmlns:xml:catalog">
  <nextCatalog catalog="jats\\dtd\\1.1d3\\catalog-jats-v1-1d3-no-base.xml"/>
  <nextCatalog catalog="jats\\dtd\\1.1\\catalog-jats-v1-1-no-base.xml"/>
  <nextCatalog catalog="jats\\dtd\\1.0\\catalog-jats-v1.xml"/>
</catalog>

DTD files used:

• jats-publishing-dtd-1.0.zip
• JATS-Publishing-1-1-MathML2-DTD.zip
• JATS-Publishing-1-1d3-MathML2-DTD.zip

catalog.xml file and DTD libraries relative to <nextCatalog> files and folders. (see note below)

C:\\catalogs\\catalogs
├── catalog.xml
└── jats
    └── dtd
        ├── 1.0
        │   ├── catalog-jats-v1.xml    # <= problematic catalog using xml:base (see note below)
        │   ├── iso8879
        │   ├── iso9573-13
        │   ├── mathml
        │   ├── Smallsamples
        │   └── xmlchars
        ├── 1.1
        │   ├── catalog-jats-v1-1-no-base.xml
        │   ├── iso8879
        │   ├── iso9573-13
        │   ├── mathml
        │   └── xmlchars
        └── 1.1d3
            ├── catalog-jats-v1-1d3-no-base.xml
            ├── iso8879
            ├── iso9573-13
            ├── mathml
            ├── Smallsamples
            └── xmlchars

Note:

• The catalog-jats-v1.xml catalog was problematic. It had a xml:base defined, which has to be removed.

<!-- problematic xml:base on the group definition -->
<group xml:base="file:///C:/Work/Tasks/DTDJournal/" prefer="public">

<!-- fixed group definition -->
<group prefer="public">

Conclusion As shown above, having a single catalog that properly references other catalogs using the <nextCatalog> definition works as expected. So, if there really exists any bugs with multiple catalogs, I feel it must be related with either:

• adding multiple catalog files as an array in the server json settings configuration file; or
• using badly formed catalog files and/or path structure.