[uf-discuss] Simplifying hierarchy in hCard

[Scott Reynen]

On Mar 29, 2006, at 4:59 PM, Ryan King wrote:

> The problem with this is that it throws out the advantages that  
> unique root class names give us, namely, context. If we flatten the  
> hierarchy, we greatly constrain our vocabulary, which we have  
> enough trouble managing, as is.

I don't see the difference as being between a flat vs. hierarchical  
structure, but rather between a hierarchy defined in the hcard spec  
and a hierarchy defined by the XHTML document itself.  No one is  
suggesting "vcard" shouldn't be the container of "fn", but some are  
suggesting that this should be assumed by parsers even when not  
explicit in the structure of the XHTML.  So the FAQ answer should  
probably explain why we want to take advantage of the existing  
hierarchy of the XHTML, e.g. because XHTML parsers already exist to  
read this content as a hierarchy.

Peace,
Scott