Wikidata:Property proposal/Term

From Wikidata
Jump to: navigation, search

Property proposal: Generic Authority control Person Organization Event
Place Space Economics Transportation Natural science
Property metadata Creative work References Term Unsorted Sister projects

See also:
Wikidata:Property proposal/Pending – properties which have been approved but which are on hold waiting for the appropriate datatype to be made available.
Wikidata:Properties for deletion – proposals for the deletion of properties.

This page is for the proposal of new properties.

Before proposing a property
  1. Check if the property already exists by looking at Wikidata:List of properties (manual list) and Special:ListProperties.
  2. Check if the property is already pending or has been rejected.
  3. Check if you can give a similar label and definition as an existing Wikipedia infobox parameter, or if it can be matched to an infobox, to or from which data can be transferred automatically. See WD:WikiProject Infoboxes for suggestions.
  4. Select the right datatype for the property.
  5. Start writing the documentation based on the preload form below and add it in the appropriate section.

Creating the property

  1. Change status=ready on template to attract the attention of a property creator.
  2. Creation can be done after 1 week by a property creator or an administrator.
  3. See steps when creating properties.

Add a request

This page is archived, currently at Archive 41.

To add a request, you should use this form:

=== {{TranslateThis | anchor = en
| de = <!-- PROPERTY NAME IN German (optional) -->
| fr = <!-- PROPERTY NAME IN French (optional) -->
<!-- |xx = property names in some other languages -->
}} ===
{{Property documentation
|status                 = <!--leave this empty-->
|description            = {{TranslateThis
  | en = ...
|subject item           = <!-- <!-- item corresponding to the concept represented by the property, if applicable; example: item ORCID (Q51044) for property ORCID (P496) --> -->
|infobox parameter      = Wikipedia infobox parameters, if any; ex: "population" in [[:en:template:infobox settlement]]
|datatype               = put datatype here (item, string, media, coordinate, monolingual text, multilingual text, time, URL, number)
|domain                 = types of items that may bear this property
|allowed values         = type of linked items (Q template or text), list or range of allowed values, string pattern...
|source                 = external reference, Wikipedia list article, etc.
|example                = {{Q|1}} → {{Q|2}}
|formatter URL          = <!-- for external identifiers, URL pattern where $1 replaces the value -->
|filter                 = (sample: 7 digit number can be validated with edit filter [[Special:AbuseFilter/17]])
|robot and gadget jobs  = Should or are bots or gadgets doing any task with this? (Checking other properties for consistency, collecting data, etc.)


(Add your motivation for this property here.) ~~~~


For a list of infobox parameters, you might want to use table format:

{{List of properties/Header}}

{{List of properties/Row|id=
|title          = audio
|type           = media
|qualifier      =
|description    = Commons sound file
|example-subject= Q187 <!-- Il Canto degli Italiani -->
|example-object = Inno di Mameli instrumental.ogg


For blank forms, see Property documentation and List of properties/Row

Property proposal: Generic Authority control Person Organization Event
Place Space Economics Transportation Natural science
Property metadata Creative work References Term Unsorted Sister projects

To reduce page size and functions for better loading,

  1. For transportation-related item property proposals, see Wikidata:Property proposal/Transportation.
  2. For economics-related item property proposals, see Wikidata:Property proposal/Economics.
  3. For natural science-related item property proposals, see Wikidata:Property proposal/Natural science.

Products & software products[edit]

partie d'alcool (fr) – (Please translate this into English.)[edit]

   In progress
Description partie d'une boisson qui consiste en alcool, exprimée en degré d'alcool ou pourcentage (fr) – (Please translate this into English.)
Data type Number
Template parameter "degré d'alcool" de "Infobox Boisson"
Domain principalement les boissons alcoolisées
Allowed values unités à déterminer
Example absinthe (Q170210) → 40 % à 90 %
Source infobox
Robot and gadget jobs import de frwiki
  • Permet l'import des données de Wikipédia. --- Jura 14:12, 23 November 2015 (UTC)
  • Symbol support vote.svg Support --- Jura 14:12, 23 November 2015 (UTC)
    • You don't need to support your own proposals. But please provdie an English label and description. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 19:21, 23 November 2015 (UTC)
  • Symbol oppose vote.svg Oppose as incomplete, and because the example value given ("40 % à 90 %") is not a number. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 14:26, 24 November 2015 (UTC)

Languages / Sprachen / Langues[edit]


   Not done
Description type of wine made primarily from a single named grape, herb or fruit variety
Data type Item
Domain Zinfandel (Q204433) (Zinfandel), Cabernet Sauvignon (Q207310) (Cabernet Sauvignon), Chardonnay (Q213332) (Chardonnay), Merlot (Q213338) (Merlot), apple (Q89) (apple), Pinot gris (Q778601) (Pinot gris), Sangiovese (Q509162) (Sangiovese), Tempranillo (Q519874) (Tempranillo), Pinot meunier (Q947208) (Pinot meunier), Pinot noir (Q223701) (Pinot noir) and many others from List of grape varieties (Q1357585) (List of grape varieties), etc.
Allowed values Q, Text
Example Zinfandel wine (Q17329207) -> Zinfandel (Q204433)
Source List of grape varieties, Varietal
Proposed by SarahStierch (talk)

Varietals aren't "genres" and that is the closest thing I can find to what would fit for listing types of grapes, fruits, or herbs used to make wines, liquors, beers, ciders, etc. This is my first time requesting a property and I'm unsure on if I did it right, but, perhaps others interested can help improve this request. Thank you for your consideration. SarahStierch (talk) 17:18, 6 July 2014 (UTC)

Pictogram voting comment.svg Comment: Sarah, could you give an example of how you see this property being used in a Wikidata statement? For something like Zinfandel (Q204433), we might be able to build a set of varietals with existing properties, e.g. "Zinfandel use (P366) varietal". Other useful statements might be "Zinfandel instance of (P31) cultivar", "Zinfandel subclass of (P279) Vitis vinifera". That instance of and subclass of usage would be consistent with how Wikidata classifies cats and dogs, e.g. Chihuahua (Q653).
Anyhow, food and drink is an interesting area for structured data. Let me know if the above makes sense or if you have other ideas about how to model things. Cheers, Emw (talk) 19:59, 6 July 2014 (UTC)
Hi User:Emw! Hmmm.... I'm not really sure actually...I'm pretty open minded and didn't give that aspect much thought outside of wanting to be able to use "varietal" as a statement. I'm not too sure...I can see the cultivar and vitis vinifera probably working best as statements versus the first varietal - but, since Zinfandel is a varietal, and it's a type of vitis vinifera.....hmmmm.... I'm leaning towards your experience in this to guide me! SarahStierch (talk) 20:06, 6 July 2014 (UTC)
Sarah, things like "Zinfandel" are tricky because they're polysemous. As you you say, Zinfandel is a type of wine and a type of grape. However, many statements for Zinfandel wine are false for Zinfandel grape, and vice versa. For example, Zinfandel wine is not susceptible to bunch rot and Zindandel grapes do not have an alcohol by volume range of 12-17%. The wine derives from the grape. I think these statements illustrate the need for two separate items for the two different senses of Zinfandel.
This kind of polysemy exists elsewhere, e.g. with the concept "influenza". Influenza is formally a type of disease, but it is often also used to refer to a type of virus. Separating the two concepts into two Wikidata items -- influenza (Q2840) and influenza virus (Q287246) -- allows us to be much more precise and expressive about each subject.
Perhaps we could do the same here with Zinfandel wine and the Zinfandel grape it derives from. That is, we could reserve Zinfandel (Q204433) for the grape and create a new item Zinfandel wine (Qx) for the wine. What do you think? Emw (talk) 00:29, 7 July 2014 (UTC)
User:Emw you are a genius! (But you probably knew that already). Making new items for wine is a GREAT idea. How do we make that happen. SarahStierch (talk) 01:59, 8 July 2014 (UTC)
@SarahStierch: I have started Wikidata:Property_proposal/Natural_science#fruit, I think the first step would be to start creating items for the fruits and linking them with their plants.--Micru (talk) 12:33, 17 August 2014 (UTC)
@Emw, SarahStierch, Micru: You are absolutely correct about the need for multiple items for Zinfandel (Q204433). It is all in one Wiki article, but Zinfandel wine and Zinfandel grapes are separate and distinct concepts, so if there is data that applies to one and not the other, then they certainly need a new item. It can even be appropriate to give the wine and grapes each their own new item, while retaining the original Zinfandel (Q204433) to cover the general concept of Zinfandel, inclusive of both the wine and grapes, that is discussed in the Wiki article. We currently have material used (P186) (alias ingredient) that can link the wine item with the grape item. Josh Baumgartner (talk) 22:46, 30 October 2015 (UTC)
Symbol oppose vote.svg Oppose use instance of (P31) or subclass of (P279) --Pasleim (talk) 16:25, 25 August 2015 (UTC)
Symbol oppose vote.svg Oppose and recommend material used (P186) instead. Josh Baumgartner (talk) 22:46, 30 October 2015 (UTC)

@SarahStierch:  Not done This is a valid use-case, but we already have material used (P186). I also note that, on Zinfandel wine (Q17329207), we already have natural product of taxon (P1582) -> Zinfandel (Q204433). Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 19:51, 23 November 2015 (UTC)

ISO 639 scope[edit]

   In progress
Description The language scope as defined by ISO 639.
Data type Item
Domain language (Q34770)
Allowed values individual language, dialect (Q33384), ISO 639 macrolanguage (Q152559), language collection.
Example English (Q1860) => individual language
Source ISO 639-3 (Q845956)
Robot and gadget jobs might be imported by bot
Proposed by Pathoschild

This property would contain the language scope defined in the ISO 639-3 standard; see Scope of denotation for language identifiers for a full description. This property is of general interest — the standard is widely recognized (including by the Wikimedia Foundation for its language codes), and the scope is used by the Wikimedia language committee to determine the eligibility for new wikis. —Pathoschild 20:56, 16 August 2014 (UTC)

citation needed. Visite fortuitement prolongée (talk) 21:05, 1 January 2015 (UTC)
duplicate of ISO 639-1 code (P218), ISO 639-2 code (P219) and ISO 639-3 code (P220)? --Pasleim (talk) 18:55, 21 January 2015 (UTC)
It's not a duplicate of those. English has ISO 639-1 code "en", ISO 639-2/3 "eng" and is an individual language. Norwegian has ISO 639-1 code "no", ISO 639-2/3 "nor" and is a macrolanguage. - Nikki (talk) 13:24, 26 June 2015 (UTC)
ISO 639-3 only includes three scopes, "individual", "macrolanguage" and "special" (see [1]), it doesn't include "dialect" or "language collection" like this proposal suggests. - Nikki (talk) 13:24, 26 June 2015 (UTC)
Symbol support vote.svg Support --Pasleim (talk) 16:16, 25 August 2015 (UTC)

Endangered languages[edit]

Please redirect this if it's being posted in the wrong place. I went to Wikimedia (Wikimedia topic Endangered Languages) with the idea and as far as I can tell this is where I am supposed to bring it.

I'd like to propose that all Wikipedia articles on languages include their conservation status, in a format nearly identical to that used for animals. While articles on animals get their citations from the IUCN Red List, the conservation status of languages would be cited from the UNESCO Red Book on world languages. Since this is a rather broad idea affecting a large number of articles, I wanted to bring it up somewhere I thought it would be heard rather than on an individual article. User:PiRSquared17 suggested it could also include conservation data from Ethnologue. At any rate, let me know what your thoughts are, everyone. Interlaker (talk) 22:18, 7 February 2015 (UTC)

  • I personally Symbol support vote.svg Support the creation of the property, which could be called "endangered language status" or something like that. Is there an official range of values? Presumably we can just adopt UNESCO's. However, note, this is similar to the case of the property cultural heritage site/monument; I can't remember whether that one was created or instead the information added within instance of (P31). --Nemo 16:32, 8 February 2015 (UTC)

EGIDS language status[edit]

   In progress
Description EGIDS language status
Data type String
Domain languoid (Q17376908)
Allowed values listed here
Example Japanese (Q5287) => 1 national, Ainu languages (Q27969) => 8b nearly extinct
Source Ethnologue (Q14790),
Proposed by Visite fortuitement prolongée (talk) 22:04, 9 February 2015 (UTC)

Motivation: Suggested by @Interlaker, Nemo bis:.

So how do we proceed here? Interlaker (talk) 22:11, 9 February 2015 (UTC)

Interlaker We wait for users to support or oppose and when an admin thinks there is a quorum they either reject the proposal or they create the property. This can take up to a month or even longer. If the property is approved then you can start using it to add the status to the wikidata item for each language. Once the wikidata item has the status it can be added to infoboxes in any of the 280 language wikipedias which have articles about this language. Start by adding your support below. Filceolaire (talk) 23:49, 1 March 2015 (UTC)
  • Symbol support vote.svg Support but change datatype to 'item' to match IUCN conservation status (P141) and create 11 items to act as targets for this property. Filceolaire (talk) 23:49, 1 March 2015 (UTC)
  • Pictogram voting comment.svg Comment @Interlaker, Visite fortuitement prolongée, Filceolaire: I too suggest creating an item for each grade, and switching to datatype=item. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 09:25, 23 March 2015 (UTC)
  • Symbol support vote.svg Support Pamputt (talk) 08:55, 19 April 2015 (UTC)
  • Symbol support vote.svg Support with datatype "item" --Pasleim (talk) 19:16, 26 April 2015 (UTC)
  • Symbol oppose vote.svg Oppose Ethnologue is not a RS for this information. They just added the category, and it's clear that in many cases they just made a guess, based on the demographic data they have, which they are also not a RS for. (It may be ethnic rather than speaker data, or may be half a century old.) There was recently a Rutger's class project on endangered languages, and the students often linked to, which suggests that many of the evaluations have little reliability. For example, Ethnologue rates Kiong as 8a moribund.[2] The other site has it as "severely endangered", but with only a 20% certaintly.[3] It looks at first glance that Ethn. has a credible source for it's assessment (Dimmendaal 2007), but that is likely only a ref for "Shifting to Efik", which does not mean the language is moribund or even severely endangered, and not for "Spoken only by people of sixty years or older" (i.e., moribund), which we must assume is unreferenced and therefore unreliable. Ethnologue would see that comment and therefore assign a ranking of 8a to the language, but without verifying that the statement is current or reliable. I don't know there assessment of this language is wrong (I just picked an article I edited yesterday), but often their assessments clearly are wrong, and unlike, they give no indication of the credibility of the ranking. I think we should have a discussion at the language wikiproject as to which sources are reliable before we start rolling out claims like these. Kwamikagami (talk) 21:13, 21 May 2015 (UTC)
  • Pictogram voting question.svg Question Is there an other source than for EGIDS language status ? Visite fortuitement prolongée (talk) 21:24, 21 May 2015 (UTC)
    • I can not find any source outside and SIL ( use and some other sources, but their scale is different from EGIDS, with only 6 levels like UNESCO scale). And the authors of EGIDS scale are members of SIL. Visite fortuitement prolongée (talk) 21:49, 21 May 2015 (UTC)
  • Symbol oppose vote.svg Oppose per Kwami. The fact that give "0 international" level to no language in the world, even English and Spanish, should have gave me a hint. Visite fortuitement prolongée (talk) 21:49, 21 May 2015 (UTC)
  • @Interlaker, Nemo bis, Filceolaire, TomT0m, Pamputt, Pasleim: Visite fortuitement prolongée (talk) 14:34, 23 May 2015 (UTC)
    • I am not a linguist but should we discuss the reliability of a source. As far as I know, ethnologue is a very well known publication. Thus, it does not matter to Wikidata whether the data are reliable; the EGIDS code exists and we just have to decide if we want to import it into Wikidata. This import could allow people to reuse this EGIDS code correlated to other data of an item. It is enough to import these data IMO. Pamputt (talk) 15:47, 23 May 2015 (UTC)
  • I Symbol oppose vote.svg Oppose using data from an unreliable source. I am happy for us to have links out to unreliable sources like IMDB to help them coordinate info with us and import info from us. Similarly I would vote to add an egids language reference code (if such a thing exists) to language items on wikidata but that is different from having a property in wikidata based on a particular datum in egids which we don't think is reliable. Once the info is in wikidata it will get added to wikipedias and allsorts of other sites because we have endorsed it. Filceolaire (talk) 02:50, 27 June 2015 (UTC)
  • Pictogram voting comment.svg Comment There seems to be no exclusive link between the classification and the suggested source. If this can be sourced from somewhere else, why not? --- Jura 17:59, 3 July 2015 (UTC)
    • Indeed. However, as I have wrote above (21 May 2015), I have searched (½ hour) an other source using or showing EGIDS scale, and I have found none. Visite fortuitement prolongée (talk) 19:13, 3 July 2015 (UTC)
      • Actually, in the meantime, I found a place that says it was developed for them. --- Jura 15:11, 4 July 2015 (UTC)

LACITO language ID[edit]

   Not done
Description identifier of a language at the web site of LACITO
Data type String
Domain languoid (Q17376908)
Allowed values letters
Example West Uvean language (Q36837) => Fagauvea
Source etc.
Formatter URL$1_popup.htm

Motivation The web site of the LACITO LACITO (Q3217451) publish some dozens pages about languages. Link the audio records of Lacito Archive (Q6468667). This property could be usefull. Or not. Visite fortuitement prolongée (talk) 15:28, 19 April 2015 (UTC)

Proposé par: Visite fortuitement prolongée (talk)

You're not really sounding convincing. Do you intend to use this property in a project? --Pasleim (talk) 19:21, 26 April 2015 (UTC)
No. Visite fortuitement prolongée (talk) 19:36, 26 April 2015 (UTC)

 Not done No support. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 19:41, 23 November 2015 (UTC)


In the age of Open Data and Linked Data, we should be able to describe structured data sources, such as data set (Q1172284), thesaurus (Q179797), database (Q8513), authority control (Q36524) (eg Integrated Authority File (Q36578), Virtual International Authority File (Q54919), etc).

The leading ontologies for describing datasets are VOID, DCAT and ADMS by the W3C. The Getty LOD documentation shows summary diagrams & links, and uses all of them to describe the Getty dataset. Our intent is not to replicate all this information, but to provide only some critical entities and properties to allow finding datasets and access points. This is a somewhat complex topic, so before proposing properties, we should look at the above models, look at some examples, and synthesize a simpler version.


Let's first look at some examples



Data Model[edit]

Based on the examples, we can extract the following items (Q), properties (P), qualifiers (q):

  • <a structured database>
  • Dataset Distribution (Q): particular version/release/format of a structured Data Set (database) that is publically available. May be created and published by other than the database owner (that's quite common)
    • official website (P856): human-readable documentation
    • URL (P) of technical documentation (Q)
    • URL (P) of Datahub (Q): structured description at, including access URLs, examples, etc
    • URL (P) of VOID machine-readable description (Q)
      • format (q): eg VOID, OAI-PMH, explain.z3950
    • URL (P) for access/download: URL that allows search/access/download of a dataset distribution
      • protocol (q): eg SPARQL, SRU, OAI-PMH. Direct file access by HTTP is default and need not be mentioned
      • file format (q): file format and/or metadata schema, eg RDF/XML, Turtle, NTriples, JSONLD, MARC21plus-xml, MARC21-xml, xMetaDiss, oai_dc, ONIX-xml, sync-repo-xml
      • file compression format (q): eg zip, gz


   In progress
Description Particular version/release of a structured Dataset, that is publicly available
Data type Item
Template parameter none
Allowed values data set (Q1172284)
Format and edit filter validation n/a
Source dcat:Distribution, adms:AssetDistribution
Robot and gadget jobs in the future yes..
Proposed by Vladimir Alexiev (talk)

distribution (dataset)[edit]

   In progress
Description Particular manner of distribution of a Data Set (database or file) that is publicly available
Data type Item
Template parameter none
Domain data set (Q1172284)
Allowed values Dataset Distribution (Q18814183)
Format and edit filter validation n/a
Source dcat:Distribution, adms:AssetDistribution
Proposed by Vladimir Alexiev (talk)

file format[edit]

(aliases: format, file type, compression format)

   In progress
Description File format, compression type, or ontology used in a file. May use several (eg Zip (Q136218) and NTriples (Q18814471))
Represents file format (Q235557)
Data type Item
Template parameter none
Domain Use as qualifier of a URL or file name (often used with data set (Q1172284) or Dataset Distribution (Q18814183))
Allowed values

Instances of file format (Q235557), such as

Target will often have Internet media type (P1163) and file extension (P1195)
Example AAT LOD dataset => URL of (P642) download (Q7126717), file format Zip (Q136218), file format NTriples (Q18814471) =>
Format and edit filter validation n/a
Proposed by Vladimir Alexiev (talk)
  • Symbol support vote.svg Support. Joe Filceolaire (talk) 02:08, 5 September 2015 (UTC)
  •  Pictogram voting question.svg Question @Vladimir Alexiev, Filceolaire: ZIP is not really a primary file format, "Zipped TTL" may be. We need a more expressive way to hadle fie formats. Internet media type (Q1667978) (View with Reasonator) can identify some formats. As for ontology. An ontology can be express in numerous file formats ... Would we need a more specific "ontology" property ? author  TomT0m / talk page 17:10, 12 November 2015 (UTC)
    @TomT0m, Filceolaire: To handle a file or URL, an application needs to know all applied formats, not just the "primary" (content) or "secondary" (compression). Combining them into one (eg "zipped turtle") is not a good idea since we'll cause a combinatorial explosion. We could split into two props if you prefer? (eg HTTP has Content-Type vs Content-Encoding) I didn't want to complicate it too much, but now that I think about it, I'm in favor of splitting.
As for Ontology, I completely agree to split it out. It's the same as void:vocabulary. (I just didn't think the WD community would be so interested in RDF datasets :-). Should I make a proposal for it? --Vladimir Alexiev (talk) 21:07, 16 November 2015 (UTC)
In general we will have an item for the dataset. We need properties to link to the various datafiles for that dataset. The question then is whether we have properties for each type of file with qualifiers for the file format and compression format (my preferred solution) or if we have separate properties for each datafile/file format/file compression format (seems clumsy). Joe Filceolaire (talk) 03:59, 22 November 2015 (UTC)

data access protocol[edit]

(aliases: communication protocol)

   In progress
Description communication protocol to use to access a dataset or service
Represents communications protocol (Q132364)
Data type Item
Template parameter none
Domain Use as qualifier of a URL (often used with data set (Q1172284) or Dataset Distribution (Q18814183))
Allowed values Instances of communications protocol (Q132364), such as SPARQL (Q54871), Open Archives Initiative Protocol for Metadata Harvesting (Q2430433)
Example AAT LOD dataset => URL of (P642) API (Q165194), protocol SPARQL (Q54871) =>
Format and edit filter validation n/a
Proposed by Vladimir Alexiev (talk)


(aliases: webpage, page)

   In progress
Description URL of something, other than official website (P856), reference URL (P854), or archive URL (P1065). Must qualify with of (P642)
Data type URL
Template parameter none
Domain any
Allowed values URL
Format and edit filter validation n/a
Robot and gadget jobs validate that URL resolves
Proposed by Vladimir Alexiev (talk)

Discussion of Dataset properties[edit]

PLEASE first comment on the need to describe Datasets, and then on the specific implementation proposed above (of course, we could have a different implementation)

What do you think of this? --Vladimir Alexiev (talk) 14:53, 7 January 2015 (UTC)
@Emw, Snipre, Kolja21, Fralambert: What do you think of this? --Vladimir Alexiev (talk) 19:35, 19 January 2015 (UTC)

Ruud Koot
Pictogram voting comment.svg Notified participants of Wikiproject Informatics

I welcome thoughts on how to describe datasets, and the above is a good basis for having a discussion around that – thanks, Vladimir. The proposed implementation would seem to work for the examples given, but I am missing thoughts on licensing and versioning of datasets, as well as on the scope of datasets to be annotated this way. For instance, if there is an item about a scholarly publication and that publication has some associated data in a database, it would make sense to annotate the item about the paper with information about the dataset. This would not necessarily require an item about the dataset itself, though that might be an option if WD:N does not stand in the way. --Daniel Mietchen (talk) 00:48, 20 January 2015 (UTC)
Sure, that's just a start. But I think we don't want to repeat all the detailed info at Datahub and VOID files. Vladimir Alexiev (talk) 01:16, 20 January 2015 (UTC)
Suggesting if there is a CKAN/DataHub entry, that should be linked from the WP page? Other than that, I think VoID actually does do a good job at the provenance. Other than that, what is the envisioned difference between a data set and a data base? The latter has a clear visibility, with a website, etc. What makes a data unique? Egon Willighagen (talk) 07:49, 20 January 2015 (UTC)
Egon, Datahub is just one of the important URLs: above I give other examples. VOID does a good job, but is only applicable to RDF datasets, and less than 30% have a VOID file.
"Dataset" and "Database" are just about the same, and there are many other similar items (eg Authority list). I've only proposed a property "dataset distribution" to point to a particular distribution of a database, since often there are many: see GND examples above.
"What make a data unique": I don't know and I don't care. Clarify the question. --Vladimir Alexiev (talk) 18:56, 21 January 2015 (UTC)
Hi I started to work on this subject. Can I reuse or complete or duplicate the box "Property documentation" ? I write these box in the comments ? or in talk page ? May be create a project Wiki4R and create a subpage for this part ? --Karima Rafes (talk) 13:57, 20 January 2015 (UTC)
Karima, go ahead and edit above, it's a wiki. I added "protocol". If you want to move the section "Datasets" to a more permanent location, go ahead: but after the voting for the properties (when it will be moved to a subsection "Archive". --Vladimir Alexiev (talk) 18:56, 21 January 2015 (UTC)
Hello, I splited the dataset distribution in dataset and distribution like in the ontology dcat. I proposed some properties in the aim to make a map like on the website and for the future web agents. I don't know exactly if the properties exist or not in Wikidata. --Karima Rafes (talk) 14:26, 22 January 2015 (UTC)
@Karima Rafes: 1. Don't see a need for "dataset" vs "distribution" property, and you don't seem to propose different examples. We don't need to copy dcat or any other ontology. 2. The markup following "Here proposition for the infobox" is broken, please fix it!! 3. Put your contributions in separate sections (one per property) and sign them (not just this comment). 4. If you want to propose a property (eg xxx:statusAccessURL), do it using the appropriate template at the top of this page, so it can be discussed and critiqued independently. (Critique about this one: one dataset may have several access URLs, so a single "status" prop won't do. 5. "I don't know exactly if the properties exist or not" is no excuse: don't propose properties before checking whether similar properties already exist. Pick any item, go to Claims, click Add and use the autocomplete. --Vladimir Alexiev (talk) 08:41, 25 January 2015 (UTC)
1. "We don't need to copy dcat or any other ontology." DCAT is an ontology for the software agents. If you don't split, you impose that there is only one way to access the data and so, only for the human. It's not logic to use DCAT only for human. 2. Sorry, I have no the time for the moment. I try to fix if wikidata want to be a hub for the software agents. Is it the moment for this debate ? (good place?) 3. 4. 5. it's not urgent. I moved my examples in my personal page for the moment examples of properties for a object dataset and distribution --Karima Rafes (talk) 09:30, 25 January 2015 (UTC)
I think wikidata should aspire to be a hub for software agents.
I think that there is a case for specialised url properties rather than using "of" as a qualifier, particularly for 'machine readable' access and particular types of info - such as 'technical info URL', 'VOID url', 'API url'.
'Datahub' should perhaps be a string property since it always refers to the datahub site - like all the other database properties.
A 'download url' property should be designed to be useable to download digital copies of books or songs as well as databases. This applies in particular when the content is available as a free download but the licence terms are not compatible with Commons.
I support 'file format', 'compression file format', 'protocol' as qualifier properties.
I'm not sure what 'dataset' and 'distribution (dataset)' are for and what they link to. Should we have a separate item for each edition of the dataset, as well as the item for the database? What if a new edition is published every day? Could we use software version (P348) or version type (P548) or edition(s) (P747) for these? Filceolaire (talk) 03:49, 22 March 2015 (UTC)
@Filceolaire: thanks for the comments!
Agree to have "specialised URLs" since these are easier to work with than "of" qualification (both for WDQ and SPARQL querying). I just wasn't bold enough to propose so many new properties.
If you think from the FRBR "work-expression-manifestation-item" point of view, a Distribution is similar to Expression or Manifestation: if it's done by someone else through significant conversion work then it's Expression (similar to a translation of a book); if it's just an update or editorial work, then it's aManifestation (simlar to an edition of a book).
Instead of a new prop Distribbution, we could use software version (P348) but currently it's for "software" only and doesn't have a "derived work" aspect (typically each consecutive version is made by the same people). It seems that edition(s) (P747) is a better fit (it's the same idea!), but do you think bibliophiles will allow the alias "distribution"? Or maybe keep them separate just for clarity?
Agree about doing "Datahub page" as an ID rather than a URL. (they did change their base from to a few years back) --Vladimir Alexiev (talk) 11:53, 31 July 2015 (UTC)
So Vladimir are you going to rewrite the proposals above, as your comments, so we can can get some of these approved? Joe Filceolaire (talk) 23:47, 2 September 2015 (UTC)
Done, see below; fixed the examples above. (Also fixed VIAF->GND in a couple examples above) Vladimir Alexiev (talk) 10:44, 4 September 2015 (UTC)

Datahub page[edit]

   In progress
Description Datahub page of a dataset
Represents Datahub (Q18814247)
Data type String
Domain data set (Q1172284) or Dataset Distribution (Q18814183)
Formatter URL$1
Proposed by Vladimir Alexiev (talk)

why ID rather than URL: they did change their base from to a few years back


serial number[edit]

Description an identifier for a specific object among the same product
Represents serial code (Q1198578)
Data type String
Domain products with specific objects notable enough to get an item
Allowed values .+
Example John F. Kennedy assassination rifle (Q2012291) → C 2766
  • Symbol support vote.svg Support --- Jura 11:04, 11 October 2015 (UTC)
  • Symbol support vote.svg Support. But make "serial code" the primary label, to match the "represents item"? --Vladimir Alexiev (talk) 21:09, 16 November 2015 (UTC)
    • Pictogram voting comment.svg Comment Vladimir Alexiev: w:serial code has only the title "serial code", but most of the article uses "serial number". Thus I made the label of Q1198578 match the proposed label instead. Hope that's ok. --- Jura 08:09, 17 November 2015 (UTC)
  • Symbol oppose vote.svg Oppose as "serial number". The example given is not a number. (I would support this as "serial code")Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 19:36, 23 November 2015 (UTC)

block size[edit]

   In progress
Description size of block for this block cipher
Data type Number
Template parameter Taille(s) du bloc dans fr:Modèle:Infobox Chiffrement par bloc ; Block sizes in en:Template:Infobox encryption method
Domain block cipher (Q543151)
Allowed values nombre — with unit : bit (Q8805)
Example 3-Way (Q223123) → 96 bit (Q8805)
Robot and gadget jobs Eventually for take values from infobox in a first time.

With this property we could centralizing informations about block cipher in wikidata and put them directly in wikipedia infobox. Metamorforme42 (talk) 14:19, 11 October 2015 (UTC)


Ruud Koot
Pictogram voting comment.svg Notified participants of Wikiproject Informatics

Symbol support vote.svg Support. author  TomT0m / talk page 16:59, 12 November 2015 (UTC)
Symbol support vote.svg Support Seems good. --Tobias1984 (talk) 21
31, 12 November 2015 (UTC)
  • Symbol support vote.svg Support but define it more generically to also handle "disk block size". Define it eg as "Unit of processing of information in bits, bytes, kilobytes, etc" and provide a couple of examples --Vladimir Alexiev (talk) 21:14, 16 November 2015 (UTC)

Roman names[edit]

Title ID Data type Description Example Inverse
Roman praenomen new  create Item standard part of the name of a Roman, link to items for specific Roman praenomen only.
See w:praenomen and w:Roman naming convention. Categories/lists: wiktionary:Appendix:Roman praenomina
Marcus Annius VerusMarcus (Q6757977) -
Roman nomen gentilicium new  create Item standard part of the name of a Roman, link to items about the Roman gens only.
See w:Roman naming conventions#Nomen. Categories/lists: w:List of Roman gentes, w:Category:Roman gentes
Marcus Annius VerusAnnia (Q2035133) -
Roman cognomen new  create Item standard part of the name of a Roman, link to items about specific Roman cognomen only.
See w:Cognomen and w:Roman naming convention. Category/lists: w:List of Roman cognomina
Marcus Annius Verus → Verus -
Roman agnomen new  create Item optional part of the name of a Roman, link to items about specific Roman agnomen only.
See w:agnomen and w:Roman naming convention
Scipio Africanus → Africanus -
Support - explain why you support the proposal
  • Symbol support vote.svg Support helps implement phase 2. Provides context specific guidance. --- Jura 12:12, 10 November 2015 (UTC)
  • Symbol support vote.svg Support. Joe Filceolaire (talk) 02:23, 11 November 2015 (UTC)
  • Symbol support vote.svg Support A good starting point to deal with Roman names on a more differentiated level. Jonathan Groß (talk) 11:02, 12 November 2015 (UTC)

Discussion of properties - explain how you think the proposal should be improved
  • Pictogram voting comment.svg Comment Nothing to add :) This similar to the properties for Chinese names. --- Jura 12:12, 10 November 2015 (UTC)
  • Pictogram voting question.svg Question What is the difference between a praenomen and a given name, and between a cognomen and a surname? Also, is there a more generic version of nomen that might be usable? (Clan name, maybe?) If avoidable, I think we should try to have as few culture-specific name properties as possible. --Yair rand (talk) 03:04, 11 November 2015 (UTC)
    • From a Wikidata perspective, it would be that praenomen link to items for praenomen, P735 to items for given names; P734 links to whatever it links and cognomen to items for cognomen (and nomen to items for gens). I added links to related categories and lists to the proposal. The article linked in the proposal explains how Roman naming as well as the function and selection of various parts evolved .. at some point, one or the other could be considered similar to given names and family names today, but later or earlier not. One of their characteristics is their designation as praenomen and cognomen.
      It's possible to use the same property for clans and Roman gens, but I don't think it helps when adding or checking values. What do you think? --- Jura 13:25, 11 November 2015 (UTC)
  • Pictogram voting comment.svg Comment I changed the second proposal to "Roman nomen gentilicium". This should avoid potential issues with other nomen that are not for the gens. @Filceolaire, Jonathan Groß: is this ok with you? Potentially, we might need an other property for names that are not any of the four. Shall we add this now as well? --- Jura 07:44, 13 November 2015 (UTC)

Discussion of proposal format - comment here on the proposal format
  • Pictogram voting comment.svg Comment the second format for proposals was chosen to view them concurrently and simplify property creation by admins. --- Jura 12:12, 10 November 2015 (UTC)

  • Symbol oppose vote.svg Oppose --- Jura 12:12, 10 November 2015 (UTC)