RE: [huml-comment] Request for a motion on PC-33 -Section 4.4.6-r ace

["Aerts, John F." <jfaerts@lasd.org>]

Title: Re: [huml-comment] Request for a motion on PC-33 -Sect

Attached for your consideration, in your endevors, are the Codes for Race and Sex that the  CA State (CJIS) and Federal (NCIC) systems use. (Real world)

 

As you can see the Federal Government and the states don't agree. In fact some of the state systems are not the same.

 

I am only sending the state codes from California but it is possible for each state (CJIS) to have its own version and translate to the Federal (NCIC) prior to forwarding to them.

 

Not to mention that local government entities have there records managment system (RMS) with their own codes that they translate for whatever system they report to. That is how you get your National Crime Statistics for/from the FBI.

 

John

 

Lieutenant John Aerts
Los Angeles County Sheriff's Department
Records & Identification Bureau

Information Systems Advisory Body (ISAB)
Los Angeles County
Consolidated Criminal History Reporting System (CCHRS)
Project Manager

Phone   562 465 7876
Fax       323 415 2666
E-mail   Aerts@lasd.org

 

-----Original Message-----
From: Bullard, Claude L (Len) [mailto:clbullar@ingr.com]
Sent: Thursday, December 05, 2002 7:02 AM
To: 'Rex Brooks'; Ranjeeth Kumar Thunga; humanmarkup-comment@lists.oasis-open.org
Subject: RE: [huml-comment] Request for a motion on PC-33 -Section 4.4.6-r ace

I'm not sure "derived" is exactly right.   If in fact, one can't say it is a physical

characteristic native to an instance, one can say it can be created as a sign

whose prototypical properties (in the Sowa sense of a prototype as a set

of properties that taken together, determine set membership) are derivable

from HumanML primary types.   Using the example I provided earlier,

 

Race:

 

A = Asian
B = Black
I = Indian
W = White
U = Unknown

 

one sees a term followed by a codelist.   What HumanML could provide

would be a set of properties for the term, race, which could then be used

to make a selection from that set given an instance.   That set might

include rules or might be a simple prototype such as slots with values for physical

characteristics common to members of the set, historical origins, and so on.

(In practice, this is hard to do, but I think that difficulty itself is valuable

in focusing the community of interest's use of the term; that in fact,

the real value of the term will decline.)

 

Note:  the same approach would apply to declaring prototypes for

races of trolls, woodland, plains, mountain, or otherwise.   So this

is not special pleading, but precisely how HumanML is intended

to be used.

 

Thanks to Dennis for pointing this one out.  It provides a good

example of how HumanML can be applied to a term of contention

such that typical users of the term can clarify precisely how

this term is defined below the level of the initial codelist.

 

len

 

 

-----Original Message-----
From: Rex Brooks [mailto:rexb@starbourne.com]

 I would prefer a stronger reason than that it simply can be shown to be non-objective despite current usages, and it can be derived from the existing PBS in a secondary schema, and it can be imported or declared from other interoperable resources. Those are sufficient, but not compelling reasons, whether reapplicable or not.

 

Attachment: race.pdf
Description: Binary data

Attachment: sex.pdf
Description: Binary data