Move redistribution to its own section

Author: jaimergp

peps/pep-0804.rst

@@ -207,6 +207,8 @@ canonical, or which versioning scheme applies to virtual DepURLs (see Appendix
 B). The corresponding answers are not given in this PEP; instead we delegate
 that responsibility to the central registry maintainers.
 
+The canonical filename for the central registry document MUST be ``registry.json``.
+
 Schema
 ^^^^^^
 
@@ -264,7 +266,7 @@ Each entry in this list is defined as:
       - Description
     * - ``id`` (required)
       - ``string`` matching regex ``^dep:.+$``
-      - The entry identifier MUST be a valid ``DepURL`` string.
+      - The entry identifier MUST be a valid DepURL string.
     * - ``description``
       - ``string``
       - Free-form field to add some details about the package. Allows Markdown.
@@ -616,6 +618,17 @@ required. Extra keys MUST NOT be allowed.
   had to be bumped to accommodate a change of release schema). In that regard, we do
   not encode explicit mapping semantics for epochs or pre-releases.
 
+Redistribution
+--------------
+
+The central registry, the known ecosystems list and the mapping documents MAY be
+packaged for offline distribution in each platform.
+
+The authors recommend placing them in the standard location for data artifacts in each
+operating system; e.g. ``$XDG_DATA_DIRS`` on Linux and others, ``~/Library/Application
+Support`` on macOS, and ``%LOCALAPPDATA%`` for Windows. The subdirectory identifier MUST
+be ``external-packaging-metadata-mappings``, and SHOULD only contain documents
+corresponding to the aforementioned schemas, which MUST use their canonical filenames.
 
 Examples
 --------