-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
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
Representative h-feed #8
Comments
dshanske This is an important question for consumers of h-feed. In my implementations, I have opted for the first feed because I have no way of ascertaining which feed is the one that I should be looking at if there are multiple. I have not seen too many pages with multiple h-feeds but I can see plenty of use cases, such as a home page with a h-feed of "newest content" and a h-feed of "most popular content". |
I wonder if a separate class should be used to determine the representative feed (i.e. "h-feed-representative") that is used in addition to h-feed. Or a separate "representative" keyword used in the same class as a "h-feed". But any solution that would not involve adding an additional class would likely be preferable. |
I don't think a class is consistent. We need something similar to the https://indieweb.org/authorship-spec |
If there are multiple h-feeds on a page, which h-feed should be considered to be the representative one for the url?
The text was updated successfully, but these errors were encountered: