<resource> element and resource 'aliases'

After stumbling across the 'scribbled notes' on the <resource> 
element at the W3C site, I realized my alias suggestion send a few 
days ago would combine well with it.  Something like the following:

  <resource name="Logo">
    <link type="image/gif" href="logo.gif">
    <link type="images/png" href="logo.png" preferred>
  </resource>

  ...

  <img src="logo.gif" resource-src=#Logo>

Note the resource-src attribute vs. the src attribute.  This is so 
newer User Agents will use the alias while older agents will revert 
to the GIF version of the logo.

Note also the 'preferred' attribute: the author prefers the UA use 
this resource over others listed. The UA is not obligated to choose 
the preferred esource, of course.

The resources can be included in a shared file (for the site) using
the <link> attribute:

  <link rel=resource href="site.res">

Rationale:
(1) site maintenance: aliases or logical names can be used to link
resources, independent of file names on the site. (Whether User 
Agents will show only the resource name and/or the actual URL of the 
resource is not specified here)
(1a) allows external sites beyond the maintainer's control to link to 
resources that might otherwise have been moved
(2) allows choices of available resources based on Agent's
abilities, medium, etc. to be made by the agent.

Regards,
Rob


On 17 Apr 97 at 0:41, Robert Rothenburg Walking-Owl wrote
  Re: Hypertext Links in HTML:

> Attached is a post from the www-html list.
> 
> It would be a good thing to expand the use of <link> relationships
> or somehow associate id/name attributes in links with their own
> URLs.
> 
> Two uses of this:
> 
> (1) When other sites (beyond the maintainer's control) maintain
> links to areas with a document that have expanded enough to merit
> their own pages, it would be useful to have a way of redirecting
> these old links.
> 
> For instance, a there is link from another site to document
> foo.html#bar however the section at id=bar/name=bar has expanded to
> merit it's own file (bar.html).  It would be convenient to specify a
> URL that the id signifies, say (in the head element)
> 
>   <link name=bar href="bar.html">
> 
> or perhaps in the document (for older browsers)
> 
>   <a name=bar refer-href="bar.html">bar</a>
>   <p>This section has been moved to <a
>   href="bar.htm">bar.html</a></p>
> 
> (2) This would also allow one to maintain 'logical' names for links
> (aliases) for an entire site. When pages are moved or reorganized,
> only the initial definition in the documents needs to be changed. Or
> (better yet) an index of aliases can be kept in a separate file
> shared on a site, referenced by <link rel=aliases
> href="aliases.html"> or something equivalent.
> 
> For example,
> 
>   <link name=Appendix href="notes/Appendix.html">
>   <link name=Notes href="notes/Notes.html">
>   <link name=Table-of-Contents href="/toc.html">
> 
> This would also help maintenance in situations where there are
> multiple links within a document to one site.
> 
> A common example when pages contain icon-links and text links in a
> menu at the bottom (and/or top) of the page:
> 
>   <link name=Purchase href="purchase-form-1.html">
> 
>   ..
> 
>   <a href=#Purchase><img src="purchase-icon.gif"></a>
>   ..
>   <a href=#Purchase>[Purchase]</a>
> 
> 
> 
> --Rob Rothenburg (wlkngowl@unix.asb.com) or (mutradio@wusb.org)
>

Received on Saturday, 19 April 1997 17:09:55 UTC