Rights Subgroup 2015-06-03
Participants:
Esme Cowles, chair (UC San Diego)
@Nick Ruest
@Trey Pendragon
@matienzo
@Chrissy Rissmeyer
Agenda
Call for agenda items
Rights statement vs. additional rights info
dcterms:rights vs. dc:rights
edm:rights vs. dc:rights
dcterms:rights vs. archiveshub:useRestrictions
Embargo/Lease
dcterms:accessRights
hydrarights:embargoReleaseDate/hydrarights:leaseExpirationDate?
Facilitator for next meetings (6/17 and 7/1)
Notes
Rights statements vs. additional rights info
dct:rights v. dces:rights - could be confusing, but they do declare different ranges, etc.
DPLA: edm:rights for URIs, dc:rights for literals
Any reason we can't do this?
Embargo/Lease
Are we good with only having a single property?
Worried about override aspect, why not just have one property
We could create a sub-property of dcterms:accessRights that is an rightsOverride
And a property for the expiration date
Action: Esme will create a PCDM extension ontology for rightsOverride and rightsOverrideExpiration.