Re: Using feeds for time/event data?

["wkearney99" <wkearney99@hotmail.com>]

> - Event name
> - Start time
> - End time
> - Host (organization)
> - Venue
> - Notes
> - URL Link

What's the expected format of each?  Are the expected to be test or 
will you support something like RDF?

Me personally?  I'd like to be able to query a calendar system with 
not only a date range but with location information.  Basically, find 
out not just what's happening, but *where* it's happening.  To find 
out what's happening here in town this weekend, or over near another 
location during a visit three months from now.

It would seem prudent to allow your venue field to support something 
that aided this process.  

The questions is "where" the data is going to get stored.  Is it 
going to be included in your record?  Is it going to get correlated 
at the searching engine and accessed there?  Is it going to exist 
within the URL as meta data?

I'd think a good first step would be to allow for a URL to be 
attached to some of fields.  This would allow the flexibility of 
putting 'more information' about the field inside the referenced 
URL.  Host is one thing, venue is another and the event is a third.  
Each of these could conceivably have their own meta data. 

For example, an event is happening at a given location.  That's one 
location (perhaps the most important).  The event is being sponsored 
by an organization with an office at a different location.  The topic 
is about something relating to specific location (unrelated to the 
venue or the host).  That's three locations, each of which might be 
of interest.  The searcher might want to find out about events put on 
by hosts from a given area.  Or relating to matters in a given area.  
Where the item occurs is not the only element of search interest.

It gets gnarly pretty quickly.  

I'm suggesting you give consideration to allow for URLs for several 
fields.  The next debate would be what meta data should exist at 
those URLs...

-Bill Kearney