Skip to content

Why didn't we use Realized and Embodied In from FRBR #124

@kcoyle

Description

@kcoyle

I received a comment asking why we didn't use the FRBR terms for the OpenWEMI properties. I actually don't remember the details, but do think this is something we should document. The comparison of the properties is:

FRBR elements/classes FRBR OpenWEMI
Work/Expression realized through expressedBy
Expression/Manifestation embodied in manifestedBy
Manifestation/Item exemplified by instantiatedBy

My recollection is that we found "realized" and "embodied" to be too concrete. Here are some definitions from the dictionary:

Expression an act... of representing in a medium
realize to bring into concrete existence
embody to make concrete and perceptible

It's obviously hard to pin down a single word that everyone can agree on. I do think that our definitions are clear:

  • Endeavor: "A creation"
  • Work: "An abstract notion of an Endeavor."
  • Expression: "A perceivable form of an Endeavor."
  • Manifestation: "A realization of an Endeavor in physical, digital, or experiential form."
  • Item: "An instantiation of an Endeavor."

If I had to define the relationships in prose (instead of as properties) I could say:

"This expression makes the creation perceivable by some (biological) sense"

"This manifestation is the concrete form of the creation in question."

"This item is a single instance of the outcome of the acts of creation."

This gets philosophical quickly - but I am interested to hear comments, especially those about how we could explain this better in the documentation.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions