Jump to content
Main menu
Main menu
move to sidebar
hide
Navigation
Main page
Prototype
Items
Properties
All Categories
Recent changes
Random page
Help about MediaWiki
Philosophical Research
Search
Search
Appearance
Create account
Log in
Personal tools
Create account
Log in
Pages for logged out editors
learn more
Contributions
Talk
Editing
User:Reversedragon/SignEntityProposal
User page
Discussion
English
Read
Edit
View history
Tools
Tools
move to sidebar
hide
Actions
Read
Edit
View history
General
What links here
Related changes
User contributions
Logs
View user groups
Special pages
Page information
In other projects
Appearance
move to sidebar
hide
Warning:
You are not logged in. Your IP address will be publicly visible if you make any edits. If you
log in
or
create an account
, your edits will be attributed to your username, along with other benefits.
Anti-spam check. Do
not
fill this in!
== 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 <i>sign</i>, 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. <del>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</del> ...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 <pre> @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 . </pre> == Works and editions [deprecated] == 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. === Lexemes approach === In lack of Sign Entities, it would be perfectly possible for a Wikibase to reinterpret the concept of in-text citations as Lexemes. Under this model, a Lexeme narrowly represents the concept of exactly what qualities of a text are rendered into written language as a citation. <cite>Terrorism and Communism</cite> has the forms "Terrorism and Communism" (its title) and "TC8" (its bop citation code), but not necessarily a number of pages or a publication year. <cite>Dragon Ball</cite> has the forms "Dragon Ball" (books), "Dragon Ball" (first show), "Dragon Ball Z" or "DBZ" (second show), "Dragon Ball" (1-volume edition), and "Dragon Ball" (3-volume edition), which are treated as [https://www.w3.org/2019/09/lexicog/#formrestriction different senses] of the phrase. <pre> @base <https://research.moraleconomy.au/entity/> . # ... prefixes <L777> wikibase:lemma "ドラゴンボール"@ja . # ... parallel Lexeme for Japanese-language usages <L778> # Dragon Ball rdf:type wikibase:Lexeme ; # the Entity is a Lexeme wikibase:lemma "Dragon Ball"@en ; wikibase:lexicalCategory <QN100> ; # work citation phrase dct:language <Q1011> ; # English (en) ontolex:sense <L778-S1>, <L778-S2>, <L778-S3>, <L778-S4>, <L778-S5>, <L778-S6> ; ontolex:lexicalForm <L778-F1>, <L778-F2>, <L778-F3> . <L778-S1> rdf:type wikibase:Sense, ontolex:LexicalSense ; skos:definition "serialized comic, any edition"@en . <L778-S2> a wikibase:Sense, ontolex:LexicalSense ; skos:definition "first show, any edition"@en . <L778-S3> a wikibase:Sense, ontolex:LexicalSense ; skos:definition "second show, any edition"@en ; lexicog:restrictedTo <L778-F2>, <L778-F3> . # S3 is only called "DBZ" <L778-S4> a wikibase:Sense, ontolex:LexicalSense ; skos:definition "books, 1-volume edition"@en . lexicog:restrictedTo <L778-F1> . # if S4 is in front of you you are most likely to call it "Dragon Ball" # ... ok to link this Sense to edition Items on wikidata containing Properties <L778-S5> a wikibase:Sense, ontolex:LexicalSense ; skos:definition "books, 3-volume edition"@en . # ... ok to link this to edition Items <L778-S6> a wikibase:Sense, ontolex:LexicalSense ; skos:definition "books, 1-volume edition with separated Z era"@en . # no restrictedTo - if S6 is in front of you it is quite possible you'll call it DBZ # ... ok to link this to edition Items <L778-F1> rdf:type wikibase:Form , ontolex:Form ; ontolex:representation "Dragon Ball"@en ; wikibase:grammaticalFeature <QNNNN> . <L778-F2> a wikibase:Form , ontolex:Form ; ontolex:representation "Dragon Ball Z"@en ; wikibase:grammaticalFeature <QNNNN> . <L778-F3> a wikibase:Form , ontolex:Form ; ontolex:representation "DBZ"@en ; wikibase:grammaticalFeature <QNNNN> . # the one frightening thing about this approach is when individual episodes happen to have bop citation codes, # and you might or might not have to make 200+ Senses. </pre> === Fragments approach === <pre> Journey to the West two editions </pre> <pre> Dragon Ball single-volume edition three-volume edition </pre> <pre> Wings of Fire Wings of Fire Graphix </pre> <pre> Into the Pit Into the Pit (game) Return to the Pit </pre> <pre> Pokémon card with clear editions </pre> == 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. <pre> Archaeopteryx lithographica </pre> <pre> Abelmoschus manihot var. pungens Abelmoschus manihot var. tetraphyllus Abelmoschus manihot subsp. manihot </pre> == Scientific models == <pre> string theory model of gravitons meaning - tentative model of gravity </pre> <pre> graviton field model meaning - tentative model of gravity </pre> <pre> loop quantum gravity meaning - tentative model of gravity </pre> == Philosophical models [deprecated] == For the purposes of modeling parallel philosophies, Fragments and Associations may not be the best approach compared with simple nested "particle-bond" structures. Elementary concepts either literal or non-literal should be stacked up into S2 statements representing particular parallel ontologies at fine levels of scale, and higher-level S2 statements can then be built on this. The signification relation should be represented through Lexemes connecting to S2 statements, or Sign Entities connecting to S0 concepts containing S2 concepts. === S2-centric approach === <pre> # rdfs:label has been omitted for brevity <SNNN3> # [S2] A version of socialism-in-one-country is the one true Leninism rdf:type seaturtle:Sign ; seaturtle:dimension <S3002> ; # S2 Statement - bold claim about reality or fiction with uncertain or subjective truth status <PNNNN> <S2093> . # model combines or unifies models - Proletariats are plural <SNNN4> # [S2] Trotskyism is the one true Leninism rdf:type seaturtle:Sign ; seaturtle:dimension <S3002> ; # S2 Statement <PNNNN> <S2091> . # model combines or unifies models - Proletariat is singular <S2091> # [F2] Proletariat is singular and multiple countries can unite at once rdf:type seaturtle:Sign ; seaturtle:dimension <S3012> ; # F2 Statement - bold claim about reality or fiction that appears to have been falsified <PNNNN> <SNN12> . # model involves elements - capable subpopulation (world) <S2093> # [S2] Proletariats are plural and belong to specific national populations rdf:type seaturtle:Sign ; seaturtle:dimension <S3002> ; # S2 Statement <PNNNN> <SNN11> . # model involves elements - capable subpopulation (national) <SNN11> # [S] capable subpopulation (national) seaturtle:dimension <S3000> . # S0 Concept <SNN12> # [S] capable subpopulation (world) seaturtle:dimension <S3000> . # S0 Concept - mathematical structure or abstract repeated pattern </pre> === Associations approach === <pre> @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 </pre> == Software versions == <pre> MediaWiki important versions </pre> == SCP reports == <pre> S447 S447-F1 (SCP-447-1), the sphere itself S447-F2 (SCP-447-2), the ooze that comes out of it </pre> == 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 <em>except</em> 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 === <pre> @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 <PNNN> <SNNNN> ; # non-unique entity can become - Ninetales skos:narrower <S2084-F1> . <S11037-F1> rdf:type seaturtle:Fragment ; <PNNN> <SNNNN> ; # variation type - Pokémon regional variant seaturtle:dimension <S3001> ; rdfs:label "Alolan Vulpix"@en ; <PNNN> <SNNNN> ; # Ice-type <PNNN> <S11037-F1> ; # non-unique entity can become - Alolan Ninetales skos:broader <S11037> . <S11038> # [S] Ninetales rdf:type seaturtle:Sign ; # the Entity is a Sign seaturtle:dimension <S3001> ; 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 seaturtle:dimension <S3001> ; rdfs:label "Alolan Ninetales"@en ; <PNNN> <SNNNN> ; # Ice-type <PNNN> <SNNNN> ; # Fairy-type skos:broader <S11038> . </pre> === Digimon === <pre> <SNNN1> # Digital Monster ver. 1 rdf:type seaturtle:Sign ; # the Entity is a Sign seaturtle:dimension <S2000> ; # Z Concept - concrete object or work rdfs:label "Digital Monster ver. 1"@en ; <P4> <SNNNN> ; # instance of - Digivice (keychain) skos:narrower <SNNN1-F1> . <SNNN1-F1> rdf:type seaturtle:Fragment ; <PNNN> <SNNNN> ; # variation type - virtual pet stage <PNNN> <SNNN1-F2> ; # non-unique entity can become - Koromon <PNNN> <SNNNN> ; # becomes Koromon within 1 hour ontolex:lexicalizedSense <SNN11> . # Botamon <SNN11> # [S] Botamon rdf:type seaturtle:Sign ; # the Entity is a Sign seaturtle:dimension <S3001> ; # S1 Concept - fictional concept rdfs:label "Botamon"@en ; rdfs:label "ボタモン"@ja ; <PNNN> <SNNNN> ; # Baby I stage skos:broader <SNNN1> ; # Digital Monster ver. 1 skos:broader <SNN22> . # Coromon (Digimon World) </pre> === Keitai Denjuu Telefang === <pre> </pre> === Monster Rancher / Monster Farm === <pre> # in Monster Rancher, hybrids are listed by their main strain </pre> == Enabling RDF mappings without creating new Entity types == One strength of Wikibase Items is their ability to create arbitrary [https://www.w3.org/TR/rdf-schema/#ch_classes data structures] ([https://en.wikipedia.org/wiki/Class_(set_theory) classes]) and immediately begin subsetting them with new data structures. Using a Wikibase extension that can associate Properties to standard properties within RDF ontologies can enable trivially coding Associations and Forms without making them permanent. One notable downside of this approach is that in cases it is actually useful to have permanent links for forms of something, the links do not have their own names such as "S14-F1". <pre># input Items <PNNN1> owl:sameAs skos:narrower . # this is managed by Wikibase RDF extension (etc) <PNNN2> owl:sameAs ontolex:evokes . <QNN10> rdf:type wikibase:Item ; <PNNN1> <QNN11> . # some Property-based statement of variant <PNNN2> <QNN21> . # some Property-based statement of meaning <QNN11> rdf:type wikibase:Item . <QNN21> rdf:type wikibase:Item . </pre> <pre># output Items <QNN10> rdf:type seaturtle:Sign, wikibase:Item ; skos:narrower <QNN11> ; skos:evokes <QNN21> . <QNN11> rdf:type seaturtle:Fragment, seaturtle:Sign, wikibase:Item ; skos:broader <QNN10> ; <QNN21> rdf:type wikibase:Item ; skos:isEvokedBy <QNN10> ; </pre> === Statement IDs approach === If it were possible to give statements particular IDs and lock them from deletion, this would serve essentially the same purpose as Association sub-Entities. <pre># input Items <PNNN1> owl:sameAs skos:narrower . # this is managed by Wikibase RDF extension (etc) <PNNN2> owl:sameAs ontolex:evokes . <QNN10> rdf:type wikibase:Item ; <PNNN1> wds:QNN10-F1 . # some Property-based statement of variant <PNNN2> wds:QNN10-A1 . # some Property-based statement of meaning wds:QNN10-F1 # named statement that happens to be labeled with an "F" rdf:type seaturtle:Fragment, wikibase:Statement ; # this may or may not be possible ps:PNNN1 <QNN11> . wds:QNN10-A1 # named statement that happens to be labeled with an "A" rdf:type seaturtle:Association, wikibase:Statement ; ps:PNNN2 <QNN21> . <QNN11> rdf:type wikibase:Item . <QNN21> rdf:type wikibase:Item . </pre> [[Category:Archived proposals]]
Summary:
Please note that all contributions to Philosophical Research may be edited, altered, or removed by other contributors. If you do not want your writing to be edited mercilessly, then do not submit it here.
You are also promising us that you wrote this yourself, or copied it from a public domain or similar
free resource
.
Copyright is complete nonsense
, but people do have to buy items to be able to charge anyone taxes.
Cancel
Editing help
(opens in new window)