This group is interested in working together to make recommendations for creating and maintaining URIs that are necessary for Samvera community projects to express appropriate RDF properties and property values. This group is a working group of the Samvera Metadata Interest Group and is considering use cases from requests and questions documented on the Metadata IG Requests and Priorities. Examples of properties that might require minting new URIs include the following:
Community terms (Sufia, CurationConcerns, possibly PCDM)
ss:arkivoChecksum = premis:hasMessageDigest or a checksum property from LC (not sure which)
ss:relativePath = premis:hasContentLocationValue or a property from ebucore (ebucore:locator?)
ss:importURL = premis:historyInfo but this might not work
ss:proxyDespoitor = marcrelator:dpt (depositor)
ss:onBehalfOf = marcrelator:cre (creator)
Accepted vocab (standard) but not available through RDF - I.e. GeoRSS, PBCore
Local vocab that everyone wants - you just don’t know it yet!
RDF that doesn’t work for me, i.e. Premis
Deliverables & Timeframe
The initial goals of the group are:
survey Samvera community to find out if there have been roadblocks or properties not found (beyond issues documented on the Metadata IG Requests and Priorities)
create decision tree for new predicates/vocabs; should they be hosted by Samvera vocab manager or hosted elsewhere?
define functional requirements for Samvera vocab manager
is versioning necessary? are there examples to support this need?
define Phases of development
General Governance Issues to be considered for Phases (timeline, testing, etc)
define workflow for requesting new predicates/vocabs from the Samvera vocab manager
Survey findings, decision tree, and functional requirements to be delivered by Hydra Connect 2016