...
Panel | ||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||||
Here we will begin to walk through the mechanics of creating the structures that will facilitate creation of the collection and its single member, in this case. First, create the top-level "collections/" pcdm:Object, which is also an ldp:BasicContainer.
Where "pcdm-object.ttl" follows:
Second, create the nested "poe/" pcdm:Object, which is also another ldp:BasicContainer.
Lastly, create an ldp:IndirectContainer, "members/" that will facilitate the establishment of relationships between "poe/" and the collection members.
Where "ldp-indirect.ttl" follows:
Similar to the previously described ldp:DirectContaner, an ldp:IndirectContainer is an LDP construct that also 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 | |||||||||
---|---|---|---|---|---|---|---|---|---|
| |||||||||
Create a new pcdm:Object, "ravenProxy/", that is an ldp:RdfSource within the "members/" IndirectContainer.
Where "pcdm-object.ttl" follows:
As mentioned in the previous step, the addition of "ravenProxy/" automatically creates the following new triple on "poe/".
|