User:Reversedragon/SignEntityProposal

Data model

A Sign Entity resembles a Wikibase Item with the capacity for representing figurative symbols. It has a main body much like a regular Wikibase Item, a conceptual area of Fragment sub-Entities which represent small-scale variations in form, and a conceptual area of meaning sub-Entities which represent literal or figurative assigned meanings. In concept, it should not be assumed that any particular Sign Entity will actually use all three of these fields. Many Sign Entities may be used for completely literal concepts which only "figuratively" refer to themselves, and many Sign Entities will have only one variation such that they will not need Fragments. This will already sound perfectly logical when assuming that Signs which do not have Fragments will have meanings, or Signs which do not have meanings will have Fragments. However, Sign Entities are also allowed to have neither any meanings nor any Fragments. In this case, a Sign Entity is representing something strictly and completely literal which is not meant to refer to anything else, exactly as it would if it had a meaning referring to itself. This characteristic of the Sign Entity is a concession to the fact that in terms of the linguistic definition of sign, all digitally-encoded Entities are themselves technically signs rather than the literal real-world concepts they model; as models of reality, or of some particular fictional reality, all Entities potentially include errors with respect to their correspondence to the relationships existing within a particular defined reality (observed or defined Facticity). As such, it fundamentally makes sense to give all concepts in an ontology the ability to be changed from figurative to literal or from literal to figurative depending on how well they are found to properly correspond to a given defined reality. If, in a hypothetical scenario, people believed in the existence of luminiferous ether into the age of digital ontologies, this concept might be encoded as a literal Entity one day, but the day this model was falsified, whoever was maintaining the ontology would want to take the same Entity and reassign it as a figurative concept with a meaning of being a falsified model of what it models. Equally, if people were convinced string theory was impossible, but experiments showed a string theory equation to be correct, it would be important to update the ontology from having one meaning of the equation literally referring to itself to having two meanings of referring to itself or referring to the real-world process it accurately models. In other areas of knowledge, such as religion or poetry, all Signs would be assumed to be figurative and the purpose of the meanings area would be to separate different meanings of the same sign

...wait, what about S2 statements. S2 statements are supposed to represent specific models of objects or signifiers put together a specific way, so that a model from mainstream Marxism-Leninism stands separate from a model from Trotskyism stands separate from a model from Christianity from Buddhism from Hinduism. do we really need the meanings field when there are S2 statements?? that is a conundrum

@base         <https://research.moraleconomy.au/entity/> .
@prefix rdf:  <http://www.w3.org/1999/02/22-rdf-syntax-ns#> .
@prefix rdfs: <http://www.w3.org/2000/01/rdf-schema#> .
@prefix skos: <http://www.w3.org/2004/02/skos/core#> .
@prefix dct:  <http://purl.org/dc/terms/> .
@prefix ontolex:   <http://www.w3.org/ns/lemon/ontolex#> .
@prefix wikibase:  <http://wikiba.se/ontology#> .
@prefix seaturtle: <https://research.moraleconomy.au/seaturtle/ontology#> .
@prefix wdt:  <https://research.moraleconomy.au/prop/direct/> .

<S14>
 rdf:type  seaturtle:Sign, skos:Concept, ontolex:LexicalEntry ;  # the Entity is a Sign, and the Sign can have meanings
 # "pre-iconographical": dishes.
 seaturtle:dimension  <S3000>;  # S0 Item - data structure or conceptual division
   # literalness/countability of the concept - Z, S0, S1, S2, etc, as defined on Wikibase instance
 rdfs:label  "countable philosophy"@en ;
 rdfs:member <S14-F1>, <S14-F2>, <S14-A1> .  # list of Fragments and Associations
 skos:narrower <S14-F1>, <S14-F2> .
 ontolex:denotes <S14-F1>, <S14-F2> .  # S14 "literally means" Fragment F1 or F2
   # if there are no Fragments, generate a Fragment F0 which links the Sign Entity back to itself, but don't do this to skos:narrower
 ontolex:evokes  <S14-A1> .
   # clarification that Associations are meanings - :evokes is to be used for word connotations, etc.
 # in SeaTurtle all three lists would be inferred from the presence of the form blocks

<S14-F1>
 rdf:type  seaturtle:Fragment, ontolex:LexicalSense ;
 skos:broader <S14> ;
 # "pre-iconographical": red dishes.
 rdfs:label  "countable philosophical framework"@en .

<S14-F2>
 rdf:type  seaturtle:Fragment, ontolex:LexicalSense ;
 skos:broader <S14> ;
 # "pre-iconographical": blue dishes.
 rdfs:label  "countable ideology"@en .

<S14-A1>
 rdf:type  seaturtle:Association, wikibase:Sense, ontolex:LexicalConcept ;
 # "iconological": the emotional significance of dishes.
 rdfs:label  "literal"@en .

Works and editions

A Sign Entity can group together works and editions for easy reference, rather than having a number of separate free-floating Items that take extra time to plan out or keep track of. The meanings area is unused given that works and editions are literal objects, and the Fragments area is used to represent specific editions for particular years, physical media, languages, localization regions, adaptation formats based very clearly on the exact same story (Scholastic comics are a good example), and so forth.

Journey to the West
two editions

Dragon Ball
single-volume edition
three-volume edition

Wings of Fire
Wings of Fire Graphix

Into the Pit
Into the Pit (game)
Return to the Pit

Pokémon card with clear editions

Binomial names

