You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Do not be scared by XML terminology gibberish, this element set is really simple and relatively broadly defined, so that it can be used for any type of metadata.
The text was updated successfully, but these errors were encountered:
That's an interesting idea... I just like to avoid adding yet another possibility for defining the same information (title, author, etc), but I'll see how this will fit into the overall concept.
Do you know any podcasting application that already interprets Dubline Core meta data?
I have not investigated that. I wanted to make sure, that in a discussion about metadata the already standardized framework is mentioned.
I know Dublin Core from the use in libraries (as in books). It is used as fallback metadata format (sometimes DC is the only data format servers can agree on) for automatic exchange of information. You can find websites, that put metadata in header of each HTML page in Dublin Core.
DC is most probably not the solution to the problem you want to solve, but it can certainly lead the way.
If we interpret podcast RSS feeds as metadata for podcasts, then we should stick to some standards, which have already been defined.
Here is RFC from IETF covering Dublin Core
https://www.ietf.org/rfc/rfc5013.txt
For more information see http://dublincore.org/metadata-basics/
and documents/standards linked there.
Do not be scared by XML terminology gibberish, this element set is really simple and relatively broadly defined, so that it can be used for any type of metadata.
The text was updated successfully, but these errors were encountered: