Where should the type information be 340
at the ieee metadata meetings we were going to in the early 90s ... there were fairly good representation from the oil industry.
at one point somebody from the oil industry had said that they had a project to define metadata for oil industry ... hoping that it would be used for recording as the data was recorded ... aka the Bob Adair model in the 60s at the science center
one big issue was trying to use an RDBMS as a repository for the oil industry metadata description. now most RDBMS have been pretty good at representing relatively uniform and homogeneous information ... minor collections of posts about origins of RDBMS and SQL
however, RDBMS can quicly get convoluted when trying to represent non-uniform and-or non-homogeneous information. they mentioned using something like 995 tables for representing the oil industry metadata in RDBMS form.
Ah! I was peripherally involved in that POSC effort too, and a good friend of mine was in...
NIH NLM has had a somewhat similar activity with UMLS
there was some joke from the early 90s about it taking 18 months elapsed time attempting to (relational) "normalize" new metadata changes corresponding with 9 months of new-changed medical knowledge.
slightly related is the glossary-taxonomy work at
Thats the good thing, but then call them ''lore''. There have been important and interesting books about programming lore. Or worse, see below :-) The ''pattern'' movement, sometime explicitly, more often implicitly, seems...
--
Where should the type information be 341
Alt Folklore Computers from Newsgroups