A Sign Entity can represent a genus containing multiple binomial names, or a species containing multiple subspecies, with the binomial names modeled as Lexemes. The meanings field may optionally be used to connect particular type specimens which were at one time claimed to belong to the genus or species. If a particular type specimen is reassigned to a different genus or species constituting a different Entity, the Association should be marked as an obsolete model.

Archaeopteryx lithographica

Abelmoschus manihot var. pungens
Abelmoschus manihot var. tetraphyllus
Abelmoschus manihot subsp. manihot

Scientific models

string theory model of gravitons
meaning - tentative model of gravity

graviton field model
meaning - tentative model of gravity

loop quantum gravity
meaning - tentative model of gravity

Philosophical models

@base  <https://research.moraleconomy.au/entity/> .
# ... prefixes

<S2084>  # [S] worker / group of people said to qualify as "workers"
 rdf:type  seaturtle:Sign ;      # the Entity is a Sign
 seaturtle:dimension  <S3001> ;  # S1 Concept - image with non-literal uses
 rdfs:label  "worker"@en ;
 rdfs:label  'group of people said to qualify as "workers"'@en ;
 ontolex:evokes  <S2084-A1>, <S2084-A2> .

<S2084-A1>  rdf:type seaturtle:Association ;
 rdfs:label  "world proletariat"@en ;
 ontolex:lexicalizedSense  <S2091> .

<S2084-A2>  rdf:type seaturtle:Association ;
 rdfs:label  "national proletariat"@en ;
 ontolex:lexicalizedSense  <S2093> .

<S2091>  # [S2] Proletariat is singular and multiple countries can unite at once
 rdf:type  seaturtle:Sign ;
 seaturtle:dimension  <S3002> ;  # S2 Concept - bold claim about reality or fiction
 rdfs:label  "Proletariat is singular and multiple countries can unite at once"@en ;
 # No Fragments - variations will be handled by other parallel Entities
 # No Associations - because the Sign likely groups other Signs, both are essentially literal

<S2093>  # [S2] Proletariats are plural and belong to specific national populations
 rdf:type  seaturtle:Sign ;
 seaturtle:dimension  <S3002> ;
 rdfs:label  "Proletariats are plural and belong to specific national populations"@en ;
 # No Fragments, no Associations

Software versions

MediaWiki
important versions

SCP reports

S447
S447-F1 (SCP-447-1), the sphere itself
S447-F2 (SCP-447-2), the ooze that comes out of it

Creature form charts

Fictional hybrids that follow neat mathematical tables of A × B may be coded as Fragments, assuming that the game in question is one where all, or the great majority of, entries in the table are implied to be possible. This is different from the case of real-world genetic hybrids where hybrids are largely unpredictable and should simply be coded as separate Sign Entities without making use of the Fragments feature. This hybrid-table approach should not be taken as guidance for coding named unique relationships between instantiated characters; as these do not belong neatly to either member of the combined group, these should also be separate Entities not connected through Fragments. This is also to say that a fusion being that is not part of a general pattern should usually not be a Fragment except in the case of self-contained keychain pets, where the Sign Entity is meant to literally represent a particular keychain with fixed behavior.

Pokémon

@base  <https://research.moraleconomy.au/entity/> .
# ... prefixes

<S11037>  # [S] Vulpix
 rdf:type  seaturtle:Sign ;      # the Entity is a Sign
 seaturtle:dimension  <S3001> ;  # S1 Concept - fictional concept
 rdfs:label  "Vulpix"@en ;
 rdfs:label  "ロコン"@ja ;
 <PNNN> <SNNNN> ;  # Fire-type
 skos:narrower  <S2084-F1> .

<S11037-F1>  rdf:type seaturtle:Fragment ;
 <PNNN> <SNNNN> ;  # variation type - Pokémon regional variant
 ontolex:lexicalizedSense  <S10386> .  # Alolan Vulpix

<S11038>  # [S] Ninetales
 rdf:type  seaturtle:Sign ;      # the Entity is a Sign
 seaturtle:dimension  <S3001> ;  # S1 Concept - fictional concept
 rdfs:label  "Ninetales"@en ;
 rdfs:label  "キュウコン"@ja ;
 <PNNN> <SNNNN> ;  # Fire-type
 skos:narrower  <S11038-F1> .

<S11037-F1>  rdf:type seaturtle:Fragment ;
 <PNNN> <SNNNN> ;  # variation type - Pokémon regional variant
 ontolex:lexicalizedSense  <S10387> .  # Alolan Ninetales

<S10386>  # [S] Alolan Vulpix
 # ... S1 item
 rdfs:label  "Alolan Vulpix"@en ;
 <PNNN> <SNNNN> ;  # Ice-type
 skos:broader  <S11037> .

<S10387>  # [S] Alolan Ninetales
 # ... S1 item
 rdfs:label  "Alolan Ninetales"@en ;
 <PNNN> <SNNNN> ;  # Ice-type
 <PNNN> <SNNNN> ;  # Fairy-type
 skos:broader  <S11038> .

Asekai (zensekai project; unreleased)

I am doing this totally from memory. Valenoern had better fix this

Valenoern
Metric 012n / Metric Lei'un'er'n
Metric 012n / Metric CypherWanton
Rexdecima
Burskandrix

Monster Rancher / Monster Farm

# in Monster Rancher, hybrids are listed by their main strain

Crossdrawn Ways / CDRW (zensekai project; unreleased)

# in CrossDRawn Ways, hybrids are listed by their texture strain rather than their main strain
sundersorce  Sundersorce "Sunder"
Bear-arms    Chase    × Sunder
Escalade     Memorō   × Sunder
(puppy)      Verve    × Sunder
Sledge       Shade    × Sunder