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
A feed generated by Podlove Publisher exports contributors of an item using the atom:contributor element from RFC4287, currently only using the atom:name and atom:uri elements, where atom:uri is typically not filled in by users :-( .
For example, current state often looks like that:
<item>
<title>FG072 Verantwortung in der Informatik</title>
<link>https://forschergeist.de/podcast/fg072-verantwortung-in-der-informatik/</link>
<pubDate>Tue, 01 Oct 2019 09:00:44 +0000</pubDate>
<guidisPermaLink="false">podlove-2019-09-25t07:03:05+00:00-ae9b4afff088687</guid>
…
<atom:contributor>
<atom:name>Tim Pritlove</atom:name>
</atom:contributor>
<atom:contributor>
<atom:name>Peter Purgathofer</atom:name>
</atom:contributor>
</item>
In my option there should be an own document about that usage, optionally extending it with fields for the role of the contributor (host, guest etc.) other external IDs e.g. Twitter handle, Facebook ID, etc.
The Atom spec even allows that using the extensionElement, see definitions below:
atomContributor = element atom:contributor { atomPersonConstruct }
atomPersonConstruct =
atomCommonAttributes,
(element atom:name { text }
& element atom:uri { atomUri }?
& element atom:email { atomEmailAddress }?
& extensionElement*)
extensionElement =
simpleExtensionElement | structuredExtensionElemen
simpleExtensionElement =
element * - atom:* {
text
}
structuredExtensionElement =
element * - atom:* {
(attribute * { text }+,
(text|anyElement)*)
| (attribute * { text }*,
(text?, anyElement+, (text|anyElement)*))
}
Then the example above could be something like that:
A feed generated by Podlove Publisher exports contributors of an item using the
atom:contributor
element from RFC4287, currently only using theatom:name
andatom:uri
elements, whereatom:uri
is typically not filled in by users :-( .For example, current state often looks like that:
In my option there should be an own document about that usage, optionally extending it with fields for the role of the contributor (
host
,guest
etc.) other external IDs e.g. Twitter handle, Facebook ID, etc.The Atom spec even allows that using the
extensionElement
, see definitions below:Then the example above could be something like that:
Other specs also define contributors on the feed level (which is actually also allowed by the Atom, also compare https://blog.podchaser.com/rss-spec/v1/
The text was updated successfully, but these errors were encountered: