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

 


Help: OASIS Mailing Lists Help | MarkMail Help

ubl-dev message

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


Subject: Re: [ubl-dev] Code vs. Identifier representation types?


Some observations:

(1) Codes are often mnemonic;  e.g., "CH" from the  ISO 3166 Country
Codes means " Confederation Helvetica." "DE" means " Deutschland." And
so on.
(2) But there are what I would call identifiers, such as SCAC  Standard
Carrier Alpha Codes, which are also mnemonic.  For example, "RDWY"
stands for Roadway Express.
(3) My gut feel says ISO 3166 is a code list since it is readily
enumerated and fairly static;  SCACs are identifiers since values are
added and dropped all the time for tens of thousands of entries;  they
cannot be readily enumerated.
(4) Yet other code lists, like ISO 5218 - the "sex" code - are easily
enumerated but not mnemonic (e.g., "1" means "male").
(5) Unintelligent enumeration systems are *always* identifiers;  e.g.,
UPC and EAN "codes" number in the billions.  The vendor part has no
intelligence or meaning, aside from its use as a key into a database to
identify the manufacturer;  likewise, the product number part is
(usually) assigned sequentially by the manufacturer itself.  Another
unintelligent identifier is the CAS Registry Number: there are millions
of chemical substances, each assigned an arbitrary CAS RN.
(6) SSNs and ZIP codes are not completely unintelligent.  But I would
still call them identifiers: they are both hard to enumerate and
constantly changing.  For SSNs, you can tell that someone whose SSN
starts with 299 got her number in Ohio - but that's about all.  SSNs are
a semi-intelligent (or semi-non-intelligent) number, and hence
identifiers.  The same for ZIP codes; you can tell that a ZIP "code"
starting with "432" refers to Central Ohio;  but ZIP codes are hard to
enumerate, constantly changing and not completely intelligent, so I
would call them identifiers.

William J. Kammerer
Novannet
Columbus, OH 43221-3859 . USA
+1 (614) 487-0320

----- Original Message ----- 
From: <kenneth.sall@gsa.gov>
To: <ubl-dev@lists.oasis-open.org>
Sent: Thursday, 14 April, 2005 02:34 PM
Subject: [ubl-dev] Code vs. Identifier representation types?


Hello,

I'm looking for some guidance in distinguishing Code and Identifier
representation types. Part of my confusion is that UBL and TBG-17 don't
agree on a very common example (based on most recent online versions):

Country. Identification. Identifier  - TBG-17
Country. Identification. Code  - UBL

Given UBL definitions from
http://docs.oasis-open.org/ubl/cd-UBL-1.0/xsd/common/UBL-CoreComponentTypes-1.0.xsd
 :


Code: "A character string (letters, figures, or symbols) that for
brevity and/or language independence may be used to represent or replace
a definitive value or text of an attribute together with relevant
supplementary information."

Identifier: "A character string to identify and distinguish uniquely,
one instance of an object in an identification scheme from all other
objects in the same scheme together with relevant supplementary
information."

On a U.S. General Services Administration (GSA) project, we are applying
this to numerous data elements. For example,

(a) A code identifying party receiving transmission; codes agreed to by
trading partners. Originally called Application Rcvrs Code (TXN06). We
have given this the BIE of Receiving_ Party. Identification. Identifier
because it uniquely distinguishes one party from all others.

(b) When considering the type of Indefinite Delivery Vehicle (IDV)
contract, there is a finite set of possible "brief" symbolic values that
can readily be enumerated. Therefore, the assigned BIE is Contract.
Indefinite Delivery Contract_ Type. Code.

(c) The FIPS Pub. 95 code for the agency of the contracting office that
executed or is otherwise responsible for the transaction was assigned
the BIE of Contracting_ Organization. Agency_ Identification. Identifier
because it uniquely distinguishes one agency from all others.

(d) Similarly, the US govt uses lots of "codes" such as NAICS codes
(North American Industry Classification System codes designate major
sectors of the economies of Mexico, Canada, and the United States) and
PSC codes (Product and Service Code). Since they "distinguish uniquely,
one instance of an object in an identification scheme from all other
objects in the same scheme", they should be Identifiers, right?

(e) Note that calling (c) and (d) Identifiers goes against the commonly
used terms (FIPS codes, NAICS codes, PSC codes). Basically, UBL reserves
the term "code" strictly for symbolic shorthand elements, right?

(f) DUNS and SSN (social security numbers) should be Identifiers.

(g) Country codes and state codes should be Codes.

Does anyone disagree with any of the above representation types? Thanks
in advance.

Kenneth Sall
SiloSmashers
XML Specialist
GSA IAE Program Management Office
U.S. General Services Administration
1 Crystal Park, Mail Stop IAA
2011 Crystal Drive, Suite 911
Arlington, VA 22202
Phone: 703.872.8589
Cell: 301-672-3269
Fax: 703.872.8598


The President's Management Agenda:
"Implementation of E-Government is important in making Government more
responsive and cost-effective."
http://www.whitehouse.gov/omb/egov/
(Embedded image moved to file: pic20899.jpg)



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