Shortcut: WD:GLOSS


From Wikidata
Jump to: navigation, search
This page is a translated version of the page Wikidata:Glossary and the translation is 3% complete.

Outdated translations are marked like this.
Other languages:
العربية • ‎azərbaycanca • ‎беларуская • ‎беларуская (тарашкевіца)‎ • ‎বাংলা • ‎bosanski • ‎català • ‎čeština • ‎dansk • ‎Deutsch • ‎Zazaki • ‎dolnoserbski • ‎Ελληνικά • ‎English • ‎British English • ‎Esperanto • ‎español • ‎euskara • ‎فارسی • ‎suomi • ‎français • ‎Frysk • ‎ગુજરાતી • ‎עברית • ‎हिन्दी • ‎hornjoserbsce • ‎magyar • ‎Հայերեն • ‎interlingua • ‎Bahasa Indonesia • ‎Ilokano • ‎íslenska • ‎italiano • ‎日本語 • ‎ქართული • ‎한국어 • ‎Ripoarisch • ‎Latina • ‎Lëtzebuergesch • ‎lietuvių • ‎latviešu • ‎македонски • ‎മലയാളം • ‎Bahasa Melayu • ‎norsk bokmål • ‎Nederlands • ‎norsk nynorsk • ‎occitan • ‎ਪੰਜਾਬੀ • ‎polski • ‎پښتو • ‎português • ‎português do Brasil • ‎română • ‎русский • ‎Scots • ‎srpskohrvatski / српскохрватски • ‎српски / srpski • ‎српски (ћирилица)‎ • ‎svenska • ‎Kiswahili • ‎ślůnski • ‎தமிழ் • ‎తెలుగు • ‎ไทย • ‎Türkçe • ‎українська • ‎اردو • ‎Tiếng Việt • ‎ייִדיש • ‎中文 • ‎中文(中国大陆)‎ • ‎中文(简体)‎ • ‎中文(繁體)‎

Wikidata tilby ein kunnskapsbase som alle kan redigere. I denne artikkelen vil vi forbetre diskusjon og kommunikasjon om prosjektet ved å definere viktig terminologi. Det er fleire viktige fordelar om vi kan bruke konsistent terminologi i prosjektet.

The Glossary is ordered conceptually rather than alphabetically, with the more general concepts presented first as much as possible. This is because it is translated into several languages, and the concepts have different names in different languages. In some cases, it is not obvious how to organize the entries. In these cases, "see also" has been added to the appropriate section.

Names and projects

  • Wikimedia is the name of a movement (see for details) that provides free knowledge to the public through the Wikimedia projects.
  • Wikimedia projects (see for details) are free wikis with a specific purpose, usually divided into multiple individual wikis for each language, as with Wikipedia. Wikidata is a multilingual Wikimedia project. There are about 800 different wikis in total for Wikimedia projects. For now, only Wikimedia projects can be linked with Wikidata.

Mediawiki er programvara som køyrer på nettstader slik som Wikipedia og Wikimedia Commons. Sjå MediaWiki.

Wikidatas utvidingar vil vera av to slag: Wikidatas tenerutviding som vil utvide Mediawiki slik at den kan samle og vedlikehalde strukturerte data, og som vil bli brukt på sjølve Wikidata nettstaden, og Wikidata klientutviding som vil gjera det mogleg for klientwikiar å hente inn og vise frem data frå ein tenarwiki på sine eigne sider, og som vil bli brukt på Wikipedia og sannsynligvis også andre nettstader.

Wikidata er ein ny nettstad som vil bli starta i løpet av den innleiande utviklinga av Wikidata-prosjektet. Det vil fungere som ein nettstad som køyrer MediaWiki og som bruker utvidinga Wikidata, og tilsaman vil dette la Wikidata-skribentar lage og manøvrere blant sider på Wikidata.

Basic terms

Data og Metadata: I Wikidata er data samlinga av alle utsegn og deira tilhøyrande referansar – generelt alt som blir lagd inn av Wikidata-skribentar i Wikidata. Motsett av dette er metadata som er alle data som Wikidata enten tar vare om denne innlegginga, eller som er forvalgt av programvara uten at det kan endrast av forfattarane. Det vil si endringshistoria om ei side, hvilken Wikidata-skribent som har lagt inn utsegna, eller som har lagt inn ein referanse.

