Scenario 1: Non-Fedora-generated OCFL containing RDF.
Fedora is smart about extracting LDP structure
Starting with an OCFL like this:
[storage_root]
├── 0=ocfl_1.0
├── ocfl_1.0.html (optional copy of the OCFL specification)
├── myobject1
├── 0=ocfl_object_1.0
├── inventory.json
├── inventory.json.sha512
├── v1
├── content
├── myobject1.ttl
└── myobject1/
└── myobject1/
Scenario 1a: myobject1.ttl contains relative subjects
@prefix dcterms: <http://purl.org/dc/terms/>. </some-context/myobject1> dcterms:title "my object 1".
curl -X GET http://localhost:8080/root/myobject
@prefix dcterms: <http://purl.org/dc/terms/>. </some-context/myobject1> dcterms:title "my object 1".
Scenario 1b: myobject1.ttl contains external URL subjects
@prefix dcterms: <http://purl.org/dc/terms/>.
<http://non-fedora-host:port/context/myobject> dcterms:title "my object 1".
curl -X GET http://localhost:8080/root/myobject
@prefix dcterms: <http://purl.org/dc/terms/>. <http://non-fedora-host:port/context/myobject> dcterms:title "my object 1".
Scenario 1c: myobject1.ttl contains LDP containment info
@prefix ldp: <http://www.w3.org/ns/ldp#>.
</some-context/myobject1> a <http://www.w3.org/ns/ldp#RDFSource>, <http://www.w3.org/ns/ldp#BasicContainer>;
ldp:contains </some-context/myobject1/child> .
