Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

TAG Feedback: of all the potential metadata...? #191

Closed
travisleithead opened this issue Mar 20, 2017 · 4 comments

Comments

@travisleithead
Copy link
Member

commented Mar 20, 2017

[Filed in response to the request for TAG feedback]

@xxyzzzq @mounirlamouri

There's lots of potential metadata to include, how/why did you pick this particular subset? e.g., why not genre, year, etc.? (Not sure if you saw this 2014 Recommendation "Metadata API for Media Resources 1.0"? http://www.w3.org/TR/2014/REC-mediaont-api-1.0-20140313/. It's part of the Semantic-web line of documents, but does have some specific metadata fields that might be thoughtfully considered.)

@xxyzzzq

This comment has been minimized.

Copy link
Collaborator

commented Mar 24, 2017

Other fields are supported by platforms such as Android and iOS and the MediaMetadata interface should be flexible to include them.

The reason why we only include title, artist and album is that the are the most common properties. We are prioritizing mobile platforms at the moment. Other fields such as year and genre are rarely shown as mobile platforms usually have limited space.

@xxyzzzq

This comment has been minimized.

Copy link
Collaborator

commented Mar 24, 2017

Regarding "Metadata API for Media Resources 1.0", is it implemented by any major browser vendor? If it is implemented someday and we want to make the Media Session API with the Metadata API, we could use an adaptor to accept the metadata from the Metadata API.

@beccahughes

This comment has been minimized.

Copy link
Collaborator

commented Jul 29, 2019

Since there hasn't been any discussion on this issue for a couple of years I am going to close it, but feel free to re-open if necessary.

@chrisn

This comment has been minimized.

Copy link
Member

commented Sep 20, 2019

I'd like to re-open this, to note that the current artist, title, album fields are music track specific, and aren't necessarily a good fit for certain kinds of content, such as podcasts or TV or radio programmes.

Is the purpose of these fields mainly for display, in which case we may want to prefer display oriented fields, such as primary title, secondary title, etc? Or do platforms want to add features that make use of the data more semantically, so that knowing the artist name, radio station name, TV series name, etc, is necessary?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
4 participants
You can’t perform that action at this time.