Welcome to WebHeadStart.org

Web Technologies

Sponsored By

WebHeadStart.org is currently in beta.
Please pardon our appearance as we work to provide you with the most comprehensive reference on today's web technologies.

Interested in advertising on WebHeadStart? Become an advertising partner today!

[WWW-HTML Mailing List Archive Home] [Messages By Thread] [Messages By Date]

XHTML2: Allow nested link elements?

From: Herr Christian Wolfgang Hujer <Christian.Hujer@itcqis.com>
Date: Mon, 20 Oct 2003 18:08:17 +0200
To: www-html-editor@w3.org, www-html@w3.org
Message-Id: <200310201809.05851.Christian.Hujer@itcqis.com>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hello dear HTML editors,

I want to suggest nested link elements.
Example:
<html>
    <head>
        <title>Configuring Transparent Content Negotiation</title>
        <link rel="chapter" href="#introduction" title="Introduction" />
        <link rel="chapter" href="#basics" title="Basics">
            <link rel="section" href="#http" title="HTTP" />
        </link>
        <link rel="chapter" href="#contneg" title="Content Negotiation">
            <link rel="section" href="#types" title="Types of Content 
Negotiation">
                <link rel="subsection" href="#typeServer" title="Server Side 
Decision" />
                <link rel="subsection" href="#typeClient" title="Client Side 
Decision" />
            </link>
            <link rel="chapter" href="#exApache" title="Configuration Example 
for Apache" />
        </link>
    </head>
    <body>
        <h1>Configuring Transparent Content Negotiation</h1>
        <h2 id="introduction">Introduction</h2>
        <h2 id="basics">Basics</h2>
        <h3 id="http">HTTP</h3>
        <h2 id="contneg">Content Negotiation</h2>
        <h3 id="types">Types of Content Negotiation</h3>
        <h4 id="typeServer">Server Side Decision</h4>
        <h4 id="typeClient">Client Side Decision</h4>
        <h3 id="exApache">Configuration Example for Apache</h3>
    </body>
</html>

I know using <link rel="chapter" /> ("Refers to a document serving as a 
chapter in a collection of documents") per definition is not really meant for 
identifying fragments of the same document, but I don't think why it 
shouldn't be used in that way, and Mozilla shows that it can be implemented 
and supported in a fine and convenient way. And anyway, often when I read 
"document" I think "information set" or "document fragment" or "element" or 
"nodeset" would be much more appropriate, anyway.

By allowing <link/> elements to be nested, authors could add some structure to 
their link elements and thus indicate e.g. which chapter a section belongs 
to, independantly of wether the hyperreferences refer to a fragment of the 
same or to another document.


Greetings
- -- 
ITCQIS GmbH
Christian Wolfgang Hujer
Geschäftsführender Gesellschafter (Shareholding CEO)
Telefon: +49  (0)89  27 37 04 37
Telefax: +49  (0)89  27 37 04 39
E-Mail: Christian.Hujer@itcqis.com
WWW: http://www.itcqis.com/ 
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2-rc1-SuSE (GNU/Linux)

iD8DBQE/lAiTzu6h7O/MKZkRAlQIAJwNyWBqUlnw1fD7tFxDDljfRzphMQCgrjJP
Fd7zOtuXUaUFynigtg92jXE=
=+THw
-----END PGP SIGNATURE-----
Received on Monday, 20 October 2003 12:10:56 GMT
Valid XHTML 1.0! Valid CSS! Site Map | Privacy Policy | Terms of Use | WebHeadStart.org © 2005 All Rights Reserved.