Data Pod Management

Editor’s Draft,

This version:
https://solid.github.io/specification/pod-management/
Issue Tracking:
GitHub
Inline In Spec
Editor:
Your Name (Your Company)

Abstract

This document describes an RDF-driven Web API for managing users and data pods of a Solid pod server. Through this common API, servers with different implementations can be managed with the same apps.

Status of This Document

This document is an incomplete draft. The sections that have been incorporated have been reviewed following the Solid process. However, the information in this document is still subject to change.

You are invited to contribute any feedback, comments, or questions you might have.

1. Introduction

Write Introduction section.

Conformance

Conformance requirements are expressed with a combination of descriptive assertions and RFC 2119 terminology. The key words “MUST”, “MUST NOT”, “REQUIRED”, “SHALL”, “SHALL NOT”, “SHOULD”, “SHOULD NOT”, “RECOMMENDED”, “MAY”, and “OPTIONAL” in the normative parts of this document are to be interpreted as described in RFC 2119. However, for readability, these words do not appear in all uppercase letters in this specification.

All of the text of this specification is normative except sections explicitly marked as non-normative, examples, and notes. [RFC2119]

Examples in this specification are introduced with the words “for example” or are set apart from the normative text with class="example", like this:

This is an example of an informative example.

Informative notes begin with the word “Note” and are set apart from the normative text with class="note", like this:

Note, this is an informative note.

References

Normative References

[RFC2119]
S. Bradner. Key words for use in RFCs to Indicate Requirement Levels. March 1997. Best Current Practice. URL: https://tools.ietf.org/html/rfc2119

Issues Index

Write Introduction section.