Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 4 Next »

This article describes the role of the “Cluster” named graph in MMS5. Layer 1 forbids arbitrary writes to this graph and instead exposes a set of LDP endpoints.

This named graph holds organizational objects that are global to the deployed MMS5 cluster. Specifically, a Repo is the container for version-controlled data (similar to a git repository), a Collection is readonly view that selects the union of any number of Refs when queried, and an Org is an entity that owns Repos or Collections.

Linked Data Platform (LDP) actions

The following list describes the LDP semantics of various HTTP operations available on Cluster objects.

  • /orgs

    • GET – Enumerates all orgs along with their public properties.

  • /orgs/{ORG_ID}

    • PUT – Creates a new org.

      • Suggested properties: dct:title "{ORG_TITLE}"

    • GET – Reads public properties of the given org.

    • PATCH – Updates an existing org.

    • DELETE -- Deletes an org.

  • /orgs/{ORG_ID}/repos/{REPO_ID}

    • GET – Enumerates all repos along with their public properties.

  • /orgs/{ORG_ID}/repos/{REPO_ID}

    • PUT – Creates a new repo.

      • Suggested properties: dct:title "{REPO_TITLE}"

    • GET – Reads public properties of the given repo.

    • PATCH – Updates an existing repo.

    • DELETE -- Deletes a repo.

  • /orgs/{ORG_ID}/collections/{COLLECTION_ID}

    • GET – Enumerates all collections along with their public properties.

  • /orgs/{ORG_ID}/collections/{COLLECTION_ID}

    • PUT – Creates a new collection.

      • Suggested properties: dct:title "{COLLECTION_TITLE}"

    • GET – Reads public properties of the given collection.

    • PATCH – Updates an existing collection.

    • DELETE -- Deletes a collection.

  • No labels