- From: Kai Eckert <kai@informatik.uni-mannheim.de>
- Date: Sat, 11 Dec 2010 10:42:36 +0100
- To: Karen Coyle <kcoyle@kcoyle.net>
- CC: "public-lld@w3.org" <public-lld@w3.org>
Am 10.12.2010 15:07, schrieb Karen Coyle: > Kai, > > What I see as tricky here is that in order to describe the citation you > must describe two things: > > The BIBLIOGRAPHIC RESOURCE that is citing, and the REFERENCE that is the > citation. > > When you describe the BIBLIOGRAPHIC RESOURCE that is citing, then you > are describing any (probably textual) BIBLIOGRAPHIC RESOURCE. This means > that your model includes more than the citation, but the whole textual > bibliographic universe. Yes, the BIBLIOGRAPHIC RESOURCE represents the textual resources that we all know, that's were the example connects to the existing models. > This gets back to the "use case" question. When I look at the use cases, > they are about creating relationships between bibliographic resources. > This is different from describing those resources. I would have thought > that the use cases would be concerned with defining the types of > relationships and seeing how connections could be made between disparate > metadata types, since most everything that is being cited has metadata > somewhere (in a library database for a book, or in a vendor database for > an article). True, this is what the use cases are about. The question is, if we can make the connection by just providing a link (:doc1 :cites :doc2). If we want to provide further information, we need the intermediate class CITATION. If we want to organize the citations without the requirement to directly link to an existing resource or if we want to represent the information as found in the citing resource, we need the intermediate class REFERENCE. > > As an example, I started a long, contentious thread on the FRBR mailing > list (which I now discover does not have an open archive - rats!) about > the problem of linking FRBR-ized metadata to non-FRBR-ized metadata. One > obvious set of non-frbr-ized metadata is citations. Perhaps I should > write this up as a use case? +1 :-) I updated the illustration once more to make the meaning of the classes clearer. Cheers, Kai -- ============================================= Kai Eckert KR & KM Research Group Universität Mannheim B6, 23-29; Building B; Room B 1.15 D-68159 Mannheim Tel.: +49 621 181 2332 Fax: +49 621 181 2682 WWW: http://ki.informatik.uni-mannheim.de ---------------------------------------------
Received on Saturday, 11 December 2010 09:43:14 UTC