Ok, that makes more sense then ... Thanks for clarifying that. I guess looking at the ISO standards would be in order - seems like it's already been thought out in detail.
Joshua Miller Head Programmer / IT Manager Garrison Enterprises Inc. www.garrisonenterprises.net [EMAIL PROTECTED] (704) 569-9044 ext. 254 ************************************************************************ ************* Any views expressed in this message are those of the individual sender, except where the sender states them to be the views of Garrison Enterprises Inc. This e-mail is intended only for the individual or entity to which it is addressed and contains information that is private and confidential. If you are not the intended recipient you are hereby notified that any dissemination, distribution or copying is strictly prohibited. If you have received this e-mail in error please delete it immediately and advise us by return e-mail to [EMAIL PROTECTED] ************************************************************************ ************* -----Original Message----- From: Matt Liotta [mailto:[EMAIL PROTECTED]] Sent: Wednesday, January 15, 2003 3:29 PM To: CF-Talk Subject: RE: RE: How to handle Calendar Scheduling of Recurring Events? I didn't mean to imply that the pattern would be plain English. I was simply using English to describe what an example pattern might be. Matt Liotta President & CEO Montara Software, Inc. http://www.montarasoftware.com/ 888-408-0900 x901 > -----Original Message----- > From: Erik Yowell [mailto:[EMAIL PROTECTED]] > Sent: Wednesday, January 15, 2003 3:12 PM > To: CF-Talk > Subject: RE: RE: How to handle Calendar Scheduling of Recurring Events? > > >I'm trying to grasp Matt's concept of a "pattern" field. How > you would > >parse it actually, I understand patterns, just not how to > allow for as > >many variables as could exist with plain English as > opposed to some type > >of codes. > > > >Matt, if you've got any more in-depth info on how you parse > a pattern > >like: "First Monday of January from 2003 to 2015 Except > January 14 2008 > >which will be rescheduled to January 15 2008" then I'd > appreciate a > >glimpse into how you're accomplishing that. > > There is logic in the pattern concept. That's what standards like ISO > 8601/RFC 2445 were built for. Though I don't know if/and what kind of > parser exists for it. For example (taken from > http://www.idealliance.org/papers/xml2001/papers/html/05- > 04-06.html ) > > The 3rd instance into the month of one of Tuesday, > Wednesday or Thursday, for the next 3 months: > > DTSTART;TZID=US-Eastern:19970904T090000 > RRULE:FREQ=MONTHLY;COUNT=3;BYDAY=TU,WE,TH;B > YSETPOS=3 > > Nasty looking rule, but there's a whole slew of standards, exceptions, > notations, etc to describe everything from gregorian to julian to > japanese calendar dates. Also, I think ISO 8601-2000 Draft has a set > of rules and notations that's even more compact (all though barely > human readable at > all) Drop a recurrence rule or pattern in one column, find (or > make) a parser for it based on reverse enginering the > specs, and voila. > > Erik Yowell > [EMAIL PROTECTED] > http://www.shortfusemedia.com > > > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Archives: http://www.houseoffusion.com/cf_lists/index.cfm?forumid=4 Subscription: http://www.houseoffusion.com/cf_lists/index.cfm?method=subscribe&forumid=4 FAQ: http://www.thenetprofits.co.uk/coldfusion/faq Structure your ColdFusion code with Fusebox. Get the official book at http://www.fusionauthority.com/bkinfo.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4
