The prefix "holo-" means "whole" in Greek, but in common use it is most associated with holograms, or maybe with the Holocaust, neither of which really fits as far as I can tell. Holomorphic functions are a thing in complex analysis, but the functions we're concerned with here have little to do with that. PiRSquared17 (talk) 02:41, 16 September 2020 (UTC)[reply]
I'm Jewish, and the similarity to "holocaust" doesn't bother me. It's also used in words like "holistic", and it's not a big deal. For better or worse, however, "Holopedia" is used as a nickname of the Minnan Wikipedia, so it can become ambiguous. --Amir E. Aharoni (talk) 11:25, 16 September 2020 (UTC)[reply]
No - it is not easy to translate (not transliterate) to Chinese if the translated name needs to be informative. In Chinese, names of Wikimedia project are never transliterated.--GZWDer (talk) 13:37, 16 September 2020 (UTC)[reply]
I also agree that the prefix "holo" has no direct relation to nazi's Holocaust. It is related to the English term "holy" (saint/spirit); "holocaust" is a composed as a name created after the genocide to describe it as a mass murdering/attack ("caust", related to "caustic") based on spirituality/religion ("holo"). And this is not proposing the use of "caust". Yes the proposal is highly related to "holomorphic functions" ("holo" because the space where the transform is not defined is very thin, almost invisible/transparent, insignificant, infinitesimal, compared to the space where it has a defined meaning, so it is difficult to observe and it just exists as a "spirit"; you can like it as well to "hologram" where this transparent space is diffused/spread "everywhere" but you don't see anything if you try to locate a point where this occurs; it also applies to "fractal spaces" and "fractal dimensions", i.e. non-integer dimensions that smoothly link spaces with countable finite dimensions), but it's too much technical for people not aware in advanced mathematics (and that also have difficulties to understand the base concept of "morphism", which actually means a transform by a regulated relation between different entities so that some properties are preserved by the transform, and which sometimes an produce no result or multiple results, possibly with uncertainty margins, i.e. just probabilistic or fuzzy results for which no universal decision can be concluded). Note that "morphism" is based on the greek radical "morph" (used also on Slavic languages) which just translates to the "form" radical in Latin (and most Italic or Germanic languages). But Greek terms in Italic/Germanic languages are considered too much scientific terminology. If we reduce "homomorphism" just to "holo" (which is also used on scientific terms based on Greek), we loose the important "form"/"morph" meaning that this feature better describes ("holo" is not a requirement), that's why I would not use it in "holopedia" which would be better used to describe a wiki-based encyclopedia about religions/spirituaty... I would largely prefer some variation based on the term "mutate" (change of form/morph, i.e. "transform"). verdy_p (talk) 14:26, 16 September 2020 (UTC)[reply]
You suppose badly. see w:en:Holomorphic function which is also mostly the same as "holomorphism", but don't confuse it with "homomorphism" which exists too (not all homomorphism are homoporphisms, this remark applies also to the reverse; however all holomorphic functions are holomorphisms, the reverse being false). Yes it is a too technical term for what would in fine would be a repository of code to transform a set of data from any types to another set of data, plus some design feature to describe them like an API, and implement them with some guided processing model matching the described API. For Abstract Wikipedia only the output would be limited to some wikitext that is embeddable in some page, a sort of "supertemplate", except that its input would not limited to just text, and its implementation not limited to be using the wiki syntax or a Lua module and the output is still transformable. The above functions could take the whole existing database of some wiki or external source in input, so the functions are just like "bricks" you can combine in a graph-like structure and it may also have timing constraints and synchronization points I can think these "functions" like an extensible API offering a set of objects with accessors or methods but working as standalone modules and insatiable many times with their own internal state, much like a javascript or Lua "object" (that you can duplicate with a "new" to copy its internal state), and in fact the "functions" describes above are most like "morphisms" rather than true "functions" in the strict mathematical meaning.verdy_p (talk) 01:00, 19 September 2020 (UTC)[reply]
