On 6/30/14, 8:13 AM, [log in to unmask] wrote:
>
> There's another, more technical point here. It's one of the reasons it's not really feasible to maintain a "stateless catalog", at least not right now, if we want to fulfill the expectations of discovery held by most library users. We can effectively load book images at the last minute because we don't search them, and we don't integrate that data (the images) within a set of search results.
For me, this would have been point #1. There's a big difference between 
pulling something in for display only vs. data that you intend to use 
for search or some other decision-making. I suspect that this could be 
the reasoning behind the "common abstraction layer" in BIBFRAME, 
although I don't believe I've seen it explained in that way. In fact, 
the motivation behind the CAL is still a bit of a mystery to me -- the 
documentation explains what it is, but not why. I'd very much like to 
hear the why from anyone who feels they understand it.

kc

-- 
Karen Coyle
[log in to unmask] http://kcoyle.net
m: 1-510-435-8234
skype: kcoylenet