Closed escowles closed 8 years ago
:+1: pending update to: https://github.com/duraspace/pcdm/blob/27a133e2f5cdbf23cf0b2c125b2eb7f086c418bb/models.rdf#L15
I like this, but I do wonder (slightly) about the semantics of the fileset being the thing with the file, since there's no transitivity here.
@tpendragon Since FileSet is a subclass of Object, it's just another layer of Objects with a File. So if your app doesn't care about FileSets, then it can just treat it as an Object.
Oh! I'm not sure FileSet in this proposal should be an object. Doesn't this open up FileSets having FileSets?
Yes, and doesn't help avoiding conflation of what metadata goes on Object (work, RWO) and Fileset. But in this change having Fileset be a subclass of Object means you don't need to create a new 'manages' property.
Collections could hasMember FileSets if they're subClassOf Object. That seems ... wrong. From meh to :-1: given this.
I agree with the concerns raised here about FileSets being subclasses of Object causing problems. Closing this issue in favor of #69, where we can continue to discuss what the relationships should look like and what metadata goes where.
Objects can either link directly to Files, or link to FileSets that link to Files:
Current PCDM:
Optional FileSet as a buffer between Object and File:
See also #69