ietf-wg-cellar / matroska-specification

Matroska specification.
http://ietf-wg-cellar.github.io/matroska-specification
Other
123 stars 45 forks source link

Update Tagging Identifiers documentation #570

Closed manuelrn closed 2 years ago

manuelrn commented 3 years ago

Hello,

The Tagging Identifiers documentation specifies the following:

In TMDB it is necessary to specify whether the content is series or movie because TMDB contains both content. And there are contents of both types that share the same identifier, so it is necessary to specify what type of content it is.

In TVDB it was not necessary to specify since it only contained series, but a while ago that changed. Now movies are also supported, so now it behaves exactly the same as TMDB does, now it is necessary to specify what type of content it is (because there are contents of both types that share the same identifier).

In TMDB the content type is specified like this:

But in TVDB, what would it be like? Same as TMDB ("movie/" and "tv/")? Or "movies/" and "series/"?

I think the second option is more appropriate. I comment this because the TMDB API is used with /movie/{movie_id} and /tv/{tv_id}, but the TVDB API is used with /movies/{id} and /series/{id}.

Thanks and regards!

robUx4 commented 3 years ago

We have to keep backward compatibility. So TVDB with just an ID must be considered as a TV show. We should add movie/ID to the same tag, but tools parsing TVDB will not understand this value and, worse, interpret it incorrectly as an ID.

So to preserve a safe backward compatibility, there should be a new tag name like TVDB2 that would work like TMBD. The TVDB being the legacy version.

manuelrn commented 3 years ago

Agree @robUx4, that's perfect.

So, as I understand it, it would be like this:

For movies:

For series:

Could you confirm if this is correct?

Thanks again!

robUx4 commented 3 years ago

That's correct. TVDB is only for series, TVDB2 can be used for both and needs a prefix (that looks like the API).

manuelrn commented 3 years ago

Okay, thanks again @robUx4!