I am hoping we can review the National Information Exchange Model (NIEM -
www.niem.gov)and see if the data dictionary (objects, entities and
definitions) could potentially be adopted as part of the RIM...I have a lot
more information on this - I'll try to put something together.
Thanks,
Lee
'We the unwilling, led by the unknowing have been doing the difficult with
little for so long that we are now ready to tackle the impossible with
nothing.' -- Local Fire communications reserve volunteer motto
Original Message-----
From: Ron Lake [mailto:rlake@galdosinc.com]
Sent: Sunday, March 25, 2007 12:29 PM
To: Rex Brooks; Renato Iannella; Karen Robinson
Cc: emergency@lists.oasis-open.org
Subject: RE: [emergency] EDXL-Reference Information Model
Hi Renato:
IS there somewhere a list of the types of things (objects/entities) to
be covered by the Reference Information Model? A classification of these
objects/entities?
Cheers
Ron
Original Message-----
From: Rex Brooks [mailto:rexb@starbourne.com]
Sent: March 25, 2007 9:21 AM
To: Renato Iannella; Karen Robinson
Cc: emergency@lists.oasis-open.org
Subject: [emergency] EDXL-Reference Information Model
Hi Renato, Karen,
I'm writing to get the task of building the EDXL Reference
Information Model started (EDXL-RIM). The TC voted last week to make
this a priority and to spend a large proportion of the upcoming
Face-to=Face meetings at the OASIS Symposium 2007 on establishing
Scope and Requirements. I volunteered to work with you to build a
EDXL Framework or Skeleton document from which we can work in the
meeting to get this effort underway. We are scheduling these
discussion for Afternoon in San Diego, California so that, hopefully,
you can participate as much as possible. I will also be attending via
teleconference, so I expect the pace will necessarily have to
accommodate us. While it is not optimal, it is doable.
I am attaching the Requirments Specification Template as a place to
start. I know my own initial impetus is the same that I consistently
warn other groups about. I feel like I know enough about this family
of specifications from having been involved with it from the start
that I can just jump in and start reeling off requirements, and I
will certainly be making initial suggestions.
However, I think we should eat our own cooking, so I am going to
start with the need to establish clear scope and requirements. I
would like to avoid the temptation to start diagramming information
classes and relationships between these classes for the time being at
least.
Although I am attaching my bare-bones start of a Requirements
Specification, I am including a first pass at the first text section:
**************************
Document Scope and Purpose
This document states the Functional Requirements for the overall
family of Emergency Data Exchange Language specifications. As such,
these requirements should be formulated as the abstract principles
which govern the enumerated elements within the individual
specifications.
For Instance, the Emergency Data Exchange Language Distribution
Element 1.0 Specification (EDXL-DE.Spec_v1.0) specifies