Write up Structure decisions

hybox / models

Data Modeling repository for HyBox (ontologies, vocabularies, best practices, requirements, etc)

Apache License 2.0

5 stars 3 forks source link

Write up Structure decisions #23

Open azaroth42 opened 8 years ago

azaroth42 commented 8 years ago

Descriptive metadata about a physical object that has been digitized will be associated with a separate resource from the digital object that maintains the binary data structures. (e.g. real world book is not owl:sameAs the pcdm:Object for the scan of that book)
Parts of digitized objects, such as the pages of a book, have a separate Object from the FileSet that groups the Non RDF Sources. Each Part object can have 0 .. many FileSets.
Objects and Collections can have their own FileSets as well as Parts, for representations of the complete object. (e.g. a PDF of the book, plus the Parts are the Pages, with Image FileSets)
FileSets are not ordered internally, or with relation to each other. Only Objects and Collections are ordered (internally, and relative to a parent Object/Collection)

And diagram in: https://github.com/hybox/models/issues/17#issuecomment-196919583

azaroth42 commented 8 years ago

Is the structure, now with hasRelatedObject this: pcdm-works

azaroth42 commented 8 years ago

I think the questionable relationships are:

Can a Collection have a member FileSet?
Can a Work have a member FileSet?
Can a Work have a member Work?
Can a Collection have a related Work?
Can a Work have a related Work?
Can an Object have a member Work?
Can an Object have a related Work?

The possible but not sensible relationships we should avoid:

Anything having a related FileSet without an intervening Object
FileSets having any object as a Member
FileSets having any related objects

azaroth42 commented 8 years ago

Can a Work have a member Work?

Journal issue as Work, with a member Article as Work would be a possible use case for this. (/ht @cmh2166)

escowles commented 8 years ago

Can a Collection have a member FileSet?

I think a thumbnail/preview/etc. would use hasRelatedObject, not hasMember. Ditto for a donor agreement, policy document, etc. So I can't think of a use for this.

Can a Work have a member FileSet? Can a Work have a member Work? Can a Collection have a related Work? Can a Work have a related Work? Can an Object have a member Work? Can an Object have a related Work?

I would say yes to all of these. For the "Can an Object..." questions, I'd say yes because a Work can, and a Work is a subclass of Object, so...

azaroth42 commented 8 years ago

Sorry, by "can" I meant "should implementations expect ... to ...".
Clearly all of them are possible, as all pcdm:Objects (and subClasses) can be the subject of hasMember, hasRelatedObject and hasFile. However we don't want hasFile to be used with Works or raw Objects in our application profile, only with FileSets.

What are the use cases for the other questions?

azaroth42 commented 8 years ago

@escowles I think your take is this: pcdm-works ?