Data is raw information, like the words you are reading right now. Wikidata is essentially a collection of structured data, or database content. Those data are generally everything entered by the Wikidata editors and bots using the entity pages and the public programming interface. The wikipages from which a user can see and enter data are organized in three data namespaces:

  1. the main namespace (for items), regrouping pages in which we can see and enter information about a specific entity,
  2. the property namespace, in which we can see information about properties, which are used to structure the information we enter into statements and the
  3. query namespace, in which we can define additional ways to extract and display the information than the main namespace.

The data in those namespaces are said to be structured because they are all organized in a way that the Wikibase software uses to ensure a certain data model and because the community defines and enforces the correct ways to enter information.

Metadata in Wikidata is structured data, that can not be created or changed by users and bots but is created by the MediaWiki software. The revision history of pages is an example of metadata. The software generates the entries with time stamps and user names.

Other Wikidata pages are classical Wikipages and consist of unstructured data or semi-structured data (Q2336004) View with Reasonator See with SQID (for example: running text or wikitext), and are meta pages, such as community discussion pages.

Specifically, an important kind of data are property data. Property data are values associated with a property to build a Claim; they are an organisation unit of the structured data. Each property is assigned a Datatype, which defines the property data values that can be used in claims built with this property.

  • Dataset

A dataset is generally any collection of (structured) Data.

In Wikidata what is called a dataset is often associated to an entity: the dataset associated to an entity is all the information shown in the identity Wikipage (the set of statements in the database who have this entity as a subject, the Wikipedia links of articles describing this entity on Wikimedia projects, ...).

We can build other datasets by combining dataset of several entities.

The datasets can be represented in different ways: as in their entity Wikipage in the form of an XML or JSON file for the robots and computing programs. Specifically in the Wikidata user interface messages, dataset refers to data associated to an entity (an item, a property or a query)

  • Dereferenceable URIs These are used during content negotiation to supply a resource description even if it is the entity itself that is addressed. This also makes it possible to supply a human-readable description or a machine readable one. The latter one would then be RDF data, according to what is more suitable. The content the dereferenced URIs point to will be available through the page Special:EntityData.

Eksport refererer til at data og metadata frå Wikidata kan gjerast tilgjengelig for gjenbruk. Maskinlesbar eksport av data er planlagt å bli tilgjengelig i almen brukte formater slik som JSON og RDF/XML.

  • Linked data This is a method for publishing structured data so that it can be interlinked and become more useful. It closely relates to how Wikidata works, by connecting entities and attaching data on linked data pages like Wikidata do for items.
  • Triplet (commonly called Triple) is how to store data as a single data entry in linked data. It consists of a subject, a predicate and an object. In Wikidata this corresponds roughly to the item, property and value.
  • Ontology - ontology (Q324254) View with Reasonator See with SQID This is an explicit and formal specification of a conceptualization. It is important that an ontology convey a shared understanding of a domain. In Wikidata this would be given by using the properties and their intended meaning in statements to describe the real world entities and concepts, through their Wikidata counterpart, associated to literal data and other entities.
  • Provenance is the history of the contributor who added a data, and of the source from which the data was extracted. Provenance is important in the case of the reuse of Open data datasets or external database use.
  • Vocabulary This is the set of terms that is used to describe the ontology. The terms used in one vocabulary can be the same as (owl:sameAs) some terms from another vocabulary. Sameness is more strict than equality.


Nettstedlekkjer er spesielle lekkjer som inneheld eit\n nettstad og ein tittel, og går frå individuelle datasett i Wikidata og til sider på andre nettstader, for eksempel på Wikipedia. Dei er brukt både for å identifisere eit datasett frå ein ekstern nettstad, og som ein erstatning for språklekkjer. Nettstadlekkjer kan og ha tilknytte merke og dei vil då vanleg vise at ei side er utvald artikkel eller tilsvarande.

  • Site is a reference to an external website in general, but in sitelinks it refers to specific registered wikis, for example a Wikipedia language version. Those sites are referenced by global site identifiers or for short siteid, technically corresponding to the wiki's DBname. For example the Latin Wikipedia's siteid is lawiki. Each external page can have only one link registered in Wikidata and one item can only have one link to each external site.
  • Badges are a kind of marker attached to a sitelink, which could identify, for example, that the article is a "featured article" on a specific site. They do not describe the external entity but the page on the specific site.


