Re: Comments on draft-ietf-msgtrk-mtqp-03.txt
[email protected] Fri, 10 Aug 2001 01:54:18 -0700 (PDT)
| Newsgroups | gmane.ietf.msgtrk |
|---|---|
| Message-ID | <[email protected]> |
> : From: [email protected] > : > The way MIME content-types are done, vendor company prefixes are > : > registered: > : > : > Registrations in the vendor tree will be distinguished by the leading > : > facet "vnd.". That may be followed, at the discretion of the > : > registration, by either a media type name from a well-known producer > : > (e.g., "vnd.mudpie") or by an IANA-approved designation of the > : > producer's name which is then followed by a media type or product > : > designation (e.g., vnd.bigcompany.funnypictures). > : > : Note, however, that this registers vnd.bigcompany.funnypictures, not > : vnd.bigcompany or bigcompany. So it isn't strictly correct to say that company > : prefixes are registered. > Ned, I read this differently -- "IANA-approved designation" modifies > "producer's name" -- which is "then followed" by a non-IANA-approved > media type or product designation. Am I totally off? IMO yes you are. You're equating designation with registration. The designations implied by the various facets are checked as part of the process, but only the entire media type is registered. And FWIW, my recollection of the design of this scheme doesn't agree with Tony's. I don't believe vendor or product registrations were ever considered as part of this process. And given recent history in the domain name space as well the recent image/tiff flap in the FAX WG (where a not-insigificant component is perceived ownership of a media type name), had IANA actually elected to implement such a registry I believe we would have a hell of a mess on our hands by now. Ned