...
Panel | ||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||||
Here we will begin to walk through the mechanics of creating the structures that will facilitate creation of the book and its pages.
Where "pcdm-object.ttl" follows:
Second, create the nested "raven/" pcdm:Object, which is also another ldp:BasicContainer.
Lastly, create an ldp:DirectContainer, "pages/" that will facilitate the establishment of relationships between "raven/" and its constituent pages.
Where "ldp-direct.ttl" follows:
An ldp:DirectContaner is an LDP construct that activates the creation of certain RDF triples when a new resource is added as a child of this container. We will see this in action next! |
...
Panel | |||||||
---|---|---|---|---|---|---|---|
| |||||||
In the same way that we used an ldp:DirectContainer to facilitate the auto-generation of triples linking "raven/" to each of the pages, now use the same pattern to auto-generate the creation of triples that link each page pcdm:Object to its their various file representations.
Where "ldp-cover-direct.ttl" follows:
Now, any new resource that is added as a child of the DirectContainer "files/" will cause the auto-generation of a new triple on "cover/" that has a predicate of pcdm:hasFile and an object of the new resource. |
Panel | |||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| |||||||||||||
Once again, we demonstrate the use of LDP in creating PCDM relationships simply as a result of repository interactions.
Where "cover.jpg" is attached. If you perform a subsequent HTTP HEAD on this new resource, you will see there is a "Link" header of rel="describedby". Update the RDF metadata of the ldp:NonRdfSource to specify that the resource is a pcdm:File, as follows:
Where "pcdm-file.ru" follows:
Repeat for the attached TIFF, cover.tif
After creating the two "cover" resources, an HTTP GET on "cover/" will include the two new triples:
Once again,
|
Panel | ||||
---|---|---|---|---|
| ||||
|
...