← Prev in month ← Prev in thread
Next in thread → Next in month →

FW: [members] EDXL-HAVE v1.0 Submitted for OASIS Standard

From
Duane Nickull <>
Date
2008-10-03T23:55:00+00:00
ID
Thread
FW: [members] EDXL-HAVE v1.0 Submitted for OASIS Standard
Title: FW: [members] EDXL-HAVE v1.0 Submitted for OASIS Standard

Congratulations to Rex and others who worked hard on this!

Duane

-- 

**********************************************************************

Senior Technical Evangelist - Adobe Systems, Inc.

Duane's World TV Show - http://tv.adobe.com/#pg+1537

Blog - http://technoracle.blogspot.com

Community Music - http://www.mix2r.com

My Band - http://www.myspace.com/22ndcentury

**********************************************************************

------ Forwarded Message

From: Mary McRae <>

Organization: OASIS

Reply-To: <>

Date: Fri, 3 Oct 2008 16:40:11 -0700

To: <>

Subject: [members] EDXL-HAVE v1.0 Submitted for OASIS Standard

OASIS Members:

The OASIS Emergency Management Technical Committee has submitted the

following specification, which is an approved Committee Specification, to be

considered as an OASIS Standard:

Emergency Data Exchange Language (EDXL) Hospital AVailability Exchange

(HAVE) Version 1.0

The text of the TC submission is appended.

You now have until 15 October to familiarize yourself with the submission

and provide input to your organization's voting representative.

On 16 October, a Call For Vote will be issued to all Voting Representatives

of OASIS member organizations. They will have until the last day of October,

inclusive, to cast their ballots on whether this Committee Specification

should be approved as an OASIS Standard or not.

Members who wish to discuss this ballot may do so through

.

In accordance with the OASIS Technical Committee Process, this Committee

Specification has already completed the necessary 60-day public review

period as noted in the submission below.

The normative TC Process for approval of Committee Specifications as OASIS

Standards is found at

http://www.oasis-open.org/committees/process-2008-06-19.php#OASISstandard

Any statements related to the IPR of this specification are posted at:

http://www.oasis-open.org/committees/emergency/ipr.php

Your participation in the review and balloting process is greatly

appreciated.

Mary

-----------------------------------------------------------

Mary P McRae

Director, Technical Committee Administration

OASIS: Advancing open standards for the information society

email:  

web: www.oasis-open.org

phone: 1.603.232.9090

-----------------------

OASIS EM TC - OASIS

Standard Submission

(a)Links to the approved Committee Specification in the TC's document

repository, and any appropriate supplemental documentation for the

specification

Editable Source (Microsoft Word):

http://docs.oasis-open.org/emergency/edxl-have/cs01/emergency_edxl_have-1.0-

spec-cs01.doc

HTML:

http://docs.oasis-open.org/emergency/edxl-have/cs01/emergency_edxl_have-1.0-

spec-cs01.html

PDF:

http://docs.oasis-open.org/emergency/edxl-have/cs01/emergency_edxl_have-1.0-

spec-cs01.pdf

Schemas:

http://docs.oasis-open.org/emergency/edxl-have/cs01/edxl-have-cs01.xsd

(b) The editable version of all files that are part of the Committee

Specification;

See "editable source" links for item (a)

(c) Certification by the TC that all schema and XML instances included in

the specification, whether by

inclusion or reference, including fragments of such, are well formed, and

that all expressions are valid;

TC so certifies.

(d) A clear English-language summary of the specification;

EDXL-HAVE specifies an XML document format that allows the communication of

the status of a hospital, its services, and its resources. These include bed

capacity and availability, emergency department status, available service

coverage, and the status of a hospital's facility and operations.

(e) A statement regarding the relationship of this specification to similar

work of other OASIS TCs or other

standards developing organizations;

No similar efforts

(f) The Statements of Use presented above;

From ESi:

http://lists.oasis-open.org/archives/emergency/200804/msg00015.html

From NuParadigm:

http://lists.oasis-open.org/archives/emergency/200808/msg00014.html

From Evolution Technologies:

http://lists.oasis-open.org/archives/emergency/200808/msg00004.html 

(g) The beginning and ending dates of the public review(s), a pointer to the

announcement of the public review(s), and a pointer to an account of each of

the comments/issues raised during the public review period(s), along with

its resolution;

Public review start March 17, 2008; Public Review end April 1, 2008.

Public review announcement:

http://lists.oasis-open.org/archives/tc-announce/200803/msg00008.html

Public review comments raised and resolution:

No public comments submitted

Public Review start 19 October 2007, end December 18 2007

Public Review announcement:

http://lists.oasis-open.org/archives/tc-announce/200710/msg00009.html

Comment Resolution log:

http://www.oasis-open.org/committees/download.php/27017/EDXL_HAVE_IssuesList

_v4.5.xls

(h) An account of and results of the voting to approve the specification as

a Committee Specification, including the date of the ballot and a pointer to

the ballot;

Committee Specification Approval Ballot:

http://www.oasis-open.org/committees/ballot.php?id=1445

(i) An account of or pointer to votes and comments received in any earlier

attempts to standardize

substantially the same specification, together with the originating TC's

response to each comment;

Not applicable (no such earlier standardization attempts or votes)

(j) A pointer to the publicly visible comments archive for the originating

TC;

http://lists.oasis-open.org/archives/emergency-comment/

(k) A pointer to any minority reports delivered by one or more Members who

did not vote in favor of

approving the Committee Specification, which report may include statements

regarding why the member voted against the specification or that the member

believes that Substantive Changes were made which have not gone through

public review; or certification by the Chair that no minority reports exist.

Chair certifies that no minority reports exist.

---------------------------------------------------------------------

This email list is used solely by OASIS for official consortium communications.

Opt-out requests may be sent to , however, all members are strongly encouraged to maintain a subscription to this list.

------ End of Forwarded Message
← Prev in month ← Prev in thread
Next in thread → Next in month →