ical and geo/location (was Re: A Japanese ...)

Hi, I've been thinking about geo and iCal for a while.

>    <Vevent>
>      <location>New York, Sheraton Hotel</location>
>      <geo>
>	<geo:Point>
>            <geo:lat>40.442673</geo:lat> <!--invented GPS coords-->
>            <geo:long>-79.945815</geo:long>
>	</geo:Point>
>      </geo>
>...

Adding geo: vocabulary to RDFical data is very welcome. But I wonder geo
coordinates are better to be associated with location (or Place), rather
than event itself. So, how about

<Vevent>
 <location rdf:parseType='Resource'>
  <dc:title>New York, Sheraton Hotel</dc:title>
  <geo:lat>40.442673</geo:lat>
  <geo:long>-79.945815</geo:long>
 </location>
 ...
</Vevent>

If we want to add some information on NY Sheraton (not the event) such as
url of the Hotel homepage or photo of the hotel, this can be extended as:

<Vevent>
 <location rdf:parseType='Resource'>
  <dc:title>New York, Sheraton Hotel</dc:title>
  <geo:lat>40.442673</geo:lat>
  <geo:long>-79.945815</geo:long>
  <foaf:homepage rdf:resource="..."/>
  <foaf:depiction rdf:resource="..."/>
 </location>
 ...
</Vevent>

And if, say, 10 events in a calendar will be held at the same place, we can
write simply

<Vevent>
 <location rdf:nodeID="aaa"/>
 ...
</Vevent>
<ex:Place rdf:nodeID="aaa">
 <geo:lat>...
 ...
</ex:Place>

without repeating the same information on the place.

Hmm.., but this requires the change of range of <location>, and "changing
the range of properties could cause problems" as Morten noted... then, is
it better to use <geo> of ical for this structured description (not a good
fit name, but is not defined in the schema yet) ?

I prefer using <location> for structured description, if possible.

cheers,

-- 
KANZAKI, Masahide a.k.a. masaka
http://kanzaki.com/info/webwho.rdf
mailto:webmaster(at)kanzaki.com
#Please use above address for a personal mail
#instead of post@kanzaki.com, which is for list only.

Received on Tuesday, 11 November 2003 09:06:21 UTC