W3C home > Mailing lists > Public > w3c-rdfcore-wg@w3.org > August 2002

Re: draft-reagle-xenc-mediatype-01.txt

From: Martin Duerst <duerst@w3.org>
Date: Tue, 20 Aug 2002 11:19:58 +0900
Message-Id: <>
To: me@aaronsw.com, w3c-rdfcore-wg@w3.org
Cc: <w3c-policy@apps.ietf.org>, <ietf-types@iana.org>, <ietf-xml-mime@imc.org>, reagle@w3.org, "Larry Masinter" <LMM@acm.org>, <ned.freed@mrochek.com>

Hello Aaron, dear RDF Core WG,

On ietf-types@iana.org and some related list, we were just looking
at http://www.w3.org/TR/xmlenc-core/#sec-MediaType which containes
some instances of text like this:

    Same as ... of application/xml as specified in RFC 3023[XML-MT]
    or the most recent specification that supercedes it.

There seemed to be general agreement that a moving target is
not a good idea.

Josef Reagle told us that he got that text from:

I wanted to tell you that you may want to fix this.

Regards,   Martin.

At 14:47 02/08/19 -0400, Joseph Reagle wrote:
>On Thursday 08 August 2002 06:07 pm, Larry Masinter wrote:
> > # Optional parameters: charset
> > #  Same as charset parameter of application/xml as
> > #  specified in RFC 3023 [XML-MT] or the most recent
> > #  specification that supersedes it.
> >
> > I admit I was a little confused on this one, and misread
> > what it said. However, I don't understand
> > "or the most recent specification that supersedes it",
> > though, since a specification may supercede RFC 3023
> > but not be appropriate for a reference to a particular
> > section.
>I'm happy to eliminate that text as I oppose those sort of references in
>general. In this case, I was merely following what I could see the rdf
>folks doing for a similar type of registration:
>   http://www.aaronsw.com/2002/rdf-mediatype.html
Received on Monday, 19 August 2002 23:30:54 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 14:53:59 UTC