buda-base / owl-schema

BDRC Ontology Schema
11 stars 2 forks source link

what to do with various props, etc for abstractworks #154

Open xristy opened 4 years ago

xristy commented 4 years ago

The superclass :BiblioEntity was added to collect the various bits of the new biblio model.

There are two :Entity classes, :Etext and :Volume, that are not under :BiblioEntity but likely should be.

Here are some properties that need consideration along with and :workRefs and other IDs

:workHasPart
:workHasReproduction
:workHasRoot
:workIsNumbered
:workMicrofilm
:workPartIndex
:workPartLabel
:workPartOf
:workPartType
:workReproductionOf - does not apper to be used
:workSeeHarvard - is used but is it redundant with :workHollis
:workSeriesContent - does not apper to be used
:workSeriesName - where does it go? On :Work or :Instance
:workSeriesNumber - where does it go? On :Work or :Instance
eroux commented 4 years ago

About etexts: in my mind we have:

About series: What's done in the BIBFRAME adaptations of RDA/FRBR (and I think we should adopt it) is:

so we should deprecate :workSeriesName which should be replaced by a proper work for the series in the future (we can do that later), and seriesnumber is in the work of the number/issue. workIsNumbered should be deprecated moving forward, it should probably be attached to issue works in the meantime.

I think when people speak of parts, they speak of parts of the original edition, not the electronic resource, so we should keep parts where they are (in the instances). Parts are instances... Ideally the locations should be in the electronic resources I think... but we can move them later.

workHasReproduction/reproductionOf should link instances (that are reproduced) to... work or instance I think.