EM Infrastructure Framework SC Public Documents

Number of Documents Show last documents per workgroup
Document Descriptions
EM Infrastructure Framework SC   (Showing 10 of 282)
Document Name # Size State Submitter Date Action
0
1K
Draft
Jeff Waters
2013-08-26
This comment resolution log entry states that no further comments were received during this latest public review of the DE 2.0 ending on Aug 6, 2013.
0
17K
Draft
Jeff Waters
2013-06-04
At the June 4th, 2013 meeting of the Infrastructure Framework Subcommittee, the members discussed the following topic: 1. TOPIC Should we advance the current DE 2.0 draft for a 15-day public review? (Answer: Yes. The following motion was passed: “I move that that we approve and recommend to the EM TC for advancement for a 15-day public review the DE 2.0 zip https://www.oasis-open.org/apps/org/workgroup/emergency-if/download.php/49304/edxl-de-v2.0-csprd03_withExtensions2.zip which supports community extensions.”) References: (1) Latest DE 2.0 zip: https://www.oasis-open.org/apps/org/workgroup/emergency-if/download.php/49304/edxl-de-v2.0-csprd03_withExtensions2.zip (2) Latest DE 2.0 Basics White Paper (also included in the zip above): https://www.oasis-open.org/apps/org/workgroup/emergency-if/download.php/49303/DE_2.0_Basics_Draft_ver_11b.doc
0
20K
Draft
Jeff Waters
2013-05-24
At the May 21, 2013 meeting of the Infrastructure Framework subcommittee, the members discussed the following topics: 1. TOPIC How should we resolve the four DE 2.0 cleanup issues identified by Brian? (Answer: Brian identified a few cleanup issues with the latest draft of the DE 2.0 after community extensions were incorporated. The issues were resolved as follows: (a) Add the extension element to the DE Envelope; (b) Use EDXLStringType more consistently; (c ) Change the name “DistributionType” to “DistributionKindType”; and (d) for otherContentType, enforce requiring either “uri” or “contentData” or both. All of these changes support the spirit of what was intended originally.) 2. TOPIC Is an additional public review needed? (Answer: Rex will explore this with Elysa and Chet. The recent changes resulted from the addition of community extensions which was raised as a comment during the last public review. ) References: (1) Latest DE 2.0 zip containing fixes discussed at this meeting: https://www.oasis-open.org/apps/org/workgroup/emergency-if/download.php/49304/edxl-de-v2.0-csprd03_withExtensions2.zip (2) Latest DE 2.0 Basics White Paper (also included in the zip above): https://www.oasis-open.org/apps/org/workgroup/emergency-if/download.php/49303/DE_2.0_Basics_Draft_ver_11b.doc
1
1MB
Draft
Jeff Waters
2013-05-22
(This zip file is the latest update to the DE 2.0 with extensions, which incorporates the following cleanup fixes: (a) Added the extension element to the DE Envelope; (b) Used EDXLStringType more consistently; (c) Changed the name “DistributionType” to “DistributionKindType”; and (d) for otherContentType, enforced requiring either “uri” or “contentData” or both. All of these changes support the spirit of what was intended originally.) This zip contains the latest version of the DE 2.0 which includes the schema, examples, specification and DE 2.0 Basics white paper, all updated in the last couple versions with the following changes: (a) all element names begin with lowercase, in accordance with EM TC naming guidance; (b) the community extension mechanism is enabled, utilizing the recommended extension schema edxl-ext-v1.0.xsd as discussed and developed in support of the Tracking of Emergency Patients (TEP) standard; (c) the "choice" mechanism for enabling defaults in the previous version, along with the defaults schema, have been removed in favor of utilizing enumerations in the body of the standard (whenever an element has a reasonable set of default values) and then recommending the use of the community extension mechanism for those users who wish to include community-specific terms. Significant formatting simplification is achieved in the main body of the standard and a tricky namespace issue is avoided by using the extension mechanism.
1
752K
Draft
Jeff Waters
2013-05-22
This updated version of the DE 2.0 Basics white paper received minor updates to the import statements in the appendices to match the latest version of the DE 2.0 zip examples. The paper is intended as a good starting point for folks new to the latest DE, including the extensions update.
0
751K
Draft
Jeff Waters
2013-05-21
This version of the DE 2.0 Basics white paper received minor updates to the import statements in the appendices to match the latest version of the DE 2.0 zip examples. The paper is intended as a good starting point for folks new to the latest DE, including the extensions update.
0
1MB
Draft
Jeff Waters
2013-05-21
(This zip file is the latest update to the DE 2.0 with extensions. Only minor import changes were made to incorporate the latest extension schema.) This zip contains the latest version of the DE 2.0 which includes the schema, examples, specification and DE 2.0 Basics white paper, all updated in the last couple versions with the following changes: (a) all element names begin with lowercase, in accordance with EM TC naming guidance; (b) the community extension mechanism is enabled, utilizing the recommended extension schema edxl-ext-v1.0.xsd as discussed and developed in support of the Tracking of Emergency Patients (TEP) standard; (c) the "choice" mechanism for enabling defaults in the previous version, along with the defaults schema, have been removed in favor of utilizing enumerations in the body of the standard (whenever an element has a reasonable set of default values) and then recommending the use of the community extension mechanism for those users who wish to include community-specific terms. Significant formatting simplification is achieved in the main body of the standard and a tricky namespace issue is avoided by using the extension mechanism.
0
1MB
Draft
Jeff Waters
2013-04-16
As a test, this zip file contains a new version of the DE 2.0 which includes the schema, examples, specification and DE 2.0 Basics white paper, all updated with the following changes: (a) all element names begin with lowercase, in accordance with EM TC naming guidance; (b) the community extension mechanism is enabled, utilizing the EDXLExtension.xsd schema as discussed and developed in support of the Tracking of Emergency Patients (TEP) standard; (c) the "choice" mechanism for enabling defaults in the previous version, along with the defaults schema, have been removed in favor of utilizing enumerations in the body of the standard (whenever an element has a reasonable set of default values) and then recommending the use of the community extension mechanism for those users who wish to include community-specific terms. The purpose of this version is to allow review of how the DE 2.0 would look and work when modified to utilize the community extension mechanism and latest associated guidance. Significant formatting simplification is achieved in the main body of the standard and a tricky namespace issue is avoided.
0
39K
Draft
Jeff Waters
2013-02-26
At the February 26th, 2013 meeting of the Infrastructure Framework Subcommittee, the members discussed the following topics: 1. TOPIC: Do we approve the motion to recommend advancement of the DE 2.0 to committee specification? (Answer: Yes. The motion passed. “No comments have been received and we would like to recommend to the EM TC that we promote the current Public Review Draft of the DE 2.0 (http://docs.oasis-open.org/emergency/edxl-de/v2.0/csprd02/edxl-de-v2.0-csprd02.zip) to committee specification”) References: (1) Committee Specification Public Review Draft of DE 2.0: http://docs.oasis-open.org/emergency/edxl-de/v2.0/csprd02/edxl-de-v2.0-csprd02.zip (2) Extended DE 2.0 Public Review Announcement: https://www.oasis-open.org/news/announcements/extended-public-review-for-edxl-distribution-element-v2-0 (3) DE 2.0 Public Review Announcement: https://lists.oasis-open.org/archives/tc-announce/201211/msg00001.html
0
15K
Draft
Jeff Waters
2012-09-25
At the brief September 25th, 2012 meeting of the Infrastructure Framework Subcommittee, the members discussed the following topics: 1. TOPIC: What are the next steps for advancing our DE 2.0 WD09 to initial public review? (Answer: Once the EM TC minutes are approved, containing the motion from last time to advance the WD09 zip to initial public review, then, as noted afterwards at the EM TC meeting, Jeff can fill out the web forms to request OASIS staff to prepare a Committee Specification Draft and advance it to public review.) 2. TOPIC: When would be a good time to follow up on our conversation regarding the “Layers” extension concept? (Answer: Let's see if we can get folks together at the next RIM meeting on Oct 4.)