...
Outside of the ".fcrepo/" directory, all other OCFL object files store the content of Fedora resources. Every Fedora resource is persisted to OCFL using exactly two files. The first is a header file located in ".fcrepo/" and the second is a content file located in the root of the OCFL object's "content/" directory. The naming and location of content files can vary depending on the type of resource they belong to. It is not necessarily possible to identify a resource's content file without first determining what type of resource it is by reading its header file.
Header Files
For a full description of the contents of Fedora header files, see Design - Fedora Header Files.
...
RDF Files
Fedora creates RDF files for three purposes:
- For persisting WebACLs associated with a given Fedora resource
- For persisting user-provided descriptions of binary resources
- For persisting user-provided properties associated with container resources
ACLs
The RDF content of WebACLs is user-provided, and must conform to the Web Access Control specifications. WebACL files are optional, and will only exist if the user creates an ACL on a Fedora resource.
Binary Descriptions
The RDF content of binary descriptions is user-provided, and can be any valid RDF. By convention, the content of the RDF should be used to describe the associated binary resource. Binary description files must exist for each binary resource and are auto-created by Fedora as empty files when a binary resource is created.
Container Properties
The RDF content of container resources is user-provided, and can be any valid RDF. Container property files must exist for each container resource and are auto-created by Fedora as empty files when a container resource is created.
Header Files
For a full description of the contents of Fedora RDF header files, see Design - Fedora RDF Header Files.