representative-hcard-formats: Difference between revisions

From Microformats Wiki
Jump to navigation Jump to search
mNo edit summary
 
Line 3: Line 3:
Examples of formats for indicating representative person info about pages that represent individual people.  Part of the [[representative-hcard]] effort.
Examples of formats for indicating representative person info about pages that represent individual people.  Part of the [[representative-hcard]] effort.


== formats ==
== FOAF autodiscovery ==
=== FOAF autodiscovery ===
In <cite>[http://lists.usefulinc.com/pipermail/foaf-dev/2002-December/004677.html foaf link rel syntax - for linking to one's foaf from homepage]</cite> on Thu Dec 12 00:44:28 UTC 2002, Dan Brickley proposed:
In <cite>[http://lists.usefulinc.com/pipermail/foaf-dev/2002-December/004677.html foaf link rel syntax - for linking to one's foaf from homepage]</cite> on Thu Dec 12 00:44:28 UTC 2002, Dan Brickley proposed:



Latest revision as of 23:07, 20 March 2008

representative hCard formats

Examples of formats for indicating representative person info about pages that represent individual people. Part of the representative-hcard effort.

FOAF autodiscovery

In foaf link rel syntax - for linking to one's foaf from homepage on Thu Dec 12 00:44:28 UTC 2002, Dan Brickley proposed:

<link rel="meta" type="application/rdf+xml" title="FOAF" href="foaf.rdf" />

for linking from a page that represents an individual to info about that person in a separate resource "foaf.rdf" in the same directory as the current page. Dan clarifies:

If we stick with the convention of a link title of "FOAF", we can get away with not worrying too much about defining an html profile for rel="meta".

BTW I'd also recommend we encourage folk to use the filename foaf.rdf

From this we infer the key elements of this format are:

  • MUST link element in the head of the document
  • MUST type="application/rdf+xml"
  • MUST rel-meta - meta value on the rel attribute
  • MUST title="FOAF"
  • SHOULD href="foaf.rdf"

Some problems with this approach:

  • requires use of the link element and thus write access to the head of the document
  • meta rel value is too generic, and doesn't really mean "person", or "representative"

FOAF primaryTopic

FOAF also has a facility for specifying the primary topic for a page.

<link rel="foaf:primaryTopic" href="#somehcard" />

For people without access to the <head> of a page, an <a> element could be used instead.

see also