[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: RE: [emergency-rim] Reminder: Meeting Today
Thanks Tom, Hi Everyone, I was just about to send out another reminder about today's meeting and decided to let this reply do double duty. Just to let you know what my personal agenda is going forward. This time of year the holidays come galloping into our lives and we get caught up in the annual syndrome of the northern hemisphere, e.g. party/visit/socialize through New Year's and fall into hangover hibernation until spring. Of course this year we get the extra added incentive of a sour economy from which escaping into our regular revelry is a welcome distraction, and those of us not sufficiently distracted by that have the transition to the next administration to keep us occupied. Regardless we have our yearly perfect productivity storm. However, for us, provided I can manage to stay in OASIS now that EDXL-RM and EDXL-HAVE have achieved Approval as Standards, I'd like to make some quiet progress on EDXL-RIM, so I'm going to suggest we move to weekly meetings after the holidays, suspend the need for quorum to get regular work done, and shoot for getting our first workproducts into first Public Review Drafts by spring. I made workproducts and drafts plural so that we can break our projects up into chunks individuals can take on for the purpose of developing first drafts and then first Public Review Drafts, such as EDXL-DE Principles, EDXL-DE scenario samples, with one each for CAP, EDXL-RM and EDXL-HAVE and EDXL Methodologies (e.g. typing practices, DOMs, ValueListURNs, Keywords). Since none of these needs to be large, and certainly should not start that way, we can start with outlines that the SC can discuss and adopt before the actual writing starts. Hopefully, no one need face a Task-Too-Big. Lastly, I would suggest that these initial workproducts ought to be concrete not abstract, but can then provide us with a set of documents based in concrete methods, techniques and examples from our existing standards from which we can synthesize abstract information models in a systematic process, rather than the other way around. Cheers, Rex >Rex, >I've got a LMCO meeting scheduled for today and will not be on the RIM call. >Regards, >Tom > >-----Original Message----- >From: Rex Brooks [mailto:rexb@starbourne.com] >Sent: Wednesday, November 05, 2008 6:53 PM >To: emergency-rim@lists.oasis-open.org >Subject: [emergency-rim] Reminder: Meeting Tomorrow > >Hi Everyone, > >I wanted to send out a reminder of our meeting tomorrow. Also, just >in case I forget, or get caught up in one of the projects hanging >fire, and haven't shown up in the first five minutes, I wanted to ask >that whomever happens to be at the meeting on time give me a ring. My >number is in my signature. > >The work is important and has been hanging fire, too. Also, now that >EDXL-RM and EDXL-HAVE have made it to Standard Status, there are two >less distractions, and two more reasosn to get EDXL-RIM in high gear. > >Cheers, >Rex >-- >Rex Brooks >President, CEO >Starbourne Communications Design >GeoAddress: 1361-A Addison >Berkeley, CA 94702 >Tel: 510-898-0670 > >--------------------------------------------------------------------- >To unsubscribe from this mail list, you must leave the OASIS TC that >generates this mail. Follow this link to all your TCs in OASIS at: >https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php -- Rex Brooks President, CEO Starbourne Communications Design GeoAddress: 1361-A Addison Berkeley, CA 94702 Tel: 510-898-0670
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]