On 12/5/06, Andy Mabbett <[EMAIL PROTECTED]> wrote:
In "adr", the class "adr" is required, of any oft eh sub-classes are used. In hCard, "adr" is optional, as are its subclasses. Should "adr" be required, if any of its sub-categories are present, in hCard?
--- this is a slightly tricky answer... from a validation point of view, something like this is completely valid HTML and microformats: <div class="vcard"> <div class="fn">foo-bar name</div> <div class="country-name">foo-bar</div> </div> now, a parse would NOT parser the country-name value as part of an address, but it is still valid. If you intend for the country-name to be part of the vcard then it MUST be a child of a class="adr". But if a class="country-name" does exist outside of an ADR, then that does not make ADR required - it could simply mean the publisher has chosen a semantic class name - not intending it to be part of the vcard. So, i guess the short answer is: If a ADR child is present it is NOT manditory to make ADR present, but it will NOT be parsed into a vCard. it will ONLY be considered part of the hCard data IF it is a child of ADR, but neither the ADR or child-property are required. I hope this makes sense and help? -brian -- brian suda http://suda.co.uk _______________________________________________ microformats-discuss mailing list [email protected] http://microformats.org/mailman/listinfo/microformats-discuss
