XML Catalog XHTML version 1.0 Schema This is modified from XHTML 1.0 strict Namespace = http://www.openhealth.org/XMLCatalog/ PUBLIC "-//XML Catalog//XSD XHTML 1.0 Strict//EN" SYSTEM "http://www.openhealth.org/XMLCatalog/xcat-xhtml1.xsd" Copyright (c) 1998-2000 W3C (MIT, INRIA, Keio), All Rights Reserved. This DTD module is identified by the PUBLIC and SYSTEM identifiers: ================ Character mnemonic entities ========================= ================ Document Structure ================================== the namespace URI designates the document profile content model is %head.misc; combined with a single title and an optional base element in any order The title element is not considered part of the flow of text. It should be displayed, for example as the page header or window title. Exactly one title is required per document. document base URI generic metainformation Relationship values can be used in principle: a) for document specific toolbars/menus when used with the link element in document head e.g. start, contents, previous, next, index, end, help b) to link to a separate style sheet (rel="stylesheet") c) to make a link to a script (rel="script") d) by stylesheets to control how collections of html nodes are rendered into printed documents e) to make a link to a printable version of this document e.g. a PostScript or PDF version (rel="alternate" media="print") style info, which may include CDATA sections script statements, which may include CDATA sections alternate content container for non script-based rendering =================== Document Body ==================================== generic language/style container =================== Paragraphs ======================================= =================== Headings ========================================= There are six levels of headings from h1 (the most important) to h6 (the least important). =================== Lists ============================================ Unordered list Ordered (numbered) list list item definition lists - dt for term, dd for its definition =================== Address ========================================== information on author =================== Horizontal Rule ================================== =================== Preformatted Text ================================ content is %Inline; excluding "img|object|big|small|sub|sup" =================== Block-like Quotes ================================ =================== Inserted/Deleted Text ============================ ins/del are allowed in block and inline content, but its inappropriate to include block content within an ins element occurring in inline content. ================== The Anchor Element ================================ content is %Inline; except that anchors shouldn't be nested ===================== Inline Elements ================================ generic language/style container I18N BiDi over-ride forced line break emphasis strong emphasis definitional program code sample something user would type variable citation abbreviation acronym inlined quote subscript superscript fixed pitch font italic font bold font bigger font smaller font ==================== Object ====================================== object is used to embed objects as part of HTML pages. param elements should precede other content. Parameters can also be expressed as attribute/value pairs on the object element itself when brevity is desired. param is used to supply a named property value. In XML it would seem natural to follow RDF and support an abbreviated syntax where the param elements are replaced by attribute value pairs on the object start tag. =================== Images =========================================== To avoid accessibility problems for people who aren't able to see the image, you should provide a text description using the alt and longdesc attributes. In addition, avoid the use of server-side image maps. Note that in this DTD there is no name attribute. That is only available in the transitional and frameset DTD. usemap points to a map element which may be in this document or an external document, although the latter is not widely supported ================== Client-side image maps ============================ These can be placed in the same document or grouped in a separate document although this isn't yet widely supported ================ Forms =============================================== forms shouldn't be nested Each label must not contain more than ONE field Label elements shouldn't be nested. the name attribute is required for all but submit & reset form control option selector option group selectable choice multi-line text field The fieldset element is used to group form fields. Only one legend element should occur in the content and if present should only be preceded by whitespace. fieldset label Content is %Flow; excluding a, form and form controls push button colgroup groups a set of col elements. It allows you to group several semantically related columns together. col elements define the alignment properties for cells in one or more columns. The width attribute specifies the width of the columns, e.g. width=64 width in screen pixels width=0.5* relative width of 0.5 The span attribute causes the attributes of one col element to apply to more than one column. th is for headers, td for data and for cells acting as both