Re: draft-freed-mime-p4-00.txt

On Wednesday, February 26, 2003, 8:42:20 PM, ned+xml-mime wrote:

> Joseph Reagle wrote:
>> On Wednesday 26 February 2003 12:54, Dan Kohn wrote:
>> > This looks very good.  It still might be useful to provide a little more
>> > of the information from
>> > <http://www.w3.org/2002/06/registering-mediatype> to give hints to other
>> > standards bodies about the ordering of their draft, to publishing an
>> > I-D, [snip]

>> For instance, it's not clear to me that we would still have to
>> generate even "stub" ietf-drafts once it is operational. I nope
>> that sending emails to the various lists with a reference to the
>> W3C document will be sufficient.

nxmmc> Actually, it should be quite clear that this will no longer be
nxmmc> necessary.

Great.

>>    3.2.8 Publication Requirements
>>    Other than IETF registrations in the standards tree, the registration
>>    of a data type does not imply endorsement, approval, or
>>    recommendation by the IANA or the IETF or even certification that the
>>    specification is adequate.

>> jmr: Could this be simplified by saying that, "presense in the standards
>> tree does not necessary imply endorsement by IANA or IETF." One should not
>> look at the tree for endorsement at all, but, at the specification's
>> level/maturity (draft, proposed draft, standard, Recommendation, etc.)
>> within their organization.

nxmmc> The IETF has this concept of recommending something in an RFC.
nxmmc> I think that's close enough to an endorsement that I don't want
nxmmc> to say the IETF never endorses anything.

This is well put. Equally, W3C has a concept of recommending something
and indeed our full standards track documents are called
Recommendations to emphasise this.

Perhaps Joseph is saying that an implied disclaimer of 'anything not
in the IETF tree may be inadequate' does not add anything and is
harmful, just as the W3C saying 'anything in the IETF tree is not a
W3C Rec and might not be any good' would be harmful.



-- 
 Chris                            mailto:[email protected]