MHonArc v2.5.0b2 -->
emergency message
[Date Prev]
| [Thread Prev]
| [Thread Next]
| [Date Next]
--
[Date Index]
| [Thread Index]
| [List Home]
Subject: RE: [emergency] FW: Suggestion: Add incidentKeyword to contentObject
I would agree with Renato, except that I know of no operational
implementations of the DE, other than the WAY previous and much
different implementation (2 years ago) that ComCARE implemented and DMIS
(and others) prototyped. Those changes were the basis for what we
previously had out for comment so the "substantive change does not
apply. In the meantime, there are LOTS of implementations (including
ours) that have been put on hold waiting for a completed voting draft to
come out that can be used in an operation prototype. The pent up
frustration is getting pretty serious. Perfection IS the enemy of good
enough.
Respectfully,
Gary A. Ham
Senior Research Scientist
Battelle Memorial Institute
540-288-5611 (office)
703-869-6241 (cell)
"You would be surprised what you can accomplish when you do not care who
gets the credit." - Harry S. Truman
-----Original Message-----
From: Renato Iannella [mailto:renato@nicta.com.au]
Sent: Monday, January 30, 2006 6:45 PM
To: Elysa Jones; Emergency_Mgt_TC TC
Cc: Rex Brooks; Tim Grapes
Subject: Re: [emergency] FW: Suggestion: Add incidentKeyword to
contentObject
On 31 Jan 2006, at 04:05, Elysa Jones wrote:
> I don't think anyone on the TC is interested in going back for a 60-
> day review at this point in the EDXL-DE. If anyone feels strongly the
> other way with respect to this change, please let me know.
Not that I feel strongly about it, but we should be aware that the OASIS
TC process defines "Substantive Change" as:
"a change to a specification that would require a compliant
application or
implementation to be modified or rewritten in order to remain
compliant."
This is undoubtedly the case for the current version of EDXL-DE.
Cheers... Renato Iannella
National ICT Australia (NICTA)
------------------------------------------------------------------------
--
This email and any attachments may be confidential. They may contain
legally privileged information or copyright material. You should not
read, copy, use or disclose them without authorisation. If you are not
an intended recipient, please contact us at once by return email and
then delete both messages. We do not accept liability in connection with
computer virus, data corruption, delay, interruption, unauthorised
access or unauthorised amendment. This notice should not be removed.
---------------------------------------------------------------------
To unsubscribe from this mail list, you must leave the OASIS TC that
generates this mail. You may a link to this group and all your TCs in
OASIS
at:
https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php
[Date Prev]
| [Thread Prev]
| [Thread Next]
| [Date Next]
--
[Date Index]
| [Thread Index]
| [List Home]