http://purl.fcla.edu/fcla/rxp-rep-profile
http://www.loc.gov/standards/mets/profiles/00000034.xml
TIPR rxp-rep-n.xml
METS documents describing representations of the RXP.
RFC 2119 (http://www.ietf.org/rfc/rfc2119.txt) defines the meanings of terms MUST, SHOULD, etc.
2010-07-06T16:39:29-04:00
Francesco Lazzarino
Florida Center for Library Automation
The Florida Center for Library Automation
5830 NW 39th Ave
Gainesville, FL 32606
flaz@ufl.edu
TIPR base METS profile
The Repository Exchange Package (RXP) is a hierarchical packaging
format designed to facilitate the exchange of Archival Information
Packages (AIPs) between digital repositories. The RXP employs METS and
PREMIS metadata documents to encode AIP preservation and structural
metadata at the root level. All other data are stored in the files
subdirectory.
link to RXP Specification: http://wiki.fcla.edu:8000/TIPR/21
None
The amdSec MUST have a digiprovMD with an mdRef that MUST reference
(via mdRef) 'rxp-rep-n-digiprov.xml' where n is an integer.
Each file not in the metadata file group SHOULD have an OWNERID
attribute. The OWNERID SHOULD match the URI identifier of the file
in the representation provenance (rxp-rep-n-digiprov.xml). OWNERID
serves as a link between the location of a file and its provenance.
All FLocats in the fileSec SHALL reference files in the "files/" directory or the rxp-rep-n-digiprov.xml files and MUST NOT reference other files.
No tools are associated with this profile
FCLA
rxp-0.96