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

HTML views should support microformats #84

Closed
bekopharm opened this issue Mar 13, 2020 · 20 comments
Closed

HTML views should support microformats #84

bekopharm opened this issue Mar 13, 2020 · 20 comments
Labels
good first issue Good for newcomers

Comments

@bekopharm
Copy link

Consider adding microformats to HTML views.

@jalcine
Copy link

jalcine commented Apr 16, 2020

Seconded! Using Microformats will:

  • make it easy for most Web tools to both present and parse
  • keep it extensible with a battle-tested format
  • make it friendly to presenting in the poster's preferred way without having to create alternative formats to show the same thing.

@mouse-reeve
Copy link
Member

thank you both for the suggestion! @jalcine can you clarify your third point? I'm not sure I understand that use case.

@jalcine
Copy link

jalcine commented Apr 17, 2020

With a Microformats parser, you can define something in HTML (mostly) anyway you'd want but still get useful structured information (similar to how one would parse JSON).

An example is my own personal site!

https://jacky.wtf to https://ruby.microformats.io/microformats?utf8=%E2%9C%93&url=https%3A%2F%2Fjacky.wtf

@jalcine
Copy link

jalcine commented Apr 17, 2020

I'd be happy to brainstorm some ideas on how to define the static pages of fedireads with microformats with you!

@mouse-reeve
Copy link
Member

mouse-reeve commented Apr 17, 2020

I see, that example is super helpful, thank you! I took a look a while back and as I recall it seems like there are a lot of natural fits around serializing book data, so brainstorming would be greatly appreciated

@bekopharm
Copy link
Author

Mayhap I should have mentioned https://microformats.io/ too. It's probably a better example to get the idea.

@mouse-reeve mouse-reeve added the good first issue Good for newcomers label Aug 18, 2020
@mouse-reeve mouse-reeve mentioned this issue Sep 30, 2020
8 tasks
@arkhi
Copy link
Contributor

arkhi commented Apr 9, 2021

There are existing definitions for structured data for books. Same goes for Rating, Person, etc.

I can work on implementing this in the book template unless anybody has any objection. :)

@arkhi
Copy link
Contributor

arkhi commented Apr 9, 2021

A useful browser addon to have is http://osds.openlinksw.com/.

@arkhi
Copy link
Contributor

arkhi commented Apr 9, 2021

An interesting problem is with the publisher property which needs to be either an Organization or a Person.

@mouse-reeve
Copy link
Member

This would just be the publishers field that already exists in the book data, right?

@arkhi
Copy link
Contributor

arkhi commented Apr 9, 2021 via email

@mouse-reeve
Copy link
Member

There's no additional metadata on that, I think it's safe to treat it as an organization.

@arkhi
Copy link
Contributor

arkhi commented Apr 9, 2021

Same thing goes with author which can more easily be one of both, I guess. :)

@arkhi
Copy link
Contributor

arkhi commented Apr 9, 2021

Another potential issue might be the bookformat property is limited to a list of values whereas the book edition is free text.

arkhi added a commit to arkhi/bookwyrm that referenced this issue Apr 9, 2021
@bekopharm
Copy link
Author

Schema is not microformats. You're mixing microdata and microformats hijacking this feature request.

Similar subject, different concept.

@arkhi
Copy link
Contributor

arkhi commented Apr 12, 2021

Hello @bekopharm… I agree microdata is not the same as microformats.

I’m sorry that you felt I hijacked the current issue. The issue being stalled for almost a year, I didn’t feel like interrupting anyone’s conversation.

The issue does not specify why microformats should be implemented and I assumed it was to provide structured data to BookWyrm, which the microdata definitions present on schema.org allow to implement more precisely than microformats to my knowledge. Let me know if there are adverse consequences to the work I’ve done.

That’s on me; I can create a new issue and refrain from mentioning this Issue in the Future.

@bekopharm
Copy link
Author

There are various use cases outlined above 🤷

I mean thanks for contributing I guess. That's always good. It's just a different thing.

@mouse-reeve
Copy link
Member

@bekopharm This is not an acceptable way to talk to people here. If you have concerns or differences of opinion about work on this project, you need to raise them with courtesy and consideration of others; there's absolutely no call to respond rudely.

@bekopharm
Copy link
Author

Wow. I'm really bewildered by your reply @mouse-reeve and a… rage close? So I asked a native speaker what might be the issue and was pointed out that "hijacking" may be the wrong wording implying terrorism when merely derailing was meant.

If it's just that I ask for forgiveness and blame the language barrier. There was no offence intended.

Otherwise I have seriously no idea what tripped you off :(

@arkhi arkhi mentioned this issue Apr 13, 2021
23 tasks
@mouse-reeve
Copy link
Member

I'm really glad to hear that the tone was unintentional! It's important to me that folks know that their contributions are valued, and that we don't diminish each other's efforts.

The ticket wasn't rage closed, I'm trying to keep on top of issues and have been closing and re-thinking many that are over a year old and haven't had much action, since the project has progressed a lot since then.

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

No branches or pull requests

4 participants