Re: <resource> [was: Proposal for SIZE attribute ]

Terry Allen (terry@ora.com)
Thu, 11 Jan 1996 06:48:00 PST


Message-Id: <199601111448.GAA02931@rock.west.ora.com>
From: Terry Allen <terry@ora.com>
Date: Thu, 11 Jan 1996 06:48:00 PST
In-Reply-To: "Daniel W. Connolly" <connolly@beach.w3.org>
To: "Daniel W. Connolly" <connolly@beach.w3.org>,
Subject: Re: <resource> [was: Proposal for SIZE attribute ]

Not nifty if it isn't integrated with EMBED (or current alias).  Not
nifty if you think that EMBED is putting the information in the wrong
place.  Not nifty if it overloads META and LINK.  

But then you haven't proposed it yet .

Regards,

--- Forwarded mail from "Daniel W. Connolly" <connolly@beach.w3.org>

>From www-html-request@w3.org Wed Jan 10 23:21:58 1996
Received: from ruby.ora.com (ruby.ora.com [198.112.208.25]) by rock.west.ora.com (8.6.11/8.6.11) with ESMTP id XAA28984 for <terry@rock.west.ora.com>; Wed, 10 Jan 1996 23:21:57 -0800
Received: from www19.w3.org (www19.w3.org [18.52.0.17]) by ruby.ora.com (8.6.12/8.6.11) with ESMTP id CAA19970 for <terry@ora.com>; Thu, 11 Jan 1996 02:21:55 -0500
Received: by www19.w3.org (8.6.12/8.6.12) id CAA16729; Thu, 11 Jan 1996 02:15:26 -0500
Resent-Date: Thu, 11 Jan 1996 02:15:26 -0500
Resent-Message-Id: <199601110715.CAA16729@www19.w3.org>
Message-Id: <m0taHAE-0002UbC@beach.w3.org>
To: preece@predator.urbana.mcd.mot.com (Scott E. Preece)
Cc: iburrell@loki.stanford.edu, www-html@w3.org
Subject: <resource> [was: Proposal for SIZE attribute ]
In-Reply-To: Your message of "Tue, 09 Jan 1996 08:06:13 CST."
             <199601091406.IAA18571@predator.urbana.mcd.mot.com> 
Date: Thu, 11 Jan 1996 02:11:10 -0500
From: "Daniel W. Connolly" <connolly@beach.w3.org>
content-length: 1569
Resent-From: www-html@w3.org
X-Mailing-List: <www-html@w3.org> archive/latest/2257
X-Loop: www-html@w3.org
Sender: www-html-request@w3.org
Resent-Sender: www-html-request@w3.org
Precedence: list

In message <199601091406.IAA18571@predator.urbana.mcd.mot.com>, Scott E. Preece
 writes:
>   From: iburrell@loki.stanford.edu (Ian Burrell)
>|
>|   I was thinking recently that a SIZE attribute that indicated the
>|   physical size in bytes of an included object would be a useful
>|   addition to HTML.
>---
>
>My mindset is sufficiently object-oriented that it really turns my
>stomach to have a referencing document specify things about the
>referenced resource.  Having said that, however, providing a way to give
>an expected-size hint bothers me a lot less than having the reference
>indicate the type of the referenced item...

We hashed this out in the office just a couple months ago, in
fact. The spec is still mostly in "back of the envelope" form, but you
can see the DTD and examples:


http://www.w3.org/pub/WWW/MarkUp/html-pubtext/resource.mod
http://www.w3.org/pub/WWW/MarkUp/html-test/resource/spec-examples


The basic idea is that a new element <resource> allows you
to say things of the form:

	The X attribute of R is Y
		as: <resource href=R> <meta name=X value=Y> ... </resource>

		A few attributes are institutionalized, and can be expressed as:

		<resource href=R X=Y X2=Y2 ...></resource>

and
	There is a link of type T from R to S.
		as: <resource href=R> <link rel=T href=S></resource>

e.g.

	The Content-Length of foo.gif is 234234
	The Content-Language of foo.html.fr is FR

	There is a PNG-format version of foo at foo.png.
	There is an PNG-format version of foo at foo.png.

	The TOC of chapter-1.html is toc.html.

Nifty, huh?

Dan



--- End of forwarded message from "Daniel W. Connolly" <connolly@beach.w3.org>


-- 
Terry Allen  (terry@songline.com), Online Books Editor, Songline Studios
               affiliated with O'Reilly & Associates, Inc.   
A Davenport Group sponsor.  See http://www.ora.com/davenport/README.html
                    Don't lose sight of the point:
 http://silicon.montaigne.u-bordeaux.fr:8001/HTML/EGYPTE/ROME/obelisk.html