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


Help: OASIS Mailing Lists Help | MarkMail Help

humanmarkup message

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

Subject: [huml] RE: [huml-comment] Request for a motion on PC-33 -Section4.4.6-r ace

Title: Message
I am casting my own vote to yes, remove the term "race" from physicalDescriptor--based on the posts, it really isn't a specific description of a physical characteristic, but the result of a derivation of other characteristics.  It certainly has predefined codelists in existence, but there isn't a universally accepted definition, so it might as well be best be derived from the primary, which would obligate it to be explicitly defined.
It feel it think it does belong in the PBS however, which is why I hesitated.  However, that doesn't mean that race is also a primary, primordial, fundamental personal identity we would like to often communicate.  It isn't necessary a cultural characteristic, but a means of personal identity that is at the core of how many of us define ourselves.  To be able to communicate or embody the "black experience living in America" for example really is experience not about culture or any specific physical description, but something transcendent.  In the ideal world, possibly we wouldn't define our core self based on our race, but that is how we communicate, and a concept we would want to communicate, now.
I'm posting to both groups, as it occurred during the public comments group.
Ranjeeth Kumar Thunga
-----Original Message-----
From: Rex Brooks [mailto:rexb@starbourne.com]
Sent: Monday, December 09, 2002 12:14 PM
To: Bullard, Claude L (Len); 'James Landrum'; Ranjeeth Kumar Thunga
Cc: humanmarkup-comment@lists.oasis-open.org
Subject: RE: [huml-comment] Request for a motion on PC-33 -Section 4.4.6-r ace

I want to make a slight clarification. We are only voting to remove the attribute race from the attributeGroup physicalDescriptors. What, if anything, it ought to be replaced with is a different issue.

From what Len made clear during the discussions is that the attribute, where needed, can be used as part of a set of properties extended from the complexType Sign in the Secondary Base Schema or in a subsequent application-area schema.


At 9:55 AM -0600 12/9/02, Bullard, Claude L (Len) wrote:
Ethnicity has a different meaning from race in the public safety databases
and it is probably more restrictive than what one might think.
Both race and ethnicity are context-dependant codelist signs.
Ethnicity - Hispanic, non-Hispanic, blank
Odd, eh?  Again, used mainly for statistics collection in this
particular application.   The problem is that there
is no definition for these that does not depend on a collection
of contexts being assigned and initialized.    These contexts
can be derived from the primary.
From: http://www.state.ma.us/msp/cru/Spb98-4nov.htm , Massachusetts:
"Revisions to the Standards for the Classification of Federal Data on Race and Ethnicity
On October 30, 1997, the Office of Management and Budget (OMB) published in the Federal Register revised standards concerning the administrative reporting of statistics as they pertain to race and ethnicity. The revised standards will have five minimum categories for data on race: American Indian or Alaska Native, Asian, Black or African American, Native Hawaiian or Other Pacific Islander, and White. In order to identify individuals of mixed race, a form must allow for the marking of more than one race category. Additionally, there will be two categories for data on ethnicity: AHispanic or Latino@ and ANot Hispanic or Latino.@ The OMB advised that data collectors should comply with these changes as soon as possible, but no later than January 1, 2003. Currently, a number of alternatives are being explored by the FBI and the UCR Program.
During a teleconference held September 28, representatives of the OMB, Department of Justice (DOJ), and the CJIS Division discussed multiresponse racial categories for the forms used by the UCR Program. >From this meeting, the following decisions were reached.
A form representing aggregate information (i.e., Age, Sex, and Race of Persons Arrested [ASR] form) does not require a multiresponse racial category. Instead, a sixth category, in addition to the five types of races listed in the OMB=s revision, called AMore than one race@ may be included on the form. Since NIBRS will collect ethnicity data, the ethnicity categories of AHispanic or Latino@ and ANot Hispanic or Latino@ will not be addressed on the ASR form which will eventually be phased out.
A form collecting information at the incident level (i.e., Supplementary Homicide Report, Analysis of Law Enforcement Officers Killed or Assaulted, and forms for NIBRS) should provide for the ability to respond to more than one racial category. Therefore, forms in this category will need to be revised.
Further information about revising UCR forms to comply with OMB=s new standards for race and ethnicity will be provided as it becomes available."
-----Original Message-----
From: James Landrum [mailto:James.Landrum@ndsu.nodak.edu]

My vote:

Delete "race"  replace with  "ethnicity."

Rex Brooks
Starbourne Communications Design
1361-A Addison, Berkeley, CA 94702 *510-849-2309
http://www.starbourne.com * rexb@starbourne.com

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

Powered by eList eXpress LLC