Title: Re: [emergency] Groups - EDXL HAVE Comments (EDXL_HAVE_IssuesList_v4.6.xls) uploaded
Rex,
Obviously, its a long email to respond...
You are making quite a few assumptions that are not correct. I did not imply that this should not be done in a group nor that everything should be done in a single vote - obviously, that's impractical.
I am not sure I understand the logic of not compiling all the comments first - we have done that as a first step for all the standards and I hope we continue to follow that process.
Finally, just putting all the comments on a spreadsheet is a non trivial issue - my opinion is that it will be easier to have all comments at one place - clearly, you can track everything since they will be related and may have been discussed before. You can easily track issues that were past the approval - the date column should help you with it. And you can filter the column to see the open issues. If you want to create a separate spreadsheet, please do so.
I am happy to discuss - I was not aware that you were discussing it in the SC nor recollect being mentioned in the last TC meeting. As I mentioned in my email, the spreadsheet would be a starting point for the discussions.
Sukumar
-----Original Message-----
From: Rex Brooks <>
To: Dwarkanath, Sukumar - INTL; <>
Sent: Fri Mar 06 17:44:27 2009
Subject: Re: [emergency] Groups - EDXL HAVE Comments (EDXL_HAVE_IssuesList_v4.6.xls) uploaded
Hi Sukumar,
We in the EM-Msg SC were going through the 28 (37 if you count the
lettered sub issues) issues submitted by the NIMS Support Center
after EDXL-HAVE was approved as an OASIS Standard.
We were considering only those and going through them one by one
without putting them into a spreadsheet yet so that we could make a
recommendation to the TC on how to resolve these post-approval
issues, e.g. an Errata or a v1.1.
I'm a little confused by including these new issues with the issues
resolved before the approval process. I know we didn't take this
work on as an SC, but we wanted to address them as part of addressing
both RM and HAVE so that the NIMS Support Center folks would know
that their concerns with both were being addressed. Obviously we did
not know that you were compiling them into a spreadsheet or taking
personal responsibility to propose resolutions.
We should probably take this up in the TC. I would feel a lot better
if this were done by a group rather than just one person. Also, as
diligent and careful as you are, I think there are just too many to
accept them as a group with some kind of single vote on all at once.
I think each resolution needs to be processed through a group.
For instance, the DOM is more than difficult to read, it is not
sufficiently legible and needs to be redone, regardless of the fact
that the schema is normative. To be honest, even if few of these
issues warrants a revision, until a group has gone through them one
by one, I won't have enough confidence to recommend either an Errata
or v1.1.
So I think we should discuss how to address these issues in the next
TC meeting. I would appreciate it if we could have only the new open
issues in a separate spreadsheet.
Cheers,
Rex
At 9:59 PM +0000 3/6/09, wrote:
>I have added the comments from NIMS SC and have reviewed it. As a starting
>point, I have provided a proposed resolution for each comment which we can
>discuss and finalize. All the comments are editorial in nature and I think
>can be fixed with an errata.
>
> -- Sukumar Dwarkanath
>
>The document named EDXL HAVE Comments (EDXL_HAVE_IssuesList_v4.6.xls) has
>been submitted by Sukumar Dwarkanath to the OASIS Emergency Management TC
>document repository.
>
>Document Description:
>List of comments on EDXL-HAVE
>
>View Document Details:
>http://www.oasis-open.org/committees/document.php?document_id=31572
>
>Download Document:
>http://www.oasis-open.org/committees/download.php/31572/EDXL_HAVE_IssuesList_v4.6.xls
>
>
>PLEASE NOTE: If the above links do not work for you, your email application
>may be breaking the link into two pieces. You may be able to copy and paste
>the entire link address into the address field of your web browser.
>
>-OASIS Open Administration
--
Rex Brooks
President, CEO
Starbourne Communications Design
GeoAddress: 1361-A Addison
Berkeley, CA 94702
Tel: 510-898-0670
