Proposal for Phase 8: extending podcast:location #668
Replies: 5 comments 5 replies
-
|
Hi James Adding a location service to copy/paste the location is cool. All hosts etc could use it. However does this mean we are agreed on the syntax for the updated location tag to be a rel=subject or rel=origin not sure why origin and instead of recorded but ok. TrueFans would be happy to test this asap. Also we plan to add it to a map to visualise the podcasts. |
Beta Was this translation helpful? Give feedback.
-
|
Yeah, I'm not fond of But - if I travel to the Eiffel Tower and record an interview there, but my podcast is based in London, then I as the podcaster am still based in London, irrespective of where I happened to record the show. Does |
Beta Was this translation helpful? Give feedback.
-
|
When we were only working with podcasters then author was easy. But now we have musicians and thus we started to use the generic term creators to cover both podcasters and artists. |
Beta Was this translation helpful? Give feedback.
-
|
I've edited the proposal to use |
Beta Was this translation helpful? Give feedback.
-
|
I love everything about this. Thanks for doing this work @jamescridland and Daniel |
Beta Was this translation helpful? Give feedback.
-
|
Great potential of this idea. So I added the changes to a feed in case someone wants to play with it: @samsethi I agree with James, about a different icon for creator/subject (I would also add a tool-tip) PD: This could be useful: find places [1] , link to OSM with the tag info [2], |
Beta Was this translation helpful? Give feedback.
-
|
Thanks David and agree will look at how we can best show this in the UI. The Tooltip is an easy quick win. |
Beta Was this translation helpful? Give feedback.
-
|
For those wishing to test this, Podnews's RSS feed - https://podnews.net/rss - now has compliant location tags in both the |
Beta Was this translation helpful? Give feedback.
-
|
We have taken on board your fallback. And pushing that update today. We have implemented the new location tag as originally proposed by Daniel J Lewis and refined by James Cridland. Below are four recent episodes from Podnews Daily showing James' different recording locations. e.g https://truefans.fm/podnews-daily/671f5681d55de476b7cb4d4a If you click the location tag we show it on a map. Our next feature is to add multiple podcasts on a map so you can see podcasts nearby and filter by category. We have the Cridland feature. Where we show all the locations of a single podcaster on a map but we can only think James will be the person who records in multiple locations. 
|
Beta Was this translation helpful? Give feedback.
-
|
Do we have any objections to this? I don’t see why we would delay formalizing these changes. |
Beta Was this translation helpful? Give feedback.
-
There are a few use-cases that the existing
podcast:locationtag does not deal with, which I'd like to try to fix for the next phase.The majority of this is the work of Daniel J Lewis; I've extended it yet further (!)
The current tag
The current tag is a SINGLE tag and lives in (I think) either the CHANNEL or ITEM.
Use case: "I would like to discover podcasts made near me"
The podcast:location tag was initially only to describe what a podcast's subject was about, not where it was recorded.
We'll fix this by adding a
relattribute, explaining what the relationship is between the podcast/episode described and the location; and by allowing this tag to be used multiple times.rel="creator"is where the podcast was recorded.rel="subject"is what the podcast is about.relis a recommended value; in its absence the default value is "subject" to maintain compatibility. However, RSS authors are STRONGLY advised to add this value going forward.Example: a show that is RECORDED IN Austin, TX - about a themepark in Australia
Use case: "I would like a quick and simple method to find podcasts about/from my country"
The podcast:location tag already contains enough information to calculate a country - which can be calculated from the
geotag and/or the OSM tag.However, this is a lot of parsing work for the podcast directory or app; and it would seem to be pragmatic to do that work when entering the information and generating the RSS feed, rather than expect an app or client to parse geo/OSM for 4.3mn podcasts; and to avoid multiple clients hitting a geo-lookup or OSM API.
We'll fix this by adding a country code,
country, which will use the standard two-character country code - ALPHA-2 from ISO 3166.Ideally, this country code would be mandatory. The question is whether that would actually break anything, or given enough notice, we'd be able to get that done.
An example for a podcast made about The Eiffel Tower might read:
Use case: "My podcast is about both Dreamworld and the Eiffel Tower"
Sure! Now this tag can be used MULTIPLE times, that's all good.
Use case: "This is all too complicated, James, can't you make it simpler?"
We'll fix this by writing a simple JavaScript library for you to generate a
podcast:locationtag of your very own, just by typing the name of a place. This would be copy/pastable, and freely licensed for any podcast hosting company to use.Example feed
https://podnews.net/rss contains a default tag in the
channeland six overwritten tags in theitemtags, as of Oct 28.Thoughts?
Beta Was this translation helpful? Give feedback.
All reactions