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.

Sign up for GitHub

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

Jump to bottom

Allow h-entry as well as/instead of Schema.org CreativeWork #486

Closed
adactio opened this issue Oct 7, 2015 · 3 comments
Closed

Allow h-entry as well as/instead of Schema.org CreativeWork #486

adactio opened this issue Oct 7, 2015 · 3 comments

Comments

@adactio
Copy link

adactio commented Oct 7, 2015

The h-entry microformat covers all the same use cases as schema.org/CreativeWork and is already in place on many sites. I think it would ease adoption to allow these classes to be used instead of (or as well as) the microdata metadata.

It should be fairly straightforward to map h-entry class names to CreativeWork item properties. I'm happy to help out with that mapping (and I'm sure many others in the microformats/indieweb community would be happy to help out too).

Cheers,

Jeremy
@aaronpk
Copy link
Contributor

aaronpk commented Oct 8, 2015

I submitted a pull request to add h-entry as an example: #499
@veganstraightedge
Copy link

👍
@cramforce
Copy link
Member

As discussed in #499 we will only have a single metadata example with "commonly used metadata" whatever that is.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
5 participants
@veganstraightedge @adactio @cramforce @aaronpk @erwinmombay