Re: [ontolog] UBL proposals for codesets?

[Leo Obrst <lobrst@xxxxxxxxx>]

Mike,

One issue with your suggestion is that, hypothetically, a concept Uruguay then really has no connection to UR or URY (these are fictitious) but only to CODESET1 and CODESET2 or perhaps you mean to CODESET1[Uruguay's index],  CODESET2[Uruguay's index]? This is therefore just a syntactic relation. One problem is: there may be no one-to-one relation between a given concept and a codeset and so also many-to-many relations between 2 codesets. But if you have an ontology node, say "ball peen hammer" and a few codesets (i.e, think of a taxonomic codeset such as the UNSPSC and NAICS), you might have to have multiple mappings.

There is obviously a semantic relation between codesets and the individual codesets should be semantically codified too. I don't disagree with that.

Re Uruguay as a concept: although it can be considered an instance typically, there are often strong reasons to have it as a concept  (eg., in a belief space where there are multiple Uruguay instances, etc).

Leo

MDaconta@xxxxxxx wrote:

Hi All,

This is an interesting difference of opinion on the meaning of a code in a
code set.  I do not believe you associate the semantics with the code itself
but with the code set or list.  In other words, the code is just an index
into a code set.  So, I would say that the burden for understanding the
semantics of a code lies with the code set and not with an individual
code.  The only burden a user of the code has (in terms of semantics)
would be to properly refer to its code set.  In turn, the code set, should
refer to an ontology that explains the semantics behind the codes.

Just my 2 cents,

- Mike

In a message dated 10/28/2002 9:03:00 AM US Mountain Standard Time, Robert.Miller@xxxxxxx writes:
 

       "A code is a representation of some thing, normally text, abbreviating it to a shortened, encoded form, and usually of the same consistent lenght within a code list.  In essence it is an abbreviation."

The implication I have read from this definition is that the 'text' the code represents is the end of the line, from a semantic viewpoint.  But the reality is that the code is a pointer to a collection of semantic information, at least some of which is likely to be of semantic significance to the application processing the information in which the code is imbedded.  I've studied the existing X12 code lists at some length, and have yet to find a code list that does not identify semantic properties beyond that of the 'text' used to describe the code.

----------------------------------------------------
Michael C. Daconta
Director, Web & Technology Services
www.mcbrad.com

--
_____________________________________________
Dr. Leo Obrst  The MITRE Corporation
mailto:lobrst@xxxxxxxxx Intelligent Information Management/Exploitation
Voice: 703-883-6770 7515 Colshire Drive, M/S W640
Fax: 703-883-1379       McLean, VA 22102-7508,
USA