W3C home > Mailing lists > Public > www-html-editor@w3.org > October to December 1999

Re: Inconsistency between IETF and W3C: XML fragments and media types

From: Dan Connolly <connolly@w3.org>
Date: Fri, 17 Dec 1999 21:55:18 -0600
Message-ID: <385B05A6.EF0F9BE8@w3.org>
To: Ian Jacobs <ij@w3.org>
CC: www-html-editor@w3.org
Ian Jacobs wrote:
> Dan, can you propose how to clear this up?

Er.. I thougt i did: change this:

> Dan Connolly wrote:
> > ========
> > http://www.w3.org/TR/1998/REC-html40-19980424/struct/links.html#adef-type-A
> >
> > type = content-type [CI]
> >     When present, this attribute specifies the content type of a piece
> > of
> >     content, for example, the result of dereferencing a URI. Content
> > types
> >     are defined in [MIMETYPES].
> > ========
> >
> > The same text occurs at
> > http://www.w3.org/TR/1999/PR-html40-19990824/struct/links.html#adef-type-A

to (something like) this:

> [snip]
> > My recollection is that type="..." is advisory: it helps user agents
> > optimize for the case that they don't know the relevant media type,
> > so they can skip fetching the thing. So it would be odd for it
> > to be mandatory. But sure enough! it is:

So... gluing it all together:

type = content-type [CI]
   the type attribute gives an advisory hint as to the Internet Media
   of the content available at the link target address. It allows
   user agents to opt to use a fallback mechanism rather
   than fetch the content if they are advised
   that they will get content in an Internet Media Type they do not

   Authors who use this attribute take responsibility to manage the risk
that it may
   become inconsistent with the content available at the link target

   [you could go into detail with an example, if you like.]

Dan Connolly
Received on Friday, 17 December 1999 22:55:28 UTC

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