Side betyr ei side eller artikkel i ein wiki. I Wikidata vil det bli sider i andre namnerom (akkurat som på Wikipedia). Sider i hovudrommet på Wikidata vil bli om datasetta.

  • Meta pages These are all pages that are not entities, i.e. do not belong to the data namespaces. Wikidata meta pages contain unstructured content represented by conventional MediaWiki code, and perhaps also future Wikidata client side inclusion code. Examples are talk pages, category pages, project pages (in the Wikidata namespace) and help pages (in the help namespace). Meta pages also comprise content and data automatically generated by the MediaWiki software (for example, the edit history of a page, or special pages).
  • Namespace - MediaWiki namespace (Q18889113) View with Reasonator See with SQID A physical division of pages in MediaWiki to group them according to overall use or some additional behavior. Examples are namespaces for categories, files, users, and in the case of Wikidata, three data namespaces: items (in the main namespace), properties and queries. See the list of namespaces.
  • Mainspace This is the namespace where all items are located. It is distinguished by its lack of a prefix.

Entities, items, properties and queries

Entitet (entity) er datainnhaldet i ei Wikidata-side, som anten kan vere eit element i hovudnamnerommet, ein eigenskap i egenskapnamnerommet eller ei spørring i spørringnamnerommet. Kvar entitet er identifisert av ein entitet-ID, som er samansett av eit prefiks og eit nummer, til dømes startar entitet-ID med Q-prefikset for eit element, og P-prefikset for ein eigenskap og U-prefikset for ei spørring. Ein entitet er òg identifisert av ein unik kombinasjon av etikett og skildring på kvart språk. Entitet kan òg tildelast eit sett av alternative fleirspråklege alias. (I ontologiar og bibliotekkatalogar som blir brukte som referanse for Wikidata, er ein entitet vanlegvis eit konkret tema eller emne, eller databaserepresentasjonen for dette, og tilsvarar i den samanhengen til det som i Wikidata er kalla eit element.)

Element (item, òg dataelement) er ei side i Wikidata hovudnamnerommet som representerer eit konkret tema, konsept eller emne. Element er identifisert av eit prefiks og eit nummer, eller ved ein sitelink til ei ekstern side, eller av ein unik kombinasjon av fleirspråkleg etikett og skildring. Element kan òg ha alias for å lette oppslag. Hovuddataområdet for eit element er lista over utsegn om elementet. Eit element kan sjåast som emnedelen av ein trippel i kopla data.

  • Property (in some languages translated to attribute) is the descriptor for a data value, or some other relation or composite or possibly missing value, but not the data value or values themselves. Each statement at an item page links to a property, and assigns the property one or several values, or some other relation or composite or possibly missing value. The property is stored on a page in the Property namespace, and includes a declaration of the datatype for the property values. Compared to linked data, the property represents a triplet's predicate.
  • Query (future feature) is a predefined search across items. A query is the descriptor for the predefined search, but not the hits generated by the search. A query can be executed to acquire search results, which may be useful for automatic generation and translation of list articles. See Wikidata:Lists task force (Wikidata phase III). Each query is an Entity and described and defined on its own page, and has its own prefixed identifier.

Identifiers and languages

Many Wikimedia projects exist in different localised versions, but not Wikidata. Wikidata is multilingual, this means all parts of the user interface and also all the pages of data content can be translated into and used in many different languages. The users can determine their favorite languages. Wikidata is meant to treat all languages the same and to interconnect the knowledge of many languages allowing data content contributed in one language to be used in all the other languages as well. The users can translate all the pages into the different local languages and therefore improve the usability step by step.

  • Title This is the name of an external linked page (known as Sitelink-title), the name of a meta page, or the Entity ID of an entity page. If the page does not belong to the main namespace, the title includes the namespace name as prefix.
    1. For items, properties and queries, the Wikidata entity title is an identifier containing the namespace prefix (if any), followed by a letter and a numeric id. A title example is Property:P17 for a property, and Q6256 for an item. The page URL consists of followed by the title. In search results, the localized label (also known as name) is presented, followed by the identifier in parenthesis (without the namespace prefix), and by the description, to make the overall string more readable. For example, if you search for "country" using the Special:Search interface, the search result will include the property "country (P17): sovereign state of this item", as well as the item "country (Q6256), region legally identified as a distinct entity in political geography".
    2. Used for sitelinks the title is a canonical string that identifies a page on an external site. The Special:ItemByTitle interface may be used for searching a page by its title on a given Wikipedia. Together the site and title form the complete sitelink. During validation of the title the string will go through a normalization procedure, and in the end the title will be the external site's canonical page name. Only after the normalization is completed and site-specific constraints are satisfied a new sitelink can be stored.
    3. Used for an meta page in non-entity namespaces the title is spelled out as is and identifies the meta page. The namespace is normally prefixed to the string, and also to the URL. Title example is Wikidata:Glossary.

