profile-uris: Difference between revisions
Jump to navigation
Jump to search
m (Reverting to latest revision by DanC) |
AndyMabbett (talk | contribs) m (dab) |
||
| Line 16: | Line 16: | ||
See also: | See also: | ||
* [[profile-examples-in-wild|Profile examples, in the wild]] | * [[profile-uri-examples-in-wild|Profile URI examples, in the wild]] | ||
* [[faqs-for-rdf]] for discussion of connecting microformats to URIs. | * [[faqs-for-rdf]] for discussion of connecting microformats to URIs. | ||
* [[hcard-profile]]. | * [[hcard-profile]]. | ||
Revision as of 09:56, 31 July 2007
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.
See also:
- Profile URI examples, in the wild
- faqs-for-rdf for discussion of connecting microformats to URIs.
- hcard-profile.