Re: FW: I-D ACTION:draft-hoschka-smil-media-type-05.txt
Philipp Hoschka <ph@w3.org> Mon, 23 October 2000 15:50 UTC
Received: by ns.secondary.com (8.9.3/8.9.3) id IAA15260 for ietf-xml-mime-bks; Mon, 23 Oct 2000 08:50:12 -0700 (PDT)
Received: from sophia.inria.fr (root@sophia.inria.fr [138.96.32.20]) by ns.secondary.com (8.9.3/8.9.3) with ESMTP id IAA15255 for <ietf-xml-mime@imc.org>; Mon, 23 Oct 2000 08:50:09 -0700 (PDT)
Received: from w3.org by sophia.inria.fr (8.10.0/8.10.0) with ESMTP id e9NFtMb15661; Mon, 23 Oct 2000 17:55:24 +0200 (MET DST)
X-Authentication-Warning: sophia.inria.fr: Host w3cdhcp15.w3.org [18.29.0.245] claimed to be w3.org
Message-ID: <39F45ED5.26317158@w3.org>
Date: Mon, 23 Oct 2000 17:52:53 +0200
From: Philipp Hoschka <ph@w3.org>
X-Mailer: Mozilla 4.7 [fr] (Win98; I)
X-Accept-Language: fr
MIME-Version: 1.0
To: Dan Kohn <dan@dankohn.com>
CC: ietf-xml-mime@imc.org
Subject: Re: FW: I-D ACTION:draft-hoschka-smil-media-type-05.txt
References: <25D0C66E6D25D311B2AC0008C7913EE00105A0F4@tdmail2.teledesic.com>
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 8bit
Sender: owner-ietf-xml-mime@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-xml-mime/mail-archive/>
List-ID: <ietf-xml-mime.imc.org>
List-Unsubscribe: <mailto:ietf-xml-mime-request@imc.org?body=unsubscribe>
Dan Kohn a écrit : > > I would strongly suggest an include by reference, as implementation > experience will likely cause further updates to 2376bis at some point. As > an example, you are actually quoting text from RFC 2376, not 2376bis Citing RFC2376 seems correct, given that RFC 2376 is a stable spec, wheras the current internet draft (which you refer to as 2376bis) is not, and has been in the making for quite a while now. Given what you write below, it looks like this has changed recently. Do you have a pointer to the decision record ? Do you know the RFC number ? Do you know when it will be published ? As I said, I am will consider removing the "reference by copy", once I found out if anybody actually requested reference by copy, and why. However, I disagree with your argument that an advantage of citing by reference is that it allows easier updates - the reference will be to a stable document, and if that document is replaced by a new document, that doesn't mean that the registration for application/smil changes as well. Propagating the changes would require an update of the application/smil document. ... > If people are not willing to look up a referenced RFC, than they probably > won't bother reading the MIME registration RFC in the first place. As I said, I think there is practical evidence to the contrary. > Also, as specified in Section 7.1 of <http://www.imc.org/draft-murata-xml>, > we would recommend referring to 2376bis for "specifying magic numbers, > fragment identifiers, base URIs, and use of the BOM". If you decide not to > do so (e.g., because of non-XPointer fragment semantics), The fragment semantics of application/smil are compatible with XPointer, as far as I can tell. >it would be worth > specifying that explicitly in your registration.
- Re: FW: I-D ACTION:draft-hoschka-smil-media-type-… muraw3c
- RE: FW: I-D ACTION:draft-hoschka-smil-media-type-… Dan Kohn
- Re: FW: I-D ACTION:draft-hoschka-smil-media-type-… Philipp Hoschka
- RE: FW: I-D ACTION:draft-hoschka-smil-media-type-… Dan Kohn
- Re: FW: I-D ACTION:draft-hoschka-smil-media-type-… Philipp Hoschka
- Re: FW: I-D ACTION:draft-hoschka-smil-media-type-… Philipp Hoschka
- Re: FW: I-D ACTION:draft-hoschka-smil-media-type-… muraw3c
- FW: I-D ACTION:draft-hoschka-smil-media-type-05.t… Dan Kohn