...
(This is included largely for completeness sake, but it is very interesting)
This is like the "LDPRs as pointlike objects" proposal, except that it removes Fedora's existing constraints on triples associated with objects in general. In this view, a Fedora object can be seen as a bag of triples with an identity (named graph). Fedora enhances the value of these bags by defining an ontology, and maintaining a set of triples that express its identity in the Fedora object model according to this ontology. Users of Fedora can embrace or extend the Fedora model, or ignore it completely.
...
In this proposal, Fedora's relationship with LDP can be seen as a "value add service:" in creating an LDP-RS, Fedora enhances the value of these LDP resources by managing s a set of triples that give it an identity in the Fedora model, describe it as such, and enable services on it such as fixity, indexing, etc.
- Any statements outside this ontology are preserved, but largely ignored by the Fedora service stack (except, perhaps general-purpose services such as triple store indexing).
- To an outside user, Fedora would appear just like a fully-featured LDP service that happens to have a lot of server-managed triples.
- Fedora would be completely usable as a generic LDP service without any knowledge of the Fedora model
- An outside user would not need to understand the Fedora model in order to understand why an LDP request failed.
- To a current user of Fedora 4, there would be no observable difference in an object and how it behaves, other than the fact that triples will not be rejected unless they contradict the Fedora ontology
Use cases
- Allow Fedora to be used with models that make use of assertions about non-repository objects (e.g. Hydra use case, tamsin johnson?)
- Allow Fedora to coexist with models that are unrelated to the Fedora ontology
- Decouple Fedora from LDP
- Fedora could be thought of as a model and set of services that exists on top of LDP, rather than as part of it.
- Named graphs for provenance would be a bit of a challenge unless there were a way to distinctly separate triples from the Fedora ontology/model from those provided by the user
- This is where the mailing list suggestion of "a way to exclude server managed triples" when GETting RDF from an object may be relevant, if support of that use case natively is a goal.
Implementation notes
- According to JIRA and the mailing list, this would be difficult to implement, given the way Fedora objects are currently expressed as JCR nodes
- I believe triples are currently expressed as properties in the JCR model. Do Fedora objects (not datastreams) have any JCR binary content? If not, could that be leveraged to implement something like this (e.g. serialize all statements that do not have a repository subject as binary)
...