.. vim: set fileencoding=utf-8: .. -*- coding: utf-8 -*- .. +--------------------------------------------------------------------------+ | | | Licensed under the Apache License, Version 2.0 (the "License"); | | you may not use this file except in compliance with the License. | | You may obtain a copy of the License at | | | | http://www.apache.org/licenses/LICENSE-2.0 | | | | Unless required by applicable law or agreed to in writing, software | | distributed under the License is distributed on an "AS IS" BASIS, | | WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. | | See the License for the specific language governing permissions and | | limitations under the License. | | | +--------------------------------------------------------------------------+ ******************************************************************************* Germanic-derived Verb Vocabulary ******************************************************************************* This reference provides Germanic alternatives to Latin-derived verbs organized by semantic clusters. These terms can be used to maintain linguistic consistency within related function names, class hierarchies, or module-level names. For core naming patterns and structural conventions, see the main :doc:`nomenclature` guide. For Latin-derived terms (project default), see :doc:`nomenclature-latin`. Germanic Naming Philosophy =============================================================================== Germanic-derived terms often provide: - **Directness**: ``get`` vs ``access``, ``make`` vs ``create`` - **Concrete imagery**: ``grab`` vs ``acquire``, ``sniff`` vs ``examine`` - **Technical familiarity**: ``ping`` vs ``probe``, ``dump`` vs ``save`` - **Compound flexibility**: ``setup``, ``handoff``, ``unswitch`` Germanic terms should only be used to maintain consistency with existing terminology or because they form a better self-contained cluster of names than the equivalent Latin-derived terms (e.g., for the variants of some enums). Verb Prefixes by Semantic Cluster =============================================================================== Analysis and Discovery ------------------------------------------------------------------------------- **find_** (discover) Detects or determines value from environment or context. **list_** (survey) Lists or enumerates members of external resource collection. **sniff_** (examine) Retrieves metadata about resource without accessing full content. Informal but established in technical contexts. **weigh_** (assess) Examines data to derive insights or patterns. Component Initialization ------------------------------------------------------------------------------- **ready_** (prepare) Fully initializes component, including registration of handlers/extensions. Used as verb, not adjective. **setup_** (configure) Applies settings or parameters to component, preparing it for operation. Compound from "set up". Computation ------------------------------------------------------------------------------- **reckon_** (calculate) Computes value from one or more inputs using defined algorithm. Data Operations ------------------------------------------------------------------------------- **ask_** (query/request) Performs structured data retrieval with parameters or filters. Also used for initiating requests. **change_** (modify) Updates in-process object state. Alternative to ``freshen_`` for disambiguation. **fetch_** (retrieve) Obtains copy of data from external resource. No release required. **freshen_** (update) Modifies state of external resource. **get_** (access) Returns value via computed or indirect access (property getter, descriptor protocol). For in-process objects only. **shape_** (transform) Changes data structure or format. Avoids Latin ``re-`` prefix. **sift_** (filter) Returns subset of objects matching specified criteria. **split_** (parse) Extracts structured data from formatted input (JSON, XML). Exception Handling ------------------------------------------------------------------------------- **catch_** (intercept) Invokes functions while capturing their exceptions for later handling. Persistence and Serialization ------------------------------------------------------------------------------- **load_** (restore) Deserializes object from persistent storage. Common pair with ``dump``. **dump_** (save) Serializes object to persistent storage. Common pair with ``load``. Presentation and Output ------------------------------------------------------------------------------- **fillin_