...
If it helps, this proposal can be also be conceptualized as a kind of 'service' provided on top of a datastream to provide an enhanced RDF CRUD API that neatly maps to an LDP concept that Fedora does not currently support, but most LDP servers do.
Use cases
- Arbitrary RDF documents as 'assets' managed by Fedora, yet accessible via the LDP-RS API. For example, Tim Berners-Lee's FOAF file.
- It contains multiple subjects, for example when providing details of linked blog posts, papers, or conferences.
- Named-graph provenance
- A place to put statements that are not allowable in Fedora objects, as a pragmatic workaround (e.g. assertions about an external resource)
Implementation notes
- Fedora may describe these resources using slightly different metadata in their corresponding 'fcr:metadata' resources.
- For example, "fedora:mixinTypes "fedora:NonRdfSourceDescription"^^<http://www.w3.org/2001/XMLSchema#string>" is probably not appropriate.
- Basic validation as well-formed RDF or SPARQL/update statements is a prerequisite for accepting content.
- The binary representation of an LDP-RS-NC as persisted in Fedora as datastream content may potentially be opaque (a decision would need to be made on this)
- The serialization format may be specified in advance. For example, Fedora may chose to serialize as turtle, always
- Fedora may perhaps chose to store the exact binary content supplied by the client via PUT, and record metadata indicating which RDF serialization had been persisted.
- Likewise, the content may be entirely opaque, leaving it an implementation decision that can change at any time.
...