profile-uris

From Microformats Wiki
Revision as of 18:37, 20 March 2008 by TobyInk (talk | contribs) (→‎Existing profile URIs: Add profile URIs for a bunch of formats, plus mega-combined-profile)
Jump to navigation Jump to search

Profile URIs

In hcalendar-issues, it is ACCEPTED that each microformat should have a profile URI, like the XFN profile.

Some issues include:

  • what domain to use? Candidates include:
    • microformats.org
    • www.w3.org
    • xmdp.org
  • what about versioning? How to keep in sync with the wiki and test materials?
  • what profile URI to use for combinations, such as hcard and hcalendar?
    • note HTML4.01 states "that one or more meta data profiles, [are] separated by white space"; though it's simpler for authors if they can just use one profile URI.
  • More profiles are needed.

One proposal is: use www.w3.org, following W3C namespace policy. As to versioning, change the profile whenever the wiki changes (within some reasonable latency, say, a couple weeks or a month). For example: an hCard Profile at w3.org, and discussion: an hCard profile that seems to work with GRDDL.

Existing profile URIs

Combined Profile

The following URL covers all non-draft Microformats as of March 2008, except XMDP and XOXO. You can mix and match it with other XMDP profiles for new/draft microformats.

http://purl.org/uF/2008/03/

Individual Microformats

Specification Profile(s)
hCard http://www.w3.org/2006/03/hcard or http://purl.org/uF/hCard/1.0/
hCalendar http://purl.org/uF/hCalendar/1.0/
hAtom http://purl.org/uF/hAtom/0.1/
hResume http://microformats.org/wiki/hresume-profile
rel-tag http://purl.org/uF/rel-tag/1.0/
rel-license http://purl.org/uF/rel-license/1.0/
rel-nofollow http://purl.org/uF/rel-nofollow/1.0/
VoteLinks http://purl.org/uF/VoteLinks/1.0/
XFN http://gmpg.org/xfn/11

Validator warning

Due to inconsistent wording of the HTML specs, HTMLTidy (and other tools?) give "Warning: <head> escaping malformed URI reference" when more than one profile is used, e.g.

<head profile="http://www.ietf.org/rfc/rfc2731.txt http://www.w3.org/2006/03/hcard">

However, this is valid according to the W3C HTML validator.

See also