hcard-tests: Difference between revisions
Jump to navigation
Jump to search
(note recent work on test repository, hg repository) |
m (Replace <entry-title> with {{DISPLAYTITLE:}}) |
||
| (11 intermediate revisions by 7 users not shown) | |||
| Line 1: | Line 1: | ||
{{DISPLAYTITLE: hCard tests }} | |||
== newest tests == | |||
From [[test-suite]]: | |||
* http://ufxtract.com/testsuite/hcard/ | |||
* http://ufxtract.com/testsuite/geo/ | |||
* ... | |||
== previous mercurial tests == | |||
[http:// | The [http://microformats.org/tests/ hcard and hcalendar tests collection] was announced in a [http://microformats.org/discuss/mail/microformats-dev/2006-June/000102.html Jun 7 2006 message] from [http://theryanking.com/ RyanKing]. | ||
They are published at http://microformats.org/tests/hcard/. Each test has an HTML file to parse and a vCard file which describes the hCard data contained in the HTML file. | |||
These | It's managed in [http://hg.microformats.org/tests/ an hg repository]. [http://www.selenic.com/mercurial/ hg/mercurial] is a distributed revision control system. It can be a little tricky to unlearn cvs habits; there are some good diagrams in [http://www.selenic.com/mercurial/wiki/index.cgi/Presentations?action=AttachFile&do=get&target=google.pdf slides from a 19 Jun talk that Bryan O'Sullivan gave at google]. The [http://www.selenic.com/mercurial/wiki/index.cgi/Presentations mercurial presentations page] also has a link to a 50 minute video. | ||
An [http://hg.microformats.org/x2v/ x2v hg repository] holds code that, by design, passes the tests. [[x2v-issues]] is a place to track issues | |||
in that code. | |||
== even older external tests == | |||
These <span id="External_Tests">external tests</span> have been obsoleted by the above test suites. | |||
DanConnolly is working on [http://dev.w3.org/cvsweb/2001/palmagent/hcardTest.html hcardTest.html]; [http://dev.w3.org/cvsweb/~checkout~/2001/palmagent/hcardTest.html?rev=HEAD&content-type=text/html;%20charset=iso-8859-1 the current version] is always available. (I dunno why cvsweb uses the ordinary looing URL for the changelog rather than the current version.) | DanConnolly is working on [http://dev.w3.org/cvsweb/2001/palmagent/hcardTest.html hcardTest.html]; [http://dev.w3.org/cvsweb/~checkout~/2001/palmagent/hcardTest.html?rev=HEAD&content-type=text/html;%20charset=iso-8859-1 the current version] is always available. (I dunno why cvsweb uses the ordinary looing URL for the changelog rather than the current version.) | ||
MarkPilgrim maintains a series of [http://diveintomark.org/projects/greasemonkey/hcard/tests/ hCard tests] for use with his [http://diveintomark.org/projects/greasemonkey/hcard/ hCard parser] | MarkPilgrim maintains a series of [http://diveintomark.org/projects/greasemonkey/hcard/tests/ hCard tests] for use with his [http://diveintomark.org/projects/greasemonkey/hcard/ hCard parser] | ||
== Related Pages == | |||
{{hcard-related-pages}} | |||
Latest revision as of 16:26, 18 July 2020
newest tests
From test-suite:
previous mercurial tests
The hcard and hcalendar tests collection was announced in a Jun 7 2006 message from RyanKing.
They are published at http://microformats.org/tests/hcard/. Each test has an HTML file to parse and a vCard file which describes the hCard data contained in the HTML file.
It's managed in an hg repository. hg/mercurial is a distributed revision control system. It can be a little tricky to unlearn cvs habits; there are some good diagrams in slides from a 19 Jun talk that Bryan O'Sullivan gave at google. The mercurial presentations page also has a link to a 50 minute video.
An x2v hg repository holds code that, by design, passes the tests. x2v-issues is a place to track issues in that code.
even older external tests
These external tests have been obsoleted by the above test suites.
DanConnolly is working on hcardTest.html; the current version is always available. (I dunno why cvsweb uses the ordinary looing URL for the changelog rather than the current version.)
MarkPilgrim maintains a series of hCard tests for use with his hCard parser
Related Pages
- hCard
- hCard cheatsheet - hCard properties
- hCard creator (feedback) - create your own hCard.
- hCard authoring - learn how to add hCard markup to your existing contact info.
- hCard examples - example usage of various classes within hCard.
- hCard examples in the wild - an on-going list of websites which use hCards.
- hcard-supporting-user-profiles - sites with user profiles marked up with hCard - a very common example.
- hCard FAQ - if you have any questions about hCard, check here.
- hCard implementations - websites or tools which either generate or parse hCards.
- hCard parsing - normative details of how to parse hCards.
- hCards and pages - semantic distinctions between different hCards on a page, and how to identify each
- hcard-user-interface - techniques and issues surrounding user-interfaces to author, publish, and display hCards.
- hCard profile - the XMDP profile for hCard
- hCard singular properties - an explanation of the list of singular properties in hCard.
- hCard tests - a wiki page with actual embedded hCards to try parsing.
- hCard advocacy - encourage others to use hCard
- hCard "to do" - jobs to do
The hCard specification is a work in progress. As additional aspects are discussed, understood, and written, they will be added. These thoughts, issues, and questions are kept in separate pages.
- hCard brainstorming - brainstorms and other explorations relating to hCard.
- hcard-parsing-brainstorming - brainstorming specific to parsing of hCard
- geo brainstorming
- hCard feedback - general feedback (as opposed to specific issues).
- hCard issues - specific issues with the specification.
- vCard errata - corrections to the vCard specification, which underlies hCard.
- vCard suggestions - suggested improvements to the vCard specification.