Wikibase/DataModel/en - Revision history

FuzzyBot: Updating to match new version of source page

2024-08-25T00:19:53Z

Updating to match new version of source page

← Older revision		Revision as of 00:19, 25 August 2024
Line 432:		Line 432:
	A TimeValue represents a point in time that might be imprecise (e.g., if only a year is given). For practical purposes (e.g., sorting values), the value will often be interpreted to be exact by filling the missing positions with more details. The structure of values of this type is as follows:		A TimeValue represents a point in time that might be imprecise (e.g., if only a year is given). For practical purposes (e.g., sorting values), the value will often be interpreted to be exact by filling the missing positions with more details. The structure of values of this type is as follows:
	* time: timestamp in a format resembling ISO 8601, the year always being signed and having between 1 and 16 digits, e.g. +2013-01-01T00:00:00Z. The month, day and time will be set to zero if they are unknown; the ''precision'' field should be relied on to determine which time digits are meaningful. The Z is meaningless and the time zone should be determined from the ''timezone'' field. For the purposes of this description, the timestamp uses historical numbering where the year 0 is undefined and the year 1 BCE is represented as -0001; note, however, that this is not the case in all serializations (see [[Wikibase/DataModel/JSON#time\|JSON]] and [[Wikibase/Indexing/RDF Dump Format#Time\|RDF]] for details).		* time: timestamp in a format resembling ISO 8601, the year always being signed and having between 1 and 16 digits, e.g. +2013-01-01T00:00:00Z. The month, day and time will be set to zero if they are unknown; the ''precision'' field should be relied on to determine which time digits are meaningful. The Z is meaningless and the time zone should be determined from the ''timezone'' field. For the purposes of this description, the timestamp uses historical numbering where the year 0 is undefined and the year 1 BCE is represented as -0001; note, however, that this is not the case in all serializations (see [[Wikibase/DataModel/JSON#time\|JSON]] and [[Wikibase/Indexing/RDF Dump Format#Time\|RDF]] for details).
	* precision: shortint. The numbers have the following meaning: 0 - billion years, 1 - hundred million years, ..., 6 - ~~millennia~~, 7 - century, 8 - decade, 9 - year, 10 - month, 11 - day, <s>12 - hour, 13 - minute, 14 - second</s><ref>Wikidata only accepts precisions up to 11. [[phabricator:T57755]]</ref>. Note that centuries and millennia do not strictly align with the most significant digits of the timestamp: for positive timestamps, centuries and millennia begin on years 1 modulo 100/1000 and end on years 0 modulo 100/1000, and vice versa for negative timestamps. For example, the 18th century begins in the year 1701 and ends in the year 1800, and the 2nd millennium BCE begins in the year -2000 (2000 BCE) and ends in the year -1001 (1001 BCE). (On the other hand, decades align with the most significant digits: the 1980s begin in 1980 and end in 1989.)		* precision: shortint. The numbers have the following meaning: 0 - billion years, 1 - hundred million years, ..., 6 - millennium, 7 - century, 8 - decade, 9 - year, 10 - month, 11 - day, <s>12 - hour, 13 - minute, 14 - second</s><ref>Wikidata only accepts precisions up to 11. [[phabricator:T57755]]</ref>. Note that centuries and millennia do not strictly align with the most significant digits of the timestamp: for positive timestamps, centuries and millennia begin on years 1 modulo 100/1000 and end on years 0 modulo 100/1000, and vice versa for negative timestamps. For example, the 18th century begins in the year 1701 and ends in the year 1800, and the 2nd millennium BCE begins in the year -2000 (2000 BCE) and ends in the year -1001 (1001 BCE). (On the other hand, decades align with the most significant digits: the 1980s begin in 1980 and end in 1989.)
	* after: integer. If the date is uncertain, how many units before the given time could it be? the unit is given by the precision.		* after: integer. If the date is uncertain, how many units before the given time could it be? the unit is given by the precision.
	* before: integer. If the date is uncertain, how many units after the given time could it be? the unit is given by the precision.		* before: integer. If the date is uncertain, how many units after the given time could it be? the unit is given by the precision.

FuzzyBot: Updating to match new version of source page

2024-08-16T22:38:17Z

Updating to match new version of source page

← Older revision		Revision as of 22:38, 16 August 2024
Line 387:		Line 387:
	Datatypes<ref>https://www.wikidata.org/wiki/Special:ListDatatypes</ref> are Entities that specify the format of [[#Property\|Property]] Values. The set of Datatypes in Wikibase is system-defined (it can be extended, but only by developers). Every [[#Datatype\|Datatype]] has a fixed [[#IRI\|IRI]], that is also system-defined.		Datatypes<ref>https://www.wikidata.org/wiki/Special:ListDatatypes</ref> are Entities that specify the format of [[#Property\|Property]] Values. The set of Datatypes in Wikibase is system-defined (it can be extended, but only by developers). Every [[#Datatype\|Datatype]] has a fixed [[#IRI\|IRI]], that is also system-defined.

	For every [[#Datatype\|Datatype]], there is one particular form of ~~Values~~ that ~~are~~ used to represent Values of that type. Wikibase distinguishes between Values that can be the subject of Snaks, called [[#Entities\|Entities]], and Values that are not the subject of Snaks, called DataValues. The following is an overview of all DataValues:		For every [[#Datatype\|Datatype]], there is one particular form of Value that is used to represent Values of that type. Wikibase distinguishes between Values that can be the subject of Snaks, called [[#Entities\|Entities]], and Values that are not the subject of Snaks, called DataValues. The following is an overview of all DataValues:

	[[Image:Wikidata_model_DataValues_UML.png\|center\|850px]]		[[Image:Wikidata_model_DataValues_UML.png\|center\|850px]]

FuzzyBot: Updating to match new version of source page

2024-04-07T22:51:26Z

Updating to match new version of source page

← Older revision		Revision as of 22:51, 7 April 2024
Line 72:		Line 72:
	[[#Property\|Property]]-[[#Value\|Value]] pairs are not the only kind of claims that can be given in a Statement. It is also possible to say, for example, that a [[#Property\|Property]] has ''no'' [[#Value\|Values]] for the given [[#Item\|Item]]. For example, one can say that a circle has ''no'' angles. Stating this can be relevant to distinguish it from the (common) case that the property has simply not been entered into Wikidata yet. Other things that one can say are related to classification, for example to state that Berlin is a city (i.e., "an instance of the class of all cities"). This is treated in a specific way since classification is important in many areas, e.g., in biologic taxonomies. For lack of a better name, any such basic assertion that one can make in Wikidata is called a {{anchor\|Snak}}'''Snak''' (which is small, but more than a byte). This term will not be relevant for using Wikidata (editors will not encounter it), but it is relevant for developers to avoid confusion with [[#Statement\|Statements]] or other claims.		[[#Property\|Property]]-[[#Value\|Value]] pairs are not the only kind of claims that can be given in a Statement. It is also possible to say, for example, that a [[#Property\|Property]] has ''no'' [[#Value\|Values]] for the given [[#Item\|Item]]. For example, one can say that a circle has ''no'' angles. Stating this can be relevant to distinguish it from the (common) case that the property has simply not been entered into Wikidata yet. Other things that one can say are related to classification, for example to state that Berlin is a city (i.e., "an instance of the class of all cities"). This is treated in a specific way since classification is important in many areas, e.g., in biologic taxonomies. For lack of a better name, any such basic assertion that one can make in Wikidata is called a {{anchor\|Snak}}'''Snak''' (which is small, but more than a byte). This term will not be relevant for using Wikidata (editors will not encounter it), but it is relevant for developers to avoid confusion with [[#Statement\|Statements]] or other claims.

	For advanced usage, it is possible to make claims that consist of more than one [[~~Wikibase/DataModel~~#~~Snaks~~\|Snak]]. For example, one might need to say that "the population of Berlin is 3,499,879, considering only the territory of the city, as estimated on 30 November 2011." Here, we have two additional Snaks that specify the territory the number refers to and the time when the measure was taken. It will be described below how exactly a claim can use additional Snaks.		For advanced usage, it is possible to make claims that consist of more than one [[#Snak\|Snak]]. For example, one might need to say that "the population of Berlin is 3,499,879, considering only the territory of the city, as estimated on 30 November 2011." Here, we have two additional Snaks that specify the territory the number refers to and the time when the measure was taken. It will be described below how exactly a claim can use additional Snaks.

	== How to read this document ==		== How to read this document ==

FuzzyBot: Updating to match new version of source page

2024-04-07T22:50:40Z

Updating to match new version of source page

← Older revision		Revision as of 22:50, 7 April 2024
Line 72:		Line 72:
	[[#Property\|Property]]-[[#Value\|Value]] pairs are not the only kind of claims that can be given in a Statement. It is also possible to say, for example, that a [[#Property\|Property]] has ''no'' [[#Value\|Values]] for the given [[#Item\|Item]]. For example, one can say that a circle has ''no'' angles. Stating this can be relevant to distinguish it from the (common) case that the property has simply not been entered into Wikidata yet. Other things that one can say are related to classification, for example to state that Berlin is a city (i.e., "an instance of the class of all cities"). This is treated in a specific way since classification is important in many areas, e.g., in biologic taxonomies. For lack of a better name, any such basic assertion that one can make in Wikidata is called a {{anchor\|Snak}}'''Snak''' (which is small, but more than a byte). This term will not be relevant for using Wikidata (editors will not encounter it), but it is relevant for developers to avoid confusion with [[#Statement\|Statements]] or other claims.		[[#Property\|Property]]-[[#Value\|Value]] pairs are not the only kind of claims that can be given in a Statement. It is also possible to say, for example, that a [[#Property\|Property]] has ''no'' [[#Value\|Values]] for the given [[#Item\|Item]]. For example, one can say that a circle has ''no'' angles. Stating this can be relevant to distinguish it from the (common) case that the property has simply not been entered into Wikidata yet. Other things that one can say are related to classification, for example to state that Berlin is a city (i.e., "an instance of the class of all cities"). This is treated in a specific way since classification is important in many areas, e.g., in biologic taxonomies. For lack of a better name, any such basic assertion that one can make in Wikidata is called a {{anchor\|Snak}}'''Snak''' (which is small, but more than a byte). This term will not be relevant for using Wikidata (editors will not encounter it), but it is relevant for developers to avoid confusion with [[#Statement\|Statements]] or other claims.

	For advanced usage, it is possible to make claims that consist of more than one [[#~~Snak~~\|Snak]]. For example, one might need to say that "the population of Berlin is 3,499,879, considering only the territory of the city, as estimated on 30 November 2011." Here, we have two additional Snaks that specify the territory the number refers to and the time when the measure was taken. It will be described below how exactly a claim can use additional Snaks.		For advanced usage, it is possible to make claims that consist of more than one [[Wikibase/DataModel#Snaks\|Snak]]. For example, one might need to say that "the population of Berlin is 3,499,879, considering only the territory of the city, as estimated on 30 November 2011." Here, we have two additional Snaks that specify the territory the number refers to and the time when the measure was taken. It will be described below how exactly a claim can use additional Snaks.

	== How to read this document ==		== How to read this document ==

FuzzyBot: Updating to match new version of source page

2023-12-17T10:44:21Z

Updating to match new version of source page

← Older revision		Revision as of 10:44, 17 December 2023
Line 22:		Line 22:
	__TOC__		__TOC__

	{{:Wikibase/DataModel/Editorial Note\|This document contains a number of "Editorial Notes". These are remarks that have been left by the editor to record some open issue or known problem. Eventually, all such notes will be addressed and removed.}}		{{:Wikibase/DataModel/Editorial Note\|1=This document contains a number of "Editorial Notes". These are remarks that have been left by the editor to record some open issue or known problem. Eventually, all such notes will be addressed and removed.}}

	== History ==		== History ==

FuzzyBot: Updating to match new version of source page

2023-05-24T03:41:35Z

Updating to match new version of source page

← Older revision		Revision as of 03:41, 24 May 2023
Line 432:		Line 432:
	A TimeValue represents a point in time that might be imprecise (e.g., if only a year is given). For practical purposes (e.g., sorting values), the value will often be interpreted to be exact by filling the missing positions with more details. The structure of values of this type is as follows:		A TimeValue represents a point in time that might be imprecise (e.g., if only a year is given). For practical purposes (e.g., sorting values), the value will often be interpreted to be exact by filling the missing positions with more details. The structure of values of this type is as follows:
	* time: timestamp in a format resembling ISO 8601, the year always being signed and having between 1 and 16 digits, e.g. +2013-01-01T00:00:00Z. The month, day and time will be set to zero if they are unknown; the ''precision'' field should be relied on to determine which time digits are meaningful. The Z is meaningless and the time zone should be determined from the ''timezone'' field. For the purposes of this description, the timestamp uses historical numbering where the year 0 is undefined and the year 1 BCE is represented as -0001; note, however, that this is not the case in all serializations (see [[Wikibase/DataModel/JSON#time\|JSON]] and [[Wikibase/Indexing/RDF Dump Format#Time\|RDF]] for details).		* time: timestamp in a format resembling ISO 8601, the year always being signed and having between 1 and 16 digits, e.g. +2013-01-01T00:00:00Z. The month, day and time will be set to zero if they are unknown; the ''precision'' field should be relied on to determine which time digits are meaningful. The Z is meaningless and the time zone should be determined from the ''timezone'' field. For the purposes of this description, the timestamp uses historical numbering where the year 0 is undefined and the year 1 BCE is represented as -0001; note, however, that this is not the case in all serializations (see [[Wikibase/DataModel/JSON#time\|JSON]] and [[Wikibase/Indexing/RDF Dump Format#Time\|RDF]] for details).
	* precision: shortint. The numbers have the following meaning: 0 - billion years, 1 - hundred million years, ..., 6 - ~~millenia~~, 7 - century, 8 - decade, 9 - year, 10 - month, 11 - day, <s>12 - hour, 13 - minute, 14 - second</s><ref>Wikidata only accepts precisions up to 11. [[phabricator:T57755]]</ref>. Note that centuries and millennia do not strictly align with the most significant digits of the timestamp: for positive timestamps, centuries and millennia begin on years 1 modulo 100/1000 and end on years 0 modulo 100/1000, and vice versa for negative timestamps. For example, the 18th century begins in the year 1701 and ends in the year 1800, and the 2nd millennium BCE begins in the year -2000 (2000 BCE) and ends in the year -1001 (1001 BCE). (On the other hand, decades align with the most significant digits: the 1980s begin in 1980 and end in 1989.)		* precision: shortint. The numbers have the following meaning: 0 - billion years, 1 - hundred million years, ..., 6 - millennia, 7 - century, 8 - decade, 9 - year, 10 - month, 11 - day, <s>12 - hour, 13 - minute, 14 - second</s><ref>Wikidata only accepts precisions up to 11. [[phabricator:T57755]]</ref>. Note that centuries and millennia do not strictly align with the most significant digits of the timestamp: for positive timestamps, centuries and millennia begin on years 1 modulo 100/1000 and end on years 0 modulo 100/1000, and vice versa for negative timestamps. For example, the 18th century begins in the year 1701 and ends in the year 1800, and the 2nd millennium BCE begins in the year -2000 (2000 BCE) and ends in the year -1001 (1001 BCE). (On the other hand, decades align with the most significant digits: the 1980s begin in 1980 and end in 1989.)
	* after: integer. If the date is uncertain, how many units before the given time could it be? the unit is given by the precision.		* after: integer. If the date is uncertain, how many units before the given time could it be? the unit is given by the precision.
	* before: integer. If the date is uncertain, how many units after the given time could it be? the unit is given by the precision.		* before: integer. If the date is uncertain, how many units after the given time could it be? the unit is given by the precision.

FuzzyBot: Updating to match new version of source page

2023-04-13T22:13:01Z

Updating to match new version of source page

← Older revision		Revision as of 22:13, 13 April 2023
Line 70:		Line 70:
	The individual things that Wikidata talks about, including Items and Properties, are called {{anchor\|Entities}}'''Entities'''. All [[#Entities\|Entities]] are Values, but many kinds of Values are not [[#Entities\|Entities]] (examples of the latter kind include Values for numbers, strings, and geographic coordinates). This is so since Wikidata does not intend to store Statements about individual data values, such as strings or numbers (but it could store [[#Statement\|Statements]] about a number as a concept that is discussed on a Wikipage, in which case the number is represented by a Wikidata [[#Item\|Item]]).		The individual things that Wikidata talks about, including Items and Properties, are called {{anchor\|Entities}}'''Entities'''. All [[#Entities\|Entities]] are Values, but many kinds of Values are not [[#Entities\|Entities]] (examples of the latter kind include Values for numbers, strings, and geographic coordinates). This is so since Wikidata does not intend to store Statements about individual data values, such as strings or numbers (but it could store [[#Statement\|Statements]] about a number as a concept that is discussed on a Wikipage, in which case the number is represented by a Wikidata [[#Item\|Item]]).

	[[#Property\|Property]]-[[#Value\|Value]] pairs are not the only kind of claims that can be given in a Statement. It is also possible to say, for example, that a [[#Property\|Property]] has ''no'' [[#Value\|Values]] for the given [[#Item\|Item]]. For example, one can say that ~~Angela~~ ~~Merkel~~ has ''no'' ~~children~~. Stating this can be relevant to distinguish it from the (common) case that the ~~children~~ ~~have~~ simply not been entered into Wikidata yet. Other things that one can say are related to classification, for example to state that Berlin is a city (i.e., "an instance of the class of all cities"). This is treated in a specific way since classification is important in many areas, e.g., in biologic taxonomies. For lack of a better name, any such basic assertion that one can make in Wikidata is called a {{anchor\|Snak}}'''Snak''' (which is small, but more than a byte). This term will not be relevant for using Wikidata (editors will not encounter it), but it is relevant for developers to avoid confusion with [[#Statement\|Statements]] or other claims.		[[#Property\|Property]]-[[#Value\|Value]] pairs are not the only kind of claims that can be given in a Statement. It is also possible to say, for example, that a [[#Property\|Property]] has ''no'' [[#Value\|Values]] for the given [[#Item\|Item]]. For example, one can say that a circle has ''no'' angles. Stating this can be relevant to distinguish it from the (common) case that the property has simply not been entered into Wikidata yet. Other things that one can say are related to classification, for example to state that Berlin is a city (i.e., "an instance of the class of all cities"). This is treated in a specific way since classification is important in many areas, e.g., in biologic taxonomies. For lack of a better name, any such basic assertion that one can make in Wikidata is called a {{anchor\|Snak}}'''Snak''' (which is small, but more than a byte). This term will not be relevant for using Wikidata (editors will not encounter it), but it is relevant for developers to avoid confusion with [[#Statement\|Statements]] or other claims.

	For advanced usage, it is possible to make claims that consist of more than one [[#Snak\|Snak]]. For example, one might need to say that "the population of Berlin is 3,499,879, considering only the territory of the city, as estimated on 30 November 2011." Here, we have two additional Snaks that specify the territory the number refers to and the time when the measure was taken. It will be described below how exactly a claim can use additional Snaks.		For advanced usage, it is possible to make claims that consist of more than one [[#Snak\|Snak]]. For example, one might need to say that "the population of Berlin is 3,499,879, considering only the territory of the city, as estimated on 30 November 2011." Here, we have two additional Snaks that specify the territory the number refers to and the time when the measure was taken. It will be described below how exactly a claim can use additional Snaks.
Line 271:		Line 271:

	{{:Wikibase/DataModel/Example\|In some cases, we want to emphasize that a property value has not just been left out (or not entered yet) but that it really does not exist. Some examples:		{{:Wikibase/DataModel/Example\|In some cases, we want to emphasize that a property value has not just been left out (or not entered yet) but that it really does not exist. Some examples:
	* ~~Angela Merkel~~ (subject) has no ~~children~~ (property).		* Circle (subject) has no angle (property).
	* Mount Everest (subject) has no [[:en:parent peak\|parent peak]] (property).		* Mount Everest (subject) has no [[:en:parent peak\|parent peak]] (property).
	Such statements should only be made in cases where one could otherwise expect an incompleteness. It is not intended that Wikidata stores all things that are not the case (e.g., "The Pacific Ocean has no ~~children~~").		Such statements should only be made in cases where one could otherwise expect an incompleteness. It is not intended that Wikidata stores all things that are not the case (e.g., "The Pacific Ocean has no angle").
	}}		}}

FuzzyBot: Updating to match new version of source page

2023-03-29T22:50:27Z

Updating to match new version of source page

← Older revision		Revision as of 22:50, 29 March 2023
Line 576:		Line 576:
	* [[:d:Wikidata:Glossary\|Wikidata Glossary]]		* [[:d:Wikidata:Glossary\|Wikidata Glossary]]
	* [[Wikibase/DataModel/Primer]]		* [[Wikibase/DataModel/Primer]]
			* [[Wikibase/DataModel/DomainConceptsMapping\|[WIP] Mapping of functional traits to Wikibase Domain concepts]]

	[[Category:Wikibase{{#translation:}}]]		[[Category:Wikibase{{#translation:}}]]

FuzzyBot: Updating to match new version of source page

2023-02-06T19:00:18Z

Updating to match new version of source page

FuzzyBot: Updating to match new version of source page

2022-11-23T21:27:48Z

Updating to match new version of source page

← Older revision		Revision as of 21:27, 23 November 2022
Line 526:		Line 526:

	Strings are represented by StringValues. All strings are considered as sequences of Unicode glyphs. As opposed to multilingual and monolingual texts, strings do not contain any language information, and are typically used directly only for strings that do not belong to a language, e.g., the post code of a UK city.		Strings are represented by StringValues. All strings are considered as sequences of Unicode glyphs. As opposed to multilingual and monolingual texts, strings do not contain any language information, and are typically used directly only for strings that do not belong to a language, e.g., the post code of a UK city.

			Note: Wikibase enforces that strings are at least one character long and disallows strings that match the regular expression <code>^\s\|[\v\t]\|\s$</code> (disallowing any strings that start or end with whitespace or contain vertical whitespace such as newlines).

	=== Monolingual texts ===		=== Monolingual texts ===

← Older revision		Revision as of 22:38, 16 August 2024
Line 387:		Line 387:
	Datatypes<ref>https://www.wikidata.org/wiki/Special:ListDatatypes</ref> are Entities that specify the format of [[#Property\|Property]] Values. The set of Datatypes in Wikibase is system-defined (it can be extended, but only by developers). Every [[#Datatype\|Datatype]] has a fixed [[#IRI\|IRI]], that is also system-defined.		Datatypes<ref>https://www.wikidata.org/wiki/Special:ListDatatypes</ref> are Entities that specify the format of [[#Property\|Property]] Values. The set of Datatypes in Wikibase is system-defined (it can be extended, but only by developers). Every [[#Datatype\|Datatype]] has a fixed [[#IRI\|IRI]], that is also system-defined.

	For every [[#Datatype\|Datatype]], there is one particular form of ~~Values~~ that ~~are~~ used to represent Values of that type. Wikibase distinguishes between Values that can be the subject of Snaks, called [[#Entities\|Entities]], and Values that are not the subject of Snaks, called DataValues. The following is an overview of all DataValues:		For every [[#Datatype\|Datatype]], there is one particular form of Value that is used to represent Values of that type. Wikibase distinguishes between Values that can be the subject of Snaks, called [[#Entities\|Entities]], and Values that are not the subject of Snaks, called DataValues. The following is an overview of all DataValues:

	[[Image:Wikidata_model_DataValues_UML.png\|center\|850px]]		[[Image:Wikidata_model_DataValues_UML.png\|center\|850px]]

← Older revision		Revision as of 19:00, 6 February 2023
Line 1:		Line 1:
	<languages/>		<languages/>
	<div style="background: #FFC; padding: 1ex; border: #B00 solid 1px; ">		<div style="background: #FFC; padding: 1ex; border: #B00 solid 1px; ">
	This is a living document, describing the [[w:Conceptual schema\|conceptual data model]] behind [[Wikibase]].		This is a living document, describing the [[w:Conceptual schema\|conceptual data model]] behind [[Special:MyLanguage/Wikibase\|Wikibase]].
	It is not a [[w:Specification_(technical_standard)\|specification]] of any concrete [[w:Data binding\|binding]], [[w:Implementation\|implementation]], [[w:data mapping\|mapping]], or [[w:serialization\|serialization]].		It is not a [[w:Specification_(technical_standard)\|specification]] of any concrete [[w:Data binding\|binding]], [[w:Implementation\|implementation]], [[w:data mapping\|mapping]], or [[w:serialization\|serialization]].
	</div>		</div>
	The '''data model of [[Wikibase]]''' describes the structure of the data that is handled in Wikibase.		The '''data model of [[Special:MyLanguage/Wikibase\|Wikibase]]''' describes the structure of the data that is handled in Wikibase.
	In particular, it specifies which kind of information users can contribute to the system.		In particular, it specifies which kind of information users can contribute to the system.
	On a more abstract level, the ~~Wikibasere~~ data model provides a [[w:Metamodeling\|metamodel]] or [[w:Ontology (information science)\|ontology]] for describing real world entities.		On a more abstract level, the Wikibase data model provides a [[w:Metamodeling\|metamodel]] or [[w:Ontology (information science)\|ontology]] for describing real world entities.
	Such descriptions are concrete models for real world entities.		Such descriptions are concrete models for real world entities.

	This document describes a conceptual model ("Which information do we have to support?") and does not specify how this data should be represented technically ("Which data structures should the software use?") or syntactically ("How should the data be expressed in a file?").		This document describes a conceptual model ("Which information do we have to support?") and does not specify how this data should be represented technically ("Which data structures should the software use?") or syntactically ("How should the data be expressed in a file?").
	Separate documents describe the serialization of the Wikibase [[w:data model\|data model]] in [[Wikibase/DataModel/JSON\|JSON]] and in [[Wikibase/Indexing/RDF_Dump_Format\|RDF]] ([[w:Resource Description Framework\|Resource Description Framework]]).		Separate documents describe the serialization of the Wikibase [[w:data model\|data model]] in [[Wikibase/DataModel/JSON\|JSON]] and in [[Special:MyLanguage/Wikibase/Indexing/RDF_Dump_Format\|RDF]] ([[w:Resource Description Framework\|Resource Description Framework]]).

	This specification is technical.		This specification is technical.
Line 25:		Line 25:

	== History ==		== History ==

	* [https://www.mediawiki.org/w/index.php?title=Wikibase/DataModel Latest Version]		* [https://www.mediawiki.org/w/index.php?title=Wikibase/DataModel Latest Version]
	* [https://www.mediawiki.org/w/index.php?title=Wikibase/DataModel&oldid=1422051 Version 15-2-23]		* [https://www.mediawiki.org/w/index.php?title=Wikibase/DataModel&oldid=1422051 Version 15-2-23]