Server managed triples (SMTs) are the portion of a Resource's triples which are generated and/or constrained by the server, and may in some cases be used by the implementation for inspection and identification of said Resources. They are related to LDP-server-managed triples. Clients may not modify these properties directly via PUT/PATCH/POST requests. Instead, they SMTS are often generated as a side effect of other actions such as creating a container or a binary, or adding a child resource. If these properties are modified by clients, the modifications will generally be ignored by the server.
Clients may request to omit server managed triples from RDF responses from the server using the "Prefer: return=representation; omit=http://fedora.info/definitions/v4/repository#ServerManaged" header as described in
the RESTful API documentation
When committing changes to the server via PUT, clients may choose not to provide the server managed triples for the resource by including the "handling=lenient; received="minimal" header as described in the RESTful API PUT documentation, which is based on https://tools.ietf.org/html/rfc7240#section-4.4
Server Managed Predicates
The following predicates are considered to be server managed (see the list of namespace prefixes later in the document), meaning that direct modification of these properties by clients will be ignored:
- ldp:contains
- premis:hasMessageDigest
- premis:hasFixity
- All predicates in the fedora namespace
- All predicates in the memento namespace
...
- premis:hasSize
- ebucore:hasMimeType
- ebucore:filename
- iana:describedby (an instance of this property is generated for binaries and cannot be removed, but clients may add additional instances of this property)
Server Managed Properties in Imported OCFL Objects
| Note |
|---|
TODO: This section needs to filled in as the import functionality is developed |
When Fedora imports existing OCFL objects, the imported objects may include RDF which would normally be server managed. Fedora should not modify the files of any imported objects until clients specifically modify the objects contents. As such, SMTs located in imported objects will need to be specially handled.