Library of Congress

Authorities & Vocabularies

The Library of Congress > Linked Data Service > LC Subject Headings

From Library of Congress Subject Headings


us: FRAD (Conceptual model)


  • URI(s)

  • Instance Of

  • Scheme Membership(s)

  • Collection Membership(s)

  • Variants

    • us: FRAR (Conceptual model)
    • us: Functional Requirements for Authority Data (Conceptual model)
    • us: Functional Requirements for Authority Records (Conceptual model)
  • Broader Terms

    • us: Entity-relationship modeling
  • Related Terms

    • us: Authority files (Information retrieval)
  • Sources

    • found: Work cat.: Patton, G.E. From FRBR to FRAD : extending the model, 2009: p. 2 (The Functional Requirements for Authority Data is the creation of the IFLA Working Group on Functional Requirements and Numbering of Authority Records; to provide an understanding of how authority data functions currently; to clarify the underlying concepts to provide a basis for refining and improving on current practice in the future) p. 3 (the FRAD model is an entity-relationship model)
    • found: Functional requirements for authority data : a conceptual model, 2009.
    • found: Wikipedia, Apr. 26, 2010 (Functional Requirements for Authority Data (FRAD), formerly known as Functional Requirements for Authority Records (FRAR) is a conceptual entity-relationship model developed by the International Federation of Library Associations and Institutions (IFLA) for relating the data that are recorded in library authority records to the needs of the users of those records and facilitate and sharing of that data; an extension and expansion to the FRBR model, adding numerous entities and attributes)
  • Change Notes

    • 2010-04-27: new
    • 2010-08-19: revised
  • Alternate Formats

Suggest terminology


The LC Linked Data Service welcomes any suggestions you might have about terminology used for a given heading or concept.

Would you like to suggest a change to this heading?

Please provide your name, email, and your suggestion so that we can begin assessing any terminology changes.

Fields denoted with an asterisk (*) are required.