[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: RE: [emergency] FW: Updated EDXL Comments spreadsheet
Please add the attached issues I forwarded to the group last week. Thanks, Tim Grapes Evolution Technologies, Inc. DHS Disaster Management egov Initiative Office: (703) 654-6075 Mobile: (703) 304-4829 firstname.lastname@example.org email@example.com -----Original Message----- From: Rex Brooks [mailto:firstname.lastname@example.org] Sent: Tuesday, December 06, 2005 8:53 AM To: email@example.com; firstname.lastname@example.org Subject: Fwd: [emergency] FW: Updated EDXL Comments spreadsheet Hi Sylvia, Everyone, Dave sent this out during our last meeting. I believe it is the latest version of the issues list with all of the dispositions. I hope Julia's notes can clear up the resolution of Renato's issues as much as we can settle those, because he was working without the issues list dispositions, particularly the three sensor message types. Perhaps someone can help with my teflon memory on Renato's questions. I believe we may not be able to answer them until we have a version of the schema with the missing message types and anything else that may have been missed due to not having the complete dispositions on the last issues list. Ciao, Rex >Mailing-List: contact email@example.com; run by ezmlm >X-No-Archive: yes >List-Post: <mailto:firstname.lastname@example.org> >List-Help: <mailto:email@example.com> >List-Unsubscribe: <mailto:firstname.lastname@example.org> >List-Subscribe: <mailto:email@example.com> >Delivered-To: mailing list firstname.lastname@example.org >X-Server-Uuid: 914ACFB1-8EBC-470E-882B-54A00EED9786 >Date: Tue, 29 Nov 2005 10:42:44 -0700 >Thread-topic: Updated EDXL Comments spreadsheet >Thread-Index: AcXjy7umnuSY82vsR46Orb4z7K07AgRQHPIg >From: "Ellis, David" <email@example.com> >To: firstname.lastname@example.org >X-WSS-ID: 6F924C931FO2373515-01-01 >Subject: [emergency] FW: Updated EDXL Comments spreadsheet >X-Rcpt-To: <email@example.com> >X-DPOP: Version number supressed > >ALL > >This is what Tom sent out. > >David E. Ellis >Information Management Architect >(505) 844-6697 > > >From: Tom Merkle [mailto:TMerkle@capwin.org] >Sent: Monday, November 07, 2005 11:48 AM >To: Elysa Jones; Ellis, David; Art Botterell; firstname.lastname@example.org; >email@example.com; Rex Brooks; Julia Ridgely; >firstname.lastname@example.org >Subject: Updated EDXL Comments spreadsheet > >Here's the final from today's marathon meeting. Please review the >resolution sections carefully. > >Regards, > >Tom Merkle > >CapWIN: <http://www.capwin.org/>www.capwin.org >Phone: (301) 614-3720 >Cell Phone: (240) 375-1966 >Fax: (301) 614-0581 >e-mail: <mailto:email@example.com>firstname.lastname@example.org > >CapWIN >6305 Ivy Lane Suite 300 >Capital Office Park >Greenbelt, MD 20770 > > >Content-Type: application/vnd.ms-excel; > name="EDXL_DE_Issues_11-07-05 Rev 01.xls" >Content-Description: EDXL_DE_Issues_11-07-05 Rev 01.xls >Content-Disposition: attachment; > filename="EDXL_DE_Issues_11-07-05 Rev 01.xls" > > >--------------------------------------------------------------------- >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 -- Rex Brooks President, CEO Starbourne Communications Design GeoAddress: 1361-A Addison Berkeley, CA 94702 Tel: 510-849-2309
--- Begin Message ---
- From: "Tim Grapes" <email@example.com>
- To: <firstname.lastname@example.org>
- Date: Tue, 29 Nov 2005 15:10:29 -0500
This has been raised before, but I suggest we add this to the DE issues list for discussion and formal disposition.
ISSUE 1 - Multiple payloads / distribution types
DE can carry multiple payloads, and I just now see a change that shows that DistributionType can be one or MANY as it should be (so that different payloads in the same DE may have different distrType). E.g. A DE with 2 payloads – one payload may be a “response” and the other be a “request”. This is a valid requirement, but then requires a way to associate distibutiontype(s) with different payloads. There are also other business needs to relate together multiple payloads within the same distribution.
- Formalize a business rule where payloads must always have the same DistributionType. Otherwise, separate messages must be created for each, or
- How to associate things to payloads? Perhaps add an element to the DE contentObject segment called something like "contentID", providing a unique way to identify each payload?
ISSUE 2 – Incident Identifier and Description 1 or many?
Same issue as above. If the business rule above is implemented, then multiple payloads within a DE need to be related to the same incident. Otherwise, need a way to relate Incident ID’s and Desc’s with each payload (the “contentObject” thought above?).
No virus found in this incoming message. Checked by AVG Free Edition. Version: 7.1.362 / Virus Database: 267.13.8/184 - Release Date: 11/27/2005--- End Message ---