- From: ryan king <ryan@theryanking.com>
- Date: Tue, 5 Dec 2006 14:43:11 -0800
On Dec 5, 2006, at 2:11 PM, Elias Torres wrote: > There's plenty of documentation/code/test cases for *specific* > microformats but no general rules for let's say additional fields > in an > hCard. Let me know if I'm missing any other documentation or overall > principle in microformats. You're not missing anything. There is no documentation for "additional fields in an hCard". There is no extensibility mechanism for individual microformats because it's not necessary. If you want to create a new vocabulary to use along with hCard, just start using it in your markup. If it becomes popular enough, you might be able to get it added to hCard (if it ever in the future diverges from a 1:1 mapping from vCard). -ryan > ryan king wrote: >> On Dec 4, 2006, at 11:04 PM, Elias Torres wrote: >>> If you can read in the uF wiki [1] there's really not much >>> guidance on >>> how to parse >>> one or all of them. >> >> There is more documentation than you suggest. See [1], which >> documents >> how to parse hcards. Much of the hCard parsing guideline apply more >> generally (extracting those common bits is on my todo list). >> >> Also, please note that we have a suite of test cases. The stable and >> agreed upon ones are here [2] and you can see work in progress in our >> mercurial repository [3]. >> >> -ryan >> >> 1. http://microformats.org/wiki/hcard-parsing >> 2. http://microformats.org/tests/ >> 3. http://hg.microformats.org/tests/ >>
Received on Tuesday, 5 December 2006 14:43:11 UTC