OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

emergency-msg message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: RE: [emergency-msg] RE: FW: [emergency] HAVE comments


Title: [emergency-msg] RE: FW: [emergency] HAVE comments
All day Friday is out for me. I can be available Monday or early Tuesday.
 
Patti


From: Rex Brooks [mailto:rexb@starbourne.com]
Sent: Wed 9/20/2006 1:54 PM
To: Tim Grapes; 'Rex Brooks'; 'Sukumar Dwarkanath'; 'Tom Merkle'
Cc: emergency-msg@lists.oasis-open.org
Subject: [emergency-msg] RE: FW: [emergency] HAVE comments

On that basis, I would be willing to have a session dedicated to
these last details of HAVE.

Fri, Mon and early Tuesday (Pacific Time) work for me.

Cheers,
Rex

At 2:07 PM -0400 9/20/06, Tim Grapes wrote:
>If you want to schedule one additional session, I'm sure we can use the DM
>conference line.
>
>1-800-320-4330  # 327547
>
>Tim
>
>
>-----Original Message-----
>From: Rex Brooks [mailto:rexb@starbourne.com]
>Sent: Wednesday, September 20, 2006 11:56 AM
>To: Sukumar Dwarkanath; rexb@starbourne.com; Tom Merkle; Tim Grapes
>Subject: Re: FW: [emergency] HAVE comments
>
>Hi Sukumar,
>
>My thinking is that we should revisit this in the 60-day comment
>period because we would not have time in the next SC meeting, which
>is next Thursday in the late afternoon, Eastern Time. The EDXL_RM
>specification is going to be quite large compared to our previous
>efforts, and I am doubtful that we will be able to get through that,
>let alone that plus HAVE.
>
>However, I could be persuaded to consider it provided we had a
>separate session, and not another long distance charge. I am in the
>process of changing my telephone service yet again and I have to
>schedule at least one one-hour pilot group meeting next week in
>addition to the Thursday slot. I will be switching to Vonage for
>these kinds of calls, but that won't kick in until after next week at
>the soonest.
>
>Regards,
>Rex
>
>At 11:16 AM -0400 9/20/06, Sukumar Dwarkanath wrote:
>>Given that additional work is required on HAVE and the draft needs
>>to change, should we discuss these issues as well and resolve them?
>>
>>Sukumar
>>
>>
>>-----------------------------------------------------
>>This communication is intended for the use of the recipient to which
>>it is addressed, and may contain confidential, personal and/or
>>privileged information. Please contact us immediately if you are not
>>the intended recipient of this communication, and do not copy,
>>distribute, or take action relying on it. Any communication received
>>in error, or subsequent reply, should be deleted or destroyed.
>>
>>
>>
>>
>>From: Renato Iannella [mailto:renato@nicta.com.au]
>>Sent: Sunday, September 03, 2006 9:26 PM
>>To: Emergency Mgt XML TC
>>Subject: [emergency] HAVE comments
>>
>>
>>Some technical comments on EDXL-HAVE 1.0 CD:
>>
>>1 - LocationCountryName is defined as an integer - should be string (line
>261)
>>
>>2 - LocationPostalCodeID is defined as an integer, but some
>>countries (eg UK) use non-integers.
>>
>>3 - Should we reuse the OASIS CIQ spec for all the
>>org/address/location elements???
>>(since they have solved all the I18N issues)
>>
>>4 - EMSOffloadMinutes has a max of 60 - will it never exceed this?? (line
>283)
>>
>>5 - ServiceCoverageStatus  - all its subelements have one of two
>>string values (available/unavailable)
>>        This could be replaced with an xsd:boolean type instead.
>>
>>6 - Surgery  - all its subelements have one of two string values
>>(available/unavailable)
>>        This could be replaced with an xsd:boolean type instead.
>>        NOTE: I assume the example (lines 1504-1514) is not correct as
>>the elements have no values?
>>
>>7 - If there is no <Bed> element under <BedCapapcity>, then I assume
>>the numbers are the total for the hospital?
>>       Otherwise, there should only be one <Bed> inside <BedCapacity>?
>>
>>8 -  Is there a document that formally defines the GEO-OASIS specification?
>>
>>
>>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.
>
>
>--
>Rex Brooks
>President, CEO
>Starbourne Communications Design
>GeoAddress: 1361-A Addison
>Berkeley, CA 94702
>Tel: 510-849-2309
>
>--
>No virus found in this incoming message.
>Checked by AVG Free Edition.
>Version: 7.1.405 / Virus Database: 268.12.5/451 - Release Date: 9/19/2006
>
>
>--
>No virus found in this outgoing message.
>Checked by AVG Free Edition.
>Version: 7.1.405 / Virus Database: 268.12.5/451 - Release Date: 9/19/2006
>


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

IEM CONFIDENTIAL INFORMATION PLEASE READ OUR NOTICE:
http://www.iem.com/e_mail_confidentiality_notice.html



[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]