Re: [Cellar] Conversation about a NON-IANA request in Matroska

[Michael Richardson <[e-mail]>]

Steve Lhomme <[e-mail]> wrote:
    > Given one of the goal on this Matroska specification is long time
    > preservation, that would seem odd to design something that renders
    > older systems incompatible with the current/new specifications. If any
    > of the MIME types we have in attachments were to become invalid all of
    > a sudden we wouldn't like it.

That's not what I suggested.

I suggested that every reader would always accept both values.

But that, at some date in the future, writers would start using the new
values.  I suggested that the date be decided now in order to:
  a) establish a deadline for readers to get updated.
  b) allow writing software to gracefully transition without having to be updated.
  (of course, such software could also have an option)

We assume that the files are forever, but that the software that reads them
will get updated now and then.

In reality, the mime type doesn't really go anywhere specific unless the file
is being transfered over email or http.  On MAC, with HFS, the MIME type
might lookup a resource type which gets associated with the file.

But I suspect that one can associate two things with one resource, and I also
suspect (having really never coded for MacOS) that it doesn't take mime types
as input anyway.

--
]               Never tell me the odds!                 | ipv6 mesh networks [
]   Michael Richardson, Sandelman Software Works        |    IoT architect   [
]     [e-mail]  http://www.sandelman.ca/        |   ruby on rails    [