Re: <A> content model in Cougar

Foteos Macrides (MACRIDES@SCI.WFBR.EDU)
Mon, 29 Jul 1996 08:28:19 -0500 (EST)


Date: Mon, 29 Jul 1996 08:28:19 -0500 (EST)
From: Foteos Macrides <MACRIDES@SCI.WFBR.EDU>
Subject: Re: <A> content model in Cougar
To: www-html@w3.org
Message-id: <01I7N007PVSY0001TB@SCI.WFBR.EDU>

Abigail <abigail@uk.fnx.com> wrote:
>[...]
>Of course, with the use of id, there's no need for <a name>.
>Does Cougar have id?
>[...]

	The -04 ("last call") IETF i18n draft has:
	
4.2.2. List of entities, elements, and attributes
[...]
   In the DTD, the LANG and DIR attributes are grouped together in a
   parameter entity called attrs.  In addition, the ID and CLASS
   attributes from RFC 1942 [RFC1942] were added to attrs, as was done
   in the latter. The ID, and CLASS attributes are required for use with
   style sheets, and RFC 1942 defines them as follows:

   ID      Used to define a document-wide identifier. This can be used
                                                           ^^^^^^^^^^^
           for naming positions within documents as the destination of a
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
           hypertext link. It may also be used by style sheets for ren-
           ^^^^^^^^^^^^^^         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^
           dering an element in a unique style. An ID attribute value is
           an SGML NAME token. NAME tokens are formed by an initial let-
           ter followed by letters, digits, "-" and "." characters. The
           letters are restricted to A-Z and a-z.
[...]

	RFC1942 is the latest IETF TABLEs draft, with the same %attrs
as i18n, and i18n has:

   <!ELEMENT ( %heading )  - -  (%text;)*>
   <!ATTLIST H1
           %attrs;
[...]
   <!ATTLIST H2
           %attrs;
[... etc]


	Cougar has:

<!--=================== Generic Attributes ================================-->

<!ENTITY % style
        "id     ID      #IMPLIED    -- document wide unique id --
         class  CDATA   #IMPLIED    -- comma list of class values --
         style  CDATA   #IMPLIED    -- associated style info --"
         >

<!ENTITY % i18n
        "lang   NAME    #IMPLIED    -- RFC 1766 language value --
         dir  (ltr|rtl) #IMPLIED    -- default directionality --"
         >

<!ENTITY % attrs "%style %i18n">

<!ENTITY % just
        "align  (left|center|right|justify)  #IMPLIED"
        -- default is left for ltr paragraphs, right for rtl --
        >

and:

<!--=================== Headings ==========================================-->

<!--
  There are six levels of headers from H1 (the most important)
  to H6 (the least important).
-->

<!ELEMENT ( %heading )  - -  (%text;)*>
<!ATTLIST ( %heading )
        %attrs;     -- id, class, style, lang, dir --
        %just;      -- text alignment --
        >


	So...  Assuming the ID attribute has the same meaning
in Cougar as in i18n and the TABLEs drafts, this appears to be
"evidence" that any ID attribute in a Heading can be treated as
a NAMEd anchor, and there's no need for <A NAME="seek_me">...</A>
either outside or inside the Heading tags for markup which
declares Cougar's DOCTYPE.

				Fote

=========================================================================
 Foteos Macrides            Worcester Foundation for Biomedical Research
 MACRIDES@SCI.WFBR.EDU         222 Maple Avenue, Shrewsbury, MA 01545
=========================================================================