User:Reversedragon/SignEntityProposal - Revision history

Reversedragon: category

2025-02-13T10:29:39Z

Reversedragon: /* Creature form charts */ remove difficult examples (sorry)

2025-02-13T10:26:41Z

Creature form charts: remove difficult examples (sorry)

@@ Line 326: / Line 326: @@
   skos:broader  <SNNN1> ;  # Digital Monster ver. 1
   skos:broader  <SNN22> .  # Coromon (Digimon World)
 </pre>
@@ Line 336: / Line 331: @@
 <pre>
 </pre>
@@ Line 354: / Line 337: @@
 <pre>
 # in Monster Rancher, hybrids are listed by their main strain
 </pre>

Reversedragon: deprecation progress

2025-02-13T10:25:04Z

deprecation progress

← Older revision		Revision as of 10:25, 13 February 2025
Line 48:		Line 48:
	</pre>		</pre>

	== Works and editions ==		== 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.		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.
Line 171:		Line 171:
	</pre>		</pre>

	== Philosophical models ==		== 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.		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.

Reversedragon: /* Works and editions */ Lexemes approach

2025-02-13T05:56:26Z

Works and editions: Lexemes approach

← Older revision		Revision as of 05:56, 13 February 2025
Line 51:		Line 51:

	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.		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>		<pre>

Reversedragon: /* Enabling RDF mappings without creating new Entity types */ statement IDs

2025-02-11T04:14:03Z

Enabling RDF mappings without creating new Entity types: statement IDs

@@ Line 340: / Line 340: @@
   rdf:type  wikibase:Item ;
   skos:isEvokedBy <QNN10> ;
 </pre>

Reversedragon: /* Enabling RDF mappings without creating new Entity types */ correction

2025-02-11T02:49:10Z

Enabling RDF mappings without creating new Entity types: correction

← Older revision		Revision as of 02:49, 11 February 2025
Line 338:		Line 338:

	<QNN21>		<QNN21>
	rdf:type ~~seaturtle:Association,~~ wikibase:Item ;		rdf:type wikibase:Item ;
	skos:isEvokedBy <QNN10> ;		skos:isEvokedBy <QNN10> ;
	</pre>		</pre>

Reversedragon: /* Enabling RDF mappings without creating new Entity types */ example

2025-02-11T02:37:13Z

Enabling RDF mappings without creating new Entity types: example

@@ Line 309: / Line 309: @@
 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.
-<pre># input
+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>
-<pre># output
+<pre># output Items
 </pre>

Reversedragon: RDF mappings without creating new Entity types

2025-02-11T02:21:13Z

RDF mappings without creating new Entity types

@@ Line 303: / Line 303: @@
 (puppy)      Verve    × Sunder
 Sledge       Shade    × Sunder
 </pre>

Reversedragon: /* Philosophical models */ S2-centric approach

2025-02-10T09:10:24Z

Philosophical models: S2-centric approach

@@ Line 110: / Line 110: @@
 == Philosophical models ==
 <pre>
@@ Line 133: / Line 169: @@
   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 ;
+  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
@@ Line 140: / Line 176: @@
   rdf:type  seaturtle:Sign ;
   seaturtle:dimension  <S3002> ;
-  rdfs:label  "Proletariats are plural and belong to specific national populations"@en ;
+  rdfs:label  "Proletariats are plural and belong to specific national populations"@en .
   # No Fragments, no Associations
 </pre>

Reversedragon: /* Pokémon */ fix example

2025-02-09T23:05:29Z

Pokémon: fix example

← Older revision		Revision as of 23:05, 9 February 2025
Line 175:		Line 175:
	rdfs:label "ロコン"@ja ;		rdfs:label "ロコン"@ja ;
	<PNNN> <SNNNN> ; # Fire-type		<PNNN> <SNNNN> ; # Fire-type
			<PNNN> <SNNNN> ; # non-unique entity can become - Ninetales
	skos:narrower <S2084-F1> .		skos:narrower <S2084-F1> .

	<S11037-F1> rdf:type seaturtle:Fragment ;		<S11037-F1> rdf:type seaturtle:Fragment ;
	<PNNN> <SNNNN> ; # variation type - Pokémon regional variant		<PNNN> <SNNNN> ; # variation type - Pokémon regional variant
	~~ontolex~~:~~lexicalizedSense~~ <~~S10386~~> . # Alolan ~~Vulpix~~		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		<S11038> # [S] Ninetales
	rdf:type seaturtle:Sign ; # the Entity is a Sign		rdf:type seaturtle:Sign ; # the Entity is a Sign
	seaturtle:dimension <S3001> ; ~~# S1 Concept - fictional concept~~		seaturtle:dimension <S3001> ;
	rdfs:label "Ninetales"@en ;		rdfs:label "Ninetales"@en ;
	rdfs:label "キュウコン"@ja ;		rdfs:label "キュウコン"@ja ;
Line 191:		Line 196:
	<S11037-F1> rdf:type seaturtle:Fragment ;		<S11037-F1> rdf:type seaturtle:Fragment ;
	<PNNN> <SNNNN> ; # variation type - Pokémon regional variant		<PNNN> <SNNNN> ; # variation type - Pokémon regional variant
	~~ontolex~~:~~lexicalizedSense~~ <~~S10387> . # Alolan Ninetales~~		seaturtle:dimension <S3001> ;

	~~<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 ;		rdfs:label "Alolan Ninetales"@en ;
	<PNNN> <SNNNN> ; # Ice-type		<PNNN> <SNNNN> ; # Ice-type
	<PNNN> <SNNNN> ; # Fairy-type		<PNNN> <SNNNN> ; # Fairy-type
	skos:broader <S11038> .		skos:broader <S11038> .

	</pre>		</pre>

← Older revision		Revision as of 10:29, 13 February 2025
Line 403:		Line 403:
	rdf:type wikibase:Item .		rdf:type wikibase:Item .
	</pre>		</pre>

			[[Category:Archived proposals]]