Fwd: Update: Re: Revised RM issues list

[Rex Brooks <rexb@starbourne.com>]

Title: Fwd: Update: Re: Revised RM issues list

> Date: Fri, 4 May 2007 05:36:16 -0700
> To: "Timothy Grapes" <tgrapes@evotecinc.com>,
> "'Rex Brooks'" <rexb@starbourne.com>, "'Aymond,
> Patti'" <patti.aymond@iem.com>, "'Ham, Gary A'"
> <hamg@BATTELLE.ORG>, "'Karen Robinson'"
> <Karen.Robinson@nicta.com.au>,
> emergency-msg@lists.oasus-open.org
> From: Rex Brooks <rexb@starbourne.com>
> Subject: Update: Re: Revised RM issues list
> Cc:
> Bcc:
> X-Attachments:
> Hi Folks,
>
> I finally figured out how to get the Line
> Numbers to work so that we can stay on the same page as we go through
> the document reviewing and responding to the issues list.
>
> I downloaded the untouched "Editable
> Source" again from Mary McRae's official announcement, where the
> Line Numbers start with "1" at
> "introduction."
>
> I will use that document for the Line
> Numbers for all of the issues, except for that "Front Matter"
> section, which is not numbered in the Publicv Review
> version.
>
> Front Matter is a small proportion of the
> 502 issues we have as of now.
>
> I will go back into the first issues we
> dealt with and update the Line Numbers to reflect the correct Line
> Numbersd from the unedited "Editable Source," which will
> remain unedited throughout the process.
>
> That way all of the issues will have one
> single source for the Line Numbers separate from the redline version.
> I will keep the edits of the proposed resolutions we develop in the
> ongoing "redline" version, which will remain separate from
> the original unedited "Editable Source"
> document.
>
> So the unedited "Editable Source"
> will always reflect the correct Line Numbers from the Public Review
> version, and I will send out the redline version at the end, or as
> requested if anyone wishes it or when/if it is necessary for someone
> else to take over the ongoing task of keeping the redline current with
> the progress we make through the comments received and recorded in the
> IssuesList.
>
> I will take the updated IssuesList Tim
> sent out yesterday and add as many of the remaining Issues as I can
> before our next meeting next Thursday, 10 May 2007.
>
> Hopefully I will be able to get them ALL
> recorded so that we can be in synch with the current raw Issues List
> from now on. It may take an all-nighter, but so be it. I don't want to
> make a career out of this and I don't want it hanging over our heads
> (my head).
>
> This way we can keep in synch with the
> updated version of the Issues List (which will get a new filename
> version-number each week) as we go through as many Issues/Comments
> each week.
>
> This should take care of the situation
> and ensure that we don't have a repeat of my frustration yesterday. My
> apologies for that. Back to back face to face meetings the previous
> two weeks can do that to ya. (Merkle and Ellis understand, since they
> also work in the SOA-RM Reference Architecture SC.)
>
> Just as a side note, I really wanted the
> procedure for handling EDXL-RM Issues settled so that we can continue
> work on the EDXL-RIM soon. The Situational Reporting Requirements is
> an issue I hope we can get to soon, but EDXL-RM takes
> priority.
>
> Cheers,
> Rex
>
> At 5:59 PM -0400 5/3/07, Timothy Grapes
> wrote:
> >  
> >  
> > Thanks,
> >  
> > Tim
> >  
> >
> > No virus found in this
> > outgoing message.
> > Checked by AVG Free Edition.
> > Version: 7.5.467 / Virus Database: 269.6.2/785 - Release Date:
> > 5/2/2007 2:16 PM
> > Attachment converted: Macintosh HD:EDXL-RM-CD-v1.0-Issu#26949C.xls
> > (XLS4/«IC») (0026949C)
>
>
> -- 
>  
> Rex Brooks
> President, CEO
> Starbourne Communications Design
> GeoAddress: 1361-A Addison
> Berkeley, CA 94702
> Tel: 510-849-2309

--

Rex Brooks
President, CEO
Starbourne Communications Design
GeoAddress: 1361-A Addison
Berkeley, CA 94702
Tel: 510-849-2309