recently-in-microformats: Difference between revisions

Latest revision as of 16:31, 18 July 2020

Recently in microformats is a place to collaboratively draft blog posts about what's recently going on with microformats. Feel free to write things in any of the sections below, and ping an admin on IRC when you'd like your writing reviewed and posted to the blog.

Recently in microformats

In the past several months there has been a considerable increase in activity in, with, and around microformats. From continued growth of stalwarts like hCard and rel-me, to emergence of federated indieweb comments based on the microformats2 h-entry and h-card. Search engines are crawling more microformats than ever, most recently hAtom and hMedia. Lastly, informal microformats meetups, as well as sessions and presentations at conferences, continue at a good monthly pace.

New implementations

New real world publishing and uses of microformats emerge every week. Here are a few examples that are enabling and enhancing key features on the web.

new rel me support

Both App.net and Svbtle now support rel-me for user profiles linking to their home pages.

https://twitter.com/microformats/status/328992420463271936

App.net in particular implemented their Domain Claiming feature based on rel-me linking from your personal site to your app.net profile (and entering your personal site in your app.net profile).

Thus the list of OAuth providers available to authenticate for web sign-in backends continues to grow. The IndieAuth library and service that implements RelMeAuth has already added support for App.net as a RelMeAuth authentication provider.

Storytlr using microformats2 for indieweb comments

The Storytlr open source blogging tool now consumes microformats2, in particular h-entry and h-card to display comments made from indieweb blog to another.

Taproot and p3k reply contexts

The Taproot and p3k blogging tools are also consuming h-entry and h-card to display original post context when publishing replies.

Google is parsing hMedia

As of somewhere in the end of 2012 or early 2013, Google has began parsing hMedia.

While not officially supporting hMedia like they do in the rich snippet support page for hCard, hReview, hCalendar (event too)& hRecipe, Google surprisingly has began to show the hMedia in the webmaster tools result.

Does Google really support hMedia?

Officially - I could not find anything related to think that Google actually support it or can read it, even when searching "Google hMedia" I could not find anything related to the fact that Google supporting hMedia.

The main focus I will take is for the hMedia is the image deceleration, because as so far it is the only type within the hMedia schema that I could say that Google supports.

Google! where is my hMedia?

The first thing many people do to find out if they have coded their web page properly with the Microformats, is entering Google Rich Snippet Tool and check their page to see if Google is parsing it correctly.

The first time I have used the hMedia schema, I could not find anything that could say that Google parses my hMedia.

Example: lets parse this page: http://goo.gl/CZQFu And we will get:

By this Google gives us the impression that it does not parse hMedia.

hMedia! There you are

I have personally used this hMedia image tagging since the 2012, and Google webmaster tools hasn`t shown me any information about reading the hMedia, somewhere near the start of year 2013, I have found Google has began parsing almost all of the hMedia photos I have tagged.

Please share your thoughts regarding the parsing of hMedia, and your opinions about what hMedia should include in Microformats2, and if you have found any other type of hMedia schema`s that Google parses.

Thanks to Aviran Zazon for investigating, screenshotting, and writing up his research on Google's hMedia support. Content has been reformatted for this blog post.

In articles and other web sites

...

Face-to-Face

New microformats and rel values

rel-in-reply-to
rel-syndication
rsvp
sheet-music is being developed
...

Interesting wiki updates

New Georgian wiki translation started!

From Twitter

...

Interesting Discussions on IRC and mailing lists

...

Past

Early on we did "This week in microformats" when there were weekly changes and discussions. See here for examples of that. These early posts are excellent examples, e.g. for guidance on formatting:

