Jonathan said: >Compare to RDF data model -- if RDF data were really stored internally >_only_ in a "triple store" format -- this can in fact be even _more_ of >a performance problem, effectively requiring many _more_ "joins" to >display anything at all. RDF triples are kind of "ultra normalized", any >performance problems due to joins in an rdbms are _even more so_ with >RDF. The Wikipedia description of RDF and triples reminds me of the presuppositions behind PRECIS, which did not work. Resources proved to be too varied, English word meanings too ambiguous, with many resources unique, for the concept to work.
We would have work records (if separate WEM records are the pattern) supporting the single expression and single manifestation of that work. We would have triples relevant to a single manifestation, and tables populated with data for a single manifestation's description. http://en.wikipedia.org/wiki/Resource_Description_Framework __ __ J. McRee (Mac) Elrod ([email protected]) {__ | / Special Libraries Cataloguing HTTP://www.slc.bc.ca/ ___} |__ \__________________________________________________________
