We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
https://validator.w3.org/feed/docs/rss2.html specifies
managingEditor - Email address for person responsible for editorial content. webMaster - Email address for person responsible for technical issues relating to channel. author - Email address of the author of the item. ( https://validator.w3.org/feed/docs/rss2.html#ltauthorgtSubelementOfLtitemgt )
A list of valid formats for email addresses is included here https://validator.w3.org/feed/docs/error/InvalidContact.html
Therefore I'd say the examples should be changed, as well as the documentation of the fields so as to specify that you should enter an email address.
I learned this by using the w3org rss feed validator https://validator.w3.org/feed
Ah, this is also a more general version of #30
The text was updated successfully, but these errors were encountered:
fix for dylang#82
72123d9
No branches or pull requests
https://validator.w3.org/feed/docs/rss2.html specifies
managingEditor - Email address for person responsible for editorial content.
webMaster - Email address for person responsible for technical issues relating to channel.
author - Email address of the author of the item. ( https://validator.w3.org/feed/docs/rss2.html#ltauthorgtSubelementOfLtitemgt )
A list of valid formats for email addresses is included here https://validator.w3.org/feed/docs/error/InvalidContact.html
Therefore I'd say the examples should be changed, as well as the documentation of the fields so as to specify that you should enter an email address.
I learned this by using the w3org rss feed validator https://validator.w3.org/feed
Ah, this is also a more general version of #30
The text was updated successfully, but these errors were encountered: