updates to http://www.w3.org/2002/12/cal/

I've been making all the iCalendar files in /test compliant by adding
vTimeZone parts, changing tzid to
/softwarestudio.org/Olson_20011030_5/. This was to fix a bug with some
files missing a timezone description in the file. iCalendar requires
this - see my notes:

http://esw.w3.org/t/view/ESW/RdfCalendarTimeZoneNotes

I regenerated all the rdf versions of the files using my java version
of ical2rdf:

http://www.ilrt.bris.ac.uk/discovery/2003/02/cal/
http://www.ilrt.bris.ac.uk/discovery/2003/02/cal/readme.txt

and added a few new ones for the the last meeting and the next one, and
the opening hours testcase:

http://lists.w3.org/Archives/Public/www-rdf-calendar/2003Mar/0014.html

More details about what I did and some notes are below.

cheers

Libby

------

Adding the timezones information to the ics files may lead to an issue
with two different X namespaces (the Olsen iCalendar timezones I am
using are generated by Evolution, and have

X-LIC-LOCATION:Europe/London

in them
while the original Apple ical files had

X-WR-TIMEZONE

and various other X-WR-* propoerties).

We could remove some or other of the x-properties, but another
possiblity occured to me:

[[
It is recommended
   that vendors concatenate onto this sentinel another short prefix text
   to identify the vendor.
]]
RFC 2445, 4.8.8.1 Non-standard Properties

- I didn't implement that, but could do.

MozexportAsCalendar.ics was ok -

[[
Description: The parameter MUST be specified on the "DTSTART",
   "DTEND", "DUE", "EXDATE" and "RDATE" properties when either a DATE-
   TIME or TIME value type is specified and when the value is not either
   a UTC or a "floating" time.
]]
RFC 2445  - 4.2.19 Time Zone Identifier

bus-hrs.ics was ok anyway, as is cal01.ics

added 'Z's to gkexample.ics - for UTC


Noted an oddity in mtg.ics:

X-WR-TIMEZONE;VALUE=TEXT:US/Eastern

rather than (say)
America/New_York

althpough apple uses
X-WR-TIMEZONE;VALUE=TEXT:Europe/London

I also added RDF checking to my makefile (using Jena)

2 warnings from

20030122mtg.rdf and
20030115mtg.rdf

[[
      <valarm rdf:parseType='Resource'>
        <attach rdf:resource='Ping'/>
          <trigger rdf:parseType='Resource'>
            <duration>-PT5M</duration>
          </trigger>
          <action
rdf:resource='http://www.w3.org/2002/12/cal/ical#audio'/>
        </valarm>
]]

Warning:
file:/Users/libby/working/java-calendar/mimedir-parser/test/generatedrdf/20030115mtg.rdf[30:38]:
{W107} Bad URI <Ping>: Cannot apply relative URI to an opaque URI
Warning:
file:/Users/libby/working/java-calendar/mimedir-parser/test/generatedrdf/20030122mtg.rdf[40:38]:
{W107} Bad URI <Ping>: Cannot apply relative URI to an opaque URI

Received on Tuesday, 25 March 2003 09:53:15 UTC