W3C home > Mailing lists > Public > www-rdf-calendar@w3.org > October 2001

XML iCal draft changes (fwd)

From: Libby Miller <Libby.Miller@bristol.ac.uk>
Date: Fri, 12 Oct 2001 13:49:46 +0100 (BST)
To: www-rdf-calendar@w3.org
Message-ID: <Pine.GSO.4.21.0110121349160.14060-100000@mail.ilrt.bris.ac.uk>


---------- Forwarded message ----------
Date: Fri, 12 Oct 2001 07:39:18 -0400
From: Eric R. Plamondon <ericp@steltor.com>
To: ietf-calendar <ietf-calendar@imc.org>
Subject: XML iCal draft changes

Good Morning,

The XML iCal draft has recently been resubmitted
through the Calendaring and Scheduling Working Group.


This is only an initial draft to restart (re-ignite?)
the discussion on a possible representation of iCal
in XML. Since the older draft expired, the goal,
with the OK from Patricia Egen and Bob Mahoney, was to
bring the draft back into the discussion, since 
many people have be asking about. The original authors
will be contacted to determine whether they want to 
continue work on the draft.

Having gone through the archives, there were a number 
of issues with the previous drafts. This version does
not attempt to correct them, but rather reopen the
discussion on them.

The goal of the XML DTD (and schema) is to represent
ical in XML. The names, formats, and structures should
be a direct mapping from the iCalendar RPC. It is not
the goal to change or improve on the iCalendar RPC.

There were a few changes made to this reposting,
from the previous draft-many-ical-xmldoc-01 document,
outlined below.

Summary of Changes
- Renamed the file from
- Renamed the document from
	"iCalendar DTD Document"
	"iCalendar DTD Document (xCal)"
- removed references to "ICALXML" and replaced
	with "xCal"
- changed the FPI for the DTD from 
	-//IETF//DTD XCAL/iCalendar XML//EN
- changed the FPI for standard value types from
	-//IETF/NOTATION XCAL/Value Type/xxx/EN
  NOTE: these changes where made to the DTD as well.
- changed all references from 
- changed the iCal namespace to xCal
- changed the proposed MIME type from
- In some of the examples, the <![CDATA[xxx]]>
	xml formatting was removed (the XML version
	of the draft, using the DTD from rfc2629,
	failed to parse properly

Property Parameters
- the following property parameters where change to
	reflect their iCal counterpart
	- delfrom  to delegated-from
	- delto    to delegated-to
	- lang     to language
	- trigtype to related
	- sentby   to sent-by

Component Properties
- the following component properties where change to
	reflect their iCal counterpart
	- desc     to description
	- end      to dtend
	- start    to dtstart
	- fbdata   to freebusy
	- recurid  to recurrence-id
	- related  to related-to
	- last-mod to last-modified
	- seq      to sequence
	- rstatus  to request-status

Structure Properties
- the following structure properties where change to
	reflect their iCal counterpart
	- ical     to vcalendar
	- event    to vevent
	- todo     to vtodo
	- journal  to vjournal
	- freebusy to vfreebusy
	- timezone to vtimezone
	- alarm    to valarm

Issues to be discussed
- should all the names be returned to upper case
	(or named case, as in XML schema).
- there are a few places where attributes are used
	instead of child elements (e.g. in the vCalendar
	element the version, prodid, calscale, and method)
- include an XML schema in this specification
- resolve other errors in the draft document
- correct the differences with "related" and "related-to"
	within the DTD
- does the name "xCal" conflict too much with the
	X-Windows calendar program by the same name
- If the original authors wish to continue work, their
	business information must be updated.
- Provide a wbxml binding for xcal.


Eric R. Plamondon
Steltor - Chief Web Architect
2000 Peel Street, 4th Floor
Montreal, Quebec
Received on Friday, 12 October 2001 08:50:05 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:14:10 UTC