5.00 score from hupso.pl for:
microformats.org



HTML Content


Titlemicroformats

Length: 14, Words: 1
Description pusty

Length: 0, Words: 0
Keywords pusty
Robots
Charset UTF-8
Og Meta - Title pusty
Og Meta - Description pusty
Og Meta - Site name pusty
Tytuł powinien zawierać pomiędzy 10 a 70 znaków (ze spacjami), a mniej niż 12 słów w długości.
Meta opis powinien zawierać pomiędzy 50 a 160 znaków (łącznie ze spacjami), a mniej niż 24 słów w długości.
Kodowanie znaków powinny być określone , UTF-8 jest chyba najlepszy zestaw znaków, aby przejść z powodu UTF-8 jest bardziej międzynarodowy kodowaniem.
Otwarte obiekty wykresu powinny być obecne w stronie internetowej (więcej informacji na temat protokołu OpenGraph: http://ogp.me/)

SEO Content

Words/Characters 5923
Text/HTML 63.57 %
Headings H1 1
H2 15
H3 18
H4 5
H5 0
H6 0
H1
H2
latest microformats news
10,000s of microformats2 sites and now 10 microformats2 parsers
microformats2 parsing spec updates
more microformats2 parsers
still simpler, easier, and smaller after all these years
evolving h-entry
how we improve moving forward
community changes
upgrading to microformats2
10th year goal
incremental steps
implied properties
prefixed classnames
combining microformats
further reading
H3
microformats.org at 11
microformats.org turns 9 — upgrade to microformats2 and more
upgrading microformats.org
upgrade sites
upgrade tools
getting started with microformats2
microformats.org at 7
humans first: admin emeriti & new admins
challenges & opportunities
microformats ~70% structured data domains
why microformats
latest in microformats
google launches microformat-powered recipe search
browse all entries by month in the blog archive
what are microformats?
microformat specifications
upcoming events
post categories
H4 tags for this entry
html5 enhanced time and data elements
media temple server hosting
microformats 2 – start publishing and parsing
tags for this entry
H5
H6
strong
humans first (machines second).
very openly licensed standards.
open spec history and editing.
specs with open revision history
specs with edit buttons
indiewebcamp events!
b
i
em humans first (machines second).
very openly licensed standards.
open spec history and editing.
specs with open revision history
specs with edit buttons
indiewebcamp events!
Bolds strong 6
b 0
i 0
em 6
Zawartość strony internetowej powinno zawierać więcej niż 250 słów, z stopa tekst / kod jest wyższy niż 20%.
Pozycji używać znaczników (h1, h2, h3, ...), aby określić temat sekcji lub ustępów na stronie, ale zwykle, użyj mniej niż 6 dla każdego tagu pozycje zachować swoją stronę zwięzły.
Styl używać silnych i kursywy znaczniki podkreślić swoje słowa kluczowe swojej stronie, ale nie nadużywać (mniej niż 16 silnych tagi i 16 znaczników kursywy)

Statystyki strony

twitter:title pusty
twitter:description pusty
google+ itemprop=name pusty
Pliki zewnętrzne 5
Pliki CSS 3
Pliki javascript 2
Plik należy zmniejszyć całkowite odwołanie plików (CSS + JavaScript) do 7-8 maksymalnie.

Linki wewnętrzne i zewnętrzne

Linki 172
Linki wewnętrzne 18
Linki zewnętrzne 154
Linki bez atrybutu Title 149
Linki z atrybutem NOFOLLOW 0
Linki - Użyj atrybutu tytuł dla każdego łącza. Nofollow link jest link, który nie pozwala wyszukiwarkom boty zrealizują są odnośniki no follow. Należy zwracać uwagę na ich użytkowania

Linki wewnętrzne

blog /blog
wiki /wiki/
discuss /wiki/irc
about /wiki/about
code & tools /wiki/code-tools
get started /wiki/get-started
kevin marks
#microformats on irc.freenode.net irc://irc.freenode.net/microformats
#microformats on freenode irc://irc.freenode.net/microformats/
blog archive /blog/
learn more about microformats /wiki/about
h-card /wiki/h-card
h-calendar /wiki/h-calendar
h-review /wiki/h-review
rel-license /wiki/rel-license
rel-tag /wiki/rel-tag
xoxo /wiki/xoxo
the list of all microformats /wiki/

Linki zewnętrzne

- http://microformats.org/feed
microformats.org at 11 http://microformats.org/2016/06/22/microformats-org-at-11
- http://julieannenoying.com/2016/06/20/happy-birthday-microformats/
julie anne noying http://julieannenoying.com/
web frameworks that rise and fall https://medium.com/@wob/the-sad-state-of-web-development-1603a861d29f
bait-and-break apis https://medium.com/@anildash/the-end-of-thinkup-e600bc46cc56
sudden site-deaths https://indiewebcamp.com/site-deaths#2015
a year ago http://tantek.com/2015/171/t1/10th-anniversary-microformats
microformats2 http://microformats.org/wiki/microformats2
microformats2 http://microformats.org/wiki/microformats2
indiewebcamp https://indiewebcamp.com/
known publishing system http://withknown.com/
wordpress plugins & themes https://indiewebcamp.com/getting_started_on_wordpress
modern microformats2 parsers http://microformats.org/wiki/microformats2#parsers
microformats2 parsing specification http://microformats.org/wiki/microformats2-parsing
microformats2 parsing issues http://microformats.org/wiki/microformats2-parsing-issues
will norris https://willnorris.com/
indieweb summit https://indiewebcamp.com/2016
a github repo for filing any new microformats2 parsing issues https://github.com/microformats/microformats2-parsing/issues
microformats2 parsers http://microformats.org/wiki/microformats2#parsers
elixir http://microformats.org/wiki/microformats2#elixir
ckruse https://github.com/ckruse
haskell http://microformats.org/wiki/microformats2#haskell
myfreeweb https://unrelenting.technology/
java http://microformats.org/wiki/microformats2#java
lewis john mcgibbney https://twitter.com/hectormcspector/status/645313144676478977
any23 is a library http://any23.apache.org/download.html
mf2j, an early-stage java microformats2 parser https://github.com/kylewm/mf2j
kyle mahan http://kylewm.com/
go http://microformats.org/wiki/microformats2#go
ruby http://microformats.org/wiki/microformats2#ruby
javascript http://microformats.org/wiki/microformats2#javascript
php http://microformats.org/wiki/microformats2#php
python http://microformats.org/wiki/microformats2#python
…hmm, looks like i should use a separate meta element: https://schema.org/startdate .

man, schema is verbose. @microformats ftw!
https://twitter.com/schofeld/status/648502325120737281
microformats 2 and schema http://www.kevinmarks.com/microformatschema.html
i still prefer @microformats over microdata https://twitter.com/robsonsobral/status/695243474048847872
@microformats are easier to write, easier to maintain and the code is so much smaller than microdata. https://twitter.com/robsonsobral/status/695260909095276544
i am not a big fan of rdf, semanticweb, or predefined ontologies. we need something lightweight and emergent like the microformats https://twitter.com/vlahan/status/742819320372334592
h-entry http://microformats.org/wiki/h-entry
yagni https://en.wikipedia.org/wiki/yagni
proposed additions http://microformats.org/wiki/h-entry#proposed_additions
draft properties http://microformats.org/wiki/h-entry#draft_properties
core properties http://microformats.org/wiki/h-entry#core_properties
tantek.com/2016/173/b1/microformats-org-at-11 http://tantek.com/2016/173/b1/microformats-org-at-11
june 22nd, 2016 http://microformats.org/2016/06/22/microformats-org-at-11
- tantek http://tantek.com/
microformats.org turns 9 — upgrade to microformats2 and more http://microformats.org/2014/06/20/microformats-org-turns-9-upgrade-to-microformats2
microformats.org http://microformats.org/
indieweb movement http://indiewebcamp.com/
google base http://microformats.org/wiki/google_base
google data http://microformats.org/wiki/google_data
commontag.org http://microformats.org/wiki/commontag
simplicity http://microformats.org/wiki/simplicity
irc http://microformats.org/wiki/irc
irc http://microformats.org/wiki/irc
email http://microformats.org/wiki/email
wiki http://microformats.org/wiki
microformats2 http://microformats.org/wiki/microformats2
microformats2 http://microformats.org/wiki/microformats2
search engines http://microformats.org/wiki/search_engines
validators http://microformats.org/wiki/validators
operator http://microformats.org/wiki/operator
h2vx http://microformats.org/wiki/h2vx
validators http://microformats.org/wiki/validators
hcard creator http://microformats.org/code/hcard/creator.html
hcalendar creator http://microformats.org/code/hcalendar/creator.html
hreview creator http://microformats.org/code/hreview/creator.html
parsers http://microformats.org/wiki/parsers
microformats2 http://microformats.org/wiki/microformats2
barnaby walters http://waterpigs.co.uk/
admins http://microformats.org/wiki/admins
rohit khare http://rohit.khare.org/
kevin marks http://kevinmarks.com/
ted o’connor http://edward.oconnor.cx/
originally posted on tantek.com http://tantek.com/2014/171/b1/microformats-org-turns-nine
microformats2 http://microformats.org/tag/microformats2
june 20th, 2014 http://microformats.org/2014/06/20/microformats-org-turns-9-upgrade-to-microformats2
- tantek http://tantek.com/
getting started with microformats2 http://microformats.org/2014/03/05/getting-started-with-microformats2
since 2004 http://microformats.org/wiki/history#2004
this php-mf2 sandbox http://waterpigs.co.uk/php-mf2
microformats 2 wiki http://microformats.org/wiki/microformats-2
microformats 2 parsing http://microformats.org/wiki/microformats-2-parsing
microformats 2 prefixes http://microformats.org/wiki/microformats2-prefixes
microformats 2: what’s new http://waterpigs.co.uk/presentations/microformats-2/#slide-2
getting started with microformats2 on waterpigs.co.uk http://waterpigs.co.uk/articles/getting-started-with-microformats2/
my articles feed http://waterpigs.co.uk/articles
notes http://waterpigs.co.uk/notes?tagged=microformats
my twitter account https://twitter.com/barnabywalters
march 5th, 2014 http://microformats.org/2014/03/05/getting-started-with-microformats2
- waterpigs.co.uk/ http://waterpigs.co.uk/
1 comment http://microformats.org/2014/03/05/getting-started-with-microformats2#comments
microformats.org at 7 http://microformats.org/2012/06/25/microformats-org-at-7
gathering http://plancast.com/p/bhk1
principles http://microformats.org/wiki/principles
dan cederholm http://simplebits.com
ryan king http://theryanking.com
robert bachmann http://robertbachmann.at/
dimitri glazkov http://glazkov.com/
drew mclellan http://allinthehead.com/
scott reynen http://typewriting.org/
admin emeriti http://microformats.org/wiki/admins#admin_emeriti
ted o’connor http://edward.oconnor.cx/
christophe ducamp http://christopheducamp.com/
community admins http://microformats.org/wiki/admins
- http://webdatacommons.org/
gender http://microformats.org/wiki/gender
rfc 6350 http://www.ietf.org/rfc/rfc6350.txt
cc0 http://creativecommons.org/publicdomain/zero/1.0/
17 different translations http://microformats.org/wiki/main_page#microformats_wiki_translations
hcard specification http://microformats.org/wiki/hcard
research contributions http://wiki.whatwg.org/wiki/time
hcard http://microformats.org/wiki/hcard
hcalendar http://microformats.org/wiki/hcalendar
h2vx http://h2vx.com
@h2vx on twitter http://twitter.com/h2vx
geo http://microformats.org/wiki/geo
value class pattern http://microformats.org/wiki/vcp
media temple http://mediatemple.net
microformats 2 http://microformats.org/wiki/microformats-2
several examples in the wild http://microformats.org/wiki/microformats-2#examples_in_the_wild
value class pattern http://microformats.org/wiki/vcp
<time> and <data> http://microformats.org/wiki/hcard-parsing#all_properties
microformats 2 http://microformats.org/wiki/microformats-2
@microformats http://twitter.com/microformats
#microformats https://twitter.com/#!/search/realtime/%23microformats
irc channel http://microformats.org/wiki/irc
june 25th, 2012 http://microformats.org/2012/06/25/microformats-org-at-7
- tantek http://tantek.com/
3 comments http://microformats.org/2012/06/25/microformats-org-at-7#comments
google launches microformat-powered recipe search http://microformats.org/2011/02/24/google-launches-microformat-powered-recipe-search
recipe view http://www.google.com/landing/recipes/
google have made it easy http://googleblog.blogspot.com/2011/02/slice-and-dice-your-recipe-search.html
wired reports http://www.wired.com/epicenter/2011/02/google-recipe-semantic/
readwriteweb also notes http://www.readwriteweb.com/archives/a_more_delicious_google_search_now_with_recipe_vie.php
continue to support and implement open standards http://microformats.org/2010/04/28/google-adds-support-for-hcalendar-and-hrecipe-rich-snippets
hrecipe http://microformats.org/wiki/hrecipe
google http://microformats.org/tag/google
hrecipe http://microformats.org/tag/hrecipe
recipe view http://microformats.org/tag/recipe-view
rich snippets http://microformats.org/tag/rich-snippets
february 24th, 2011 http://microformats.org/2011/02/24/google-launches-microformat-powered-recipe-search
- frances http://fberriman.com
5 comments http://microformats.org/2011/02/24/google-launches-microformat-powered-recipe-search#comments
xfn http://microformats.org/wiki/xfn
see microformats events on the wiki http://microformats.org/wiki/events
see also indiewebcamp events! http://indiewebcamp.com/events
events http://microformats.org/category/events
news http://microformats.org/category/news
this week in microformats http://microformats.org/category/this-week
wordpress http://wordpress.org
(mt) media temple http://mediatemple.net/
no www http://no-www.org/

Zdjęcia

Zdjęcia 11
Zdjęcia bez atrybutu ALT 6
Zdjęcia bez atrybutu TITLE 11
Korzystanie Obraz ALT i TITLE atrybutu dla każdego obrazu.

Zdjęcia bez atrybutu TITLE

http://microformats.org/wordpress/wp-content/themes/microformats/img/logo.gif
http://microformats.org/wordpress/wp-content/themes/microformats/img/xml.gif
http://julieannenoying.com/wp-content/uploads/2016/06/ermergerd.jpg
http://0.gravatar.com/avatar/02cd45622e90350cc061aaaa02229195?s=16&d=http%3a%2f%2f0.gravatar.com%2favatar%2fad516503a11cd5ca435acc9bb6523536%3fs%3d16&r=pg
http://tantek.com/presentations/2012/07/html5-microformats2/microformats-logo.png
http://0.gravatar.com/avatar/02cd45622e90350cc061aaaa02229195?s=16&d=http%3a%2f%2f0.gravatar.com%2favatar%2fad516503a11cd5ca435acc9bb6523536%3fs%3d16&r=pg
http://0.gravatar.com/avatar/4a57cddee3c50aefa893005dcdd33b64?s=16&d=http%3a%2f%2f0.gravatar.com%2favatar%2fad516503a11cd5ca435acc9bb6523536%3fs%3d16&r=pg
https://chart.googleapis.com/chart?chtt=2012%20domains%20with%20structured%20data&chs=500x350&chds=a&cht=p&chd=t:127381,11709819,897080,629319,30417192,69569,9890,615681,4109,3952674,16976232&chl=html-mf-hrecipe|html-mf-xfn|html-mf-geo|html-mf-hcalendar|html-mf-hcard|html-mf-hlisting|html-mf-hresume|html-mf-hreview|html-mf-species|html-microdata|html-rdfa
http://0.gravatar.com/avatar/02cd45622e90350cc061aaaa02229195?s=16&d=http%3a%2f%2f0.gravatar.com%2favatar%2fad516503a11cd5ca435acc9bb6523536%3fs%3d16&r=pg
http://1.gravatar.com/avatar/5efecf1ab796b265639688a5825dc449?s=16&d=http%3a%2f%2f1.gravatar.com%2favatar%2fad516503a11cd5ca435acc9bb6523536%3fs%3d16&r=pg
/wordpress/wp-content/themes/microformats/img/mf-lg-ora.gif

Zdjęcia bez atrybutu ALT

http://0.gravatar.com/avatar/02cd45622e90350cc061aaaa02229195?s=16&d=http%3a%2f%2f0.gravatar.com%2favatar%2fad516503a11cd5ca435acc9bb6523536%3fs%3d16&r=pg
http://0.gravatar.com/avatar/02cd45622e90350cc061aaaa02229195?s=16&d=http%3a%2f%2f0.gravatar.com%2favatar%2fad516503a11cd5ca435acc9bb6523536%3fs%3d16&r=pg
http://0.gravatar.com/avatar/4a57cddee3c50aefa893005dcdd33b64?s=16&d=http%3a%2f%2f0.gravatar.com%2favatar%2fad516503a11cd5ca435acc9bb6523536%3fs%3d16&r=pg
http://0.gravatar.com/avatar/02cd45622e90350cc061aaaa02229195?s=16&d=http%3a%2f%2f0.gravatar.com%2favatar%2fad516503a11cd5ca435acc9bb6523536%3fs%3d16&r=pg
http://1.gravatar.com/avatar/5efecf1ab796b265639688a5825dc449?s=16&d=http%3a%2f%2f1.gravatar.com%2favatar%2fad516503a11cd5ca435acc9bb6523536%3fs%3d16&r=pg
/wordpress/wp-content/themes/microformats/img/mf-lg-ora.gif

Ranking:


Alexa Traffic
Daily Global Rank Trend
Daily Reach (Percent)









Majestic SEO











Text on page:

blog wiki discuss about code & tools get started latest microformats news microformats.org at 11 thanks to julie anne noying for the meme birthday card. in this day and age of web frameworks that rise and fall like seasonal fashion displays, bait-and-break apis, and sudden site-deaths, it’s nothing short of incredible that we’ve been able to continue evolving, improving, and growing microformats use for 11 years. all that incremental work has produced quite a lot since a year ago. most recently, we’ve made great progress with iterating, publishing, and deploying microformats2 support. i believe microformats.org has surived as a community, and microformats as a technology, by continuing to focus on solving smaller, simpler problems first, and then iterating only as needed with real world use-cases. it’s an approach i think works as a good starting point for nearly any project. -tantek 10,000s of microformats2 sites and now 10 microformats2 parsers the past year saw a huge leap in the number of sites publishing microformats2, from 1000s to now 10s of thousands of sites, primarily by adoption in the indiewebcamp community, and especially the excellent known publishing system and continually improving wordpress plugins & themes. new modern microformats2 parsers continue to be developed in various languages, and this past year, four new parsing libraries (in three different languages) were added, almost doubling our previous set of six (in five different languages) that brought our year 11 total to 10 microformats2 parsing libraries available in 8 different programming languages. microformats2 parsing spec updates the microformats2 parsing specification has made significant progress in the past year, all of it incremental iteration based on real world publishing and parsing experience, each improvement discussed openly, and tested with real world implementations. the microformats2 parsing spec is the core of what has enabled even simpler publishing and processing of microformats. the specification has reached a level of stability and interoperability where fewer issues are being filed, and those that are being filed are in general more and more minor, although once in a while we find some more interesting opportunities for improvement. we reached a milestone two weeks ago of resolving all outstanding microformats2 parsing issues thanks to will norris leading the charge with a developer spec hacking session at the recent indieweb summit where he gathered parser implementers and myself (as editor) and walked us through issue by issue discussions and consensus resolutions. some of those still require minor edits to the specification, which we expect to complete in the next few days. one of the meta-lessons we learned in that process is that the wiki really is less suitable for collaborative issue filing and resolving, and as of today are switching to using a github repo for filing any new microformats2 parsing issues. more microformats2 parsers the number of microformats2 parsers in different languages continues to grow, most of them with deployed live-input textareas so you can try them on the web without touching a line of parsing code or a command line! all of these are open source (repos linked from their sections), unless otherwise noted. these are the new ones: elixir – created by ckruse. haskell – created by myfreeweb java (2) the java parsers are a particularly interesting development as one is part of the upgrade to apache any23 to support microformats2 (thanks to lewis john mcgibbney). any23 is a library used for analysis of various web crawl samples to measure representative use of various forms of semantic markup. the other java parser is mf2j, an early-stage java microformats2 parser, created by kyle mahan. the elixir, haskell, and java parsers add to our existing in-development parser libraries in go and ruby. the go parser in particular has recently seen a resurgence in interest and improvement thanks to will norris. these in-development parsers add to existing production parsers, that is, those being used live on websites to parse and consume microformats for various purposes: javascript (cross-browser client-side, and node) php python as with any open source projects, tests, feedback, and contributions are very much welcome! try building the production parsers into your projects and sites and see how they work for you. still simpler, easier, and smaller after all these years usually technologies (especially standards) get increasingly complex and more difficult to use over time. with microformats we have been able to maintain (and in some cases improve) their simplicity and ease of use, and continue to this day to get testimonials saying as much, especially in comparison to other efforts: …hmm, looks like i should use a separate meta element: https://schema.org/startdate . man, schema is verbose. @microformats ftw! on the broader problem of schema.org verbosity (no matter the syntax), kevin marks wrote a very thorough blog post early in the past year: microformats 2 and schema 2015-06-30 more testimonials: i still prefer @microformats over microdata * * * @microformats are easier to write, easier to maintain and the code is so much smaller than microdata. * * * i am not a big fan of rdf, semanticweb, or predefined ontologies. we need something lightweight and emergent like the microformats this last testimonial really gets at the heart of one of the deliberate improvements we have made to iterating on microformats vocabularies in particular. evolving h-entry we have had an implementation-driven and implementation-tested practice for the microformats2 parsing specification for quite some time. more and more we are adopting a similar approach to growing and evolving microformats vocabularies like h-entry. we have learned to start vocabularies as minimal as possible, rather than start with everything you might want to do. that “start with everything you might want” is a common theory-first approach taken by a-priori vocabularies or entire “predefined ontologies” like schema.org’s 150+ objects at launch, very few of which (single digits?) google or anyone bothers to do anything with, a classic example of premature overdesign, of yagni). with h-entry in particular, we started with an implementation filtered subset of hatom, and since then have started documenting new properties through a few deliberate phases (which helps communicate to implementers which are more experimental or more stable) proposed additions – when someone proposes a property, gets some sort of consensus among their community peers, and perhaps one more person to implementing it in the wild beyond themselves (e.g. as the indiewebcamp community does), it’s worth capturing it as a proposed property to communicate that this work is happening between multiple people, and that feedback, experimentation, and iteration is desired. draft properties – when implementations begin to consume proposed properties and doing something explicit with them, then a postive reinforcement feedback loop has started and it makes sense to indicate that such a phase change has occured by moving those properties to “draft”. there is growing activity around those properties, and thus this should be considered a last call of sorts for any non-trivial changes, which get harder to make with each new implementation. core properties – these properties have gained so much publishing and consuming support that they are for all intents and purposes stable. another phase change has occured: it would be much harder to change them (too many implementations to coordinate) than keep them the same, and thus their stability has been determined by real world market adoption. the three levels here, proposed, draft, and core, are merely “working” names, that is, if you have a better idea what to call these three phases by all means propose it. in h-entry in particular, it’s likely that some of the draft properties are now mature (implemented) enough to move them to core, and some of the proposed properties have gained enough support to move to draft. the key to making this happen is finding and citing documentation of such implementation and support. anyone can speak up in the irc channel etc. and point out such properties that they think are ready for advancement. how we improve moving forward we have made a lot of progress and have much better processes than we did even a year ago, however i think there’s still room for improvement in how we evolve both microformats technical specifications like the microformats2 parsing spec, and in how we create and improve vocabularies. it’s pretty clear that to enable innovation we have to ways of encouraging constructive experimentation, and yet we also need a way of indicating what is stable vs in-progress. for both of those we have found that real world implementations provide both a good focusing mechanism and a good way to test experiments. in the coming year i expect we will find even better ways to explain these methods, in the hopes that others can use them in their efforts, whether related to microformats or in completely different standards efforts. for now, let’s appreciate the progress we’ve made in the past year from publishing sites, to parsing implementations, from process improvements, to continuously improving living specifications. here’s to year 12. originally published at: tantek.com/2016/173/b1/microformats-org-at-11. june 22nd, 2016 tantek comments off microformats.org turns 9 — upgrade to microformats2 and more nine years ago we launched microformats.org with a basic premise: that it is possible to express meaning on the web in html in a simple way—far simpler than the complex alternatives (xml) being promoted by mature companies and standards organizations alike. today microformats.org continues to be a gathering place for those seeking simpler ways to express meaning in web pages, most recently the growing indieweb movement. looking back nine years ago, none of the other alternatives promoted in the 2000s (even by big companies like google and yahoo) survive to this day in any meaningful way: google base google data yahoo’s commontag.org too many xml approaches to count from this experience, we conclude that what large companies support (or claim to prefer) is often a trailing indicator (at best). large companies tend to promote more complex solutions, perhaps because they can afford the staff, time, and other resources to develop and support complex solutions. such approaches fundamentally lack empathy for independent developers and designers, who don’t have time to keep up with all the complexity. if there’s one value that’s at the heart of microformats’ focus and continued evolution of simplicity, it is that empathy for independent developers and designers, for small consulting shops, for curious hobbyists who are most enabled and empowered by the simplest possible solutions to problems. we now know that no amount of large company marketing and evangelism can make up for a focus on ever simpler solutions which take less time to learn, use, and reliably maintain. as long as we focus on that, we will create better solutions. community changes speaking of taking less time, we’ve learned some community lessons about that too. perhaps the most important is that as a community we are far more efficiently productive using just irc and the wiki, than any amount of use of email. in fact, the microformats drafts that were developed wtih the most email (e.g. haudio) turned out to be the hardest to follow and discuss (too many long emails), and sadly ended up lacking the simplicity that real world publishers wanted (e.g. last.fm). email tends to bias design and discussions towards those who have more time to read and write long emails, and (apparently) enjoy that for its own sake, than those who want to quickly research & brainstorm, and get to actually creating, building, and deploying things with microformats. thus we’re making these changes effective today: irc for all microformats discussions, whether research, questions, or brainstorming email only for occasional announcements and to direct people to irc. wiki for capturing questions, brainstorming, conclusions, and different points of view we’re going to update the site to direct all discussion (e.g links) to the irc channel accordingly. hope to see you there: #microformats on irc.freenode.net upgrading to microformats2 over the past few years microformats2 has proven itself in practice, with numerous sites both publishing and consuming, several open source parsing libraries, and a growing test suite. all the lessons learned from the evolution from original microformats, from rdfa, and from microdata have been incorporated into microformats2 which is now the simplest to both publish and parse. it’s time to throw the switch and upgrade everything to microformats2. this means three things: upgrading microformats.org first, we’re starting by upgrading the links on the microformats.org home page to point to the microformats2 drafts, which are ready for use. we’ll be incrementally upgrading the markup of the microformats.org site itself to use microformats2 markup. upgrade sites second, if you publish any kind of semantic information, start upgrading your web pages to microformats2 across the board. if you’re concerned about what search engines claim to support, there are two approaches to choose from: know that search engines are a trailing indicator, and as microformats2 usage grows, they’ll index it as well. or: use one classic microformat (supported by all major search engines) at top of your page, e.g. on the , in addition to your microformats2 markup throughout your pages. search engines only really care to summarize the primary topic or purpose of a web page in their “rich snippets” or “cards”, and thus that’s sufficient. check out the latest validators which now include some microformats2 support as well! upgrade tools third, this is a call to upgrade all microformats supporting tools to microformats2. as nearly all of these are open source, this is an open call for contributions, updates, patches, etc. for: operator h2vx validators hcard creator hcalendar creator hreview creator if it generates microformats, upgrade it to instead generate microformats2. if it consumes microformats, upgrade it to also consume microformats2 (which may be most easily done by making use of one of the microformats2 parsers that has backward compatible parsing built in). 10th year goal as we enter the tenth year of microformats.org let’s make it our collective goal to upgrade our pages, our sites, and our tools to microformats2. our goal is to complete all the above upgrades by microformats.org’s tenth birthday, if not sooner. let’s get to work. thanks to barnaby walters and fellow microformats admins rohit khare, kevin marks, & ted o’connor for reviewing drafts of this post. thanks to kevin especially for some copy edits! this post was originally posted on tantek.com. tags for this entry microformats2 june 20th, 2014 tantek comments off getting started with microformats2 classic microformats have been serving the web community’s need to extend html’s expressive power since 2004. through an evolutionary, open, rigorous community process and human-first design principles, structured use of the class and rel attributes have paved the cowpaths of publishing data about people, places, events, reviews, products and more. microformats2 is the next big effort by the community to improve how microformats are authored, parsed and defined. version two has multiple working open source implementations which independents are using in production and is easier to publish and consume than ever. in this series of guides i’ll show you how to be the next site publishing and consuming microformats. you can see how a microformats parser sees your markup by pasting any of the code samples below into this php-mf2 sandbox. go ahead and experiment with adding more properties and see what happens! incremental steps in order to demonstrate some of the differences between microformats 2 and classic microformats/other competing technologies, i’ll use the process of content-out markup — going from plain text to html and finally adding a sprinkling of microformats. let’s start with my favourite example: mentioning a person. as plain text: barnaby walters with html: barnaby walters with classic microformats: barnaby walters that’s 37 extra characters and a whole extra nested element just to say “this link is to a person”, not to mention the strangely named root classname (vcard? i thought this was an hcard?) and multiple cryptic fn n classnames. competing technologies are typically even longer and messier. with microformats 2 this all becomes much simpler: barnaby walters weighing in at only 15 characters, this is quicker to type, easier on the eyes and easier to remember. there are two fundamental changes in microformats 2 which make this helium-esque lightness possible: implied properties and prefixed classnames. implied properties when you give class=h-card to an element, you’re saying “this element represents a person”. in many cases the element will be simple; just a name, perhaps with a link or photo. why should you add extra elements and classnames just to tell a dumb computer which bit is the name, url or photo url when that information is already expressed by the markup? implied properties save you from this tedium. when you specify an element as an h-card without explicitly defining which parts are the name, url or photo url, the parser will figure out what you meant. and it’s not just for h-cards either — thanks to the new generic parsing in microformats 2, this shorthand works for any microformat. prefixed classnames classic microformats used plain classnames which looked like any other (e.g. vcard, n or note). there were a few problems with this — classnames would clash, cause false positives or be thrown away by developers who weren’t microformats-aware (“these classnames aren’t doing anything!”). this also meant parsers were tricky to write, as each one had to maintain a long list of classnames used by each microformats, resulting in many parsers quickly going out of date. prefixing classnames solves both of these problems: semantic microformats2 classnames are set apart from styling hooks, and parsers can figure out which classnames to look for, cutting down on maintenance. there are 5 prefixes: h-* root classnames specify that an element is a microformat, e.g. p-* specifies an element as a plain-text property, e.g. my name u-* parses an element as a url, e.g. dt-* parses an element as a date/time, e.g.

i’ll demonstrate the use of all of these prefixes with some real-world examples. firstly, another h-card, more fleshed out than the earlier example. this might be the sort that you put on your homepage: p-name, u-url and u-photo are fairly standard properties you’ll see over and over again. another improvement in microformats 2 is increasing consistency between different microformat specifications — again, making them easier to authors to remember and consumers to understand. a nice side effect is that a single element can be more than one type of microformat at once — for example a h-entry and h-review. to demonstrate dt-* and e-*, here’s a note (like a tweet or short blog post), marked up using h-entry: here, i want the html inside the content to be passed to the parser, so i mark it up as e-*. notice i’m also specifying that content as the summary and name — one element can be parsed as multiple properties. i’m using the time element to mark up the time this note was published. because i’ve prefixed the classname with dt- and it’s on a time element, parsers know to look in the datetime attribute if it exists. combining microformats the third area in which microformats2 improves on the previous version is in combining microformats and making each microformat specification more reusable — for example, both a person or an event might have an address, so it makes sense to reuse the same markup for both. there are many reasons to combine microformats — say you want to specify the author of a blog post or review. you would do so by making the p-author of the post an h-card:
further reading hopefully this overview tickled your interest and gave you a firm foundation from which to base further investigation. to learn more about the topics covered in this post, see the following urls: the microformats 2 wiki, specifically: microformats 2 parsing microformats 2 prefixes the microformats 2: what’s new presentation i gave at exeter web this article reposted from getting started with microformats2 on waterpigs.co.uk, and is the first of a series covering microformats2. be sure to follow my articles feed to be notified about the others. i also post notes about microformats quite often. they’re syndicated to my twitter account too. march 5th, 2014 waterpigs.co.uk/ 1 comment microformats.org at 7 last week the microformats.org community celebrated its 7th birthday at a gathering hosted by mozilla in san francisco and recognized accomplishments, challenges, and opportunities. humans first: admin emeriti & new admins the microformats tagline “humans first, machines second” forms the basis of many of our principles, and in that regard, we’d like to recognize a few people and thank them for their years of volunteer service as community admins: dan cederholm (co-founder) ryan king (co-founder) robert bachmann dimitri glazkov drew mclellan scott reynen they’ve each been essential positive community contributors and guides over the years, and as admin emeriti are always welcome back should they decided to become admins again. we’re also pleased to announce two new community admins: ted o’connor of apple christophe ducamp both have similarly been consistent positive contributors to microformats for years, and we’re very happy they’ve stepped up as community admins. challenges & opportunities during microformats.org’s first seven years, we’ve seen many other attempts to promote structured data on the web. some have since disappeared or been retired, one never got past an initial blog post, a couple have gained traction, and couple were just launched in the past two weeks: 2005-2009(?): structuredblogging 2005-2011: google base schema 2007-2011(?): google data api/elements 2009-2009(?): yahoo et al commontag.org 2010-2012+ facebook ogp meta tags 2011-2012+ google/ms/y! schema.org 2012-2012+ twitter cards meta tags 2012-2012+ openmetadata.org each of these is a signal that there are a few people (or a company) who want to do something with structured data on the web better than what they thought was already out there. we can view each of these as a set of challenges and questions: what problems were these created to solve? are they solving similar, overlapping, or different problems than microformats? did their creators know about microformats? did they try using microformats? are they open efforts (or at least trying to be open), or are they vendor-specific? we can also view each of these as feedback, whether intended or not, and opportunities to improve microformats. open source teaches us that great ideas come from everywhere, thus we should analyze and document other efforts, seeking to answer the above questions. if these alternative efforts are solving the same or similar problems as microformats, how can we improve microformats to meet their needs with established open standards? if they’re addressing different problems, are those problems that microformats should be expanded to solve? and if they’re open efforts, how can we best collaborate and produce even better solutions together? microformats ~70% structured data domains even after seven years and the emergence of various alternatives, according to the web data commons as of 2012, microformats still have the greatest adoption across different websites for publishing structured data in html: our continuing success is no indication that we should rest. we should document the alternatives as they emerge, do our best to answer the questions posed, and reach out to other communities to find areas of overlap to collaborate. with greater collaboration comes greater interoperability. why microformats as we continue to evolve and expand microformats, we should keep in mind the principles and values that brought us here. here are a few of the core values that still distinguish microformats as a technology, effort, and community: humans first (machines second). microformats are designed primarily for humans, and primarily for the greatest number of humans, whether authoring, or representing (e.g. the microformats community spearheaded and got the most inclusive “gender” property ever designed into the vcard 4 (rfc 6350) – which hcard 1.1 and 2 uses). mozilla front end developer / ux engineer gordon brander recently remarked to me, “microformats work within existing web designer/developer workflow, which makes them easy and convenient. other solutions require learning new attributes, which is enough of a barrier to just not bother.” when i related this to sam weinig of the safari team, he made an astute observation and comparison: “essentially what you’re saying is that bolt-on solutions, even just attributes, whether for accessibility like ‘longdesc’, or for semantics like rdfa/microdata, just don’t work as well.” very openly licensed standards. by virtue of being creative commons licensed from the start, and public domain / cc0 compatible since late 2007, microformats are the most openly available standards developed world-wide. cc0 provides the maximum freedom to re-use, publish, and if you’ve got a better idea, fork, experiment, and submit suggestions. just like open source. this openness has shown to be particularly effective on the microformats wiki, which has 17 different translations in progress. these independent translators from around the world, who by virtue of committing their work to the public domain / cc0, perhaps know that not only are they sharing their work, but that the work they do cannot be taken from them. once placed into the public domain, their work remains there, always reusable at any point in the future, by anyone. contrast this with any form of writing/creating that is owned. if it’s owned it can be bought, and thus taken away from you. while that’s a perfectly reasonable trade to make for an income, for standards and longevity, it’s important that our work remain maximally public, as an open resource for generations to come. and finally, to date, no other standards organization has chosen to put all their research, examples, specifications etc. in the public domain / cc0. we invite every open standards organization to do so. open spec history and editing. two key distinguishing factors that contribute to our community openness are aspects of microformats specs: specs with open revision history – every microformats specification has an open revision history dating back to the launch of microformats.org seven years ago. an open revision history provides a level of transparency, accountability, and provenance second to none. in comparison, the other efforts listed above lack any kind of open revision history, e.g. clearly showing date-time, who edited, and how much changed in each spec. the microformats wiki revision histories are also easily browsable and delta-changes-viewable, far more usable/accessible than web views on revision control systems (e.g. w3c’s cvs and hg repositories). specs with edit buttons – also unprecedented and unmatched, every microformats specification is on a wiki page, editable by any account holder, should they find typos or other obvious errata / minor edits (spec editors handle larger spec edits, though anyone may copy a spec and demonstrate major edits for consideration in a copy). the community value of allowing such open editing cannot be understated. many longtime contributors started interacting with the microformats community by jumping in and making minor edits or suggestions on the wiki (some, like brian suda, first participated by contributing edits to the original hcard specification, though we quickly followed up on irc). latest in microformats the past year has seen several interesting and useful developments in and related to microformats. html5 enhanced time and data elements in november 2011 there was a heated discussion in the w3c html wg and whatwg about the html5

Numbers of all words: 5615

One word

Two words phrases

Three words phrases

the - 5.84% (328)
for - 4.67% (262)
and - 3.94% (221)
form - 3.15% (177)
microformat - 3.01% (169)
formats - 2.89% (162)
microformats - 2.87% (161)
are - 1.14% (64)
that - 1.12% (63)
all - 0.98% (55)
class - 0.91% (51)
ted - 0.84% (47)
with - 0.8% (45)
art - 0.77% (43)
this - 0.75% (42)
any - 0.71% (40)
microformats2 - 0.71% (40)
spec - 0.71% (40)
our - 0.71% (40)
use - 0.71% (40)
you - 0.68% (38)
parse - 0.61% (34)
time - 0.57% (32)
has - 0.55% (31)
out - 0.55% (31)
year - 0.52% (29)
web - 0.52% (29)
open - 0.52% (29)
more - 0.5% (28)
have - 0.5% (28)
here - 0.5% (28)
from - 0.48% (27)
one - 0.48% (27)
publish - 0.46% (26)
name - 0.46% (26)
other - 0.45% (25)
parser - 0.45% (25)
some - 0.45% (25)
not - 0.45% (25)
which - 0.45% (25)
microformats. - 0.43% (24)
than - 0.43% (24)
element - 0.43% (24)
new - 0.39% (22)
data - 0.39% (22)
ever - 0.37% (21)
community - 0.37% (21)
able - 0.37% (21)
even - 0.37% (21)
they - 0.36% (20)
mark - 0.36% (20)
age - 0.36% (20)
very - 0.36% (20)
start - 0.36% (20)
end - 0.36% (20)
work - 0.34% (19)
can - 0.34% (19)
but - 0.34% (19)
king - 0.34% (19)
see - 0.32% (18)
develop - 0.32% (18)
these - 0.32% (18)
implement - 0.3% (17)
try - 0.3% (17)
site - 0.3% (17)
post - 0.3% (17)
like - 0.3% (17)
microformats.org - 0.3% (17)
parsing - 0.3% (17)
how - 0.28% (16)
date - 0.28% (16)
support - 0.28% (16)
their - 0.28% (16)
add - 0.28% (16)
view - 0.28% (16)
parsers - 0.28% (16)
html - 0.28% (16)
properties - 0.28% (16)
specification - 0.27% (15)
edit - 0.27% (15)
years - 0.27% (15)
first - 0.27% (15)
e.g. - 0.27% (15)
now - 0.27% (15)
there - 0.27% (15)
it’s - 0.25% (14)
each - 0.25% (14)
test - 0.25% (14)
over - 0.25% (14)
them - 0.25% (14)
improve - 0.25% (14)
wiki - 0.25% (14)
google - 0.25% (14)
classname - 0.25% (14)
just - 0.23% (13)
real - 0.23% (13)
both - 0.23% (13)
what - 0.23% (13)
also - 0.23% (13)
about - 0.23% (13)
way - 0.23% (13)
publishing - 0.23% (13)
day - 0.23% (13)
simple - 0.23% (13)
me, - 0.23% (13)
search - 0.23% (13)
irc - 0.21% (12)
past - 0.21% (12)
entry - 0.21% (12)
page - 0.21% (12)
classnames - 0.21% (12)
url - 0.21% (12)
— - 0.21% (12)
sites - 0.21% (12)
world - 0.21% (12)
many - 0.21% (12)
different - 0.21% (12)
its - 0.21% (12)
standard - 0.21% (12)
implementation - 0.21% (12)
should - 0.21% (12)
part - 0.2% (11)
get - 0.2% (11)
come - 0.2% (11)
few - 0.2% (11)
using - 0.2% (11)
were - 0.2% (11)
standards - 0.2% (11)
– - 0.2% (11)
h-card - 0.2% (11)
been - 0.2% (11)
recipe - 0.2% (11)
effort - 0.2% (11)
upgrade - 0.2% (11)
make - 0.18% (10)
your - 0.18% (10)
read - 0.18% (10)
source - 0.18% (10)
who - 0.18% (10)
thank - 0.18% (10)
too - 0.18% (10)
comment - 0.18% (10)
h-entry - 0.18% (10)
problem - 0.18% (10)
blog - 0.18% (10)
most - 0.18% (10)
markup - 0.18% (10)
every - 0.18% (10)
those - 0.18% (10)
article - 0.16% (9)
example - 0.16% (9)
problems - 0.16% (9)

- 0.16% (9)
learn - 0.16% (9)
less - 0.16% (9)
change - 0.16% (9)
long - 0.16% (9)
event - 0.16% (9)
solutions - 0.16% (9)
design - 0.16% (9)
author - 0.16% (9)
rel - 0.16% (9)
discuss - 0.16% (9)
efforts - 0.16% (9)
two - 0.14% (8)
draft - 0.14% (8)
semantic - 0.14% (8)
own - 0.14% (8)
want - 0.14% (8)
microformats, - 0.14% (8)
better - 0.14% (8)
much - 0.14% (8)
late - 0.14% (8)
ago - 0.14% (8)
thanks - 0.14% (8)
was - 0.14% (8)
let - 0.14% (8)
back - 0.14% (8)
continue - 0.14% (8)
made - 0.14% (8)
we’re - 0.14% (8)
admin - 0.14% (8)
2012 - 0.14% (8)
making - 0.14% (8)
(e.g - 0.14% (8)
human - 0.14% (8)
schema - 0.12% (7)
html5 - 0.12% (7)
easier - 0.12% (7)
improvement - 0.12% (7)
simpler - 0.12% (7)
when - 0.12% (7)
person - 0.12% (7)
(e.g. - 0.12% (7)
implementations - 0.12% (7)
thus - 0.12% (7)
launch - 0.12% (7)
barnaby - 0.12% (7)
walters - 0.12% (7)
propose - 0.12% (7)
of the - 0.45% (25)
in the - 0.45% (25)
the microformats - 0.36% (20)
on the - 0.32% (18)
microformats 2 - 0.32% (18)
to the - 0.23% (13)
to microformats - 0.18% (10)
of microformat - 0.18% (10)
2 parsing - 0.16% (9)
of microformats - 0.16% (9)
or the - 0.16% (9)
with a - 0.16% (9)
the past - 0.16% (9)
microformats2 parsing - 0.14% (8)
thanks to - 0.14% (8)
for the - 0.14% (8)
real world - 0.14% (8)
and the - 0.14% (8)
we have - 0.12% (7)
in microformats - 0.12% (7)
open source - 0.12% (7)
barnaby walters - 0.12% (7)
if you - 0.12% (7)
to microformats2 - 0.12% (7)
are the - 0.12% (7)
of these - 0.12% (7)
the web - 0.12% (7)
an element - 0.12% (7)
past year - 0.12% (7)
all the - 0.11% (6)
is that - 0.11% (6)
use of - 0.11% (6)
and more - 0.11% (6)
there are - 0.11% (6)
the microformats2 - 0.11% (6)
out the - 0.11% (6)
publishing and - 0.11% (6)
parsing spec - 0.09% (5)
from the - 0.09% (5)
use the - 0.09% (5)
classic microformat - 0.09% (5)
with microformats - 0.09% (5)
a person - 0.09% (5)
and thus - 0.09% (5)
blog post - 0.09% (5)
microformats2 parsers - 0.09% (5)
easier to - 0.09% (5)
all of - 0.09% (5)
as well - 0.09% (5)
the new - 0.09% (5)
that a - 0.09% (5)
about microformats - 0.09% (5)
microformats are - 0.09% (5)
and in - 0.09% (5)
want to - 0.09% (5)
that the - 0.09% (5)
of microformats. - 0.07% (4)
the wiki - 0.07% (4)
the html - 0.07% (4)
this is - 0.07% (4)
and it - 0.07% (4)
some of - 0.07% (4)
is the - 0.07% (4)
public domain - 0.07% (4)
time to - 0.07% (4)
revision history - 0.07% (4)
open revision - 0.07% (4)
an open - 0.07% (4)
years ago - 0.07% (4)
element as - 0.07% (4)
a good - 0.07% (4)
structured data - 0.07% (4)
have been - 0.07% (4)
web page - 0.07% (4)
href="http://waterpigs.co.uk">barnaby walters - 0.07% (4)
we should - 0.07% (4)
are they - 0.07% (4)
the most - 0.07% (4)
the microformats.org - 0.07% (4)
the other - 0.07% (4)
to support - 0.07% (4)
we’re very - 0.07% (4)
one of - 0.07% (4)
continue to - 0.07% (4)
search engines - 0.07% (4)
to microformats2. - 0.05% (3)
we can - 0.05% (3)
be the - 0.05% (3)
from a - 0.05% (3)
started with - 0.05% (3)
should be - 0.05% (3)
level of - 0.05% (3)
by the - 0.05% (3)
have made - 0.05% (3)
all microformats - 0.05% (3)
these are - 0.05% (3)
in their - 0.05% (3)
to see - 0.05% (3)

- 0.05% (3)
properties and - 0.05% (3)
the first - 0.05% (3)
in and - 0.05% (3)
microformats community - 0.05% (3)
seven years - 0.05% (3)
standards organization - 0.05% (3)
their work - 0.05% (3)
know that - 0.05% (3)
the public - 0.05% (3)
domain / - 0.05% (3)
number of - 0.05% (3)
microformats as - 0.05% (3)
about the - 0.05% (3)
html5
the past year - 0.11% (6)
element as a - 0.07% (4)
each of these - 0.05% (3)
here are a - 0.05% (3)
public domain / - 0.05% (3)
the public domain - 0.05% (3)
some of the - 0.05% (3)
parses an element - 0.05% (3)
all of these - 0.05% (3)
in microformats 2 - 0.05% (3)
to the new - 0.04% (2)
url or photo - 0.04% (2)
is that a - 0.04% (2)
— for example - 0.04% (2)
a person or - 0.04% (2)
parsing microformats 2 - 0.04% (2)
microformats 2 and - 0.04% (2)
to be the - 0.04% (2)
a few people - 0.04% (2)
as a technology, - 0.04% (2)
structured data on - 0.04% (2)
for this entry - 0.04% (2)
every microformats specification - 0.04% (2)
an open revision - 0.04% (2)
the microformats wiki - 0.04% (2)
the html5

Here you can find chart of all your popular one, two and three word phrases. Google and others search engines means your page is about words you use frequently.

Copyright © 2015-2016 hupso.pl. All rights reserved.
FB | +G | Twitter

Hupso.pl jest serwisem internetowym, w którym jednym kliknieciem możesz szybko i łatwo sprawdź stronę www pod kątem SEO. Oferujemy darmowe pozycjonowanie stron internetowych oraz wycena domen i stron internetowych. Prowadzimy ranking polskich stron internetowych oraz ranking stron alexa.