W3C home > Mailing lists > Public > www-html-editor@w3.org > April to June 2003

Request for enhancement in TR's: list all attributes of certain types

From: Herr Christian Wolfgang Hujer <Christian.Hujer@itcqis.com>
Date: Tue, 15 Apr 2003 10:17:24 +0200
To: www-html-editor@w3.org
Message-Id: <200304151017.37781.Christian.Hujer@itcqis.com>

Hash: SHA1

Hello dear HTML editors,

I have just some small suggestions in improving technical reports:

a) All reports should have indizes like element indizes, attribute indizes, 
property indizes, where appropriate. XHTML Modularization doesn't have these 
indizes. That's not really a problem because I can use the Index of HTML 4.01 
instead, but there are already some slight differences between XHTML 
Modularization based XHTML variants and HTML 4.01, so I would have preferred 
to use the XHTML Modularization, XHTML 1.1 or XHTML Basic documents as an 

b) There should also be an index about the attribute types listing all 
attributes of a certain type, e.g. for XHTML Modularization:
URI head@profile, html@xmlns, blockquote@cite, q@cite, a@href, 
applet@codebase, del@cite, ins@cite, form@action, input@src, img@longdesc, 
img@src, area@href, object@classid, object@codebase, object@data, 
frame@longdesc, frame@src, iframe@longdesc, iframe@src, script@src, 
link@href, base@href

(notation form taken from XPath)

Why would one want such an index?
For instance, one could want to look for all possibilities to link documents, 
or where it's possible to specify the media type(s) for offline linking or 
(in XHTML 2.0) content negotiation, where to specify Link types etc..

I for myself am currently implementing an XHTML crawler that is checking for 
bad links and creating link statistics using Java and therefore required a 
list of all attributes that are URIs. That's how I got that idea. (I know not 
every attribute which is a URI is to be followed by such a crawler, e.g. 
head@profile and html@xmlns won't be followed by such a crawler, so the 
attribute specifications of course are required, but) an index to identify 
all these attributes is slightly more helpful.

(Yes I know my user agent has a "Find in this Page" facility, which I used on 
XHTML Modularization chapter 5 to identify all URI attributes ;-)

It's nothing really important, just a suggestion to make those great technical 
reports even more better.

Greetings and thank you for your great work on these technical reports
- --
Christian Wolfgang Hujer
Geschäftsführender Gesellschafter
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/
Version: GnuPG v1.0.7 (GNU/Linux)

Received on Tuesday, 15 April 2003 04:18:21 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 15:08:48 UTC