Il CD di internet/CD.iso/INTERNET/HTML/HOTMETAL/DTDS/HTML.DTD

Text File | 1994-06-17 | 23.4 KB | 582 lines

<!-- DOCTYPE HTML [  -->

<!--    html.dtd v1.1  3June94

        Document Type Definition for the HyperText Markup Language
        as used by the World Wide Web application (HTML DTD).

        This is not a formal part of the HTML development being led
        by Dave Raggett and Dan Connolly but attempts to contribute
        to that development only by assisting users in creating
        reasonably structured documents from which it should be
        straightforward to move to formalized versions of the HTML DTD
        when appropriate.

-->

<!--
Note from SoftQuad regarding use of this DTD in the HoTMetaL
World Wide Web Editor:

This is a special version of the HTMLplus DTD which has had all the
elements (and most of the attributes) stripped out which are NOT in
the HTMLdtd v1.11 1994. In order to increase the likelihood of
future compatibility of documents created with HoTMetaL, HTML
attributes which are likely to not be in the next revision of HTML have
been left out.

Accordingly, its best use is for creating new documents. That is, its
restrictiveness will be helpful in giving context-sensitive guidance
during document creation. At the same time, that restrictiveness will
minimize the usefulness of HoTMetaL with files which use original
HTML markup flamboyantly.
However:
1. This is a feature and means that opening an old document with
"Rules Checking Off" will still allow you to insert any markup anywhere.
2. Opening a document with "Rules Checking Off" and then turning rules
on will result in useful error messages with the cursor being placed where
the markup is not in conformance with the more restrictive DTD. In
this way, files may be cleaned up for future use.
3. To receive a DTD designed particularly to accept almost any file
created before there was an HTML DTD, send email to:
       [e-mail]
4. To put your name on a list to receive updates of the DTD as they
come along, send email to:
       [e-mail]
-->

<!--
ENTITY DECLARATIONS

Brief Introduction:
 <!ENTITY % foo "X | Y | Z"> is a macro definition for parameters and in
 subsequent statements, the string "%foo;" is expanded to "X | Y | Z"

 Various classes of SGML text types:

  CDATA  text which doesn't include markup or entity references
  RCDATA text with entity references but no markup
  PCDATA text occurring in a context in which markup and entity references
     may occur.
-->

<!-- Core HTML+ DTD omits following features; HoTMetal includes forms: -->
<!ENTITY % HTML.figures "IGNORE">
<!ENTITY % HTML.emph "IGNORE">
<!ENTITY % HTML.forms "INCLUDE">
<!ENTITY % HTML.obsolete "IGNORE">
<!ENTITY % HTML.icons "IGNORE">

<!ENTITY % URL "CDATA" -- a URL or URN designating a hypertext node -->

<!-- Browsers should render the following types of emphasis
     distinctly when the obvious rendering is impractical

     I = italic, B = bold, U = underline, TT = teletype font,
     REV = reverse video for highlighting hit areas in the result of a query
-->

<!ENTITY % emph1 "I|B|U|TT|CITE|EM|STRONG|KBD|VAR|DFN|CODE|SAMP">
<!ENTITY % emph2 "REV">
<!ENTITY % emph3 "HIDE">

<![ %HTML.emph [ <!ENTITY % emph  "%emph1;|%emph2;|%emph3;"> ]]>
<!ENTITY % emph  "%emph1;">

<![ %HTML.forms [ <!ENTITY % misc2 "|INPUT|TEXTAREA|SELECT"> ]]>
<!ENTITY % misc2 "">

<!ENTITY % literal " XMP | LISTING ">

<!ENTITY % lit-content "RCDATA">

<!ENTITY % misc "BR  %misc2;">

<!ENTITY % text "#PCDATA|A|IMG|%emph;|%misc; ">

<!ENTITY % paras "P|PRE">

<!ENTITY % lists "UL|OL|DL">

<!ENTITY % block1 "ADDRESS|HR">

<![ %HTML.forms [ <!ENTITY % block3 "|FORM"> ]]>
<!ENTITY % block3 "">

<![ %HTML.obsolete [ <!ENTITY % block4 "|MENU|DIR|BLOCKQUOTE"> ]]>
<!ENTITY % block4 "|BLOCKQUOTE">

<!ENTITY % block "%block1;  %block3; %block4;">

<!ENTITY % setup "(TITLE? & ISINDEX? & BASE? & META* & LINK*)">

<!ENTITY % main "%block;|%lists;|%paras;|%literal;">

<!-- these entities are used to simplify element definitions -->

<!ENTITY % heading "H1|H2|H3|H4|H5|H6">

<!ENTITY % body-content "%heading; | %main;|IMG|A|">

<![ %HTML.obsolete [<!ENTITY % anchorname "name NMTOKEN #IMPLIED"> ]]>
<!ENTITY % anchorname "">

<![ %HTML.forms [
 <!ENTITY % fields "text|password|checkbox|radio|submit|reset|image|
                        hidden"  -- newer browsers will support longer list -- >
]]>


<!-- Core DTD includes basic Latin-1 entities -->
<!ENTITY % ISOlat1 PUBLIC "ISO 8879-1986//ENTITIES Added Latin 1//EN">
%ISOlat1;

<!-- additional entities normally found in Latin-1 char sets -->
<!ENTITY % ISOnum PUBLIC "ISO 8879-1986//ENTITIES Numeric and Special Graphic//EN">
%ISOnum;

<!-- diacritical marks normally found in Latin-1 char sets -->
<!ENTITY % ISOdia PUBLIC "ISO 8879-1986//ENTITIES Diacritical Marks//EN">
%ISOdia;

<!-- misc. from ISO Publishing entities -->
<!ENTITY ndash  SDATA " - "--=en dash-->
<!ENTITY mdash  SDATA "--"--=em dash-->
<!ENTITY ensp   SDATA " "--=en space (1/2-em)-->
<!ENTITY emsp   SDATA " "--=em space-->
<!ENTITY hellip SDATA "..."--=ellipsis (horizontal)-->
<!ENTITY vellip SDATA "."--=ellipsis (vertical)-->

<!-- misc. from HTML.dtd -->
<!ENTITY amp SDATA "&"     -- ampersand -->
<!ENTITY gt SDATA ">"      -- greater than -->
<!ENTITY lt SDATA "<"      -- less than -->
<!ENTITY quo SDATA '"'    -- quotation mark -->
<!ENTITY nbsp SDATA "<? nonbreaking-space>">

<!-- standard ISO/WWW icons courtesy of Bert Bos and Kevin Hughes, see
         gopher://gopher.let.rug.nl/00/ftp/pub/Bert/WWWicn.940218

    These can be used in place of default symbols for list items or as
    part of hypertext links, and save time needed to download images.
    Browsers can define them in terms of library images or as URL/URNs.
-->

<![ %HTML.icons [
  <!ENTITY ftp SDATA "ftp" -- ftp server -->
  <!ENTITY gopher SDATA "gopher" -- gopher server -->
  <!ENTITY telnet SDATA "telnet" -- telnet connection -->
  <!ENTITY archive SDATA "archive" -- archive server -->
  <!ENTITY filing.cabinet SDATA "filing.cabinet" -- filing cabinet -->
  <!ENTITY folder SDATA "folder" -- folder or directory -->
  <!ENTITY fixed.disk SDATA "fixed.disk" -- fixed media drive -->
  <!ENTITY disk.drive SDATA "disk.drive" -- removeable media drive -->
  <!ENTITY document SDATA "document" -- unspecified document type -->
  <!ENTITY unknown.document SDATA "unknown.document" -- unrecognised document type -->
  <!ENTITY text.document SDATA "text.document" -- text/plain, text.html etc. -->
  <!ENTITY binary.document SDATA "binary.document" -- binary data -->
  <!ENTITY binhex.document SDATA "binhex.document" -- binhex format -->
  <!ENTITY audio SDATA "audio" -- audio sequence -->
  <!ENTITY film SDATA "film" -- film or animation, such as an MPEG movie -->
  <!ENTITY image SDATA "image" -- photograph, drawing or graphic of any kind -->
  <!ENTITY map SDATA "map" -- geographical or a schematic map -->
  <!ENTITY form SDATA "form" -- fill-out form -->
  <!ENTITY mail SDATA "mail" -- email messages -->
  <!ENTITY parent SDATA "parent" -- parent of current document -->
  <!ENTITY next SDATA "next" -- next document in current sequence -->
  <!ENTITY previous SDATA "previous" -- previous document in current sequence -->
  <!ENTITY home SDATA "home" -- home document -->
  <!ENTITY toc SDATA "toc" -- table of contents -->
  <!ENTITY glossary SDATA "glossary" -- glossary of terms etc. -->
  <!ENTITY index SDATA "index" -- searchable index -->
  <!ENTITY summary SDATA "summary" -- summary -->

  <!ENTITY calculator SDATA "calculator" -- A calculator -->
  <!ENTITY caution SDATA "caution" -- Warnign sign -->
  <!ENTITY clock SDATA "clock" -- A clock -->
  <!ENTITY compressed.document SDATA "compressed.document">
  <!ENTITY diskette SDATA "diskette" -- A diskette -->
  <!ENTITY display SDATA "display" -- A computer screen -->
  <!ENTITY fax SDATA "fax" -- A fax machine -->
  <!ENTITY mail.in SDATA "mail.in" -- mail-in tray -->
  <!ENTITY mail.out SDATA "mail.out" -- mail-out tray -->
  <!ENTITY mouse SDATA "mouse" -- mouse/pointing device -->
  <!ENTITY printer SDATA "printer" -- hardcopy device -->
  <!ENTITY tn3270 SDATA "tn3270" --tn3270 terminal session -->
  <!ENTITY trash SDATA "trash" -- waste paper basket -->
  <!ENTITY uuencoded.document SDATA "uuencoded.document" -- uuencoded data -->
]]>

<!-- BASIC TYPES OF ELEMENTS:
Brief Introduction:
  <!ELEMENT tagname - - CONTENT> elements needing end tags
  <!ELEMENT tagname - O CONTENT> elements with optional end tags
  <!ELEMENT tagname - O EMPTY> elements without content or end tags

The content definition is:
       -  an element declaration as defined above
       -  a tagname
       -  (brackets enclosing the above)
These may be combined with the operators:
  A*      A occurs zero or more times
  A+      A occurs one or more times
  A|B     either A or B
  A?      A occurs zero or one times
  A,B     first A then B
  A&B     both A and B (in either order A B or B A)
-->

<!-- BODY OF THE DTD:   -->

<!ELEMENT HTML O O (HEAD, BODY)>
<!ATTLIST HTML
        charset CDATA   #IMPLIED -- eg "ISO-2022-JP" for japanese --
        version CDATA #FIXED  "html.dtd v1.20" -- the HTML+ version number -->

<!ELEMENT HEAD O O (%setup;) -- delimits document wide properties -->

<!ELEMENT BODY O O  (%body-content)*>


<!-- Document headers -->
<!ELEMENT (%heading;) - - (%text;)+>

<!-- character emphasis -->
<!ELEMENT (%emph1;) - O (%text;)*    >

<!ELEMENT P - O (%text;)+>

<!ELEMENT HR - O EMPTY -- Horizontal Rule -->
<!ELEMENT BR - O EMPTY -- forced line break -->

<!ELEMENT PRE - - (%text;)+ -- preformatted fixed pitch text -->

<!ELEMENT ADDRESS - - (#PCDATA|P|HR|IMG|A|BR)* -- info on author -->

<!ELEMENT (%literal) - -  %lit-content>

<!-- Lists which can be nested -->
<!ELEMENT OL - O (LI)+ -- ordered list -->

<!ELEMENT UL - - (LI)+ -- unordered list -->

<!ELEMENT (MENU|DIR) - O   (LI)+  -- obsoleted lists -- >

<!-- List items for UL and OL lists

 By default UL list items have bullets while OL list items
 are numbered in a style dependent on nesting. For extra impact
 specify an explicit image with the icon attribute or a string
 with the label attribute. This attribute can also be used with
 SGML entities to specify standard icons, e.g. label="&folder;"
-->

<!ELEMENT LI - O (#PCDATA|%lists;|%paras;|%emph1;|%block1;|A|IMG|FORM|XMP)*>
<!ATTLIST LI
        icon     %URL;  #IMPLIED -- image for use in place of bullet --
        label   CDATA   #IMPLIED -- when you can't show the icon image -->

<!-- Definition Lists (terms + definitions) -->
<!ELEMENT DL - - (DT+, DD)+>

<!ELEMENT DT - O (%text;)+          -- term to be defined -- >
<!ELEMENT DD - O (%text;|DL|UL|OL|P|HR|PRE|IMG|A|XMP|#PCDATA)+   -- definition text -- >


<!-- Hypertext Links from points within document nodes

 The HREF attribute specifies the link destination as a URL or URN.

 The TITLE attribute may be used for links in which the destination
 node doesn't define a title itself, e.g. non-html documents.

 The REL attribute is used to specify how the browser interprets
 the link when this document is being used as a hypertext path
 REL="Path" causes the linked document to be treated as a path
 and inserted into the current path, while REL="Node" treats
 the linked document as a node on the current path. REL="Embed"
 is a hint to embed the referenced node into the current document.
-->

<!ELEMENT A - - (#PCDATA | BR | IMG | %emph;)*>
<!ATTLIST A
        href    %URL;   #IMPLIED -- destination node --
        %anchorname;             -- see HTML.obsolete --
        rel     CDATA   #IMPLIED -- forward relationship type --
        rev     CDATA   #IMPLIED --  reverse relationship type --
        methods NAMES #IMPLIED -- supported public methods of
           the object: TEXTSEARCH, GET, HEAD, ... --
        name   CDATA   #IMPLIED -- when otherwise unavailable (obs) --
        title   CDATA   #IMPLIED -- when otherwise unavailable -->

<!-- Other kinds of relationships between documents

 There are a set of standard RELationship types which alter the
 browser's navigation menu:

    UseIndex        searchable index
    UseGlossary     shared glossary
    Contents        shared contents page
    Previous        previous document in a hypertext path
    Next            next document in a hypertext path
    Bookmark        named with the title attribute
    Made            Defines who is the "maker" of this document
    Help            provides help on this document
    Annotation      an additional note on current document
    Reply           a note with equal footing to current document
    Subdocument     defines parent->child relationship
    Parent          defines child->parent relationship
    StyleSheet      an associated style sheet

 Bookmarks allow authors to define a set of useful links
 which are to be accessed via a menu, rather than as conventional
 in-line hypertext links. Previous and Next links are inserted
 by the browser when interpreting a separate document as a path.
 See above description of REL="Node" and REL="Path" for <A>.

 The FROM attribute makes it possible to specify annotation
 links separately from the document text flow. The FROM
 attribute specifies an ID for the source of a link, while
 the HREF attribute specifies its destination. HTTP servers
 can use the WWW-Link: header to "insert" such annotations
 into documents.
-->

<!ELEMENT LINK - O EMPTY>
<!ATTLIST LINK
        href    %URL;  #REQUIRED -- destination node --
        src     %URL;   #IMPLIED -- an image for displaying link --
        id      ID      #IMPLIED -- to allow meta info on links --
        rel     CDATA   #IMPLIED -- forward relationship type --
        rev     CDATA   #IMPLIED -- reverse relationship type --
        title   CDATA   #IMPLIED -- when otherwise unavailable -->

<!-- Document title -->
<!ELEMENT TITLE - - (#PCDATA)    >

<!-- Original document URL for resolving relative URLs  -->
<!ELEMENT BASE - O EMPTY>
<!ATTLIST BASE HREF %URL; #IMPLIED>

<!-- Signifies the document's URL accepts queries,
     and may be implied by HTTP header info -->
<!ELEMENT ISINDEX - O EMPTY>
<!ATTLIST ISINDEX href %URL; #IMPLIED -- defaults to document's URL -->

<!--
 Servers should read the document head to generate HTTP headers
 corresponding to META elements, e.g. if the document contains:

        <meta name="Expires" value="Tue, 04 Dec 1993 21:29:02 GMT">

 The server should include the HTTP date format header field:

        Expires: Tue, 04 Dec 1993 21:29:02 GMT

 Other likely names are "Summary", "Keywords", "Created",
 "Owner" (a name) and "Reply-To" (an email address)

 These elements can be used to construct IAFA style templates
 which describe the contents of the server. The templates are
 then used for automatic indexing of servers.

 The effectiveness of indexing is dependent on using well defined
 keywords drawn from standard sets.

 The Document-Icon header is used to specify a URL for
 use as an icon in the hotlist and history list.
-->

<!ELEMENT META - O EMPTY>
<!ATTLIST META
        id      ID      #IMPLIED -- to allow meta info  --
        name    CDATA   #IMPLIED -- HTTP header e.g. "Expires" --
        value   CDATA   #IMPLIED -- associated value -->

<![ %HTML.obsolete [

<!ELEMENT (MENU|DIR) - - (LI)+ -- plain single/multicolumn lists-->

]]>

<![ %HTML.emph [

<!-- additional character emphasis -->
<!ELEMENT (%emph2;) - O (%text;)*>
<!ATTLIST (%emph2;)
        id      ID      #IMPLIED -- link destination --
        charset CDATA   #IMPLIED -- eg "ISO-2022-JP" for japanese -->

<!-- content is hidden, equivalent of LaTeX's \kill -->
<!ELEMENT HIDE - - (%text;) -(HIDE)>

]]>

<!ELEMENT BLOCKQUOTE - - (#PCDATA|%paras;|%lists;|%block1;|
                                    BR|IMG )* -- block quote (obsolete) -->

<![ %HTML.forms [

<!--
 The form contents are sent to the server upon pressing a submit
 button. Forms can be associated with scripts, e.g. to make one
 selection field effect which options are enabled for other fields.

 Clicking on a selection or typing into a text field result in events
 which are processed by the script. Event handlers are associated
 with each field or with the form itself. The script language is
 deliberately restricted to avoid any security issues.

 Fields can be disabled (greyed out) or marked as being in error.
 The MESSAGE element may be used by the server to set error messages.
 Servers can store state information in forms with hidden input fields.
 These are not displayed and can be used to hold transaction handles etc.
-->

<!ELEMENT FORM - - ((%main;|%heading;|IMG)*, MESSAGE?) -(FORM)
           -- in this futuristic version, forms can't be nested -->
<!ATTLIST FORM
        action  %URL;   #IMPLIED -- defaults for URL for current doc --
        script  %URL;   #IMPLIED -- locally executed event handlers --
        method  CDATA   #IMPLIED -- GET, PUT, POST, DELETE etc. --
        enctype CDATA   #IMPLIED -- encoding type for form transfers --
        id      ID      #IMPLIED
        charset CDATA   #IMPLIED -- eg "ISO-2022-JP" for japanese -->

<!-- Types of INPUT field:
 text: one line text fields, size gives visible width of field in chars
       where value may grow beyond this up to MAX (MAXLENGTH) chars.
 password: like text fields but with no echo of typed characters
 checkbox: for simple yes/no choices
 radio: for one from many choices, each radio button in a group
        has the same NAME but a different VALUE.
 submit: Sends form to server. If the SRC attribute specifies an
       icon the point clicked is sent to the server as per ISMAP.
       The default NAME for this field is "Submit". The VALUE is used
       as the buttobn label. The NAME/VALUE are submitted with the form
       contents to allow servers to work out which button was pressed.
 reset: Resets fields to their initial values. The VALUE is used as the
       button label. The SRC attribute can be used for an icon button.
 int: for input of integers, SIZE attribute gives width of field
 float: for input of floating point numbers
 date: for input of dates
 url: for input of universal resource locators
 hidden: used by server for state info, opaque to client
 range: integer range from MIN to MAX, rendered as a slider etc.
 scribble: Pen input, which may include time and pressure info, the
        background can be initialised to an image with the SRC attribute
 audio: sound input with up to MAX seconds
-->
<!ELEMENT INPUT - O EMPTY>
<!ATTLIST INPUT
        id      ID      #IMPLIED -- to allow meta info  --
        name    CDATA   #IMPLIED -- attribute name (may not be unique) --
        type    (%fields) text   -- a wide variety of field types --
        charset CDATA   #IMPLIED -- eg "ISO-2022-JP" for japanese --
        size    CDATA   #IMPLIED -- visible size of text fields --
        min     NUMBER  #IMPLIED -- for range controls --
        max     NUMBER  #IMPLIED -- for range controls or text fields --
        maxlength NUMBER #IMPLIED -- max length of text fields (equiv to max)--
        value   CDATA   #IMPLIED -- attribute value (altered by user) --
        checked (checked) #IMPLIED -- for check boxes and radio buttons --
        disabled (disabled) #IMPLIED -- if grayed out --
        error   (error) #IMPLIED -- if in error --
        src      %URL;  #IMPLIED -- for SUBMIT, SCRIBBLE & AUDIO fields --
        alt     CDATA   #IMPLIED -- alternative text for VT100's etc --
        align (top|middle|bottom) top -- for IMAGE fields only -->

<!-- multiline text input fields, we probably will want
     to generalise this to accept arbitrary clipboard data
     e.g. hypertext and images, in addition to plain text -->
<!ELEMENT TEXTAREA - - RCDATA -- multi-line text fields -->
<!ATTLIST TEXTAREA
        id      ID      #IMPLIED -- to allow meta info  --
        name    CDATA   #IMPLIED -- attribute name (may not be unique) --
        cols    NUMBER  #IMPLIED -- visible width in characters --
        rows    NUMBER  #IMPLIED -- visible height in characters --
        wrap    (wrap)  #IMPLIED -- wrap input in text area --
        disabled (disabled) #IMPLIED -- if grayed out --
        error   (error) #IMPLIED -- if in error --
        charset CDATA   #IMPLIED -- eg "ISO-2022-JP" for japanese -->

<!--
     The EDIT attribute when present allows you to type and
     edit the selected option.

     The SRC attribute allows for graphical menus, e.g. users
     wanting to buy a house could click on each of the areas on
     a map that they were interested in.
 -->
<!ELEMENT SELECT - - (OPTION+) -- combo style selection lists -->
<!ATTLIST SELECT
        src      %URL;  #IMPLIED -- for graphical menus --
        id      ID      #IMPLIED -- to allow meta info  --
        name    CDATA   #IMPLIED -- attribute name (may not be unique) --
        edit    NUMBER  #IMPLIED -- width of editable selection --
        multiple (multiple) #IMPLIED -- permits multiple selections --
        error   (error) #IMPLIED -- if in error --
        charset CDATA   #IMPLIED -- eg "ISO-2022-JP" for japanese -->

<!-- The SHAPE attribute defines a region in the image that
     is specified by the SRC attribute for the SELECT element -->
<!ELEMENT OPTION - O RCDATA>
<!ATTLIST OPTION
        id      ID      #IMPLIED -- to allow meta info  --
        value   CDATA   #IMPLIED -- attribute value --
        selected (selected) #IMPLIED -- if initially selected --
        disabled (disabled) #IMPLIED -- if grayed out --
        shape   CDATA   #IMPLIED -- list of points for shaped region --
        charset CDATA   #IMPLIED -- eg "ISO-2022-JP" for japanese -->

<!--
 Scripts executed by the client need a way of displaying
 warning/error messages. We define an element so that the
 server too can initialise this one-per-form message area.
 Clients should preferably avoid displaying the message
 in-line, as the window size may prevent the user from
 seeing the message.
 -->
<!ELEMENT MESSAGE - O RCDATA -- place for error/warning/info -->
<!ATTLIST MESSAGE
        id      ID      #IMPLIED -- to allow meta info  --
        status  (info|warning|error) info
        charset CDATA   #IMPLIED -- eg "ISO-2022-JP" for japanese -->
]]>


<!-- IMG is intended to migrate for use in-line; "FIG"  will be used
for block graphics in the future. For now, browsers support only IMG.
-->

<!ELEMENT IMG - O EMPTY>
<!ATTLIST IMG
        src     %URL;   #REQUIRED -- where to get image data --
        align   (top|middle|bottom) top  -- top, middle or bottom --
        alt     CDATA   #IMPLIED -- description for text-only displays --
        ismap   (ismap) #IMPLIED  -- send mouse clicks/drags to server -->


<!-- Like MENU and DIR, the following elements may appear in existing
documents. All five elements are not declared as having a structural
context. HoTMetaL will report them as errors on import and users can
turn them into allowed elements.
-->

<!ELEMENT KEY  - - (#PCDATA|%emph1;)*>
<!ELEMENT PLAINTEXT - - RCDATA>
<!ELEMENT NEXTID - O EMPTY>
<!ATTLIST NEXTID N CDATA #IMPLIED
          -- The number is a name suitable for use
             for the ID of a new element. When used, the value
             has its numeric part incremented. EG Z67 becomes Z68.
             This is proposed for removal and is included here only
             to allow documents which include the element to be opened.
          -->


<!-- The END -->
<!-- ]  -->