Terminology

The following terms are used within these pages to convey specific meanings in most instances; it should be obvious whether or not this meaning is intended through context:

Access (verb) - To reference or use in any way.

Content (noun) - A general term for anything that can be introduced or changed by a datapack.

Define (verb) - To introduce something that does not exist otherwise--usually in the context of structured data or resources.

Ephemeral (adjective) - Exists or is useful only within the scope it is defined.

External (adjective) - Defined in a namespace other than the pack's primary namespace.

Namespace (noun) - A datapack namespace; refers to the name of a 1st level subdirectory of the data directory in a datapack (<datapack name>/data/<namespace>).

Owned (adjective) - See Owned Objects.

Pack (noun) - Somewhat interchangeable term for "datapack"--tends to be used in the context of datapack content, while "datapack" tends to be used in the context of datapack files/directories.

Pack ID (noun) - See Pack ID. Interchangeable with "primary namespace".

Persistent (adjective) - Exists for longer than the scope it is defined.

Primary Namespace (noun) - See Primary Namespace.

Private (adjective) - See Private Content.

Public (adjective) - See Private Content.

Registry (noun) - A 2nd level subdirectory of the data directory in a datapack (<datapack name>/data/<namespace>/<registry>).

Resource (noun) - A file within a registry or registry tag.

Scope (noun) - All possible commands that could possibly be executed as a direct result (i.e. would be limited by max_command_sequence_length) of a function's/function tag's execution.

---

The use of uppercase bolded words such as MUST, SHOULD, MAY, etc. are in adherence to RFC 2119.

Code-block text surrounded by angle brackets conveys that it should be replaced by what is inside the angle brackets conceptually. For example, in the context of a pack with pack ID foo, <pack ID> means foo.