Naming: Difference between revisions
From
(Created page with "Replimat is divided into Category:Materials, Category:Transformations, Category:Parts, Category:Techniques, Category:Projects, and :Category:Lifecyc...") |
No edit summary |
||
| (23 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
Replimat | Replimat contains [[:Category:Vitamins|vitamins]], [[:Category:Materials|materials]], [[:Category:Transformations|transformations]], [[:Category:Parts|parts]], [[:Category:Techniques|techniques]], [[:Category:Projects|projects]], and [[:Category:Lifecycles|lifecycles]]. Names for patterns in each of these categories follow conventions noted on this page. Conventions are intended to function as guidelines to reduce effort required to choose an appropriate name. Where necessary, they may be overridden at any level within the system, but doing so should serve as a hint toward improved organization. | ||
* A name should function as a label for a single pattern within it's category. | * A name should function as a label for a single pattern within it's category. | ||
* A name should be unique within it's category. | * A name should be unique within it's category. | ||
* A name should function with minimal modification (for instance: replacing spaces with underscores) as an OpenSCAD | * A name should function with minimal modification (for instance: replacing spaces with underscores) as an NopSCADlib / OpenSCAD, OpenJSCAD, or Rust function identifier, a wiki page name, etc. | ||
* A name should be plural, to enable project-wide [https://en.wikipedia.org/wiki/Object%E2%80%93relational_mapping object relational mapping] efforts (more details [https://flourishlib.com/docs/fORM.html here]). | |||
* Adjective structure should follow the pattern: opinion size age shape color origin material purpose '''noun'''. | |||
<youtube>GFQaEYEc8_8</youtube> | |||
=References= | |||
* [http://www.bkent.net/Doc/simple5.htm A Simple Guide to Five Normal Forms in Relational Database Theory] | |||
* [https://www.bbc.com/culture/article/20160908-the-language-rules-we-know-but-dont-know-we-know The language rules we know – but don’t know we know] | |||
* [https://en.wikipedia.org/wiki/Linguistic_relativity Wikipedia: Linguistic relativity] | |||
* [https://archive.org/details/in.ernet.dli.2015.30957 Language In Thought And Action by Hayakawa, S. I.] | |||
Latest revision as of 16:36, 13 January 2023
Replimat contains vitamins, materials, transformations, parts, techniques, projects, and lifecycles. Names for patterns in each of these categories follow conventions noted on this page. Conventions are intended to function as guidelines to reduce effort required to choose an appropriate name. Where necessary, they may be overridden at any level within the system, but doing so should serve as a hint toward improved organization.
- A name should function as a label for a single pattern within it's category.
- A name should be unique within it's category.
- A name should function with minimal modification (for instance: replacing spaces with underscores) as an NopSCADlib / OpenSCAD, OpenJSCAD, or Rust function identifier, a wiki page name, etc.
- A name should be plural, to enable project-wide object relational mapping efforts (more details here).
- Adjective structure should follow the pattern: opinion size age shape color origin material purpose noun.
