DITA 1.3 topic
A generic DITA topic, the base of every DITA information type.
About
DITA is the OASIS architecture for modular technical documentation, published with the DITA Open Toolkit, Oxygen and component content management systems. The generic topic is what concepts, tasks and references specialise.
These are the technical content document types of DITA 1.3 Errata 02, with the whole module tree they include.
Good to know
- Keys, conrefs and links are not resolved; DITA-OT or a CCMS checks those.
- The example is by xmlvalid.com.
Files
41 files · 517.3 KB-
technicalContent/dtd/topic.dtd main
-
technicalContent/dtd/abbreviateDomain.ent
-
technicalContent/dtd/equationDomain.ent
-
base/dtd/hazardstatementDomain.ent
-
base/dtd/highlightDomain.ent
-
base/dtd/indexingDomain.ent
-
technicalContent/dtd/markupDomain.ent
-
technicalContent/dtd/mathmlDomain.ent
-
technicalContent/dtd/programmingDomain.ent
-
technicalContent/dtd/releaseManagementDomain.ent
-
technicalContent/dtd/softwareDomain.ent
-
technicalContent/dtd/svgDomain.ent
-
technicalContent/dtd/uiDomain.ent
-
base/dtd/utilitiesDomain.ent
-
technicalContent/dtd/xmlDomain.ent
-
base/dtd/deliveryTargetAttDomain.ent
-
base/dtd/topic.mod
-
base/dtd/topicDefn.ent
-
base/dtd/commonElements.ent
-
base/dtd/commonElements.mod
-
base/dtd/tblDecl.mod
-
base/dtd/metaDecl.mod
-
technicalContent/dtd/abbreviateDomain.mod
-
technicalContent/dtd/equationDomain.mod
-
base/dtd/hazardstatementDomain.mod
-
base/dtd/highlightDomain.mod
-
base/dtd/indexingDomain.mod
-
technicalContent/dtd/markupDomain.mod
-
technicalContent/dtd/mathmlDomain.mod
-
technicalContent/dtd/mathml/mathml3-ditadriver.dtd
-
technicalContent/dtd/mathml/mathml3/mathml3.dtd
-
technicalContent/dtd/mathml/mathml3/mathml3-qname.mod
-
technicalContent/dtd/programmingDomain.mod
-
technicalContent/dtd/releaseManagementDomain.mod
-
technicalContent/dtd/softwareDomain.mod
-
technicalContent/dtd/svgDomain.mod
-
technicalContent/dtd/svg/svg11-ditadriver.dtd
-
technicalContent/dtd/svg/svg11/svg11-flat-20110816.dtd
-
technicalContent/dtd/uiDomain.mod
-
base/dtd/utilitiesDomain.mod
-
technicalContent/dtd/xmlDomain.mod
The validator loads all of these with their folder structure, so includes and imports resolve as published.
Example document
topic.xml · 547 B · valid against this schema
In CI and from code
The same schema by its name, dita-1.3-topic, through the API.
npx @xmlvalid/cli validate "**/*.xml" --schema dita-1.3-topic
- uses: xmlvalid/validate-action@v1
with:
files: "**/*.xml"
schema: dita-1.3-topic
api-key: ${{ secrets.XMLVALID_API_KEY }}
curl https://xmlvalid.com/api/v1/validations \
-H "Authorization: Bearer $XMLVALID_API_KEY" \
-F document={{ $schema->example ?? 'document.xml' }} -F schema=dita-1.3-topic
Free accounts get 100 API validations a month. On Pro, a URL monitor can check a published document against this schema every hour and email you when it breaks. More CI setups