Released php-mf2 v0.2.9 with GPG signed tags and verification guide (blogpost coming soon), hProduct backcompat support. packagist.org/packages/mf2/mf2#v0.2.9 github.com/indieweb/php-mf2#v029
Released php-mf2 v0.2.9 with GPG signed tags and verification guide (blogpost coming soon), hProduct backcompat support. packagist.org/packages/mf2/mf2#v0.2.9 github.com/indieweb/php-mf2#v029
@sophiedennis you might find something of interest on microformats.org/wiki/cite esp. examples, also h-cite microformat in active use (there’s at least one on this page :)
Working on #shrewdness I’m coming to realise that there are at least two usefully distinct levels of semantic data on the web:
There’s the basic “object” level at which microformats act, defining simple, basic-level objects like posts and people with properties like name
, phone
and content
.
Then there’s the level at which HTML works, marking up blocks of text and creating a tree of elements, each of which gives context to the text it contains, for example blockquote
elements for containing content from another source, code
elements for “computer code” (might be some space to make that more useful — who’s up for adding the type
attribute to code
?) and so on.
So what? So these are the two sufficiently standardised levels at which content on the web can be made portable, and mutually understood by many parties. Any additional undefined semantics introduced by author-defined classnames and the meaning communicated by their default styling is unportable, and will be lost when that content is viewed elsewhere (for example shown in a reader or as a cross-site comment.
So how can you tell if your content is sufficiently portable? For the object-level (microformats) a validator like indiewebify.me can be used. Strangely, there aren’t as many tools for the markup level, but one surefire way to check is to disabled CSS in your browser. Is your content still understandable using only the default styles? If so it’s probably pretty portable.
Released php-mf2 v0.2.7 with contributions from @aaronpk and @gregorlove — some small new features and plenty of bugfixes in this release, available now from Packagist or Github
Initial draft of a #taproot logo:
Got stuck for inspiration (trees are cliché and, in the UK, ironically associated with the conservatives) so looked on wikipedia, and found this beautiful photo by Stephen Ausmus:
So made a stylised version for a laugh, and actually really like it. It shares some colours with the indiwebcamp logo
whilst remaining stylistically separate and visualises a lot of #indieweb principals: a centralised node split up into a more diverse ecosystem, but still connected by the green strands of standards (many of which are #microformats, also associated with the colour green).
Still a WIP though — thoughts?
php-mf2 users: requesting your feedback for Mf2\fetch()
microformats-from-URL function just added to dev-master. I want to get this nice and polished before adding it to a versioned release, and would appreciate feedback, specifically on the documentation and debugging support.
@ricard_dev depends exactly what you want to mark up — if marking up a book in a product listing, try microformats.org/wiki/h-product. If actually marking up a book (e.g. HTML ebook) then you could use h-entry for each chapter or something. Hop in #microformats on freenode IRC if you need any more assistance :)
Thoughts about #microformats whilst reading Lakoff’s Women, Fire and Dangerous Things — mf vocabularies e.g. h-card, h-entry, h-event are basic-level categories, the level at which:
E.g. h-entry ≈ “post”
Rather than RDF or schema.org which seek to create pure, objectivist, hierarchies of categories — our brains simply don’t work like that.
@dshanske your notes are looking great, and very nicely marked up too! You should consider marking up comments as h-cites nested as p-comment properties — more: indiewebcamp.com/comments-presentation#How_to_markup
Learned about the XHTML Enemies Network http://xen.adactio.com/ from @briansuda #xfn #microformats #html
Documented a bunch of experimental h-entry properties w/ examples microformats.org/wiki/h-entry, it’s growing more and more expressive yet remaining concise and memorable, down to extensive intense #indieweb selfdogfooding.
Also documented a bunch more #microformats2 adoption examples in the wild. Not on the list? Add yourself! Want to join the party? Getting started is easy!
Last night: built #indieweb commenting on posts direct from my feedreader using #micropub #indieauth #webmention #microformats — video demo:
Example replies sent using this technique: 1, 2
Next up: cleaning code, implementing likes, distilling learnt knowledge into diagrams, code.
Futher reading:
Query microformats2 like XPath — @notenoughneon created this nifty function for handling #microformats data more easily
@tomayac for example like this?
<a class="h-card h-org">Hypothetica Inc.</a>
php-mf2 gives
{
"items": [
{
"type": [
"h-card",
"h-org"
],
"properties": {
"name": [
"Things"
]
}
}
],
"rels": [
]
}
which is correct, one microformat with multiple vocabularies, which effectively allows multiple vocabularies to be mixed, e.g. you can have a h-review which is also an h-entry.
@bromann all the interesting work being done in the indiewebcamp.com community (e.g. cross-site comments are being done with mf2, and they’re easier to author+more clearly documented than classic mf, so makes a lot of sense to start using now!
@bromann even better (and easier!), add microformats2 h-card microformats.org/wiki/h-card, validate with indiewebify.me/validate-h-card
#idea: a microformat for download signatures/checksums, allowing browsers to automatically verify files without people having to go into the terminal and use shasum
or gpg --verify
@frimmin people are indeed using microformats, classic docs are still majority of the wiki but mf2 vocabs all documented microformats.org/wiki/microformats2#v2_vocabularies, open source microformats.org/wiki/parsers available, validation tools e.g. indiewebify.me
A lot of microformats activity in the indiewebcamp.com community enabling things like cross-site comments/likes/reposts/rsvps, link previews, autodiscovery, feed readers just beginning development.
@_aitor “apps/repositories” not specific or user-focused enough to base improvements/requirements on — what is the data being *used* for, in terms of the people using the UIs you want to build?
E.G. do you want people to be able to search based on ingredient(s)? Or find only recipes which can be made within time available? Or to offer a UI to convert quantities into units the cook is more familiar with? Or to scale quantities depending on the number of people the cook is making food for?
@_aitor what is the use case and how does h-recipe fail to address it? #microformats IRC on freenode is a better place to discuss it than twitter