We're doing a group code-sprint to build an events aggregator for
Portland Oregon at http://calagator.org . This is to try provide a
single point of presence that comprehensively tracks all the regional
events.
We've successfully been able to scan both upcoming and eventful for
hCal information - getting the venue, the time, a description and
facts like that.
However one of the challenges we're facing is plucking out location
information - which we are not finding well expressed in hcal
instances in the wild. Our strategy is two-fold: We will brute force
or special case parse websites with events that don't (or refuse to)
comply with any kind of standard, but we do want to encourage a
standard, and parse whatever standards we can find.
It looks like there is another microformat called 'vcard' which has
some of this. I am going to look at this next. Both upcoming and
eventful use vcard to store some location information, but in the case
of eventful it doesn't seem to be as precise as upcoming. { Clearly
in the case of eventful we can always use their evdb api but we see
this as a good test case of other cases we will have to tackle. }
Is there some standard that most or even some fraction greater than
say 10% of the sites publishing events subscribe to?
Leaving georss out of this question for now - clearly we'll consume
that in the cases where we see it - and encourage it.
a
_______________________________________________
Geowanking mailing list
[email protected]
http://lists.burri.to/mailman/listinfo/geowanking
