Jump to content

User:Reversedragon/SignSubpageProposal: Difference between revisions

From Philosophical Research
Lexemes and Wavebuilder
sense / sensu label
Line 15: Line 15:
I am not totally sure if this truly belongs on this page, but I have found a way for Wavebuilder combinations on Lexemes to make sense. Lexemes should not be combined with Items and Items should not be combined with Lexemes. This is what was already implied to be the case the way things already were. But now, I have a more solid image of how Lexemes should be used.
I am not totally sure if this truly belongs on this page, but I have found a way for Wavebuilder combinations on Lexemes to make sense. Lexemes should not be combined with Items and Items should not be combined with Lexemes. This is what was already implied to be the case the way things already were. But now, I have a more solid image of how Lexemes should be used.


Lexemes should be used about as they were in [https://codeberg.org/reverseDragon/wavebuilder-unstable/src/commit/9aea1a493146025e80fe29421ac90b5da50f63c2/dict/190-thesaurus.dict thesaurus.dict]. We start with fairly basic words, and combine one word with another that suggests the sense the word is used in to arrive at a more specific term. This probably deserves its own Wavebuilder operator. It has the characteristic of being order-dependent, like Wordiverse's "how does X become Y" operator (which is more or less the same as the [[Ontology:P135|"characterization" Property]] in concept, in that it requests the two elements that combine to form a particular result). <s>Term InSense Y?</s> X Sensu Y.
Lexemes should be used about as they were in [https://codeberg.org/reverseDragon/wavebuilder-unstable/src/commit/9aea1a493146025e80fe29421ac90b5da50f63c2/dict/190-thesaurus.dict thesaurus.dict]. We start with fairly basic words, and combine one word with another that suggests the sense the word is used in to arrive at a more specific term. This probably deserves its own Wavebuilder operator. It has the characteristic of being order-dependent, like Wordiverse's "how does X become Y" operator (which is more or less the same as the [[Ontology:P135|"characterization" Property]] in concept, in that it requests the two elements that combine to form a particular result). X Sensu Y.


=== Demo ===
=== Demo ===


<dl class="wikitable hue data_wavebuild">
<dl class="wikitable hue data_wavebuild">
{{HueRoster|P=Wavebuilder: hyponym| staging-ground |OP=sensu| place }}
{{HueRoster|P=Wavebuilder: hyponym| staging-ground |OP=sense| place }}
</dl>
</dl>


<dl class="wikitable hue data_wavebuild data_pkmn">   
<dl class="wikitable hue data_wavebuild data_pkmn">   
{{HueRoster|P=Wavebuilder: hypernym| stage |OP1=sensu| place }}
{{HueRoster|P=Wavebuilder: hypernym| stage |OP1=sense| place }}
</dl>
</dl>


<pre>&lt;!--      en: stage  SENSU  place  PRODUCES  staging-ground --&gt;
<pre>&lt;!--      en: stage  SENSU  place  DUBBED  staging-ground --&gt;
&lt;!-- en: FROM  stage  SENSU  place  PRODUCING staging-ground --&gt;</pre>
&lt;!-- en: FROM  stage  SENSU  place  DUBBED staging-ground --&gt;</pre>




[[Category:Policy guides]]
[[Category:Policy guides]] __NOTOC__

Revision as of 06:13, 3 June 2025

Now that Ontology pages have gotten so elaborate, and become more or less fully functional as semantic MediaWiki entries, it is likely that the Wikibase feature is going to be outright removed and the main namespace turned into something more like a home for human-readable names in various languages that form simple links to both Lexemes (standardized versions of terms themselves) and Ontology pages. The Ontology namespace could be dropped entirely, or more likely, used solely for number-based page names while the main namespace holds the readable ones.

With this change, there is a question of how to best realize book editions and Lexeme Senses, both of which are still relatively cumbersome to input and make use of quickly.

Book editions

These were addressed in the Sign Entity proposal.

Lexeme Senses

[unfinished]

Lexemes and Wavebuilder

I am not totally sure if this truly belongs on this page, but I have found a way for Wavebuilder combinations on Lexemes to make sense. Lexemes should not be combined with Items and Items should not be combined with Lexemes. This is what was already implied to be the case the way things already were. But now, I have a more solid image of how Lexemes should be used.

Lexemes should be used about as they were in thesaurus.dict. We start with fairly basic words, and combine one word with another that suggests the sense the word is used in to arrive at a more specific term. This probably deserves its own Wavebuilder operator. It has the characteristic of being order-dependent, like Wordiverse's "how does X become Y" operator (which is more or less the same as the "characterization" Property in concept, in that it requests the two elements that combine to form a particular result). X Sensu Y.

Demo

Wavebuilder: hyponym
staging-ground
sense
place
Wavebuilder: hypernym
stage
sense
place
<!--       en: stage  SENSU  place  DUBBED  staging-ground -->
<!-- en: FROM  stage  SENSU  place  DUBBED  staging-ground -->