>>> Both FOAF and vCard have unstructured personal name properties >>> (foaf:name and v:fn) that address this. >> >> But vCard required both N and FN, so if you only have FN, you can't get an N >> without a lot of dictionary-based domain knowledge and special rules. (Or >> you can make a GIGO N...) > > Hmm ... that's not how it's implemented in hcard.
It is, actually. hCard requires both FN and N, but allows N to be implied by FN in some cases. http://microformats.org/wiki/hcard#Implied_.22n.22_Optimization Ted
