Also not an expert on any of this stuff, but my understanding is that
PREMIS is a dictionary that allows you to describe who owns something,
whether the thing is legit, what's done to preserve it, what you need to
use it, and rights management information.

It's a flexible standard -- i.e. there are many legitimate ways to
implement it that are totally incompatible with compliant systems.

<soapbox>Few phrases mean less in systems than "support" when it comes to
metadata -- the devil is in the details. Despite being around half a
century and dominating the library landscape, variations in how MARC is
supported still generate grief. Even the lowly CSV file which has been
around well over 40 years and which sees plenty of real world action in
library applications gets implemented in different ways. As standards
become more complex and abstract, both the containers and content become
more divergent and the carbon-based liveware more confused, resulting in
situations where standards undermine their own objectives.

As such, best to focus on the operational effect needed and being able to
get stuff in/out. If you can do that, you're golden whether or not you're
technically compliant.</soapbox>

kyle




On Fri, Dec 7, 2018 at 7:36 AM McDonald, Stephen <[log in to unmask]>
wrote:

> You have the right general idea about the nature of IFLA LRM.  LRM is
> essentially a merging and reformulation of FRBR, FRAD, and FSRAD.  It is
> not a metadata schema.
>
> BIBFRAME is an implementation of RDA, which is a metadata schema based on
> FRBR.  BIBFRAME is still under development, and is currently only used for
> development and experimental purposes.  LRM is too new for any system to be
> called LRM compliant.  Work is underway to bring both RDA and BIBFRAME in
> line with LRM.  The new version of RDA is available as a beta release, but
> is still incomplete.  Exactly how closely RDA and BIBFRAME will comply with
> LRM is to be seen.
>
> I know very little about PREMIS, but I believe it has no relationship with
> FRBR or LRM.  It is a metadata schema that views resources from a very
> different perspective.
>
> -----Original Message-----
> From: Code for Libraries <[log in to unmask]> On Behalf Of Josh
> Welker
> Sent: Thursday, December 6, 2018 2:58 PM
> To: [log in to unmask]
> Subject: [CODE4LIB] BIBFRAME, IFLA LRM, and PREMIS
>
> Hi all,
>
> Can anyone explain the relationship between IFLA LRM, BIBFRAME, and PREMIS?
>
> From what I can tell, IFLA LRM is not actually a metadata schema. Rather,
> it is just a list of top-level entities involved in a bibliographic
> resource and how they are related to each other (e.g. a *work* has many
> *expressions*, and an *expression* has one *work*).
>
> BIBFRAME is an actual metadata schema containing elements like title,
> author, etc. that describe the higher-level entities defined by IFLA LRM.
> Except does it? BIBFRAME 2.0 was conceptualized in 2016, and the IFLA LRM
> was published in December 2017. If I were to use BIBFRAME today to describe
> a book, would that metadata be IFLA LRM-compliant?
>
> My question about PREMIS is much the same. Is it compliant with IFLA LRM?
> Furthermore, is it possible to catalog with PREMIS and BIBFRAME together?
> For instance, if I have a BIBFRAME representation of a book at
> www.mysite.com/mybook, can I use that URI as the PREMIS Object?
>
> Maybe these are questions that are not fully answered yet because of the
> lack of concrete BIBFRAME implementations.
>
> Joshua Welker
> Library Systems and Discovery Coordinator James C. Kirkpatrick Library
> University of Central Missouri Warrensburg, MO 64093 JCKL 2260
> 660.543.8022
>