...
- How will the PREMIS be used?
- support standard external policy audit tool
- harvest and index for curatorial queries
- generate a preservation view of objects
- Do we want to define a standard dissemination of PREMIS or a standard storage for PREMIS? (contract vs. implementation)
- Which parts of the PREMIS schema must be stored as such and which parts may be generated on the fly, from Fedora and other system data?
- How do Fedora objects, datastreams and versions map onto PREMIS object types?
- How do the relationships between these get encoded, is there a PREMIS vocabulary for these relationships?
- Do the requirements of the object/storage element indicate a need to retrieve a set of standard metadata from the low level storage module?
- Will we use PID for objectIdentifier? If so do we want to require a universally unique PID (UUID) to better support future migration of stored PREMIS?