"Lowde, Chris A" wrote: > > There is a slight problem with the following statement: > > Then the server says, "OK, 19970105 is a Sunday; is the day being > asked about a Sunday?". > > When it is Sunday in Houston, it could well, and for 6 hours, 5 for 1 week > in April, will be, Monday in London. > > When the calendar user is traveling and is looking at a calendar that is > housed in TimeZone1, is currently in TimeZone2 and is looking at an event > for a time when they are in TimeZone3 the issue of who is expanding what > becomes non-trivial. In general it should be done by the server which will > be the only system that will have all the information about the user on > which to base the expansion. The proposal in CAP is that CUAs ask for times in UTC. And the server would dish out the correct replies. If the CUA wishes to know the original timezones, then it MUST ask for TZID and fetch the approiate VTIMEZONE data from the CS. So in a sense your are correct. The CS must understand timezones. So John's email is still correct in that the CS can fetch the data given the search criteria. I think the debate is, does a CS: 1) Only return un-expanded components? 2) Only return expanded components - with some limit? 3) Only return components expanded by request. Default un-expanded. 4) Only return components un-expanded by request. Default expanded. If we get concensus on one of these, then the issue is how do we ask? I would like to see a poll with responses: 1-YES, 1-NO, 1-ABSTAIN 2-YES, 2-NO, 2-ABSTAIN 3-YES, 3-NO, 3-ABSTAIN 4-YES, 4-NO, 4-ABSTAIN And of cource any examples on how to ask the CS given the CAP ~language~. I would say: 1-NO, 2-NO, 3-YES, 4-NO -Doug
begin:vcard n:Royer;Doug tel;pager:650-274-8960 or pager@Royer.com tel;cell:650-274-8960 tel;home:650-274-8960 tel;work:805-957-1790 x541 x-mozilla-html:FALSE url:http://Royer.com/People/Doug version:2.1 email;internet:doug@home.royer.com adr;quoted-printable:;;801 Woodside Rd. #14=0D=0ASuite 244;Redwood City;CA;94061;USA x-mozilla-cpt:;0 fn:Doug Royer end:vcard
Attachment:
smime.p7s
Description: S/MIME Cryptographic Signature