humanmarkup message
[Date Prev]
| [Thread Prev]
| [Thread Next]
| [Date Next]
--
[Date Index]
| [Thread Index]
| [Elist Home]
Subject: [humanmarkup] RE: [humanmarkup-comment] First Working Draft ofHM.Requirements
- From: Rex Brooks <rexb@starbourne.com>
- To: "Bullard, Claude L (Len)" <clbullar@ingr.com>
- Date: Tue, 26 Mar 2002 11:18:30 -0800
Title: RE: [humanmarkup-comment] First Working Draft of
HM.Re
Somehow I missed this yesterday. Darn! Sylvia just drew my
attention to it. "...MUST include..." has been changed
to "...MUST be designed to include..." It now reads:
The Primary Base HumanML
Schema MUST be designed to include a HumanIdentifier Element that is
compatible with and interoperable with the U.S. Federal Government
standards, standards accepted by a majority of Public Safety
Institutions, Federal, State and Local Law Enforcement
practices,HR-XML specifications, American Medical Association
standards and any standards so designated by the OASIS HumanMarkup
Technical Committee. Thus, all HumanML modules SHOULD be compatible
with and interoperable with these standards and recommended
practices.
Please refer to my response to Sylvia's comments for the
reasoning I accepted from her comments. The basic idea is to not paint
ourselves into a corner.
Please note that the last sentence uses SHOULD because it is
probably not possible to be completely compatible and interoperable
with all of the systems in all of our modules.
At 1:44 PM -0600 3/25/02, Bullard, Claude L (Len) wrote:
"The Primary Base HumanML Schema MUST include a
HumanIdentifier Element that is compatible with and interoperable with
the U.S. Federal Government standards, standards accepted by a
majority of Public Safety Institutions, Federal, State and Local Law
Enforcement practices,HR-XML specifications, American Medical
Association standards and any standards so designated by the OASIS
HumanMarkup Technical Committee. Thus, all HumanML modules should be
compatible with and interoperable with these standards and recommended
practices."
Beginning at the turn of the last centurythe process
of identification in many public agencies relies not much on
pure physical characteristics (See Bertillon System -
anthropometric identification). It relies typically on
fingerprints and DNA where identification must be absolute. In
other cases, simple processing may rely on a combination of a
current photo and physical characteristics. The process of
identification is typically matched to the need for correct
identification.
There are very precise definitions extant and publicly
available for live scan fingerprint systems and the information they
are required to support. DNA
systems are quite a bit more
complex.
So our human identifier code elements have to
be fairly limited in the primary schema.
Exactly
Physical characteristics for LE systems will
also be a
small set and not nearly as detailed as they would be
for say, medical applications and perhaps even the VR
systems.
Yes, and that is why those systems will have their own schemata,
written to requirements that follow on after this document, and yes,
it doesn't get easier.
Even the seemingly obvious and simple means such as
recording names become complicated if inherited in a module that has a
cultural
component. Anthropometric means are better and
biometric means are best.
That's a problem I don't think we can solve in the primary base
schema. All we can do is prevent ourselves from starting with a set of
elements and attributes that will engender those inheritance problems
at the get go while providing ourselves with enough rope to hang
ourselves with later on down the line. I agree on the anthropometric
and biometric for the identifier add-ons, but I am hoping that we
won't have to deal with that stuff, just go along with it. We need
only add the preferential and behavioral enablers to that, for later
schemata and that is more than enough to chew on.
However, that is a different set of elements than what is
included in the humanIdentifier itself. How we do that, I leave to
you.
len
Someday this will be behind us.
Ciao,
Rex
--
[Date Prev]
| [Thread Prev]
| [Thread Next]
| [Date Next]
--
[Date Index]
| [Thread Index]
| [Elist Home]
Powered by eList eXpress LLC