bhessert
commented
7 years ago Hi Gabriel, Good point! Give me a call if you want to touch base. Bill 5748506621
On Sunday, October 22, 2017, Gerzer notifications@github.com wrote:
I think that there should be some required taxonomies. For example, all podcast feeds should be required to specify a level of "explicit-ness" from a preset list of tags. I understand the push to give publishers as much freedom as possible, but in a handful of scenarios, I think that the JSON spec itself should guarantee client applications the ability to filter by, say, "explicit-ness". Otherwise, it would be hard for a user to be sure that they're only looking at SFW (or whatever the case) podcasts. For the most part, I agree, publishers should be able to choose whatever taxonomies they want, but some taxonomy categories should be required.
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/DotPodcast/dotpodcast/issues/1, or mute the thread https://github.com/notifications/unsubscribe-auth/ARLez75w-HUuARJobMZucd3qDOv3LAz-ks5suzBagaJpZM4QB7LX .
hellosteadman
I think that there should be some required taxonomies. For example, all podcast feeds should be required to specify a level of "explicit-ness" from a preset list of tags. I understand the push to give publishers as much freedom as possible, but in a handful of scenarios, I think that the JSON spec itself should guarantee client applications the ability to filter by, say, "explicit-ness". Otherwise, it would be hard for a user to be sure that they're only looking at SFW (or whatever the case) podcasts. For the most part, I agree, publishers should be able to choose whatever taxonomies they want, but some taxonomy categories should be required.