Future of Hydra and RDF
How can we reposition Hydra to embrace RDF more fully - and maybe ditch XML-based metadata?
How can we structure objects and component parts via RDF?
RDF might still be serialised to XML for preservation and recovery.
UCSD has Hydra over its "old" DAMS with a layer in between to make the RDF in the underlying database look like a Fedora datastream
WGBH Hydra DAM uses RDF but displays it as PBCore
ScholarSphere has its triples in a datastream
UCSD's list of releationships (and why) would be useful to the community - and how they relate to MODS/DC/PBCore/whatever
Solving this problem togather would prevent fragmentation and provide a common solution
Action:
- Start a "Hydra and RDF" page on the wiki
- Need a "Hydra and RDF" working group
- Document common transforms (in and out) between useful metadata schema and RDF