[Fwd: Re: [Ietf-caldav] iCal to XML Schema mapping proposal]

The requirement for an XSD schema per se is interesting.

Maybe I/we could do something with GRDDL quickly...

-- 
Dan Connolly, W3C http://www.w3.org/People/Connolly/
D3C2 887B 0F92 6005 C541  0875 0F91 96DE 6E52 C29E

Forwarded message 1

  • From: Doug Royer <Doug@Royer.com>
  • Date: Mon, 12 Dec 2005 12:21:43 -0700
  • Subject: Re: [Ietf-caldav] iCal to XML Schema mapping proposal
  • To: ietf-caldav@osafoundation.org
  • Message-ID: <439DCDC7.70709@Royer.com>
The XML representation of calendaring discussion is taking place
on xcal@inet-consulting.com. And that might be the best place
to discuss XML and calendaring.

The http://inet-consulting/mailman/admindb/xcal sign up page
is working. The web site is having some problems - working on that now.


Zbarcea, Hadrian wrote:
> Hi,
> 
> I would like to propose an XML Schema Mapping for the iCalendar format
> (RFC2445).
> 
> Calendars and scheduling information are an extremely important aspect
> of any business process.  The need for business process automation is
> increasing.  SOA based architectures are increasingly popular and
> already provide measurable benefits to many companies around the world.
> There is a wide range of use cases involving automated decision making
> that would benefit from calendaring information of resources or people
> participating to a business process being available.
> 
> While RFC2445 is the de facto standard for calendaring data interchange
> it is not well suited for use in SOA and Web Services (WS) which are
> based on XML technologies.  Previous attempts were made to provide such
> mappings (such as xCal -
> http://www.ietf.org/internet-drafts/draft-royer-calsch-xcal-03.txt) but
> they are not sufficient for use in WS (which depend on WSDL and XML
> Schema).  The CalDAV effort is also approaching calendaring data
> interchange from a different perspective from what I could gather.
> 
> A standard mapping of iCalandar to XML is needed and long overdue.
> Based on my research there is nothing to fill the gap.  Please find
> attached an (incomplete) draft of an XML Schema.  
> 
> There are 2 types that need to be mapped: VTimeZoneType and VAlarmType.
> I will finish them in the coming days.  There are probably other details
> to be sorted out and I am looking forward to any feedback you might
> have.
> 
> Please let me know if your group has an interest in incorporating this
> schema or if you have any suggestion about how it could be used.
> 
> Thank you,
> 
> Hadrian Zbarcea
> Senior Engineer
> IONA Technologies
> 200 West St, #400
> Waltham, MA 02451
> (781) 902-8322
> 
> 
> 
> 
> ------------------------------------------------------------------------
> 
> _______________________________________________
> Ietf-caldav mailing list -- Ietf-caldav@osafoundation.org
> See http://ietf.webdav.org/caldav/ for more CalDAV resources
> http://lists.osafoundation.org/mailman/listinfo/ietf-caldav

-- 

Doug Royer                     | http://INET-Consulting.com
-------------------------------|-----------------------------

               We Do Standards - You Need Standards
_______________________________________________
Ietf-caldav mailing list -- Ietf-caldav@osafoundation.org
See http://ietf.webdav.org/caldav/ for more CalDAV resources
http://lists.osafoundation.org/mailman/listinfo/ietf-caldav

Received on Monday, 12 December 2005 19:34:21 UTC