In message <[EMAIL PROTECTED]>, Brian Suda <[EMAIL PROTECTED]> writes
>--- there currently are parsing rules for singleton instance of >properties. Both hCalendar and hCard can take a GEO property. The first >GEO property found after the root property (vcard or vevent) will be >used as the GEO for that instance. So something like the following code >would NOT get confused: > >- vevent >-- hcard & location >--- geo >-- vcard attendee >--- geo But what if there is no GEO for the location: - vevent -- vcard & location -- vcard attendee --- geo or if the order is reversed on the page: - vevent -- vcard attendee --- geo -- vcard & location --- geo How can we cater for such circumstances? -- Andy Mabbett * Say "NO!" to compulsory UK ID Cards: <http://www.no2id.net/> * Free Our Data: <http://www.freeourdata.org.uk> * Are you using Microformats, yet: <http://microformats.org/> ? _______________________________________________ microformats-discuss mailing list microformats-discuss@microformats.org http://microformats.org/mailman/listinfo/microformats-discuss