Skip to content
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

Do Not Restrict H-Feed to Only Contain H-Entry #3

Open
dshanske opened this issue Sep 12, 2020 · 6 comments
Open

Do Not Restrict H-Feed to Only Contain H-Entry #3

dshanske opened this issue Sep 12, 2020 · 6 comments

Comments

@dshanske
Copy link
Member

microformats/h-entry#16

This should actually be an h-feed issue, not an h-entry issue.

@dshanske
Copy link
Member Author

Thoughts...

  • An h-feed of h-cards could be a contact, follow venue list?
  • An h-feed of h-events could be an upcoming or past events list

@btrem
Copy link

btrem commented Feb 21, 2021

I'm thinking about an opening-hours microformat. Jacky (last name?) suggested a feed of h-events. I think a new h-feed property called p-feed-type or p-children-type or something like would be useful. Authors could create a feed of h-events or h-cards as @dshanske suggested. And new event type h-opening-hours could be a special type of event. When an h-feed is a collection of h-opening-hours, it's the operating hours of a business.

@barnabywalters
Copy link

barnabywalters commented May 26, 2021

Thinking about this from a user’s perspective: an h-feed represents something which could meaningfully be subscribed to, and/or presented in a feed reader. By default this includes anything with name, content and published properties. The presence of an author, either at the feed or child level is also usually implied. Additionally, I can imagine a few other useful cases which fit into the same concept.

  • an h-feed containing h-entries makes sense as a feed of posts you could subscribe to in a feed reader
  • an h-feed containing h-events makes sense as a feed of events you could subscribe to in a calendar
  • an h-feed of h-cards could potentially represent a chronologically ordered list of people. In this case, I’m not so convinced that an h-feed makes more sense than just having a bunch of h-cards on a page, except that wrapping them in an h-feed allows you to name it and assign an author to it. I had a few ideas about how to use things like this in the past, e.g. as a modern blogroll.

@capjamesg
Copy link
Member

@barnabywalters I agree. I could see myself doing this for a feed of h-reviews and even h-recipes (for subscribing to the ways in which I brew coffee at home). A feed of h-cards could be used as an extended blog roll, potentially, or for similar use cases wherein one links to multiple other personal sites.

@capjamesg
Copy link
Member

One could take this even further and create a h-feed for a trip using h-geo markup. I am only starting to support h-geo on my blog but I could see a use for a feed that shows, say, all of the h-geo checkins I have for a trip that I have taken.

@calebhearth
Copy link

I'm using h-feed to contain a heterogenous collection of h-entry and h-cite on https://calebhearth.com/now and my comments (web mentions) sections on various pages including https://calebhearth.com/this-gem-is-mentionable are h-feeds of h-cite.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants