tag:blogger.com,1999:blog-3338174527262061848.post7272810916070678733..comments2023-09-29T08:51:56.163-07:00Comments on Coyle's InFormation: Models of bibliographic dataKaren Coylehttp://www.blogger.com/profile/02519757456533839003noreply@blogger.comBlogger3125tag:blogger.com,1999:blog-3338174527262061848.post-41495495080913690872011-08-18T03:15:16.476-07:002011-08-18T03:15:16.476-07:00Thanks for this; I haven't been following the ...Thanks for this; I haven't been following the BL linked data too closely, so I would have missed this if not for your post. What an interesting looking data model! I agree that modelling publication as an event makes a lot of sense.Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-3338174527262061848.post-63517613042552481322011-08-15T09:38:43.731-07:002011-08-15T09:38:43.731-07:00Thanks, Richard. One of the primary issues I have ...Thanks, Richard. One of the primary issues I have with FRBR is that it quite deliberately constrains data to a single model. I think this will even create problems for RDA, and have already seen one place where RDA paints itself into a corner with its strict adherence to FRBR. <br /><br />My operating concept right now is "VIEWS" -- that we should be able to support a variety of views of our data, depending on what we're doing with it at a given time. I think I'll call this the "lava lamp" approach to data -- kind of like linked data but with a fluid nature. And it also sounds more fun.Karen Coylehttps://www.blogger.com/profile/02519757456533839003noreply@blogger.comtag:blogger.com,1999:blog-3338174527262061848.post-31465941717408536612011-08-15T02:37:27.466-07:002011-08-15T02:37:27.466-07:00Tim Hodson's blog post, British Library Data M...Tim Hodson's blog post, <a href="http://consulting.talis.com/2011/07/british-library-data-model-overview/" rel="nofollow">British Library Data Model: Overview</a> on his work with the BL team, provides an insight in to the thinking behind the development of the model. He promises to turn this post in to a short series to "<i>tease out some of the more interesting aspects and give an overview of the discussions that led to the current model</i>" - I will hold him to that when he returns from holiday ;-)<br /><br />I whole hardly agree with your suggestion that we explore a variety of models for [our] data. The BL's Neil Wilson, in his <a href="http://consulting.talis.com/resources/presentations-from-linked-data-and-libraries-2011/" rel="nofollow">presentation from Linked Data and Libraries 2011</a> where the BnB data release was announced (there is a recorded video stream if you are interested), made it clear that this was a contribution to the conversation around the way to describe bibliographic resources in the future.<br /><br />The benefit of working with a Linked Data model is that it is flexible and can accommodate additions and differences, thus avoiding the <i>one model to rule them all</i> approach that has never really worked well for us in the past. So, as you would obviously expect from me, I encourage that conversation to take place using Linked Data techniques as a way to accommodate the inevitable overlapping differences in approach and need.<br /><br />One final plea - remember we are modelling data to describe the <i>things</i> that libraries provide access to, not the records that have previously held that data. Those records are a valuable source of information, but should not constrain access to and understanding of the information people need.<br /><br />Richard WallisAnonymousnoreply@blogger.com