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?


Ken,

In short I've always considered this to be the distinction:

Code: An abbreviation that is used to represent an entity, for purposes
of conciseness and interoperability (ex: in data exchanges). So Country
Code is an excellent example.

Identifier: A value that is used to represent an entity, for purposes of
distinguishing that entity from amongst other entities of the same class
for a specific purpose. SSN, driver's license number, etc. are - in my
mind - examples of identifiers.

Joe

Joseph Chiusano
Booz Allen Hamilton
Visit us online@ http://www.boozallen.com
 

> -----Original Message-----
> From: kenneth.sall@gsa.gov [mailto:kenneth.sall@gsa.gov] 
> Sent: Thursday, April 14, 2005 2:35 PM
> To: ubl-dev@lists.oasis-open.org
> 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-CoreC
> omponentTypes-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]