@@ Line 1: / Line 1: @@
-<entry-title>Recently in microformats</entry-title>
+{{DISPLAYTITLE:Recently in microformats}}
 '''<dfn>Recently in microformats</dfn>''' is a place to collaboratively draft blog posts about what's recently going on with microformats. Feel free to write things in any of the sections below, and ping an [[admin]] on [[IRC]] when you'd like your writing reviewed and posted to the [http://microformats.org blog].
 == Recently in microformats ==
+In the past several months there has been a considerable increase in activity in, with, and around microformats. From continued growth of stalwarts like [[hCard]] and [[rel-me]], to emergence of federated indieweb comments based on the [[microformats2]] [[h-entry]] and [[h-card]]. Search engines are crawling more microformats than ever, most recently [[hAtom]] and [[hMedia]]. Lastly, informal microformats meetups, as well as sessions and presentations at conferences, continue at a good monthly pace.
 === New implementations ===
-* [[Google is parsing hMedia]]. Webmaster dashboard.
+New real world publishing and uses of microformats emerge every week.  Here are a few examples that are enabling and enhancing key features on the web.
-* ...
+==== new rel me support ====
+Both [https://app.net App.net] and [https://svbtle.com Svbtle] now support [[rel-me]] for user profiles linking to their home pages.
+https://twitter.com/microformats/status/328992420463271936
+App.net in particular implemented their Domain Claiming feature based on rel-me linking from your personal site to your app.net profile (and entering your personal site in your app.net profile).
+Thus the list of OAuth providers available to authenticate for [[web sign-in]] backends continues to grow. The [[IndieAuth]] library and service that implements [[RelMeAuth]] has already added support for App.net as a RelMeAuth authentication provider.
+==== Storytlr using microformats2 for indieweb comments ====
+The [http://indiewebcamp.com/Storytlr Storytlr] open source blogging tool now consumes [[microformats2]], in particular [[h-entry]] and [[h-card]] to [http://indiewebcamp.com/comment#Display_received_comments display comments] made from indieweb blog to [http://eschnou.com/entry/testing-indieweb-federation-with-waterpigscouk-aaronpareckicom-and--62-24908.html another].
+==== Taproot and p3k reply contexts ====
+The [http://indiewebcamp.com/Taproot Taproot] and [http://indiewebcamp.com/p3k p3k] blogging tools are also consuming [[h-entry]] and [[h-card]] to display original post context when publishing replies.
+==== Google is parsing hMedia ====
+As of somewhere in the end of 2012 or early 2013, Google has began parsing hMedia.
+While not officially supporting hMedia like they do in the [http://support.google.com/webmasters/bin/answer.py?hl=en&answer=99170 rich snippet support page] for [[hCard]], [[hReview]], [[hCalendar]] (event too)& [[hRecipe]], Google surprisingly has began to show the [[hMedia]] in the webmaster tools result.
+===== Does Google really support [[hMedia]]? =====
+Officially - I could not find anything related to think that Google actually support it or can read it, even when searching "Google hMedia" I could not find anything related to the fact that Google supporting [[hMedia]].
+The main focus I will take is for the [[hMedia]] is the image deceleration, because as so far it is the only type within the [[hMedia]] schema that I could say that Google supports.
+===== Google! where is my hMedia? =====
+The first thing many people do to find out if they have coded their web page properly with the [[Microformats]], is entering [http://www.google.com/webmasters/tools/richsnippets Google Rich Snippet Tool] and check their page to see if Google is parsing it correctly.
+The first time I have used the [[hMedia]] schema, I could not find anything that could say that Google parses my [[hMedia]].
+Example: lets parse this page: [http://goo.gl/CZQFu http://goo.gl/CZQFu] And we will get:
+[http://i.imgur.com/FCRm58s.png http://i.imgur.com/FCRm58s.png]
+By this Google gives us the impression that it does not parse [[hMedia]].
+===== hMedia! There you are =====
+I have personally used this [[hMedia]] image tagging since the 2012, and Google webmaster tools hasn`t shown me any information about reading the hMedia, somewhere near the start of year 2013, I have found Google has began parsing almost all of the [[hMedia]] photos I have tagged.
+[http://i.imgur.com/LcDYDSz.png http://i.imgur.com/LcDYDSz.png]
+'''Please share your thoughts regarding the parsing of [[hMedia]], and your opinions about what [[hMedia]] should include in [[Microformats2]], and if you have found any other type of [[hMedia]] schema`s that Google parses. '''
+Thanks to [[User:ISRAELi|Aviran Zazon]] for investigating, screenshotting, and writing up his research on Google's hMedia support. Content has been reformatted for this blog post.
 === In articles and other web sites ===
@@ Line 16: / Line 58: @@
 * [[events/2013-03-01-microformats-dinner]]
 * [[events/2013-04-02-html5devconf-microformats2-html5]]
+** video: http://www.youtube.com/watch?v=BNk-Bkc-CAo
+* [[events/2013-04-02-microformats-dinner]]
+* [[events/2013-04-08-sensored-meetup]]
+* [[events/2013-05-14-microformats-google-io]]
 * ...
 === New microformats and rel values ===
+* [[rel-in-reply-to]]
+* [[rel-syndication]]
+* [[rsvp]]
+* [[sheet-music]] is being developed
 * ...
 === Interesting wiki updates ===
-* ...
+* New [[Main_Page-ka|Georgian]] wiki translation started!
 === From Twitter ===

recently-in-microformats: Difference between revisions

Latest revision as of 16:31, 18 July 2020

Contents