Språkattributtar er språkspesifikke merkelappar og skildringar som er knytt til datasett. Desse skal vare lesbare og forenkle tolkinga av omfanget til datasettet, det vil si typen av entitet.

  • Language fallbacks (language chains)
These are methods to systematically replace missing language attributes with strings from alternate languages. The exact replacement rules can be chosen depending on the type of page, whether the user is logged in, or the user preferred languages.
  • Label
Also known as name (not to be confused with title), this is a language-specific name used for items, properties and queries. This is usually the most important name the entry is known under, or the most general or easily understandable phrase it will be known as internally to the project. Within Wikidata this takes the role of the title in Wikipedia and is used as the primary means to distinguish entries. For items it does not need to be unique, neither in the language or the overall project, but it must be unique together with the description. For properties it must be unique within the given language. Uniqueness for a combination of a label and a description is a hard constraint that must be satisfied before a change can be saved, although it may be removed in the future.
Labels should use the language specific conventions for capitalization of proper names and phrases as seems fit for the specific entry. In listings the label will be followed by the description so they join as a single list entry.
See Help:Label.
  • Description
This is a language-specific descriptive phrase for an item, property or query. It provides context for the label (for example, there are many items about places with the label "Cambridge"). The description therefore does not need to be unique, neither within a language or the overall project, but it must be unique together with the label. Uniqueness for a combination of a label and a description is a hard constraint that must be satisfied before a change can be saved.
See Help:Description for more information, including proper styling of descriptions.
  • Aliases
These are marked as Also known as in the user-interface. They are language-specific alternate labels and can be as many as necessary.
See Help:Aliases.

Claims and statements

Elements of a statement

In order to use Wikidata, the knowledge contained in different sources must be decomposed. A source might read Wolfgang Amadeus Mozart was a composer who was born 27 January 1756 and died in 5 December 1791. We need to decompose the information contained in this sentence and transform it into claims and statements: name: Wolfgang Amadeus Mozart; date of birth: 27 January 1756; date of death: 5 December 1791; occupation: composer. Both claims and (Wikidata) statements are expressed into a so called statement to be used as linked data by external websites or organization, but they are slightly refined to fit their purpose in Wikidata. Usually the statement itself in linked data is described by a single triplet, but when the statement in itself is reified, it is possible to say something more about the statement. We may say it has a value, that is our original triple (or tuple to be more general), and we may say something about that value like when and how the value is recorded or measured. Such statements about a statement is in Wikidata called qualifiers to separate them more clearly from our statements. Without doing this it could be difficult to separate the different types of statements from each other.

Statements describing references for the particular reified statement can also be made. Those are also statements about statements, but they have different roles and are also given special names. This is done by adding references. References are also reified statements so we can make statements about them, that is we can give them qualifiers. Note that references are reified statements about reified statements. It is a good thing that we can talk about references with qualifiers, that makes it somewhat clearer. (Another way to say things about references is to give them their own items and to add statements about it.)

To implement the basic assertion, the core triplet or rather the duplet as the subject is given as the item itself, a small structure called a snak is used. Those come in several versions, each specialized for a single purpose. Statements hold such snaks, and they are also the inner parts of statements about statements that is qualifiers, references and ranks. Part of the specialization for snaks is that some of them can hold a value of a special type, a datatype. A snak will refuse to hold any other type than what it is configured to store.

During the lifetime of a statement it might be set to normal, until it is deemed preferred, and later on it might be replaced by a more up to date value and marked deprecated. Those values are nothing more than statements about the reified statement, but it is given its own name and appearance in the user interface.

  • Claim is a piece of data about the entity on whose page the claim appears. A claim consists of a property (such as "Location") and a value (e.g., "Germany"), or some other relation or composite or missing value. A claim can have qualifiers, such as temporal qualifiers saying that the claim is valid within a specific time frame. Compared to the triplets used in linked data, a claim uses a property to express the predicate of a triplet and a value to express the object of a triplet. Claims form part of statements on item pages, where they can be augmented with references and ranks; they can also occur on non-item data pages.

