Groups - ws-calendar-schema-v1.0-wd18.zip uploaded

I was not aware that the suggestion was to rename the xcal namsapce.  In effect that means you are running an completely different  specification. I would find it hard to justify my continuing involvement  in what is essentially somebody elses spec. There will continue to be a  specification worked on within the calendar wolrd and that will be the  one that implemnts the IEFT RFC, that is in the ietf namesapce.  Inevitably, the OASIS spec will drift having nothing to moor it to  icalendar.  As I understand it there is a need for a wscalendar namespace and I  approve the naming approach Bill suggested. That should not imply  renaming an ietf spc namespace. After that it's no longer an ietf spec.  On 03/17/2011 06:59 AM, Considine, Toby (Campus Services IT) wrote: > ??? >
> We discussed this last Friday for maybe half the meeting and no objections were raised. >
> In PR01, there was my original icalendar.xsd (completely incompatible with your later work) and a ws-calendar.xsd (completely incompatible with your later work). OASIS process keeps these around as "legitimate" schemas unless we, as a TC, formally say "oops" because "perhaps people have a lot of work that relies upon them" >
> I would assert that there is no such work, and that we should use the current schemas, and their heirs, as the work. >
> As to the namespace change, that was in Bill Cox's paper that was the first agenda item last week. We need a formal vote to direct OASIS staff. > > > "It is the theory that decides what can be observed."
- Albert Einstein >
> Toby Considine
> Chair, OASIS oBIX Technical Committee
> U.S. National Inst. of Standards and Tech. Smart Grid Architecture Committee
> Facilities Technology Office
> University of North Carolina
> Chapel Hill, NC >
>
Email: Toby.Considine@ unc.edu
>
Phone: (919)962-9073
>  http://www.oasis-open.org
> blog: www.NewDaedalus.com > > >