This article is a stub. You can help the IndieWebCamp wiki by expanding it.
On the IndieWeb, you are your URL and your URL is you. With a well-designed indieweb site, as humans we can discover all the information you choose to share about yourself.
This page is for documenting and brainstorming ways to discover that same information automatically by following a combination of semantic markup and algorithms.
Typical IndieWeb sites have profile and often contact information right there on the home page.
Best publishing practice: mark it all up with hCard, especially your hyperlinks to other profiles with class="u-url url" and rel="me". This will create a representative hCard which can then be used by other sites.
Examples in the wild:
Best parsing practice: when given an indieweb URL that represents a person, parse it for a representative hCard and use that hCard for information about that person. Details:
Separate Contact Page
Some IndieWeb sites have contact information on a separate page from the home page, but linked from the home page. While such links may be obvious to humans, e.g. with text labels like "Contact" or "About", it's not at all obvious to parsers where to find more information.
Examples of sites with separate contact/about pages:
Most Indie web sites have updates on their home page, a stream of updates as it were, e.g.:
Best Parsing Practice: parse the given URL for hAtom (and preferably microformats2 h-entry).
Others have a simple intro/contact page as their home page, and provide updates at another URL, e.g.:
To discover information about a post on a post permalink page:
To find the POSSE copies of an original post, on that original post's permalink page:
To find an original post from a POSSE'd copy, on that POSSE'd copy's permalink page:
Real Time Updates
... rel=hub ... on link to PuSH hub for your updates.
For an improved Salmon key-discovery flow (i.e. not using DRY-violating XRD files and web-breaking email-like identifiers) we need to expose public keys somehow.
Public key exchange was also discussed at the IndieWeb dinner on November 1st, 2013, in the context of this in-person using QR codes. Potentially the QR code could simply be a URL pointing to the user's website, where a public key could be extracted from microformat encoding.
Help or About
HTML has the rel="help" value, but it's not clear that it conveys the "about" kind of resources you link to.
There are bunch of legacy discovery methods that are worth documenting, in case you want to interoperate with legacy systems that depend on them.
... rel=alternate ... type=...+xml ...
We should deprecate separate feeds as