Utsegn (også kalla fakta, påstand, argument og trippel, men det siste er ikkje heilt riktig) er ein bit data frå eit datasett, som er tatt vare på inne på ei side. I det enklaste tilfellet er eit utsegn eit par av ein eigenskap og ein verdi (for eksempel «Stad: Tyskland»), men ofte har eit utsegn ytterligare kvalifisering (slik som mellombels kvalifisering). Sjå Data modellen. Legg merke til at Wikidata ikkje gjer noko anslag om korrektheita (sanninga) til eit utsegn, påstandane samlast bare inn og rapporterast vidare med ein referanse til kildea.

  • Values (or datavalues) are the information pieces embedded in each claim. Depending on their datatype, they can be a single value (like a number) or a value consisting of several parts (like a geographical position with longitude and latitude). In order to specify that a property has no value or a property's value is unknown, a marker (snak type) other than the default "custom value" may be selected:
Modify the snaktype (value/some value/no value) here.
  1. Ingen verdi is a marker for when there certainly is no value for the property (example: if a human has no children, the corresponding item would receive this marker for child (P40)). Assigning the "no value" marker is a proper statement and is different to an item lacking a property. Latter implicates that it is unknown whether the property has no or some value.
  2. Ukjend verdi is a marker for when there is some value but the exact value is not known for the property. "Some value" means that there is nothing known for the value except that it should exist and not imply a negation of the claim (example: if the date of a human's death is completely unknown the item would receive this marker for date of death (P570), denoting that the human is, in fact, dead — however, with the date of death being unknown).
  3. Oppgjeven verdi is a marker for when there is a known value for the property that can be specified. This is the default snak type when creating a snak/claim/statement.
  • Snak is a single, basic assertion in Wikidata, including property-value assertions, "no value" assertions, and others. Statements are composed of one-to-many snaks. Snaks are an integral part of the data model, but, normally, this term will not be exposed to editors and users of Wikidata. For more information, see mw:Wikibase/DataModel#Snaks.
  • Datatype (data value type or value type) is the kind of data values that may be assigned to a property, and specifies how the data values are stored in each claim. Each property is assigned a pre-defined datatype. Not all values can be linked, as long as there are certain datatypes missing. The development of new datatypes is still in progress. See also Special:ListDatatypes for currently available datatypes.
  • String (short for character string) is a general term for a sequence of freely chosen characters interpreted as text (e.g. "Hello") — as opposed to a value interpreted as a numerical value (3.14), a link to an item (e.g. [[Q1234]]) or a more complex datatype (the set {1,3,5,7} ). Wikidata will in addition to a string datatype support language specific texts; "monolingual-text" and "multilingual-text" as the value of a property.
  • Qualifier is a part of the claim that says something about the specific claim, often in a descriptive way. A qualifier might be a term according to a specific vocabulary but can also be a variant descriptive phrase (whether those terms or phrases are free text or part of some vocabulary would probably be up to the Wikidata community).
  • Rank is a quality factor used for simple selection/filtering in cases where there are many statements for a given property (see Help:Ranking). There are three possible ranks:
  1. Deprecated rank is used for a statement that contains information that may not be considered reliable or that is known to include errors. (For example, a statement that documents a wrong population figure that was published in some historic document. In this case the statement is not wrong – the historic document that is given as a reference really made the erroneous claim – but the statement should not be used in most cases.)
  2. Normal rank is used for a statement that contains relevant information that is believed to be correct, but may be too extensive to be shown by default. (For example, historic population figures for Berlin over the course of many years.)
  3. Preferred rank is used for a statement with the most important and most up-to-date information. Such a statement will be shown to all users and will be displayed in Wikipedia infoboxes by default. (For example, the most recent population figures for Berlin.)

Referanse (eller referanse, litteraturhenvising og kjelde) beskriver opphavet til eit utsegn i Wikidata. Kjelder er ofte datasett i seg sjøl, for eksempel ei bok. Wikidata vil ikkje gjera noko forsøk på å gi svar på om eit utsegn er riktig eller ikkje, men kun gi ei referanse. Kva som vil vara ei gyldig referanse er antatt å bli gjenstand for debatt blant Wikidata-skribentar.

  • External identifier Some properties have values that are strings used in other organisations' databases to uniquely identify an item. For example, an ISBN for a book or the unique part of the URL of a movie or an actor in the Internet Movie Database.

Tilhøyrande termar

  • RDF/XML er eit format for å serialisere RDF i XML. Sjå RDF/XML.

See also