A server Server managed triple triples (SMT for short) is any triple for a resource which is created and managed 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 server implementation for inspection and identification of said resources. As such, clients Resources. They are related to LDP-server-managed triples. Clients may not modify these properties directly via PUT/PATCH/POST requests. Instead, they are often generated as a side effect of other actions , such as creating a container or a binary, or adding a child resource.
...
When committing changes to the server via PUT, clients may provide all non-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 properties predicates are considered to be server managed (see the list of namespace prefixes later in the document):
...
In addition to predicates, the following URIs are considered server managed when provided as the object of an rdf:type property:
- <> rdf:type fedora:* (any type in the fedora namespace)
- <> rdf:type memento:* (any type in the memento namespace)
- <> rdf:type ldp:* (any type in the ldp 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)
Namespaces Referenced in this Document
| Prefix | Namespace |
|---|---|
| fedora |
...
...
...
...
...
...