Notes on W3C Schema Version


The W3C Schema has been generated from the Journal Publishing DTD for use in XML tools that can not read DTDs.The Schema is not intended for maintenance.

In order to mitigate problems found in testing with various processors' differing interpretations of Schema syntax, this Schema has been generated out of a flattened rendition of the NLM Journal Publishing DTD. While the structural constraints on document tagging expressed by this schema are identical to those of the DTD, the DTD's modular architecture is not reflected in the schema's organization. Changes to the Tag Set will be made by making modifications to the DTD, and a modified Schema will be generated from the modified DTD.

Getting the Files

The W3C Schema files are available by anonymous FTP: ftp://ftp.ncbi.nih.gov/pub/publishing_dtd.

A direct link to the files is available: ftp.ncbi.nih.gov/pub/publishing_dtd/journal-publishing-dtd-1.1.zip.

The W3C Schema is available on the Web: http://dtd.nlm.nih.gov/1.1/xsd/journalpublishing.xsd

Schema Structure

The Schema contains four modules:

Each of these modules corresponds to one of the namespaces in play:

  • journalpublishing.xsd (null, default namespace)

  • xlink.xsd (xlink namespace: http://www.w3.org/1999/xlink)

  • xml.xsd (xml namespace: http://www.w3.org/XML/1998/namespace)

The modules import one another. For the schema to work all modules must be in the same directory.

Tools

The Schema has been tested and found to perform properly in:

  1. Apache Xerces XML parser (for Java, version 2.5.0)

  2. XML Spy (version 2004 rel.3)

  3. Microsoft Word XML 2003 Professional (see below)

The document element of an instance document, depending on the tools used, may require namespace and attribute declarations to associate the document with the schema. For Xerces and XMLSpy, these may take the form of:

<article xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="journalpublishing.xsd">
where the xsi:noNamespaceSchemaLocation attribute points to the journalpublishig.xsd module on the system.

MS Word 2003

Cautions when using MS Word 2003 Professional

The mechanism for associating a document with a schema in MS Word 2003 Professional differs considerably from the above. The declarations (namespace declaration for the xsi namespace, and the xsi:noNamespaceDeclaration attribute) are NOT required and may confuse the system.

A schema may be bound to a document in MS Word 2003 as follows:

  1. Add the schema to the list of schemas available. This can be done (though only when an XML document is open) through the "XML Schema" tab under the "Templates and Add-ins" menu option (under "Tools"). When the schema is selected, Word will want a URI to associate with it (despite the fact that this document type has no default namespace). We have used the following:

    URI: http://namespace.nih.gov/journalpublishing.xsd
    Alias: Journal Publishing schema

    When this schema is added, the XLink schema must also be added (it is imported by the main schema). Its URI is derived from the xlink.xsd file; we have used

    Alias: W3C XLink schema

    Then MSWord will want to attach the journalpublishing.xsd schema again (presumably since it is imported by XLink). This operation can be cancelled.

  2. In the XML Schema tab of the Templates and Add-ins dialog box, associate the open document with the schema by checking the box next to the schema in the list.

    Use the "Save As XML" feature with the "Save Data only" box checked to save clean XML using only allowed tags.


PubMed Central
NCBI | NLM | NIH
Department of Health & Human Services
Freedom of Information Act | Disclaimer
Last updated: February 23, 2004