David M Pimentel wrote:
It strikes me that one way to address this situation might be to focus not only on the nature of the relationships between (FRBR) entities, but also on who makes (and hence values) particular relationships.
Absolutely! I think this would be handled well through application profiles. The Dublin Core folks have been working on this in the bibliographic realm. There are already examples of application profiles, such as those for Z39.50 and for the OpenURL. Done well, you should be able to make decisions about the meaning of a relationship based on how it is defined in the particular application profile. What this means is that different communities can have their own peculiar (and some will be peculiar) sets of relationships and definitions without being constrained by the needs of others. (Which I think is what has tripped up the library and archive communities in the past -- that we didn't have a way to express different views using the same data elements.) Here's one article on application profiles. There are probably many more and perhaps better ones that others can contribute. I think I'll start a page on APs on the futurelib wiki. http://www.ariadne.ac.uk/issue25/app-profiles/ kc -- ----------------------------------- Karen Coyle / Digital Library Consultant [EMAIL PROTECTED] http://www.kcoyle.net ph.: 510-540-7596 skype: kcoylenet fx.: 510-848-3913 mo.: 510-435-8234 ------------------------------------
