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

 


Help: OASIS Mailing Lists Help | MarkMail Help

emergency-if message

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


Subject: Groups - edxl-de-v2.0-csprd03_withExtensions2.zip uploaded


Submitter's message
A few cleanup issues were identified at our IF meeting yesterday and fixes incorporated into this update to the DE 2.0. These changes were: (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. Thanks to Brian for helping to identify the issues and to Rex as well for helping to resolve them.
-- Jeff Waters
Document Name: edxl-de-v2.0-csprd03_withExtensions2.zip

Description
(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.
Download Latest Revision
Public Download Link

Submitter: Jeff Waters
Group: EM Infrastructure Framework SC
Folder: Requirements
Date submitted: 2013-05-22 09:12:35
Revision: 1



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