Wikidata:Property proposal/Archive/13

From Wikidata
Jump to navigation Jump to search


cadastral code / / / / codice catastale

Descriptionthe cadastral code, as defined by local/national administrations. Codice catastale (Q1053729)
Data typeString
Template parametere.g. it:template:Divisione amministrativa codice catastale
Domaincities/towns
Allowed valuese.g. for the Italian "new" catastal code, \w\d{3}
ExampleAbbadia Cerreto → "A004"
Sourcefrom Wikipedia infoboxes, and from external sources like this
Robot and gadget jobsSamoaBot is ready to import this
Proposed byRicordisamoa

I think it's needed and useful; we could use qualifiers to distinguish between different code versions. Ricordisamoa 20:09, 20 April 2013 (UTC)

Should we use qualifiers or simply imply the code version? --Ricordisamoa 22:51, 2 May 2013 (UTC)
I think we must use qualifiers, maybe the begin\end date of validity (when will be available the DataType), or the code version. --β16 - (talk) 08:10, 3 May 2013 (UTC)

✓ Done Created for Italian comunes only.--Micru (talk) 03:28, 15 August 2013 (UTC)

separated from / forked from

✓ Done Created as a single one separated from (P807).--Micru (talk) 01:41, 17 August 2013 (UTC)

separated from

Descriptionsubject was founded by members of the organization separating from object
Data typeItem
Template parameter"separated from" in en:template:Christian denomination
Domainorganization
Allowed valuesorganization
ExamplePresbyterian Church in America (Q3555519) => Presbyterian Church in the United States (Q3268181)
Proposed byJfhutson (talk)
Discussion

Traces the origin of separating organizations in other organizations. Jfhutson (talk) 14:23, 4 May 2013 (UTC)

Can this be achieved with the existing part of (P361) property and date qualifiers like until? For example, 'Presbyterian Church in America' part of 'Presbyterian Church in the United States' until (date of separation)? Emw (talk) 17:28, 4 May 2013 (UTC)
The PCA did not exist until it separated. It was founded because of disagreements between individuals within the church, so those individuals formed a new body. --Jfhutson (talk) 17:55, 4 May 2013 (UTC)
Good point. The basic semantics of this property -- part of something separating into something new -- seem applicable well beyond religious schisms. It seems like it could easily cover events like forks in software development, seccession (like South Sudan separating from Sudan), and likely other types of branching splits. Emw (talk) 18:46, 4 May 2013 (UTC)

 Support--Micru (talk) 01:46, 8 July 2013 (UTC)

forked from

Descriptionwhat other software program this forked from
Data typeItem
Template parameterDoesn't seem to exist on English Wikipedia; not sure about others
Domaininstances of computer program (or descendants)
Allowed valuesinstances of computer program (or descendants)
ExampleXEmacs => GNU Emacs
Sourcehttp://www.dwheeler.com/oss_fs_why.html#forking
Discussion

There are many cases where such forks are well-documented, and this will allow us to automatically construct graphs (visual or otherwise) of the lineage. It would also be a good use case for qualifiers (date forked) when they are available. Superm401 - Talk 07:43, 4 April 2013 (UTC)

It might be appropriate to reuse based on ("the work(s) used as basis for subject") for this. I'm not sure, and that isn't well-documented. Superm401 - Talk 07:49, 4 April 2013 (UTC)
  • This property seems useful, but I would suggest that it's applicable in other domains, and thus should be crafted to be more generic. This relationship seems like a high-level genealogical description that could apply to evolutionary descent, historical linguistics, population migration, and historical splits in world religions and political movements and parties. The different domains use different idioms, but they seem to describe the same underlying thing. Emw (talk) 04:13, 10 April 2013 (UTC)
    Although I agree that evolutionary descent, population dynamics, etc. are similar/analogous to "forked from" in some ways, I think that's too broad. I have a couple possible updated proposals:
    1. Use a qualifier for based on (P144), e.g. "derivative work". I think "based on" is too vague without qualifiers; it could mean anything from "inpisred by" to "reimplementation of" (e.g. the GNU system is a cleanroom re-implementation of UNIX ("based on" in one sense), but not a derivative work of it). A qualifier makes "based on" more useful.
    2. Have a separate broader property than "forked from", but not so broad as the above. Perhaps, "derived from copyrighted work".
    Everyone, let me know what you think (I tend towards preferring the qualifier approach now that they're available), and if you prefer I make a new proposal, I can do that. Superm401 - Talk 02:53, 27 May 2013 (UTC)
  • There is another proposal that could be used for software as well: separated from.--Micru (talk) 02:03, 8 July 2013 (UTC)

mentions

   Not done
Descriptioncitations and quotes of Authors and other Works.
Data typeItem
Domainbooks, but maybe can be extended at every Creative Work (citations are commons in Movies too).
Allowed valuesIn the Books, domain, we could start with Authors and Works. I'm not sure if we want to use this for quotes as well.
Examples:it:
SourceIt is a property form Schema.org (I mapped it here).
Proposed byAubrey (talk)

It would be very useful to store the chapter/page/section of the citing work. I can say, for example, that Hamlet cites the bible (bad example, I know), but like this is not useful. With qulifiers, we could say that the First act of Hamlet cites the third cchapter of the Genesis, which I think is something worth saving.

In it.source, we have 2 templates that could map this property: AutoreCitato and TestoCitato (cited author and cited text). These templates make a wikilink from the cited author/text to his/its wikisource page, and also create a category which stores all the pages in which the author/text has been cited (ex. s:it:Categoria:Testi in cui è citato Dante Alighieri). --Aubrey (talk) 16:05, 1 June 2013 (UTC)

  •  Wait I think it is better to wait until the book data model is more developed and the people more used to it. Properties like this will be used later on, when we are already bored of adding standard properties. My suggestion is to wait.--Micru (talk) 18:16, 12 June 2013 (UTC)

 Not done Might be reconsidered in the future, though.--Micru (talk) 02:22, 17 August 2013 (UTC)

date of burial (en) / Begräbnisdatum (de)

   Not done
Descriptiondate on which a person was buried
Data typePoint in time
Domainperson
ExampleCarl Lagercrantz (Q14559751) => 2004-07-26
Proposed bySchneelocke (talk) 14:59, 12 August 2013 (UTC)
Discussion

We already have place of burial (P119), so it would make sense to also have this. -- Schneelocke (talk) 14:59, 12 August 2013 (UTC)

 Support--Kompakt (talk) 06:45, 13 August 2013 (UTC)
 Oppose Could this not be expressed using start time (P580) as a qualifier of place of burial (P119)?--Micru (talk) 01:17, 17 August 2013 (UTC)
 Oppose Use significant event (P793) => burial (Q331055) with qualifier point in time (P585) and P766 (P766). Filceolaire (talk) 12:14, 17 August 2013 (UTC)

 Not done As per Filceolaire and myself.--Micru (talk) 16:19, 17 August 2013 (UTC)

Código Bien de Interés Cultural

DescriptionCultural property identifier for Bien de Interés Cultural (Q23712) in Spain. See es:Bien_de_Interés_Cultural#Codificación
Data typeString
Template parameterCommons:Template:BIC
Domainplaces: cultural properties in Spain
Allowed valuesRI-(AR|BI|MU|51|52|53|54|55|56)-\d{7}(-0{4})?
ExampleTorre de Morales (Q14563353) => "RI-51-0009163"

✓ Done Asset of cultural interest code (P808)--Micru (talk) 23:33, 17 August 2013 (UTC)


Law article

   Not done
Descriptionarticle of a law
Data typestring (I think, as it is more flexible than number in case some countries use different systems)-invalid datatype (not in Module:i18n/datatype)
Exampleen:Template:Cite constitution
Proposed byZolo (talk) 07:34, 25 April 2013 (UTC)

Needed to cite legal texts. Cannot think of a good, non-ambiguous label though. --Zolo (talk) 07:34, 25 April 2013 (UTC)

 Oppose But I think the proposal in not well defined: what is needed is a property or perhaps 2 about the article and a section or paragraph. Here an analysis is required in order to find a system which can be applied to most of legal literature. Snipre (talk) 11:14, 28 April 2013 (UTC)

 Not done I will propose a "position in document" as alternative.--Micru (talk) 03:54, 18 August 2013 (UTC)

according to

   Not done
Descriptionproperty to associate a claim with an individual, group, or school of thought that advances it
Data typeItem
Allowed valuesindividuals, groups, or schools of thought
ExampleFort Roughs → country: <Principality of Sealand → according to: Paddy Roy Bates>; <United Kingdom → according to: Government of the United Kingdom>
Proposed by — PinkAmpers&(Je vous invite à me parler)
Discussion

One of the founding principles of Wikidata is that we need to be able to represent multiple divergent points of view without declaring any individual one to be correct. As such, we need a property essentially saying "this group/person claims such-and-such". "Stated in" only makes sense for creative works, and "imported from" only makes sense with other databases and the like. This will be useful for all sorts of complicated or contested issues, such as border disputes, competing scientific theories, or definition-related disagreements. — PinkAmpers&(Je vous invite à me parler) 15:54, 31 May 2013 (UTC)

 Oppose If you source with the newspaper article, the official report of an organisation, an TV/radio emission according to Help:sources you don't need this property which doesn't provide any possibility to check if the affirmation is correct. Snipre (talk) 17:52, 31 May 2013 (UTC)
But we don't need to check if the claim is correct. That's what ranks will be for. And no, a reliable source stating that Paddy Bates claimed sovereignty over Sealand doesn't constitute a TV station stating that he actually held such sovereignty. (In fact, journalistic/academic objectivity would prohibit any reliable source from saying such a thing.) — PinkAmpers&(Je vous invite à me parler) 06:14, 2 June 2013 (UTC)
If we want to say: Senkaku Islands is part of Japan according to Japan and part of China according to Japan, could arguably be expressed by "Senkaku Island. part of Japan. stated in: some japanese sources. etc." But still that may not be extremely clear. So agree that we need something, but I think it should be used as a qualifier, not in a source. (part of Japan, according to: Japanese government, source: text that says that it is the Japanese position).
This is related to Wikidata:Property proposal/Generic#Truth value. We apparently need a RFC on those things. --Zolo (talk) 07:05, 2 June 2013 (UTC)

 Not done--Micru (talk) 03:54, 18 August 2013 (UTC)

WPDA id

   Done: WDPA ID (P809) (Talk and documentation)
Descriptionidentifier in World Database on Protected Areas (Q3569967)
Data typeString
Template parameter"wpda" in fr:Template:Infobox_Aire_protégée
Domainplaces: protected areas
ExampleDry Island Buffalo Jump Provincial Park (Q3364718) => 18608
Sourceinfobox
Robot and gadget jobsimport from template
 Support Quasi-universal, the best ID for protected area, even if it's not up to date in every country. --Fralambert (talk) 11:55, 10 August 2013 (UTC)

units produced (en) / Einheiten produziert (de)/ unités produites (fr)/ esemplari prodotti (it)/ unidades producidas (es)

   Not done
Descriptionnumber of units produced
Data typeNumber (not available yet)
Template parameter"production" in en:template:Infobox automobile
DomainTerms
ExampleFerrari 288 GTO (Q176152) --- ( units produced ) ---> 272
Robot and gadget jobs"production" in en:template:Infobox automobile
Proposed byLucaBiondi (talk) 12:46, 20 August 2013 (UTC)
Discussion

production start date (en) / Produktion Starttermin (de)/ production date de début (fr)/ data di inizio produzione (it)/ fecha de inicio de la producción (es)

   Not done
Descriptiondate of the start of the production
Data typePoint in time
Template parameter"von" in de:template:Infobox PKW-Modell
Domainterm
ExampleOpel Kadett E (Q2025180) --- ( date of the start of the production ) ---> Aug 1984
Robot and gadget jobs"von" in de:template:Infobox PKW-Modell
Proposed byLucaBiondi (talk) 14:42, 20 August 2013 (UTC)
Discussion


I've done this for Opel Kadett E (Q2025180):
significant event (P793) equal to production (Q739302)
start time (P580) agosto 1984
end time (P582) maggio 1993
Do you think production (Q739302) is correct? LucaBiondi (talk) 19:25, 20 August 2013 (UTC)

production end date (en) / letzten Tag der Produktion (de)/ dernier jour de production (fr)/ data di fine produzione (it)/ último día de la producción (es)

   Not done
Descriptiondate of the start of the production
Data typePoint in time
Template parameter"bis" in de:template:Infobox PKW-Modell
Domainterm
ExampleOpel Kadett E (Q2025180) --- ( date of the end of the production ) ---> Mai 1993
Robot and gadget jobs"bis" in de:template:Infobox PKW-Modell
Proposed byLucaBiondi (talk) 14:42, 20 August 2013 (UTC)
Discussion
  • This property could be used also for others terms like Computers, Ships, aeroplanes and so on...
  • This proposal will be deleted: redundant with an existing property (see significant event (P793)) Snipre (talk) 17:37, 20 August 2013 (UT

IUCN protected areas category

Descriptionprotected areas category by the World Commission on Protected Areas (Q2734584) in International Union for Conservation of Nature (Q48268). See also IUCN conservation status (P141)
Data typeItem
Template parameter
Domainplaces: protected areas
Allowed valuesIa, Ib, II, III, IV, V and VI:
  • IUCN category Ia: Strict Nature Reserve (Q14545608)
  • IUCN category Ib: Wilderness Area (Q14545620)
  • IUCN category II: National Park (Q14545628)
  • IUCN category III: Natural Monument or Feature (Q14545633)
  • IUCN category IV: Habitat/Species Management Area (Q14545639)
  • IUCN category V: Protected Landscape/Seascape (Q14545646)
  • IUCN category VI: Protected Area with sustainable use of natural resources (Q14545652)
    • ExampleDry Island Buffalo Jump Provincial Park (Q3364718) => II
    Sourceinfobox or en:Category:Protected areas by World Conservation Union category
    Robot and gadget jobsimport from template or category
  • Added the template above. Someone might want to propose/create it. --  Docu  at 09:46, 10 August 2013 (UTC)
    •  Support As category determined by international convention. --Fralambert (talk) 12:00, 10 August 2013 (UTC)
     Support --Tobias1984 (talk) 07:56, 15 August 2013 (UTC)
     Support — Ivan A. Krestinin (talk) 08:38, 19 August 2013 (UTC)

    ITIS TSN (en) / ITIS TSN (de)

       Done: ITIS TSN (P815) (Talk and documentation)
    DescriptionITIS TSN, i.e. the unique Taxonomic Serial Number defined by Integrated Taxonomic Information System
    Data typeString
    Template parameterNA
    DomainAll plant and animal scientific names at all ranks (up to kingdom)
    ExampleOceanic whitetip shark => 160330
    Sourcehttp://www.itis.gov
    Robot and gadget jobsData can be downloaded from itis, http://www.itis.gov looks like it is free to use for a bot
    Proposed bySilkyShark (talk) 00:51, 8 June 2013 (UTC)
    Discussion

    <empty>

    What's the reason for this proposal? What should we do with this database id? How to use it? To source something? Regarding plants the provided information is very unreliable. --Succu (talk) 21:04, 8 June 2013 (UTC)
    It identifies the 'data item', giving us a way to use other references and making sure that all references are for the same species, it also does give reference information, in my opinion the reliability of all taxo info seems to be depending on which field you are in, some databases are considered the correct for animals, or one type of animals and wrong for plants, mushrooms, algae, bacteria and so on and vice versa. I think that wikidata should refer to them all. SilkyShark (talk) 03:38, 9 June 2013 (UTC)
    I also see the problem that ITIS is quite outdated (most squamta entries are as of 1996). However, ITIS is huge and in contrast to many other databases in the public domain and all data is accessible. Thus, we could use it as a basis for referencing all those basic things like species A in genus B if both, A and B have still the same name. Also it can be used as the basis for authors and year of description claims as these do not change in most cases. However, I would not add new items based on ITIS or even add claims if others exist.  — Felix Reimann (talk) 19:50, 25 June 2013 (UTC)
    ITIS is good source when you don't have any other source for taxonomy. I wouldn't use it for bot runs, or at least not in specific things. But I think it could be used to add higher than family taxonomic ranks. I don't know if it is good argument but getting ITIS link from wikidata helps making new articles and using it as rough source for taxonomy. Linnea (talk) 20:08, 3 July 2013 (UTC)
    to keep this alive:  Support. as ITIS is the only public domain taxonomy database I know, I think ITIS is important as a basis.  — Felix Reimann (talk) 15:25, 9 August 2013 (UTC)

     Support--Micru (talk) 13:08, 15 August 2013 (UTC)

     Support good generic taxonomic database. Quiet reliable for taxon authority. Liné1 (talk) 10:23, 16 August 2013 (UTC)

    ✓ Done --Tobias1984 (talk) 22:08, 21 August 2013 (UTC)

    isotope of (or 'element')

       Not done
    Descriptionconnect all isotopes with their respective elements
    Data typeItem
    Template parameterInfobox isotope: num_protons (can be matched to atomic number)
    Domainterm
    Exampledeuterium (Q102296) "isotope of" hydrogen (Q556)
    Format and edit filter validationonly link to elements
    Sourcephysics literature
    Proposed by--Tobias1984 (talk) 16:41, 14 August 2013 (UTC)
     Support --Jakob (Scream about the things I've broken) 16:47, 14 August 2013 (UTC)
     Support --Paperoastro (talk) 19:56, 14 August 2013 (UTC)
     Support LucaBiondi (talk) 21:53, 15 August 2013 (UTC)
    Again there is the conflict between "instance of" and this new property. Snipre (talk) 07:52, 18 August 2013 (UTC)
    How would you use instance and subclass for isotopes? H is a subclass of elements and H-1, H-2 and H-3 are each a subclass of H? H-1, H-2 and H-3 would also be a subclass of isotopes? --Tobias1984 (talk) 16:06, 18 August 2013 (UTC)
    I tried it out using subclass of. It would currently result in this tree (using only subclass of):
    --Tobias1984 (talk) 16:45, 18 August 2013 (UTC)
    Correct: we have to create an new item for all element representing the concept of the elements and then as instance of this new item all items describing the isotopes (just a small correction the current item for helium is in reality helium-2 item for sitelinks point of view). We have the same case in chemistry with isomere like butanol (Q663902) which can be divided into butan-1-ol (Q16391) and 2-butanol (Q209332)Snipre (talk) 17:02, 18 August 2013 (UTC)
    Good to know. I guess we don't really need this property then and we can just wait for the number datatype from which isotopes can be queried by using "number of protons". --Tobias1984 (talk) 17:16, 18 August 2013 (UTC)

     Not done as the proposer I think using subclass of is the better choice. --Tobias1984 (talk) 20:43, 22 August 2013 (UTC)

    decays to

       Done: decays to (P816) (Talk and documentation)
    Descriptionconnect all radioactive isotopes (parents) with their daughters
    Data typeItem
    Template parameterInfobox isotope: decay_product
    Domainterm
    Exampleuranium-235 (Q848497) "decays to" Thorium-231 (a couple of hundred of items for all isotopes need to be created)
    Format and edit filter validationonly link to isotopes
    Sourcephysics literature
    Proposed by--Tobias1984 (talk) 16:41, 14 August 2013 (UTC)
    Discussion

    ✓ Done --Tobias1984 (talk) 20:45, 22 August 2013 (UTC)

    decay mode

       Done: decay mode (P817) (Talk and documentation)
    Descriptionthe type of decay that a radioactive isotope undergoes (should be used as a qualifier for "decays to")
    Data typeItem
    Template parameterInfobox isotope: decay_mode1 (2, 3, 4)
    Domainterm
    Exampleuranium-235 (Q848497) "decay mode" alpha decay (Q179856)
    Format and edit filter validationonly link to isotopes
    Sourcephysics literature
    Proposed by--Tobias1984 (talk) 16:41, 14 August 2013 (UTC)
    Discussion

    ✓ Done --Tobias1984 (talk) 20:46, 22 August 2013 (UTC)

    date retrieved

       Done: retrieved (P813) (Talk and documentation)
    Descriptiondate that information was retrieved from a database or website.
    Data typePoint in time
    Template parameterNone. Template parameter: "accessdate" in citation templates (the "Cite xxx" series) at the English Wikipedia.
    DomainPart of statement references. Not to be used in claims or qualifiers.
    Allowed valuesdate
    ExampleSource: stated in ->BNF: Date retrieved->June 7, 2013
    Robot and gadget jobsinformation that bots should include when they import data from online web sites or databases
    Proposed byFilceolaire (talk)
    Discussion

    Motivation. Support point in time (P585) can be misinterpreted. For example if we have a population figure for 2009 then point in time (P585) should be used as a qualifier to identify the year the population was measured. point in time (P585) 2009. We need a different qualifier to tell when the population information was retrieved from the database. Filceolaire (talk) 11:54, 8 June 2013 (UTC)

    @Byrial and Sniper: That does make sense. --Tobias1984 (talk) 16:18, 8 June 2013 (UTC)
    The ambiguity is not date retrieved vs date of validity of the claim, it is between various dates that can apply to the source itself. Sometimes, we may want to provide both the date when the document was created and the date when it was accessed. Note that en:Template;Cite web has both of these (respectively called "date" and "accessdate"). --Zolo (talk) 16:22, 8 June 2013 (UTC)
    Isn't the creation of the document publication date (P577) --Tobias1984 (talk) 16:26, 8 June 2013 (UTC)
    Yes, but there is no guarantee that users will use publication date (P577) to mean "date of publication" rather than "date retrieved". And really if I saw just one date, I would tend to think it means "date of publication". And if I saw "date of publication: 2005, date: 2007", I would open my eyes in bewilderment. --Zolo (talk) 16:33, 8 June 2013 (UTC)
    Possible solution: Different labels for properties when used as statement or source-qualifier. --Tobias1984 (talk) 16:39, 8 June 2013 (UTC)
    What Zolo says do make sense, but the proposal as it is now (both text and the motivation) does not, as sources and qualifiers are different things which cannot be mistaken for each other. If the proposal is rewritten along the lines of Zolo's argumentation, I may support it. As the proposal is now, it does not make sense, and I have to oppose. Byrial (talk) 17:11, 8 June 2013 (UTC)
    It is true that my support does not really match the description of this property, nor the initial motivation. I think that the use of the word "qualifier" was a terminological mistake, as is shown by the mention @Filceolaire, can I change the description in the template from "qualifier for source statements" to as "property to be used in the 'reference' part of a statement"  ?
    The problem with that is that 'date retrieved' won't be used in a primary source statement (The wikidata page template in english uses 'source' not 'reference' for these statements so that is what I've called them). It will be used to qualify a 'stated in' database source or a web site source property so I think 'qualifier for source statements' is the right term.. Filceolaire (talk) 21:01, 8 June 2013 (UTC)
    "Statement" is the term used in WD:Glossary. It is not used in item pages themselves, so that it is a bit confusing, but still they are not qualifiers are there is no softwarewise hierarchy between properties in the reference field. I think we can simply say "to be used in the source field". --Zolo (talk) 05:11, 9 June 2013 (UTC)
    Changed to 'used in the source field for online sources' though I think there is a hierarchy for properties in the sources between the property you enter when you click 'source' and the properties you enter later by clicking 'add'. Filceolaire (talk) 08:09, 9 June 2013 (UTC)
    @Zolo I can imagine a population figure where the population property has the qualifier 'as of' 2009 to tell us what year the census was carried out and the source for this has a 'publication date' 2010 for the date the hard copy was published and a second source, for the online version of the same info, has a 'date retrieved' 6 June, 2013. Each of these date properties have different meanings and I don't think any of them can be combined without creating confusion. Filceolaire (talk) 21:01, 8 June 2013 (UTC)
    @Zolo. Don't add complexity by mixing database and document. If you have a document, the date of publication is enough, no access date is required and I would say no access date is relevant. When access date is necessary ? When the data origin is not static and no normal way exists to track changes in the source. So you can have only one date for source, date of publication or as of for date access, if you have 2, one is unecessary and has to be deleted.
    And be coherent: if you are afraid that people don't use the correct property between date of publication and as of, how do you want to offer a simpler system by adding a new property ? Snipre (talk) 17:39, 8 June 2013 (UTC)
    I would also think that in many cases the accessdates is not very interesting, but things are not always as clear cut as database entries vs scholarly articles. The access date is provided for most quality content in Wikipedia, for all types of online sources. It is documented in all examples provided in the documentation en:template:cite web, one of Wikipedia's most used templates. We can't discount that on a vague feeling that is is not useful.
    I do not expect to eliminate errors by adding a new property, but it will make them easier to detect. The confusion is much more likely between publication date (P577) and point in time (P585) than between publication date (P577) and "date retrieved" (all the more as "as of" cannot be translated exactly in all languages). If we have a "date retrieved" property, we will not need point in time (P585) in the reference field, so that we can detect it as a likely error. We cannot do that if we use "as of" for "date retrieved". --Zolo (talk) 18:45, 8 June 2013 (UTC)
    Domain description amended as proposal below. Filceolaire (talk) 22:23, 9 June 2013 (UTC)
    @Zolo. I am not so sure: for all hard documents you will have a publication date and no contributor will add twice the publication date property with two different dates: he will understand the problem and will look for a better property. For online database there is no publication date so considering the action of adding a data in wikidata as a publication of the data seems for me very strange. But contributors will definitively use point in time (P585) so they will be aware of that property so what is the differentce of point in time (P585) as qualifer and "date retrieved" for sources ? I agree that the sense "date retrieved" is a little better but in the other sense you add a new property leading to more choices and this will increase the number of wrong choices statistically speaking. Snipre (talk) 12:03, 10 June 2013 (UTC)
    I think people will sometimes use point in time (P585) to mean date of publication, especially if it is renamed from "as of" to "date" which seems necessary because "as of" does not really mean "date something took place". Granted, using separate items for metadata about the source itself should make things more manageable, but still I would be surprised if we do not encounter this problem, and I do not think a separate "date retrieved" property would make anything substantially more complex. --Zolo (talk) 15:40, 10 June 2013 (UTC)
    Proposal edited so it doesn't describe the 'date retrieved' as a qualifier. Filceolaire (talk) 21:52, 11 June 2013 (UTC)

    Developed from

       Not done
    DescriptionThe aircraft which formed the basis for this aircraft (most likely can apply to other things, not just aircraft)
    Data typeItem
    Template parameteren:template:Infobox aircraft developed from
    Domainterm
    ExampleAvro Lancaster Q203622 => Q672994 Avro Manchester
    Proposed byDanrok (talk) 18:58, 16 May 2013 (UTC)
    What is it you are asking? Danrok (talk) 20:35, 16 May 2013 (UTC)
    Ups, I misread the description. Would this work for technology in general? Like H-Bomb developed from atomic-bomb? --Tobias1984 (talk) 20:52, 16 May 2013 (UTC)
    H-Bomb developed from atomic-bomb? Probably not, but I'm not a scientist. It might apply to other things like products, for example some new cars are based on older cars, and not always designed from scratch due to the time and expense involved in designing a totally new car. For example, Ford Orion based on Ford Escort (same chassis I believe).Danrok (talk) 13:22, 18 May 2013 (UTC)
    There were properties "derived from" and "based on". --AVRS (talk) 20:25, 18 May 2013 (UTC)

     Not done - discussion ended without any support. --Tobias1984 (talk) 19:24, 24 August 2013 (UTC)

    has member

       Not done
    Descriptionpair property for member of (P463)
    Data typeItem
    Domainorganization
    Allowed valuesorganizations only
    ExampleOpeth (Q18557) => Mikael Åkerfeldt (Q450285)
    Proposed byMicru (talk)
    Discussion

    Motivation: There is no generic property for "members of organizations" only specific ones like P100 (P100), cast member (P161), member of sports team (P54) and member of political party (P102). Eventually this property could be combined with the proposed property "as", providing greater flexibility instead of having to create specific properties every time. Micru (talk) 21:56, 13 August 2013 (UTC)

     Support --Nightwish62 (talk) 22:35, 13 August 2013 (UTC)
     Support good for Template:Constraint:Inverse. Also: At least P100 (P100) will be deleted and replaced with member of (P463). We have too many "member of something" properties.PfD member states. --Tobias1984 (talk) 07:08, 14 August 2013 (UTC)
     Oppose I do not think cast member (P161) should be replaced with a "has member" property (it may be possible to use a more general property than P161 with qualifiers, but am not sure that cast members can really be considered "members" of a movie). member of sports team (P54) and member of political party (P102) can probably be replaced with member of (P463), but not with a "has member" property, as they work the other way around. We could decide that it should be supplemented with the reciprocal "has member" but I do not see much use for that, and I think we should try to avoid properties that require hundreds of values for a single item (the Chinese Communist Party probably has thousands of members in Wikidata...). --Zolo (talk) 07:54, 14 August 2013 (UTC)
    Is your opposition regarding the substitution of p161 only, or also against the creation of the property for other uses? I agree with you and with FelixReimann's comment below that this property should be only for complete lists of members whenever it makes sense.--Micru (talk) 12:19, 14 August 2013 (UTC)
    It is also against other uses. Restricting its use for complete list sounds sort of appealing but I do not think it is realistic and Wikidata's data-structure does not seem to be really suited for that. We can only source and qualify individual statements, not a set of statements using a particular property, so taht we cannt state "this list is complete according to X". Things may become messy if different sources conflict or when the list changes over time. Actually we have rather similar issues with has part(s) (P527). --Zolo (talk) 16:22, 14 August 2013 (UTC)
    Would it be better if I propose a specific property for bands?--Micru (talk) 05:05, 15 August 2013 (UTC)
    If that is really needed, I won't oppose that. But I think querying member of (P463) would work just as fine and would avoid redundancies and the associated maintenance burden. --Zolo (talk) 15:10, 16 August 2013 (UTC)
     Comment To provide an additional value to member of (P463), this property should only be used, if the list of members is complete. Thus, if organization "has member" person is set, person member of (P463)organization must also be set (adding appropriate constraints) but not vice versa. Otherwise, it's just duplication of the same information.  — Felix Reimann (talk) 10:14, 14 August 2013 (UTC)

     Not done more opposition to the idea than support at this time. --Tobias1984 (talk) 19:27, 24 August 2013 (UTC)

    work/Werk

       Done: notable work (P800) (Talk and documentation)
    Descriptionobject's notable scientific work or work of art
    Data typeItem
    Template parameteren:Template:Infobox writer, parameter notableworks
    DomainPerson
    Proposed byŠlomo (talk) 00:47, 8 February 2013 (UTC)
    I think there should be more precise properties. A painter would have the works as simple "creator", an actor of a film or play should be described as "performed in", a producer or director should be described as such. --NaBUru38 (talk) 21:30, 8 February 2013 (UTC)
    Redundant. Freebase automatically add works, if the work has the property "work by ...". This should be possible in Wikidata as well.--Kolja21(talk) 22:49, 13 February 2013 (UTC)
     Comment In that case, we would still need to define the property, I would have thought. Danrok (talk) 03:30, 27 February 2013 (UTC)

     Comment An alternative: opus magnum, or plural: opera magna. Also, the term is: "[...] distinguished in usage from "masterpiece" by a requirement that it is a work on a large scale, and by the absence of a requirement that it is generally regarded as among the creator's most successful works."- Ssolbergj (talk) 03:17, 27 February 2013 (UTC)

     Comment Would that work with living people? Seems to imply the best of a person's lifetime work, in which case it would only apply to non-living people, or am I mistaken? Danrok (talk) 03:38, 27 February 2013 (UTC)
     Comment I don't think it would be wrong to define the most significant work(s) of a person's career so far. But the stronger wording of "opus magnum/opera magna" might encourage people to defineone, or a befittingly small selection of works. A property named Notable works might tempt some people to think that everything that's written on wikipedia could be considered notable. -Ssolbergj (talk) 04:20, 27 February 2013 (UTC)
     Support Danrok (talk) 04:57, 27 February 2013 (UTC)
    • Well, now that I think of it, I  Oppose because the relation should be written in the item on the work, not the creator. --NaBUru38 (talk) 20:37, 1 March 2013 (UTC)
      •  Comment Well, this obviously concerns a select few (or even just one) of the creator's works. Don't you think a centralised list, on the creator's item, would be easier to keep track of? -Ssolbergj (talk) 23:30, 1 March 2013 (UTC)
        • Several works are created by several people. So listing them on the creator's side doesn't reflect that. I know that technically it's possible to follow the proposal, but it seems more reasonably to me to list the authors in items on works. --NaBUru38 (talk) 18:49, 8 March 2013 (UTC)
    •  Support since there is no built-in reciprocal relationship among properties at this point. Espeso (talk) 03:18, 7 March 2013 (UTC)

    ✓ Done John F. Lewis (talk) 00:40, 14 August 2013 (UTC)

    bibliography

       Not done
    Descriptionlink to article with author bibliography
    Data typeItem
    DomainAuthors
    ExampleLeo Tolstoy bibliography is Leo Tolstoy bibliography
    Robot and gadget jobsArticle names are regular, so some automation is possible
    Proposed byEugeneZelenko (talk) 03:16, 11 April 2013 (UTC)

     Oppose When Phase 3 of Wikidata development is complete, we'll be able to generate lists which will make Wikipedia articles that are just lists redundant. Silver hr (talk) 19:45, 26 April 2013 (UTC)

    Wikidata will only be able to generate a bibliography if all the items have wikidata items. Until then there will be bibliographic articles. Filceolaire (talk) 20:37, 14 May 2013 (UTC)

     Support As long as we have bibliographical articles we can use this property to link to them. Filceolaire (talk) 20:37, 14 May 2013 (UTC)

     Comment Maybe also a way to relate the Wikipedia-articles to the Author-namespace in Wikisource? -- Lavallen (block) 11:06, 3 August 2013 (UTC)

     Oppose This will be the results of phase 3 of wikidata: no need of property for that. Just by using a query and the property author with the correct value we will get all documents created by a person.Snipre (talk) 12:00, 6 August 2013 (UTC)

     Not done No consensus John F. Lewis (talk) 00:41, 14 August 2013 (UTC)

    Note: For musicians there is the property discography (P358). --Kolja21 (talk) 02:08, 12 February 2014 (UTC)

    Notable work

       Done: no label (P801) (Talk and documentation)
    DescriptionTitle(s) of notable work(s) (publications, compositions, sculptures, films, etc.) by the subject, if any.
    Data typeItem
    Template parameterw:template:infobox person, w:template:infobox writer Notable
    Domainperson, writer, film director, etc.
    Allowed valuespublications, compositions, sculptures, films, etc.
    Examplew:James Cameron, w:Stephen King, etc
    Sourceinfobox
    Robot and gadget jobs?
    Proposed by Ę-oиė  >>>  ™
    From the most famous of the work I think, like Jurasic Park and ET from Steven Spielberg. Actually this is to accommodate "notable" parameter on infobox person or writer.  Ę-oиė  >>>  ™ 19:37, 18 April 2013 (UTC)
     Comment I'm a bit surprised we don't have this property yet. That said, the fact that the work is notable is assumed, so I think simply "work" would be a better label. Also, it should be noted that this would be an inverse property of a generic 'creator' property for works. Emw (talk) 20:30, 20 April 2013 (UTC)
     Comment - Isn't this just the reverse of the author property? If a film, book, or something is notable, then it is an item on Wikidata and that item is linked with author to the creator. For your example a "director" property for movies might be a better idea. --Tobias1984 (talk) 07:28, 2 May 2013 (UTC)
    Did you click my example for w:James Cameron & w:Stephen King? There is a property fo Notable work on infobox at wp.en. And YES there are have some items (for notable work) that linked to Wikidata. Ę-oиė  >>>  ™ 09:47, 2 May 2013 (UTC)
     Support This can be as a short curated list of notable works for a person. Useful for infoboxes and queries. The list of works might be cluttered with a lot of things that are notable on Wikidata. This property return just a few items for an infobox for example. We do the same curated thing for pictures instead compared to the commons-category. --Tobias1984 (talk) 18:35, 7 August 2013 (UTC)

    ✓ Done John F. Lewis (talk) 00:42, 14 August 2013 (UTC)

    student

       Done: student (P802) (Talk and documentation)
    DescriptionStudent(s) of a person
    Data typeItem
    Template parameter"notable_students" in en:Template:Infobox scientist
    Domainperson
    Allowed valuesperson
    ExampleQ937 (Einstein) => Q87554 (Ernst G. Straus)
    Proposed byJfhutson (talk)
    Discussion

    We have doctoral student, but many other teacher-student relationships are important. Jfhutson (talk) 20:59, 3 May 2013 (UTC)

     Question Wouldn't this work better in the other direction with the student pointing to the teacher? Ostensibly a teacher could have many times more students than students will have teachers, I would think. Joshbaumgartner (talk) 09:18, 9 May 2013 (UTC)

    ✓ Done John F. Lewis (talk) 00:46, 14 August 2013 (UTC)

    Professorship

    Descriptionprofessorship position held by this academic person
    Data typeItem
    Domainperson
    ExampleStephen Hawking Q17714 => Q865664 Lucasian Professor of Mathematics
    SourceCan be sourced here Category:Professorships by subject.
    Proposed byDanrok (talk) 02:31, 18 May 2013 (UTC)
    Discussion

    ✓ Done John F. Lewis (talk) 00:52, 14 August 2013 (UTC)

    academic major (en) / Hauptfach (de)

    Descriptionmajor someone studied at college/university
    Data typeItem
    Domainpeople
    ExampleBarack Obama (Q76): educated at (P69) => Columbia University (Q49088), qualifier "academic major" => political science (Q36442)
    Proposed byKompakt (talk) 09:19, 2 August 2013 (UTC)
    Discussion

    As a qualifier with educated at (P69).--Kompakt (talk) 09:19, 2 August 2013 (UTC)

    •  Support --Nightwish62 (talk) 12:07, 2 August 2013 (UTC)
    •  Comment - What counts as an academic major? How will this be used for university systems that don't distinguish between majors and minors. --Tobias1984 (talk) 12:58, 2 August 2013 (UTC)
      It's your main field of studies. You don't have to add a minor if it doesn't exist in the curriculum, or there's no such explicit destinction. I mean if someone studies computer science, it is "computer science". If someone studies geography, it is "geography". While university systems are different in many countries, any student has a main subject or "major". You could probably rename it to "field of studies" (or German "Studienfach"), but I'm not sure that would be the better naming. The terms "major" and "minor" are used in English-speaking countries, and the corresponding "Hauptfach/Nebenfach" are common in human sciences in Germany as well.--Kompakt (talk) 13:53, 2 August 2013 (UTC)
    •  Comment If we make the major a qualifier of alma mater, then the thesis and title (BSc, MSc, PhD, Dipl.-Ing., ...) should probably be as well. However I'm not sure if in this case it should be the academic major acting as a qualifier of the alma mater instead of the other way around. —Ruud 22:19, 2 August 2013 (UTC)
      You're right, "thesis" that your proposed earlier could become a qualifier here, too. For the title, we do have a property already (academic degree (P512)). Regarding your second point, I think it's basically as broad as it is long. As educated at (P69) is also used with educational institutions in general, like high schools, etc., I'd say it's better to keep that structure.--Kompakt (talk) 07:57, 4 August 2013 (UTC)

    academic minor (en) / Nebenfach (de)

    Descriptionminor someone studied at college/university
    Data typeItem
    Domainpeople
    Examplesame usage as "academic major"
    Proposed byKompakt (talk) 09:19, 2 August 2013 (UTC)
    Discussion

    As a qualifier with educated at (P69).--Kompakt (talk) 09:19, 2 August 2013 (UTC)

    Observer state / beobachterstaat (?) / observateur d'état / государства-наблюдателя / observador de estado

       Not done
    Descriptionstates observing policies and work done by the international organization
    Data typeItem
    Domainsovereign state (country), organization
    Example<Iran>, observer state in the WTO
    SourceExternal reference, lists of memberships
    Proposed byKristian Vangen 08:02, 2 April 2013 (UTC)
     Oppose Property:P100 with qualifiers is doing the job Snipre (talk) 09:45, 2 April 2013 (UTC)
    I see. And when will it become possible to ad qualifiers? --Kristian Vangen 15:24, 2 April 2013 (UTC)
    In some weeks (2-3) Snipre (talk) 18:03, 8 April 2013 (UTC)
     Support, member states are different from observer states. Also, some organizations don't have states as members, so I'd suggest renaming the peroperties to "member" and "observer". --NaBUru38 (talk) 19:08, 18 April 2013 (UTC)
    Support renaming P100 to "member". Weakly support adding a different "observer" property, rather than using a qualifier, as an observer is not really a member. --Zolo (talk) 12:23, 24 April 2013 (UTC)
     Support, the way this is written up though it needs clarification. If it is intended to be a property for claims of a state, then the label should be changed to 'observer of' (as a partner to the existing 'member of' property), and the description should be more clear, such as 'international organization that the subject organization has observer status with' or some such wording.Joshbaumgartner (talk) 10:48, 9 May 2013 (UTC)
     Oppose - P100 (P100) is going to be deleted (Wikidata:Properties_for_deletion#member_states_.28P100.29). It would be better to have a qualifier for member of (P463) that says "type of membership". Example:
    • State A
    • type of membership = observing state (qualifier)
    • start time = 1950 (qualifier)
    • end time = 2004 (qualifier)
    • type of membership = full membership (qualifier)
    • start time = 2004 (qualifier)
    • State B
    • type of membership = full membership (qualifier)
    We should archive this proposal and start a discussion about a qualifier. --Tobias1984 (talk) 11:35, 3 August 2013 (UTC)
    No need for a new property. 'instance of' will work well for this qualifier:
    • State A
    -Filceolaire
    That is another good way of handling it. Any way this property is clearly not needed. --Tobias1984 (talk) 09:11, 18 August 2013 (UTC)

     Not done the discussion revealed a better way of handling this kind of information. --Tobias1984 (talk) 19:37, 24 August 2013 (UTC)

    Place of worship

       Not done
    Descriptionchurch, temple, etc. of an organization
    Data typeItem
    DomainOrganization: parishes, religious congregations
    ExampleThe Church of Gudmundrå would fit as an object in Gudmundrå parish with this property. See: this as an example.
    Proposed bysee Wikidata talk:Property proposal/Place#article about church (or similar)
    I think it could be useful to also have a prperty for an image of the building, for the same purpose as above. In the building-article, the general image-property can be used, but this is for a more specific purpose in the organisation-article. -- Lavallen (block) 08:52, 20 April 2013 (UTC)
    "place of assembly" or "venue" might work as property labels too. I wouldn't mind having several properties though. The image you mention would go on the item about the building. --  Docu at 21:50, 21 April 2013 (UTC)
    Your correct, it's better to add an image-property to the architecture-item. -- Lavallen (block) 07:03, 29 April 2013 (UTC)
    •  Oppose This property seems redundant with part of (P361). If a particular place of worship is part of a secularly-defined or ecclesiastically-defined area, then 'part of' P361 could capture that information. Places of worship within an area could be separated from other parts of an area by having a query select only parts of the area that are an instance of a place of worship. This approach would allow for varying levels of precision, e.g. instances of any given type of venue in any given type of organization, where the type of venue and type of organization are simply query parameters. Emw (talk) 04:08, 25 April 2013 (UTC)
    • My point is that this sort of domain-specific information can be better captured with generic properties. An inverse property of "part of" -- e.g. "has part" -- is easily envisionable, and would capture this information while also putting the part-whole claim on the 'whole' (the organization) rather than the 'part' (the building). Having a proliferation of domain-specific properties will raise the barrier to entry for users trying to learn how to find things. Using fewer, but more expressive, generic properties to capture this information as explained above would allow users find items that match what they're looking for much more easily. Emw (talk) 12:13, 25 April 2013 (UTC)
    • "has part" suggests ownership .. with your suggestion, you'd need a qualifier to define the nature of the part. Essentially, this would lead to two properties being needed for the same. --  Docu  at 05:02, 29 April 2013 (UTC)
    • Huh? How does saying "X has part Y" imply "X owns Y"? I don't see how that's the case. Saying 'China part of Asia' does not imply that Asia "owns" China, nor would 'Asia has part China'. Other relevant examples are at the bottom of Help:Basic_membership_properties: 'has part' would simply swap the subjects and objects of each claim there, and not introduce the implication of ownership between those items. Emw (talk) 11:59, 29 April 2013 (UTC)
    • I see the point of 'has part-property' even if it isn't created yet as far as I understand. But it looks to me like we still need a qualifier-property to describe what kind of part it is! --Lavallen (block) 12:44, 29 April 2013 (UTC)
    • What do you mean, precisely? One interpretation is that we need to know what kind of thing the subject is. That problem is solved by instance of (P31) and subclass of (P279) --having a proliferation of 'part of' properties for each different type of entity is unsustainable. Another interpretation is that we need to know what meaning of "part of" is intended. I think that's a reasonable concern. We likely need better semantics to describe precisely what kind of "part" something is. There's an ongoing discussion about that at Property_talk:P361#Neutrons. Emw(talk) 02:32, 30 April 2013 (UTC)
    • One of my problems with "instance of" is that it does not make sense to translate it. In English it means everything, but in Swedish it means nothing. It sounds like something a politician would say, a nice looking part of semantic, with no substance. But if you tell me that '"has part" "Gudmundrå kyrka" ("instance of" "church")' is correct, it's fine with me. It does not have to be beautifull, it just have to work. And I saw the talk at "Property_talk:P361" yesterday and it feels like centuries I studied predicate logic, so I abstain from participating there. -- Lavallen(block) 05:27, 30 April 2013 (UTC)
    • Your problem with "instance of" seems to be with its colloquial usage, which is indeed often nebulous as you say. However, the instance of (P31) property is based onrdf:type, and thus isn't some meaningless phrase, but rather a fundamental tool for classification recommended for the Semantic Web by the W3C. It's used ontokens (instances) to describe what type (class) they are a member of.Emw (talk) 19:00, 5 May 2013 (UTC)
    Church buildings should have the claim has use (P366) = structure of worship (Q1370598), then all places of worship within an administrative unit can be searched for and found. Same goes for otehr things like cinemas, shopping malls, etc. Danrok (talk) 17:23, 22 May 2013 (UTC)
    The link with the organization was meant to limit it to that organization. --  Docu  at 18:51, 2 June 2013 (UTC)
    OK. This is described as the "church, temple, etc. of an organization". What kind of organization? I can't follow the example because it is Swedish only. Could you give an example which is available in more languages? Danrok (talk) 01:45, 9 June 2013 (UTC)

     Oppose. I think 'part of' can be used to link items to their place of worship. This is used to indicate you are 'part of' a congregation. Filceolaire (talk) 09:10, 18 August 2013 (UTC)  Not done currently no support for creation. --Tobias1984 (talk) 19:39, 24 August 2013 (UTC)

    aircraft insignia image

       Not done
    Descriptionaircraft identification insignia used by an organization
    Data typeCommons media file
    Domainorganization
    ExampleAfghan Air Force -> aircraft insignia image -> Afghan National Army emblem.svg
    Source[:en:List of air forces] contains all current air forces and their roundels
    Robot and gadget jobsCommons Category:Roundels
    Proposed byJoshbaumgartner (talk)

    Roundels are a key identification element for air forces and other military aircraft operators. Most all have one of some form or another. This property would allow the organization to be linked to its roundel(s). Joshbaumgartner (talk)

     Comment Can we find a generic term for the emblem of military unit and to avoid a specific property for the navy, the air force or the ground force ? Snipre (talk) 09:28, 12 May 2013 (UTC)
     Comment A broader property such as 'aircraft insignia image' would be just fine as far as I am concerned. Roundels aren't specific to air forces, other branches may use them as well, and no reason to have separate props for each. Joshbaumgartner (talk) 13:32, 12 May 2013 (UTC)

     Not done --Tobias1984 (talk) 19:40, 24 August 2013 (UTC)

    Opus/Catalogue Number

       Not done
    DescriptionSee w:Catalogues of classical compositions
    Data typeItem
    Domaincreative work/ musical compositions
    ExampleDie Walküre (Q324319) -> WWV 86b
    Robot and gadget jobsIt can be imported from IMSLP
    Proposed by--Micru (talk) 13:47, 15 August 2013 (UTC)
    Discussion

     Support--Micru (talk) 13:47, 15 August 2013 (UTC)

     Not done catalog code (P528) has been extended, so it can be used instead of this property.--Micru (talk) 13:52, 19 August 2013 (UTC)

    arXiv eprint identifier

       Done: arXiv ID (P818) (Talk and documentation)
    DescriptionEprint identifier, without any "arXiv:" prefix. Prior to April 2007, the identifiers included a classification, an optional two-letter subdivision, and a 7-digit YYMMNNN uear, month, and sequence number of submission in that category. E.g. gr-qc/0610068 or math.GT/0309136. After April 2007, the format was changed to a simple YYMM.NNNN.
    Data typeString
    Domainsources
    Allowed valuessee: Understanding the arXiv identifier
    SourceTemplate:Cite arXiv (Q6927043)
    Proposed byMicru (talk)
    Discussion

    Motivation: Needed to import Cite arXiv template. Micru (talk) 19:42, 12 August 2013 (UTC)

    ADS bibcode

       Done: ADS bibcode (P819) (Talk and documentation)
    DescriptionThe document's w:bibcode in the Astrophysics Data System
    Data typeString
    Domainsources
    Example2006PNAS..10312269D.
    SourceTemplate:Cite journal (Q5624899)
    Proposed byMicru (talk)
    Discussion

    Motivation: Needed to import Cite journal template.--Micru (talk) 20:37, 14 August 2013 (UTC)

     Support --Tobias1984 (talk) 08:09, 15 August 2013 (UTC)
     Strong support --Paperoastro (talk) 11:26, 15 August 2013 (UTC)

    arXiv classification

    DescriptionarXiv classification, e.g. hep-th. Optional. To be used only with new-style eprint identifiers, that do not include the classification.
    Data typeString
    Domainsources
    Allowed valuessee: Understanding the arXiv identifier
    Example<A catalogue of multiplicity among bright stellar systems (Q14558831)> arXiv classification <astro-ph>
    SourceTemplate:Cite arXiv (Q6927043)
    Proposed byMicru (talk)
    Discussion

    Motivation: Needed to import Cite arXiv template. Micru (talk) 19:42, 12 August 2013 (UTC)

    Operating system (en) / Betriebssystem (de)/ Système d'exploitation (fr)/ sistema operativo (it)

       Not done
    DescriptionOperating system of the computer
    Data typeItem
    Template parameter"os" in en:template:Infobox information appliance
    Domainterm (computer)
    Allowed valuesfor the future we could think to allow only items with Instance of equal to operating system (Q9135)
    Exampleexample Commodore 64 (Q99775) --- ( os ) ---> KERNAL (Q1362489), Amstrad CPC (Q478829) --- ( os ) ---> AMSDOS (Q577303)
    Robot and gadget jobswe could read "os" value in en:template:Infobox information appliance
    Proposed byLucaBiondi (talk) 11:45, 20 August 2013 (UTC)

    Archiving this. --  Docu  at 18:16, 25 August 2013 (UTC)

    CGNDB Unique Identifier (en) / Identificateur de la BDTC (fr)

    DescriptionThe Identifier the geographical feature of the Geographical Names Board of Canada / Commission de toponymie du Canada, see Geographical Names Board of Canada (Q1896569)
    Data typeString
    Template parameteren:Template:Cite cgndb
    Domainplace
    Allowed values\D{5}
    ExampleRed River of the North (Q156006) --> GAWTC, GBFMO
    Sourcehttp://www4.rncan.gc.ca/search-place-names/name.php
    Proposed byFralambert (talk) 18:06, 4 August 2013 (UTC)
    Discussion

    mascot (en) / Maskottchen (de)

       Done: mascot (P822) (Talk and documentation)
    Descriptionmascot of an organization, e.g. a sports team or university
    Data typeItem
    Template parameter"mascot" in w:Template:Infobox University
    Domainorganization
    ExampleCarnegie Mellon University (Q190080) => Scotty (Q14565326)
    Sourcesee above
    Robot and gadget jobsCould be imported from Wikipedia by a bot.
    Proposed bySchneelocke (talk) 21:39, 12 August 2013 (UTC)
    Discussion
     Support - looks like something we should have. --Tobias1984 (talk) 09:07, 16 August 2013 (UTC)
     Support - I almost proposed this a couple weeks ago, but I instead just supported the more generic nickname property. I think this is something we need anyway. TCN7JM 09:36, 16 August 2013 (UTC)
     Support – does sounds useful. AutomaticStrikeout 15:52, 16 August 2013 (UTC)
     Support --Nightwish62 (talk) 18:37, 24 August 2013 (UTC)

    ✓ Done

    speaker (en) / Sprecher (de)

       Done: speaker (P823) (Talk and documentation)
    Descriptionsomeone who takes a role as speaker in events like keynotes or presentations
    Data typeItem
    Domainevents
    ExampleGoogle I/O 2013 => Larry Page
    Proposed byNightwish62 (talk) 17:56, 30 June 2013 (UTC)
    Discussion
     Support - Also needed for Wikisource [1] = Napoleon. --Tobias1984 (talk) 10:06, 15 August 2013 (UTC)

    ✓ Done --Tobias1984 (talk) 06:38, 26 August 2013 (UTC)

    Meteoritical Bulletin Database ID

    DescriptionID in the meteorite database of the Meteoritical Society
    Data typeString
    Template parameterNot used in meteorite infobox
    Domainterm: meteorites
    ExampleNorthwest Africa 7034 (Q2596468) = http://www.lpi.usra.edu/meteor/metbull.php?code=54831 = 54831
    Format and edit filter validationonly numbers
    Sourcehttp://www.lpi.usra.edu/meteor/
    Proposed by--Tobias1984 (talk) 08:34, 13 August 2013 (UTC)
    Discussion
     Support LucaBiondi (talk) 12:44, 18 August 2013 (UTC)

    ✓ Done --Tobias1984 (talk) 08:08, 26 August 2013 (UTC)

    possible causes / (fr) causes possibles

       Done: has cause (P828) (Talk and documentation)
    Descriptioncauses that might be connected to the medical condition
    Data typeItem
    Template parameternew infobox form French medicine project would be interested in this information
    Domainterm
    Allowed valuesall types of causes
    Examplebone fracture (Q68833) = stress fracture (Q41392)
    Format and edit filter validationtarget item has to be a subclass of injury or medical causes
    Sourcemedical literature
    Robot and gadget jobs?
    Proposed by--Tobias1984 (talk) 14:38, 25 July 2013 (UTC)
    Discussion
    • I guess it depends on the semantics. I like 'possible causes' better, because a property 'causes' to me would suggest that a specific disease is ALWAYS caused by certain causes. In many cases, there are several possibilities, but only some are realized in each case (e.g., blindness can be caused by certain types of accidents or certain genetic predispositions, but hardly every is it caused by both in combination).--Matthiassamwald (talk) 19:43, 5 August 2013 (UTC)

    ✓ Done --Jakob (Scream about the things I've broken) 15:18, 28 August 2013 (UTC)

    OEIS (en)

       Done: OEIS ID (P829) (Talk and documentation)
    DescriptionID in On-Line Encyclopedia of Integer Sequences
    Data typeString
    Domainterm
    ExampleFermat number (Q207264)=>A000215
    Proposed byGZWDer (talk) 09:52, 15 June 2013 (UTC)
    Discussion
     Support --Tobias1984 (talk) 09:08, 5 August 2013 (UTC)
     Support--Micru (talk) 13:33, 20 August 2013 (UTC)
     Support--LucaBiondi (talk) 11:11, 25 August 2013 (UTC)

    ✓ Done --Jakob (Scream about the things I've broken) 15:18, 28 August 2013 (UTC)

    Building developer

     Support standard item in building infoboxes. Shawn in Montreal (talk) 19:48, 28 February 2013 (UTC)

    •  Oppose Missing template. People really shouldn't abandon their proposals. It would be good if all proposers would check their proposals frequently and update information in the template. --Tobias1984 (talk) 17:41, 12 August 2013 (UTC)
     Comment there is no requirement for a property to exist in an infobox, and I have not abandoned this proposal, it is still here. Danrok (talk) 16:54, 28 August 2013 (UTC)
     Comment Also the developer field does exist, as you can see on the Shard page. Danrok (talk) 16:56, 28 August 2013 (UTC)
    All properties need the template filled out as documentation for the talk page. It hasn't been filled out since February, so calling this abandoned seems fitting. --Tobias1984 (talk) 17:22, 28 August 2013 (UTC)
    OK, abandon it. I think developer (P178) can be used for this now. Danrok (talk) 16:01, 29 August 2013 (UTC)

    Not done Snipre (talk) 17:00, 29 August 2013 (UTC)

    stock market index

       Not done
    DescriptionThe stock market index of which this company is a component.
    Data typeItem
    Template parameter"traded_as" in en:Template:Infobox company
    Example 1MISSING
    Example 2MISSING
    Example 3MISSING
    Proposed byDanrok (talk) 23:39, 24 February 2013 (UTC)
    I don´t see that. For example, at en:Apple Inc. there is "Nasdaq", but I would see this as a meta:Wikidata/Notes/Data_model_primer#Qualifiers of the value of the ticker symbol property. And in this example, the ticker symbol is a weblink too. --Goldzahn (talk) 12:32, 25 February 2013 (UTC)
    Nasdaq is an index, not a market. --NaBUru38 (talk) 23:11, 25 February 2013 (UTC)
    en:List of stock market indices, en:List of stock exchanges: NASDAQ provides three indexes, NASDAQ-100 is one of them. Therefore the Infobox shows at "traded_as": en:stock exchange, en:ticker symbol and en:stock market index. Stock exchange and stock market index are items. The ticker symbol is a weblink with an en:anchor text (a string). The weblink is www.nasdaq.com/symbol/aapl and the anchor text is AAPL. What I don´t know is if wikidata weblinks will have an anchor text or not (I can´t see it there) --Goldzahn (talk) 05:37, 26 February 2013 (UTC)

     Comment sorry for the confusion! I was thinking stock market rather than index when I created this, but a property for index (e.g. NASDAQ) would be needed, and market as another property (e.g. NYSE). Danrok (talk) 20:11, 28 February 2013 (UTC)

     Comment NASDAQ is a stock exchange market NASDAQ Danrok (talk) 20:24, 28 February 2013 (UTC)
    I´m afraid that thing is just called "stock exchange market". The category is "Stock exchanges in the United States" and that is why I proposed "stock exchange" below. And in en:Category:Stock exchanges you will find them all. --Goldzahn (talk) 04:59, 1 March 2013 (UTC)
     Comment It is of importance to know about the market a stock is traded in, especialiy the IPO. Everybody can create an index, so banks, newspapers and companies create their own index. Stock on indices are frequently exchanged so what is part of the DAX 100 today is different from what was DAX 100 a year ago and totaly different from what it was 10 years ago. So we need it other way round. We need companies as properties for the index. So you will have to keep up the properties of the index not of the companies.--Giftzwerg 88 (talk) 10:35, 10 March 2013 (UTC)

    Dedicated to

       Done: dedicated to (P825) (Talk and documentation)
    DescriptionPerson to whom the creative work was dedicated
    Data typeItem
    DomainCreative work of any kind
    ExampleDie Walküre (Q324319) => Ludwig II of Bavaria (Q44039)
    Proposed by--Micru (talk) 15:07, 15 August 2013 (UTC)

    ✓ Done--Micru (talk) 14:15, 26 August 2013 (UTC)

    tonality / musical key

       Done: tonality (P826) (Talk and documentation)
    Descriptionthe key of a piece usually refers to the tonic note and chord, which gives a subjective sense of arrival and rest. This property will be used to import w:Category:Compositions_by_key
    Data typeItem
    Domaincreative work/ musical compositions
    Allowed valuessee en:Category:Musical keys;
    ExamplePiano Sonata No. 31 (Q146767) -> A-flat major (Q719309)
    Robot and gadget jobsimport of the category "compositions by key"
    Proposed by--Micru (talk) 04:28, 15 August 2013 (UTC)
    Discussion

    ✓ Done As "tonality / musical key".--Micru (talk) 14:41, 26 August 2013 (UTC)

    BBC identifier (pid)

    DescriptionIdentifier for the corresponding programme on the BBC website. For example the pid for Dr. Who is b006q2x0. It can also be used to retrieve data about that programme from the BBC. It is similar to e.g. the IMDB identifier property.
    Data typeString
    Template parameteren:template:infobox television pid, en:template:infobox pid pid
    Domaintelevision series and radio shows
    Allowed valuesstrings
    ExampleThe Archers <BBC identifier (pid)> b006qpgr
    SourceInfobox Television and Infobox radio show on en.wiki or any equivalent on other Wikipedias
    Proposed byGnarql (talk)
    Comments

    ✓ Done--Micru (talk) 14:58, 26 August 2013 (UTC)

    parent club (en)

       Done: parent club (P831) (Talk and documentation)
    Descriptionparent club of this team
    Data typeItem
    Template parameter"majorleague" and "pastmajorleague" in the MiLB infobox, "affiliations" in the NBADL infobox, ect.
    Domainorganization
    ExampleRochester Red Wings (Q1966948) → Minnesota Twins (Q604879)
    Robot and gadget jobsBots could help with adding this property
    Proposed byTCN7JM 02:53, 7 August 2013 (UTC)
    Discussion

    I believe a property is needed to portray the affiliation of hundreds of teams in minor leagues of sports to their major league affiliates. Past affiliates could be shown using the start and end date qualifiers. TCN7JM 02:53, 7 August 2013 (UTC)

    •  Comment could you expand on the description a little more what "affiliation" encompasses. With such a wording people are going to use it all over Wikidata. How will it work outside of sports? --Tobias1984 (talk) 07:25, 7 August 2013 (UTC)
      Hmm. Perhaps "affiliated with" may not have been the best wording. I think the wording I was really looking for was "parent club". I've changed the title and the description to match this. TCN7JM 11:21, 7 August 2013 (UTC)
    •  Comment Sorry but I think 'Parent club' is much too specific. 'affiliated with' is better. Examples where this can be used outside sport include:
    'Union' affiliated with 'political party'
    'Political action Committee' affiliated with 'political party'
    'local boy scout troop' affiliated with 'local church'
    'Wikimedia UK' affiliated with 'Wikimedia Foundation'
    It is similar to 'member of' but used for links between two organisations and anywhere the relationship is not called 'membership'.
    It is not used for links to things like 'Atheism' or 'Vegetarianism' where there is no formal organisation you can point to. (In those cases use 'instance of' 'atheist' or 'vegetarian'.) Filceolaire (talk) 15:30, 18 August 2013 (UTC)
    I mainly proposed this property with sports clubs in mind. I'm not sure how to make the proposal less biased towards sports, but if you would like to, go right ahead. TCN7JM 15:38, 18 August 2013 (UTC)
     Comment we have parent company already, we also need to cover parent agencies, for organizations like government agencies. What about parent organization for non-companies? Danrok (talk) 15:07, 28 August 2013 (UTC)
    That won't work. Any Major League Baseball teams and all of it's minor league affiliates are in the same organization, so that term is too ambiguous. TCN7JM 22:05, 28 August 2013 (UTC)
     Support I'm happy to take your word for it. Danrok (talk) 02:31, 29 August 2013 (UTC)

    political color (en) / politische Farbe (de)

       Not done
    DescriptionColor(s) used to represent a political party or movement
    Data typeItem
    Template parameter"colors" in w:en:Template:Infobox political party
    Domainorganization
    ExampleWhig Party (Q42183) => [ blue (Q1088), buff (Q2085487) ]
    Sourcehttps://en.wikipedia.org/wiki/Political_colour
    Proposed bySchneelocke (talk) 16:15, 12 August 2013 (UTC)
    Discussion
     Question - the template says string but your example links to 2 items. --Tobias1984 (talk) 18:42, 12 August 2013 (UTC)
    Oh, yes, good catch! I've changed it to "item". -- Schneelocke (talk) 21:40, 12 August 2013 (UTC)
     Support standard piece of information. But it could be argued that for a political party we could also use the normal color property. --Tobias1984 (talk) 16:00, 16 August 2013 (UTC)
     Question Yes, couldn't we just use the normal color property? AutomaticStrikeout 16:48, 16 August 2013 (UTC)

    interchange (transfer) / пересадка

    Descriptionstation to which you can transfer from this station
    Data typeItem
    Domaintrain stations
    ExampleBiblioteka Imeni Lenina (station of Sokolnicheskaya line) has interchange to Alexandrovsky Sad (station of Filyovskaya line) in Moscow metro.
    Proposed byEnzet (talk) 18:09, 1 April 2013 (UTC)
    •  Comment I think, it can be used mostly for Underground (Metro) stations, not proper railway stations.--Ahonc (talk) 15:08, 22 May 2013 (UTC)
    •  Support For all types of rail stations, and all types of interchange stations (inside and out). We should think about connected/near bus stations as well. Perhaps these should also be listed, and use a qualifier to indicate the type of station; bus, metro train, tram, etc. Danrok (talk) 15:28, 22 May 2013 (UTC)
      • The problem is how to determine what is transfer between 2 different types of transport. For example, can we think that there is transfer if there are about 100 meters between transfering stations? --Emaus (talk) 21:59, 13 July 2013 (UTC)
    This can be sourced, to some extent at least. See here for cited OSIs for Euston station. Danrok (talk) 02:45, 27 August 2013 (UTC)
     Comment this has been created now, but may need a time (duration) qualifier in the future, that indicates how long the passenger has to get to the next station without being charged extra. Danrok (talk) 01:55, 30 August 2013 (UTC)

    inspired by / прототип

       Not done
    Descriptionperson inspired fictional person
    Data typeItem
    Domainfictional persons
    ExampleSherlock Holmes inspired by Joseph Bell
    Proposed byEugeneZelenko (talk)
    Discussion

     Not done based on (P144) has been renamed to cover "inspired by" too.--Micru (talk) 14:09, 26 August 2013 (UTC)


    public holiday's (en) / feriados (pt)

    Descriptionpublic holiday's that occur in some place (country, city...)
    Data typeItem
    Domainevent
    Allowed valuesplace
    ExamplePortugal (Q45) => Portugal Day (Q183563)
    Proposed bySarilho1 (talk) 21:36, 14 August 2013 (UTC)
    Discussion

    Qualifiers could be use to describe when the public holiday is celebrated, except for mobile festivities (like: Easter) - Sarilho1 (talk) 21:36, 14 August 2013 (UTC)

    I'm sorry, it wasn't supposed to use string datatype but item datatype, I'll change. The exception that I was talking about was the time qualifier for mobile festivities. Because they are mobile, we can't say when they are celebrated. - Sarilho1 (talk) 13:49, 15 August 2013 (UTC)
    This property will link to all public holidays celebrated in a place but doesn't identify which holiday is the particular holiday associated with that place. Most countries have a particular holiday they identify as their national holiday (July 4 in the USA, St Patricks day in Ireland). In some countries every village has their own special day. Should we just have a qualifier for the "type" of holiday? Filceolaire (talk) 20:17, 15 August 2013 (UTC)
    I suppose we could have qualifier 'instance of' 'national holiday'; 'local holiday'; 'public holiday'; 'bank holiday'. Filceolaire (talk) 20:30, 15 August 2013 (UTC)
    Normally, in the item's page it should have a statement saying where it is celebrated (symmetrical property), so there won't be lack of information. Anyway, I think it could be used a qualifier to do it, if needed. - Sarilho1 (talk) 20:55, 15 August 2013 (UTC)

    festivity taking place in administrative unit

       Not done
    Descriptionfestivity that takes place in the administrative unit
    Data typeItem
    Domainplace
    ExampleValencia (Q8818) => Falles (Q1143768), Portugal (Q45) => Portugal Day (Q183563)
    Proposed byMicru (talk)
    Discussion

     Support It might be easier than the public holiday suggested above, because the celebration item could contain the claim "instance of:public holiday". Micru (talk) 18:11, 16 August 2013 (UTC)

    Aren't you making it even more complicated now? National Day of Sweden (Q1348730) is a banking day in Sweden, it has official recognition, but it is not celebrated to any recognized degree, if you do not happen to be at a place the royal family is visiting at that very day. I think more people are celebrating May 17 or July 4 in Sweden than June 6. -- Lavallentalk(block) 18:44, 16 August 2013 (UTC)
    I guess we are talking about official celebrations, that must be confirmed, probably, by a constitution. So, I prefer my propose, because we can say which holidays have place in some location, including internationals celebrations, like Christmas. - Sarilho1 (talk) 18:52, 16 August 2013 (UTC)
    We have items like Christmas in Japan, why not try to do something around them? -- Lavallentalk(block) 19:11, 16 August 2013 (UTC)
    That's the problem. It's a unofficial celebration, so these property become useless. In all over the world there are celebrated unofficial public holidays. If we want to use this property, we just can use it to official celebrations. - Sarilho1 (talk) 20:42, 16 August 2013 (UTC)
    All celebrations are unofficial, even Christmas in the country I live. If you are working on these holidays or not is a matter between the employer and employee. (Except for banks who follow special rules.) From my point of view, any kind of item can be attached to this kind of property, even "Ramadan in Greenland". Then you can add "instance of public holiday" or not to any of those items together with other properties describing their importance. -- Lavallentalk(block) 12:24, 17 August 2013 (UTC)
    I have removed the official recognition requirement and I have changed it to "festivity" which is more general. Better now?--Micru (talk) 05:46, 17 August 2013 (UTC)

     Support Doostdar (talk) 12:02, 18 August 2013 (UTC)

    • The label "festivity taking place in administrative unit" .. compared to "public holiday's (en) / feriados (pt)" in the previous proposal: I think this goes in the right direction, though, I'm not sure if either label is ideal. Maybe "Holiday/festivity in administrative unit". Note "public holidays" could also have been used on the item of the holiday itself. Maybe it's better to have a distinct property for that. --  Docu  at 07:13, 24 August 2013 (UTC)
     Oppose in the current format: administrative item are already full of statements. Better add a property in the festivity items saying in which country it is an official celebration. Snipre (talk) 11:45, 24 August 2013 (UTC)
     Oppose as per Snipre. Danrok (talk) 22:13, 27 August 2013 (UTC)
    I don't think this is necessarily limited to countries. Some public holidays are more local. Possibly lists at countries or other administrative units may be more concise/easier to maintain. --  Docu  at 22:15, 27 August 2013 (UTC)
    Note that we have public holiday proposed above this one. Festivities may be a bit problematic, unlike public holidays, there is not necessarily an official list. To me, a festivity is just about any festival-type event. Even small admin units can have many of those, especially when looked at historically. Danrok (talk) 00:13, 28 August 2013 (UTC)
    Ok. Let's go with the previous property. Would you create it? --  Docu  at 06:21, 28 August 2013 (UTC)
     Oppose This should go the other way around, in my opinion; also per Danrok. --Rschen7754 08:22, 28 August 2013 (UTC)
     Oppose. Use the Public Holiday property above with an instance of (P31) qualifier to indicate what type of holiday in a place. Filceolaire (talk) 09:48, 28 August 2013 (UTC)

     Not done As per comments.--Micru (talk) 15:11, 28 August 2013 (UTC)

    XPath (en)

       Not done
    DescriptionNavigational description for automatic extraction of a specific part of a HTML or XML page, used for further analysis.
    Data typeString
    Template parameternot applicable
    DomainPart of a reference for automatic verification for any type of entity.
    Allowed valuesString according to the XPath specification.
    ExamplePlease check examples at XPath.
    Format and edit filter validationIt is possible to verify Xpath-statements with a regex, but it will be rather complex.
    SourceExternal reference, usually as a URI (that is an existence of an URI is a prerequisite for use of this property)
    Robot and gadget jobsThis property will be used for a planned extension, but can also be used by gadgets or bots. The extension will only act on this property if it is part of reference for a statement.
    Proposed byJeblad (talk) 15:59, 21 June 2013 (UTC)
    Discussion

    The intended behavior is to follow Wikidata:Property_proposal/Pending#URL/Website to the site, get the content and then optionally extract a fragment of content with an Xpath-statement, and then check if Property:P387 (quote) can be found within this content. If there is no quote available the check is against the actual value in the statement, and then the match must be more accurate.

    It can work together with other parts of a reference to automate verification of a statement, but only the previous two are planned for inclusion in an extension. It should be possible to use it as an ordinary property, even without the extension, and it should be possible to write gadgets that does the same thing as the extension, but they will make the perceived speed of the site significantly slower.

    This property does not need to be available before some time, that is the URL property must be available for this property to be usable. Jeblad (talk) 15:59, 21 June 2013 (UTC)

    Art-name (zh:号)

       Not done
    Descriptionsee en:Art-name.
    Data typeString
    Domainperson
    Example 1MISSING
    Example 2MISSING
    Example 3MISSING
    Proposed byGZWDer (talk) 11:35, 28 May 2013 (UTC)
    Discussion
     Support After reading en:Art-name, it seems relevant.--Micru (talk) 01:34, 8 July 2013 (UTC)
     Support.--Qiyue2001 (talk) 11:29, 29 July 2013 (UTC)
     Oppose template is missing examples. --Tobias1984 (talk) 12:35, 4 August 2013 (UTC)
     Oppose Shouldn't we use pseudonym (P742) with qualifier 'instance of' 'Art name'? Filceolaire (talk) 10:45, 17 August 2013 (UTC)
     Oppose use pseudonym (P742) Snipre (talk) 11:17, 1 September 2013 (UTC)

     Not done - No consensus for creation. --Jakob (Scream about the things I've broken) 16:05, 1 September 2013 (UTC)

    premiere (place)

       Not done
    Descriptionplace of the premiere (of an opera, musical, film...)
    Data typeItem
    Domainopera, musical, film...
    Example 1MISSING
    Example 2MISSING
    Example 3MISSING
    Proposed byAppo92 (talk) 15:15, 7 February 2013 (UTC)
    Discussion
     Comment yes, I think it is essentially the same thing. Danrok (talk) 23:58, 4 March 2013 (UTC)
    •  Question "Place" is a bit generic. There's "theater" / "city" / "country"... --FA2010 (talk) 21:49, 15 March 2013 (UTC)
    •  Question "premiere" is ambiguous. Every new production of an old opera has its "premiere". What is probably meant is "world premiere". (E. g. in German: "Premiere" as opossed to "Uraufführung") --FA2010 (talk) 21:51, 15 March 2013 (UTC)
    • For films, for example, there may be a world premiere at one festival such as Cannes or Venice followed by a notable North American premiere at Toronto or Sundance, and so on. And of course a film festival premiere often precedes a theatrical premiere, when the film opens commercially, in wider release. Could we have qualifiers so that all such notable premieres could be entered? Shawn in Montreal (talk) 15:46, 5 April 2013 (UTC)
     Support It would be better to combine the premiere date and premier place into one property with the other one being the qualifier.

    Item: Movie Name 

       Statement: Premiere place = Club, Event, Etc (This could be the same for movies)
       Qualifier: Premiere date = YYYYMMDD
       Qualifier: country = USA

    --Napoleon.tan (talk) 12:42, 30 April 2013 (UTC)

     Comment I am thinking that things like like this could be covered using a key event property which could have a qualifier called event type, and further date and place qualifiers. Danrok (talk) 15:42, 23 May 2013 (UTC)
    Key event=> Premiere; qualifiers - location, date. Filceolaire (talk) 21:01, 20 August 2013 (UTC)

    Previous name of - later name of / transformed from - transformed to / period of existence of (en)

       Not done
    Descriptionsubject which were renamed, rebranded, repurposed, transformed (including fusion or division)
    Data typeItem
    Template parametermaybe "před 1" a "po 1" from cs:Šablona:Infobox zaniklý stát as an example for vanished states
    Domainprimarily organization (including administrative units), eventually place, person, work, term etc.
    Allowed valuestype of the linked item should be generally identic with the affected item (but there are exceptions, e. g. organization as successor of a person)
    Exampleexamples:
    Sourceinvividually (solution of interwiki conflicts)
    Robot and gadget jobsfilter types of existing interwiki conflicts
    Proposed byŠJů (talk) 17:01, 3 August 2013 (UTC)
    Discussion
    Generally, most of such cases can be treated using followed and preceded by. However, the property should distinguish whether the pretended/followed subject is identic (somethink like "also known as"), transformed or quite different.
    No, if you add start time (P580) and end time (P582) you can sort by the date. Snipre (talk) 10:10, 18 August 2013 (UTC)


     Not done --Nightwish62 (talk) 22:52, 1 September 2013 (UTC)

    IMO number (en)

       Not done
    DescriptionInternational Maritime Organisation allocated number, remains unchanged throughout life of ship (regardless of renaming).
    Data typeString
    Template parameterInfobox ship under field ship identification
    DomainApplies solely to larger ships
    Allowed valuesSeven digit number only
    ExampleMoonlight II (Q4738728), Queen Elizabeth 2 (Q1333553)
    Format and edit filter validation7 digit number can be validated with edit filter Special:AbuseFilter/17
    SourceExternal reference, Wikipedia list article (either infobox or source)
    Proposed byNick (talk) 23:49, 1 September 2013 (UTC)
    Discussion
     duplicate see IMO ship number (P458) --Tobias1984 (talk) 07:08, 2 September 2013 (UTC)
     Not done per Tobias1984. --Ricordisamoa 08:07, 2 September 2013 (UTC)

    date of stable version (en) / Datum der stabilen Version (de)

       Not done
    Descriptiondate when the stable version is released.
    Data typePoint in time
    Template parameter"latest release date" in en:Template:Infobox_software
    DomainProducts and services (incl. software products)
    ExampleInksape stable version date 2012-12-17
    Proposed byNobelium (talk) 21:15, 20 August 2013 (UTC)
    See if significant event (P793) can do the same job ? Snipre (talk) 21:21, 20 August 2013 (UTC)
    I doubt that it is clear what the key event of (in particular) software is. That might be initial release, latest release, latest stable release or something else. --Nobelium (talk) 21:35, 20 August 2013 (UTC)
    'Key event' for software is any of the above. Each are key events and can be described using the 'key event' property. Filceolaire (talk) 23:23, 20 August 2013 (UTC)
    I think publication date (P577) would work as a qualifier for software version identifier (P348). --Izno (talk) 22:17, 20 August 2013 (UTC)
    @Nobelium Please look at the talk page of significant event (P793) to understand the concept behind significant event (P793).Snipre (talk) 09:37, 22 August 2013 (UTC)
    Hu, now (I think) I understand the system. Thank you very much :)
    Just two remaining questions: 1) May I reject/close the proposal 2) publication date (P577) or point in time (P585) as qualifier? --Nobelium (talk) 19:17, 22 August 2013 (UTC)
    So we add publication date (P577) to the list Products and services (incl. software products) so nobody will suggest such a property again? Sorry, if I don't understand the system :( --Nobelium (talk) 22:30, 21 August 2013 (UTC)

     Not done --Tobias1984 (talk) 14:49, 2 September 2013 (UTC)

    BioLib

    DescriptionBioLib is an international encyclopedia of plants, fungi and animals.
    Data typeString
    Template parameterw:Template:Taxon, w:Template:TaxonIds
    Domainterm / taxon
    Example138591
    Robot and gadget jobsImport from all templates and infoboxes
    Proposed by--Micru (talk) 13:08, 15 August 2013 (UTC)
    Discussion
     Support LucaBiondi (talk) 12:34, 18 August 2013 (UTC)
     Support Liné1 (talk) 14:51, 23 August 2013 (UTC)
     Support Danrok (talk) 18:29, 29 August 2013 (UTC)

    ✓ Done - Unanimous support for creation. --Jakob (Scream about the things I've broken) 14:58, 3 September 2013 (UTC)

    Encyclopedia of Life (EOL)

    Descriptionfree, online collaborative encyclopedia intended to document all of the 1.9 million living species known to science.
    Data typeString
    Template parameterw:Template:Taxon, w:Template:EOL, w:Template:TaxonIds
    Domainterm / taxon
    Example1044544
    Sourceapi
    Robot and gadget jobsImport from all templates and infoboxes
    Proposed by--Micru (talk) 13:08, 15 August 2013 (UTC)
    Discussion
     Support --Tobias1984 (talk) 15:14, 15 August 2013 (UTC)
     Support LucaBiondi (talk) 12:30, 18 August 2013 (UTC)
     Support Liné1 (talk) 14:44, 23 August 2013 (UTC)
     Support Danrok (talk) 17:38, 27 August 2013 (UTC)

    Train Depot / /

       Done: train depot (P834) (Talk and documentation)
    DescriptionWhere do they park the railway cars. Name of traction maintenance depot(s) of rail line.
    Data typeItem
    Template parameterTemplate:Infobox_rail_line
    Domainplace
    Sourceinfobox
    Proposed byMange01 (talk) 21:16, 13 March 2013 (UTC)

    Proposal copied to new template layout by Danrok (talk) 18:24, 30 August 2013 (UTC)

    Discussion
    •  Oppose Not every line have its depot. One depot may serve differnt lines, and also one line can be served by different depots.--Ahonc (talk) 12:34, 15 May 2013 (UTC)
    Why would that disallow this property? Danrok (talk) 00:03, 25 May 2013 (UTC)

     Support Sounds good such data is important for lines also for metro lines. --Base (talk) 12:53, 28 June 2013 (UTC)

    GSS code (2011)

    DescriptionUK Government Statistical Service code, a fixed length code of nine characters, new codes introduced in 2011 known as GSS code replaces older ONS code
    Data typeString
    Template parameteren:template:infobox settlement see Metropolitan Borough of Bolton infobox, shown in use there.
    Domainplace
    Allowed values9 chars
    ExampleQ1364541 => E08000001
    SourceONS coding system
    Proposed byDanrok (talk) 22:49, 19 May 2013 (UTC)
    Discussion

    feast (en) / fête (fr)

       Done: feast day (P841) (Talk and documentation)
    DescriptionSaint's principal feast day
    Data typeItem
    Template parameter"feast_day" in en:Template:Infobox saint
    Domainperson
    Allowed valuesday
    ExampleSaint Patrick (Q165479) => March 17 (Q2419)
    Proposed byAyack (talk) 17:50, 26 August 2013 (UTC)
    Discussion

    day in year for periodic occurrence

    Descriptionto define when a specific holiday or periodic event occurs. Can be used as property or qualifier
    Data typeItem
    Allowed valuesitems allowing calculation of date, such as en:Category:Days of the year or more specific ones that might still need creation, e.g. first Sunday in May (Q14582865)
    Example
    It's just maths, which can be coded in programs. Here's the some formula for working out the date for Easter: Calculating the Date of Easter. It would be bad practice to look up a date in a data table, when it can be calculated. Calculating it means the answer can always be found - not possible with data because time is endless and data isn't. Danrok (talk) 12:10, 31 August 2013 (UTC)
    I think it may still be worth storing the definitions here. For Easter Monday (Q209663), http://search.cpan.org/~sbeck/Date-Manip-6.40/lib/Date/Manip/Examples.pod might give 0:0:0:0:0:0:0*EASTER,ND1. --  Docu  at 12:18, 31 August 2013 (UTC)
    We have items for each day of the year. We have items for each day of the arabic year (and articles for these in Arabic and Farsi). We need to create articles for "first sunday in May" and all the other similar days. These should have properties specifying the day of the week and the earliest and latest day of the year. That should define them.
    We also need items for all the days from Mardi Gras to Easter Monday, whose timing is tied to Easter, each with a statement of how many days before Easter Sunday they should be. For the timing of Easter Sunday we need an item for the 'Spring Equinox', an item for the 'first Full moon after the spring equinox' and Easter is the Sunday after that.Filceolaire (talk) 21:18, 31 August 2013 (UTC)
    • "We need to create articles for "first sunday in May" and all the other similar days.": Agree, let's create them when needed.
      "These should have properties specifying the day of the week and the earliest and latest day of the year.": Not sure about this. I think either we should defined the frequency in a standardized format (e.g. "1*5:1:7" mentioned above) or leave it to parsing the label "First Sunday in May".
      For Easter related days occurrences, it would be good to have items such as "Easter + 10 days". --  Docu  at 21:01, 1 September 2013 (UTC)

    International Music Score Library Project ID (IMSLP)

       Done: IMSLP ID (P839) (Talk and documentation)
    DescriptionThe w:International Music Score Library Project (IMSLP), also known as the Petrucci Music Library after publisher Ottaviano Petrucci, is a project for the creation of a virtual library of public domain music scores, based on the wiki principle.
    Data typeItem
    Domaincreative work/ musical compositions
    ExampleDie Walküre (Q324319) -> Die Walküre, WWV 86B (Wagner, Richard)
    Robot and gadget jobsimport w:Template:IMSLP2 and w:Template:IMSLP
    Proposed by--Micru (talk) 13:43, 15 August 2013 (UTC)
    Discussion

    ✓ Done--Micru (talk) 18:51, 3 September 2013 (UTC)

    has subitem / subitem of

       Not done
    DescriptionProperties to connect items spawned from a main item
    Data typeItem
    Template parameterIt would import articles connected with Template:Main (Q6797933)
    Domainmeta
    Allowed valuesitems
    ExampleWilliam Shakespeare (Q692) <has subitem/subitem of> Shakespeare's life (Q8018307), or Finland (Q33) <has subitem/subitem of> history of Finland (Q202808)
    SourceWikipedias
    Robot and gadget jobsit would require a bot importer
    Proposed byMicru (talk)
    Discussion

    Motivation: Some items don't have meaning on their own because they are extensions of a main item. They are usually connected in Wikipedia using Template:Main (Q6797933). I was wondering if it would make sense to reproduce this kind of relationship in Wikidata like William Shakespeare (Q692) <has subitem/subitem of> Shakespeare's life (Q8018307), or Finland (Q33) <has subitem/subitem of> history of Finland (Q202808). Micru (talk) 23:21, 13 August 2013 (UTC)

    •  Support  – The preceding unsigned comment was added by King jakob c 2 (talk • contribs).
    •  Oppose the connection is in my opinion so general, that we might as well not make it. I don't think anybody is going to query something like "I want to know all subitems that can be assigned to William Shakespeare (Q692)" --Tobias1984 (talk) 05:56, 14 August 2013 (UTC)
      Not that query, but for instance it might be useful for visualizers (like Reasonator), to show which other items contain links to useful Wikipedia articles or connections to related Commons categories.--Micru (talk) 12:14, 14 August 2013 (UTC)
      There is a relation between these items which we should represent, especially as some WPs will include the subitem information in the main article, instead of making it a separate article. This property seems a good way to represent this relation. If, for instance, all economic statistics are on the 'economy of' subitem page. Filceolaire (talk) 03:44, 15 August 2013 (UTC)
    •  Oppose The relation is based on particular articles of some wikipedias and are not an universal relation: we have to avoid to import specific classification of some wikipedias in wikidata. 141.6.11.14 10:11, 14 August 2013 (UTC)
      history of the United States (Q131110) has 57 language versions. I wouldn't call that "a specific classification"...--Micru (talk) 12:14, 14 August 2013 (UTC)
      Wouah, an example and you do a general case. How many country articles follow this rule ? And if you wait 10 years you will get a History of the economy in US article. There is the category tool in wikipedia to solve this problem and this is the best tool because this tool is specific to each wikipedia as the splitting of subjects between the different articles. Snipre (talk) 12:57, 15 August 2013 (UTC)
      There are many more examples and I'm sure you are able to find them too. It doesn't matter if the item divisions are specific to a language, you can do the query for the langugage you are interested in, and then you get the articles related. Another option could be to use "main topic" to describe orphan items.--Micru (talk) 17:27, 15 August 2013 (UTC)
      Yes, there are many examples but I know the reasons of the creation of the existence of articles like History of XXX: this is just because of the main article of XXX was too long and splitting the article in different new articles for readability reasons. But this is completly arbitrary and dependent on the policy of each wikipedia. And finally what is the criterion to allow the link with the property has subitem / subitem of ? Can I create a link World war II has subitem Adolf Hitler ? There is a strong connection, I hope you agree. And know can I link Catholic church has subitem Galileo ? The Galileo case is strongly connected to Catholic church. Washington DC has subitem George Washington ? And for Russia has subitem Catherine The Great ? Italia has subitem pizza ? There is no limits so this will be a mess because you can through this property link what you want if you think there is a connection. Snipre (talk) 12:30, 24 August 2013 (UTC)
      Snipre: In 10 years the categories will have been replaced by wikidata queries because the category tool is much too blunt an instrument. Our job is to come up with a way of classifying the various items and wikipedia pages so the wikidata query tool can find what the user is looking for. This property will be useful in establishing the link between these pages. If you can think of a better way to describe the relationship between these pages then please feel free to do so. For example we could rename "Main Category topic" to "Main topic" - see comment by Micru above. Would you prefer that? Personally I prefer the current proposal. Filceolaire (talk) 17:43, 15 August 2013 (UTC)
    •  Support Filceolaire (talk) 03:44, 15 August 2013 (UTC)
    • As a note, this was discussed at Wikidata:Property proposal/Archive/7#Subitem. --Izno (talk) 23:32, 19 August 2013 (UTC)
    •  Oppose it probably good to not turn the semantic direction around in the middle of the tree. --Tobias1984 (talk) 19:29, 24 August 2013 (UTC)

    Alternative: subject headings

    Since there is no consensus and it was already discussed before I have marked it as "not done", could you please take a look to subject headings as an alternative? --Micru (talk) 14:07, 26 August 2013 (UTC)

    Paleobiology Database identifier (PaleoDB)

    DescriptionThe w:Paleobiology Database is an online resource for information on the distribution and classification of fossil animals, plants, and microorganisms.
    Data typeString
    Template parameterw:Template:Taxon, w:Template:TaxonIds
    Domainterm / taxon
    Example40565
    Proposed by--Micru (talk) 13:08, 15 August 2013 (UTC)
    Discussion
     Support Liné1 (talk) 14:50, 23 August 2013 (UTC)
     Support --Tobias1984 (talk) 09:31, 6 September 2013 (UTC)

    ✓ Done --Tobias1984 (talk) 09:41, 6 September 2013 (UTC)

    INEI municipality code or Peruvian municipality code

       Done: UBIGEO code (P844) (Talk and documentation)
    Descriptioncoding system for the identification of geographical locations in Peru. Used for the regions, provinces and districts of Peru. Maintained by (INEI) the National Institute of Statistics and Informatics of Peru
    Data typeString
    Template parameter"ubigeo" in en:template:Infobox Peru region, "ubigeo" in en:template:Infobox Province Peru and "blank_info_sec1" in en:template:Infobox district
    Domainall regions, provinces and districts of Peru.
    Allowed valuestwo, four or six digits including leading zeros
    ExampleCusco region: ’08’, Cusco province: ’0801’ and Cusco district: ’080101’
    Source[2], en:UBIGEO
    Proposed by--AgainErick.
    Discussion

    Naming the property as 'Peruvian municipality code' same as in German district key (Property:P440) for Germany or 'INEI municipality code' as in INSEE (Property:P374) for France. --AgainErick.

    SIRUTA (en) / SIRUTA (ro)

       Done: SIRUTA code (P843) (Talk and documentation)
    Descriptionro:SIRUTA is the Romanian National code for settlements (villages, cities, communes and villages)
    Data typeString
    Template parameter"cod_clasificare" in ro:Format:Infocaseta Așezare
    Domainplaces in Romania
    Allowed valuesfrom 2 to 6 digits: \d{2,6}
    Example
    SourceINSSE: [3] (the link is not always functional)
    Proposed byStrainu (talk) 22:57, 21 June 2013 (UTC)
    Discussion
    Good point. I updated the proposal. --  Docu  at 22:09, 27 August 2013 (UTC)


    Overpass Permanent ID / Overpass Permanenter Identifikator / ? / ? / ?

       Not done
    DescriptionA overpass-api query on the openstreetmap data to find the specified object.
    Data typeString
    Domainplace
    Allowed valuesa valid overpass query
    Example
      • Bode Museum (Q157825) → [bbox:52.49675239781482,13.342037200927734,52.545147384258826,13.444244384765625];(relation["tourism"="museum"]["name"="Bode-Museum"]);(._;>;);out body; → Result
      • Riverside (Q1925824) → [bbox:41.475639,-91.590176,41.504808,-91.518745];(relation["name"="Riverside"]["place"="city"]);(._;>;);out body; → Result
    Proposed byShisma (talk)

    We already have OpenStreetMap relation ID (P402). While it is much more easy to handle, it can only point to a specific type of object in openstreetmap (Relation). Also internal IDs within opensteetmapare not intended to be linked on as they are not stable links to semantical objects. IDs may be replaced in osm if the objects are refined. A very common way to query openstreetmap data is the so called Overpass API using Permanent IDs which is, in fact a query (and not an ID). But since openstreetmap data is in permanent flow, this is also a more stable way to get data from osm. Don't get me wrong: I still want to keep OpenStreetMap relation ID (P402) because I think its simpler and in many cases its stable enough for entities like countries or buildings. But the Permanent-ID is more established and recommended by the openstreetmap community.


    overpass-turbo.eu provides a nice interface to experiment with. any questions? opinions?--Shisma (talk) 09:49, 12 August 2013 (UTC)

    • [bbox:52.49675239781482,13.342037200927734,52.545147384258826,13.444244384765625];(relation["tourism"="museum"]["name"="Bode-Museum"]);(._;>;);out body;
      looks more like a two sets of coordinates and a name than an ID. Don't they have anything shorter? --  Docu  at 11:43, 12 August 2013 (UTC)
    Instead of filtering by an (arbitrary) bounding box, one could also use administrative boundaries as a criterion: area["name"="Berlin"]["admin_level"=4];(relation["tourism"="museum"]["name"="Bode-Museum"](area));(._;>;);out body; link. --Tyr (talk) 12:57, 12 August 2013 (UTC)

    or filter by surrounding landmarks area["name"="Museumsinsel"];(relation["name"="Bode-Museum"](area));(._;>;);out body; = something called "Bode-Museum" on something called "Museum Island (Q151963)" --Shisma (talk) 13:33, 12 August 2013 (UTC)

    •  Support If this is the way OSM prefers we access their info (rather than linking to relations) then we should certainly have this property.
      • Can you give an example of a boundary map for a country or city? We really need to start adding these to wikidata.
      • Should we change the datatype to URL? We should have that datatype enabled sometime this month.
        • IMHO it should not be a URL, but the query string only. The overpass-API is a public, but again in some way resource restricted service. It's easy to build the complete URL from the query String by prepending the overpass-apis entrypoint, but it's easy to exchange the concrete overpass-server if it's necessary in the future (e.g. to point to a wikimedia-server running overpass instead). Even today there are two overpass servers online. --Jongleur1983 (talk) 16:40, 12 August 2013 (UTC)
      • How does this work with WikiMiniAtlas? It would be great to be able to link to a boundary map in WikiMiniAtlas from a Wikipedia infobox item imported from Wikidata. Filceolaire (talk) 16:09, 12 August 2013 (UTC)
      • Do we have an trace that this is "the way OSM prefers we access"? --  Docu  at 14:03, 15 August 2013 (UTC)
    • If the main effect of this is to add boundry boxes to wikidata, we might was well wait for suggested datatype for these. In the meantime, existing coordinates can be used to query OSM. OSM might also want to add our stable Q numbers on their side. --  Docu  at 14:03, 15 August 2013 (UTC)

    date of retirement (en) / Pensionierungsdatum (de)

       Not done
    Descriptiondate on which the subject retired from their job
    Data typePoint in time
    Domainperson
    ExampleDavid Poole (Q5238647) => 1991
    Proposed by82.83.144.130 17:15, 9 August 2013 (UTC)
    Discussion
    To end an occupation and being retired is not always the same thing. -- Lavallentalk(block) 17:00, 25 August 2013 (UTC)
    Key event can cover this. No new property required. Filceolaire (talk) 04:17, 28 August 2013 (UTC)
    •  Oppose in favour of end date as a qualifier of occupation (covers all termination reasons), and use key event to indicate the specifics if known. Danrok (talk) 15:58, 28 August 2013 (UTC)
     Comment flagged as not done - the date a person's employment ended is already covered by end time (P582). If an additional qualifier is needed, I'd suggest something like termination reason=item, rather than a date. Danrok (talk) 12:44, 31 August 2013 (UTC)
     Comment Also, retirement (Q946865) (fully retired from all work) would be indicated using significant event (P793) = retirement (Q946865) and point in time (P585) = date. Danrok (talk) 12:48, 31 August 2013 (UTC)

    author citation (en) / Autorenkürzel (de)

    Descriptionstandard abbreviation of an author's name, used to cite the first description of a new species
    Data typeString
    Domainperson
    ExampleBarbara Baehr (Q2883901) => Baehr
    Sourcehttp://en.wikipedia.org/wiki/Author_citation_%28botany%29
    Proposed by82.83.144.130 17:49, 9 August 2013 (UTC)
    Discussion

    Note that this is different from taxon author (P405) (currently also known as "author citation"), which is used on taxon items to indicate the author who described a species. 82.83.144.130 17:49, 9 August 2013 (UTC)

    Comment / Kommentar

       Not done
    DescriptionComment
    Data typeMultilingual text (not available yet)
    Template parameterAdditional information
    DomainAny item
    Allowed valuesAny useful information which cannot be described semantically. Will be replaced by a "Comment" Property with multilingual text datatype once this datatype is available.
    Example 1MISSING
    Example 2MISSING
    Example 3MISSING
    Proposed byFilceolaire (talk)
    Discussion

     Support as nom. See discussion above. Filceolaire (talk) 12:26, 6 August 2013 (UTC)

     Comment I thought multilingual text is not on the roadmap anymore. --Tobias1984 (talk) 12:35, 6 August 2013 (UTC)
    That depends on whether we can show a need for them - like some pending properties that use them. Filceolaire (talk) 02:04, 15 August 2013 (UTC)

     Support--Micru (talk) 17:22, 15 August 2013 (UTC)

    • This one seems to miss the point of Wikidata. It's not well defined and could be construed to basically mean anything anywhere. (Heck, we could completely replace Wikipedia just with this one property. :D) --Izno (talk) 23:53, 22 August 2013 (UTC)
     Oppose Wikidata proposes facts and no comments or discussions. This is the job of Wikipedia. If something needs to be discussed, this has to be done in Wikipedia. Snipre (talk) 09:16, 28 August 2013 (UTC)
     Oppose Seems to go against the point of Wikidata, and with technical limitations against its usage I don't think it should be made. Ajraddatz (Talk) 17:15, 2 September 2013 (UTC)
    • I could see this being useful for internal use, to store and point out data that we haven't yet figured out how to store semantically (with whatlinkshere of the comment property perhaps being used as a cleanup list), but permanent use kind of ruins the point. Are uses of this property intended to be temporary? --Yair rand (talk) 18:08, 2 September 2013 (UTC)
    • I think a property like this can be useful for internal use here in this project, not intended for the client. But I cannot see why "multilingual text" should be used, a comment in a lingua franca in the string datatype would be enough. An alternative would be that the developers add "yellow paperclips" to the software. -- Lavallentalk(block) 04:36, 3 September 2013 (UTC)

     Not done Lack of consensus. John F. Lewis (talk) 22:42, 5 September 2013 (UTC)

    Caption / Bildunterschrift / légende

       Not done
    Descriptioncaption of the corresponding image
    Data typeMultilingual text (not available yet)
    Template parameter"caption" in en:template:Infobox person
    Domainall types
    Exampleimage (P18): "File:Jane Fonda Cannes nineties.jpg"
    • Caption (as qualifier): "Jane Fonda at the 2007 Cannes Film Festival"
    Proposed byMartssnail (talk)
    Discussion

    Needed for infoboxes. Martssnail (talk) 19:34, 24 July 2013 (UTC)

    A caption is not the same as a title. As you said, an editor can use the same picture for different items (and purposes): a member of the Vaisya community, a man in traditional clothing, the first owner of a fast food restaurant in New Delhi. That makes 3 captions for a picture with the label "Badruddin Ambedkar (1947)". --Martssnail (talk) 11:58, 25 July 2013 (UTC)
     Oppose because proposed datatyp is multilingual. Take a look at this discussion here - the datatype maybe never will exist! Better to work with qualifier for the language. --Nightwish62 (talk) 18:39, 26 July 2013 (UTC)
    How do you do that if this is added as a qualifier for image (P18)? As far as I can see there's no way to add a qualifier on to a qualifier. I guess if we at least get the monolingual datatype then this could just have multiple values associated with it, but the multilingual datatype seems a much cleaner implementation. -- Nemo157 (talk) 02:41, 22 August 2013 (UTC)
     Support--Micru (talk) 13:41, 14 August 2013 (UTC)
     Support -- Nemo157 (talk) 02:41, 22 August 2013 (UTC)
    • I would oppose this as too language dependent and quite frankly, too editor-dependent. As well, we don't have a good understanding yet of how Commons might integrate with Wikidata. --Izno (talk) 23:51, 22 August 2013 (UTC)
     Oppose A caption should be stored with the photo on Commons. If a photo is used across many items, we'd potentially have many different captions for the same photo. That's not how photo captioning works. There are standards regarding captions, e.g. AP Caption Style. Danrok (talk) 02:52, 25 August 2013 (UTC)
     Oppose I have doubts that an image that needs caption should be used in image (P18) at all, since that is editor-related and therefor should be added in the client and not here. qualifiers like "as of: 1945" or "direction: east" would do fine, for persons or buildings, but not much more complicated things like that. -- Lavallentalk(block) 05:22, 25 August 2013 (UTC)
    •  Weak oppose. That does not seem fit very well in Wikidata. However there are countless infoboxes that provide captions to images and that is not very convenient to provide local captions in Wikipedia if the image can be changed from Wikidata. I think we should think of ways to generate captions using other qualifiers. For instance we could make use applies to part, aspect, or form (P518) or depicts (P180) (P518 seems more correct to me). --Zolo (talk) 07:40, 5 September 2013 (UTC)

     Not done No consensus for creation from above. John F. Lewis (talk) 22:44, 5 September 2013 (UTC)

    Transliteration - Latin script / Transliteration / Translittération / OTHERS

       Not done
    DescriptionQualifier to 'official name' to transliterate names in Cyrillic, arabic, chinese, hebrew etc scripts into latin script.
    Data typeString
    DomainOfficial names
    ExampleMoscow (Q649) 'Official name' 'Москва'. 'Transliteration - Latin script' 'Moskva'.
    Proposed byFilceolaire (talk)
    Discussion
    •  Support. as nominator. Official names in scripts you don't know can be confusing. Adding a transliteration may be helpful. Filceolaire (talk) 16:32, 18 August 2013 (UTC)
    •  Oppose - The transliterations are not the same to all latin languages. A Swedish transliteration from Russian does not look the same as one to English. It can also be different if you transliterate the same letters from Ukrainian compared with one from Russian. Observe that this does not always affect the Swedish label, since the English or German transliteration may have become more used in Swedish than the correct Swedish transliteration. Also observe that latin-latin transliterations exists, for example between English and Latvian. This can maybe instead be solved with another datatype. -- Lavallentalk(block) 12:25, 20 August 2013 (UTC)
    •  Oppose. What Lavallen said, plus consider that multiple romanization systems may exist even for the same pair of languages. Take a look at this, for example—for Russian alone a dozen system of romanization exist, all of which are used in English to some extent. The property need to be more specific to be useful, and definitely more than one is needed.—Ëzhiki (Igels Hérissonovich Ïzhakoff-Amursky) • (yo?); August 20, 2013; 18:44 (UTC)
    Also English can have latin-latin transcriptions: Kebnekaise (Q214011) comes from Giebmegáisi in Northern Sami (Q33947) -- Lavallentalk(block) 19:04, 20 August 2013 (UTC)

     Not done No consensus for creation. John F. Lewis (talk) 22:50, 5 September 2013 (UTC)

    is/was/also known as/the same as (en)

       Not done
    Descriptionused to mean these two things is/was the same.
    Data typeItem
    Examplevitamin C (Q199678) => DL-ascorbic acid (Q193598), vitamin A (Q18225) => retinol (Q424976)
    Proposed byGZWDer (talk) 05:38, 21 August 2013 (UTC)
    Discussion
    •  Oppose the examples are about the same chemical, but they are not about the same subject. Ascorbic acid in an organism is not the same thing as ascorbic acid in a beaker. Also I think the scope of this property is not a single semantic concept. Being something and 'having been' something are just to distinct for example. --Tobias1984 (talk) 07:06, 21 August 2013 (UTC)
    Tobias: I'm not sure I understand what you are saying. How would you describe the relationship between vitamin C (Q199678) and DL-ascorbic acid (Q193598)?
    How are the properties of Ascorbic acid in an organism different from ascorbic acid in a beaker? Should they have different items? Filceolaire (talk) 14:02, 21 August 2013 (UTC)
    To me a similar example would be to merge the item for "car" with the item for "car accident". The properties of the car don't change but they are expressed in a different situation. A somewhat clumsy link would be: DL-ascorbic acid (Q193598) = "pharmaceutical/biological properties (described in)" = vitamin C (Q199678). --Tobias1984 (talk) 14:17, 21 August 2013 (UTC)
    I think I see what you mean. DL-ascorbic acid (Q193598) is a chemical compound. vitamin C (Q199678) is a collection of pharmaceutical/biological effects which can be caused by DL-ascorbic acid (Q193598) and other related compounds. Is that it?
    This suggests the relation is sort of like DL-ascorbic acid (Q193598) instance of (P31) vitamin C (Q199678) but not quite. Filceolaire (talk) 15:09, 21 August 2013 (UTC)
    No. said to be the same as (P460) is for things that are widely thought to be the same as but they aren't or it is disputed. Filceolaire (talk) 15:09, 21 August 2013 (UTC)
    You can also use said to be the same as (P460) with status "deprecated" or with "start-end date" for the period that it was thought to be the same.--Micru (talk) 18:26, 21 August 2013 (UTC)
     Oppose On the basis that as far as I can see, the examples given are not exactly the same thing. From the article "Ascorbic acid is one form ("vitamer") of vitamin C". That suggests to me that, possibly, ascorbic acid is a subclass of vitamin C. Danrok (talk) 15:10, 27 August 2013 (UTC)
     Oppose We have the alias for that. Snipre (talk) 09:11, 28 August 2013 (UTC)

     Not done No consensus for creation. John F. Lewis (talk) 22:52, 5 September 2013 (UTC)

    Exchange rate to U.S. Dollar

       Not done
    DescriptionThe cost in U.S. dollars of one unit of this currency
    Data typeNumber (not available yet)
    Template parameter"Exchange rate"
    DomainCurrency articles for the Global Economic Map
    Allowed valuesnumber with 'dollar' dimension
    Example 1MISSING
    Example 2MISSING
    Example 3MISSING
    Sourcehttp://www.xe.com/
    Robot and gadget jobsBots should be doing this task
    Proposed byMcnabber091 (talk) 19:05, 24 August 2013 (UTC)
    Discussion
    •  Support--Filceolaire (talk) 20:51, 24 August 2013 (UTC)
    •  SupportMcnabber091 (talk) 00:17, 25 August 2013 (UTC)
    •  Oppose I don't think taking dollars as reference point is a good idea. It hasn't been around for most of human history and it might be difficult to source the exchange rate for currencies that have no economic connection to the dollar (probably up to the 20th century). I think we should go with gold as our reference point because that can be sourced to the beginning of currencies and we can calculate the modern dollar to euro value e.g. from the cost of 1 kg of gold in euro and in dollar. --Tobias1984 (talk) 10:50, 25 August 2013 (UTC)
    Tobias that is a good suggestion regarding the relevance of gold throughout history. The reason for USD being the central reference is that we live in a fiat currency system currently based around the federal reserve. Plus we are not longer on the gold standard. A commodities property proposal section is needed. Thanks for the suggestion, this is a philosophical economic question honestly.Mcnabber091 (talk) 04:26, 26 August 2013 (UTC)
    In my opinion economics is pure philosophy :) If this property really needs to be in dollars I suggest naming it "exchange rate to U.S. dollar". It will need time qualifiers for the time this exchange rate was valid. Probably also a place qualifier. The price of one dollar probably varies depending on the country and bank you visit. To keep data coherency we should go with a more or less stable source. --Tobias1984 (talk) 06:12, 26 August 2013 (UTC)
    While the foreign exchange markets currently us the dollar as their universal yardstick that has not always been the case and may not always be the case in future. This property can be used to show the exchange rate to any currency by changing the number dimension. I would oppose changing the name from "Exchange rate".
    While having a "Price per kilo" property, to show the cost of gold and other commodities, sounds like a good idea it hardly seems like a reason to oppose this property. Can you change that Tobias? Filceolaire (talk) 14:27, 26 August 2013 (UTC)
    The situation is far more complex than having a single exchange rate property. There are many types of exchange rates which are constantly changing. I don't think we will be storing minute-by-minute rates any time soon, but we could consider storing monthly rates, in which case there's still more than one original source. Here's an example source BIS effective exchange rate indices. If monthly is too frequent, we could just store quarterly rates, or even just annual rates (e.g. December's rate). Danrok (talk) 15:27, 3 September 2013 (UTC)
     Strong oppose for being US Dollar specific. Use qualifiers as for example: Exchange rate (qualifier instance of (P31): United States dollar (Q4917)): 4,50. Or use and wait for datatype number with unit.  Oppose for the property as a whole: The exchange rate to whatever changes continuously. If this property is created, why shouldn't someone update the property by adding a new value every single second? I do not think that datatype number is designed to hold continuously changing values.  — Felix Reimann (talk) 17:05, 3 September 2013 (UTC)
     Not done This one needs more thought, then a new proposal. Danrok (talk) 21:22, 4 September 2013 (UTC)

    Saskatchewan Register of Heritage Property identifier (en) / identifiant Saskatchewan Register of Heritage Property (fr)

    DescriptionThe unique identifier of Saskatchewan Register of Heritage Property
    Data typeString
    Domainplace
    Allowed valuesnumber only
    ExampleHutchinson Building (Q5950648) ---> 2292
    Sourcehttp://www.tpcs.gov.sk.ca/heritage-property-search
    Proposed byFralambert (talk) 02:20, 3 August 2013 (UTC)
    Discussion
     Comment Seems ready for creation. --  Docu  at 19:08, 6 September 2013 (UTC)
    ✓ Done --Fralambert (talk) 00:14, 7 September 2013 (UTC)

    number of episodes

       Not done
    DescriptionNumber of episodes made for a TV series or a radio drama series (please note that this excludes news programmes)
    Data typeNumber (not available yet)
    Template parameteren:template:infobox television num_episodes (no. of episodes), en:template:infobox radio show num_episodes
    Domaintelevision series and radio shows
    Allowed valuespositive integers without units
    ExampleThe Archers <number of episodes> 17010
    SourceInfobox Television and Infobox radio show on en.wiki or any equivalent on other Wikipedias
    Proposed byWylve (talk)

    Common property for television and radio shows. Wylve (talk) 15:33, 20 April 2013 (UTC)

     Comment not always a case of an episode going missing. Historically, many episodes of certain series were deliberately overwritten (due to a lack of expensive video tapes), or simply broadcast live and not recorded at all. We may know that an episode was broadcast because it is recorded in schedules, without any further detailed information available. Some of these are not likely to have their own wikipedia article, but perhaps we can create them as wikidata items? Some examples are here: Missing Episodes. Danrok (talk) 15:47, 5 September 2013 (UTC)

     Not done per lack of consensus (proposal has been open for over four months).--Jasper Deng (talk) 18:47, 5 September 2013 (UTC)

    story set in time / Handlung spielt zur Zeit / История происходит во время / ? / ?

       Not done
    Descriptionthe narrative of this work is set in the year/at the time
    Data typePoint in time
    Domainwork (literature, film, music, video games, everything with a narrative)
    Allowed valuescan have multible values
    ExampleNineteen Eighty-Four (Q208460) → 1984

    In the Year 2525 (Q145269) → 2525
    2001: A Space Odyssey (Q103474) → 2001
    300 (Q131390) → 480BC

    Mega Man 5 (Q2360194) → 2000
    Proposed byShisma (talk)
    Discussion
    please feel free to propose a better naming--Shisma (talk) 21:34, 27 August 2013 (UTC)
     Support> The name seems fine to me. Filceolaire (talk) 05:37, 28 August 2013 (UTC)
    Wouldn't this need both start and end dates? --Yair rand (talk) 07:21, 28 August 2013 (UTC)
    actually I think it should have multiple start and end dates. but i don't know if its possible --Shisma (talk) 08:12, 28 August 2013 (UTC)
     Oppose I think the best way to do this is to have a location setting property only, and use time qualifiers to indicate the time setting. Danrok (talk) 17:16, 28 August 2013 (UTC)
    wow, not bad ^^--Shisma (talk) 18:58, 28 August 2013 (UTC)

     Not done Per the oppose, existing properties could fulfil this as a qualify for a location etc. John F. Lewis (talk) 09:52, 4 September 2013 (UTC)

    story set in location / Handlung spielt an Ort / История происходит в месте / ? / ?

    Descriptionthe narrative of this work is set at this location
    Data typeItem
    Domainwork (literature, film, music, everything with a narrative)
    Allowed valuescan have multible values
    ExampleNineteen Eighty-Four (Q208460) → London (Q84)

    In the Year 2525 (Q145269) → unknown
    2001: A Space Odyssey (Q103474) → outer space (Q4169), Moon (Q405)

    300 (Q131390) → Thermopylae (Q194450)
    Proposed byShisma (talk)
    Discussion
    please feel free to propose a better naming--Shisma (talk) 21:34, 27 August 2013 (UTC)
     Support. The name seems fine to me. Filceolaire (talk) 05:36, 28 August 2013 (UTC)
    Could this be also used for wars? Or other events? --Yair rand (talk) 07:18, 28 August 2013 (UTC)
    for this purpose we already have country (P17), located in the administrative territorial entity (P131) and continent (P30)--Shisma (talk) 08:12, 28 August 2013 (UTC)
    So why wouldn't those properties work for all cases that "set in (location)" could be used for? --Yair rand (talk) 08:57, 28 August 2013 (UTC)
    because Nineteen Eighty-Four (Q208460) → located in the administrative territorial entity (P131) → London (Q84) would mean the book is in London. this property says that the story in the book is set in London--Shisma (talk) 09:30, 28 August 2013 (UTC)
    I see. So, would this property be usable for nonfiction stories? --Yair rand (talk) 03:07, 29 August 2013 (UTC)
    Yes; and fiction stories set in real places and fiction stories set in fictional places - if the place has an item. Filceolaire (talk) 20:07, 30 August 2013 (UTC)
    sure, why not?--Shisma (talk) 18:10, 30 August 2013 (UTC)
     Support and use time qualifiers to indicate the period in time. Danrok (talk) 17:17, 28 August 2013 (UTC)
     CommentFor a given scene in a film there's going to be at least one Setting (narrative), and at least one Filming location. These are not always the same place, for example For a Few Dollars More (Q153677) was filmed in Spain (Q29), but set in New Mexico (Q1522). So, I think we should have another property for filming location which can be used as a qualifier for the location setting, along with the period setting. Danrok (talk) 00:00, 1 September 2013 (UTC)
    I agree --Shisma (talk) 13:38, 1 September 2013 (UTC)
    proposed that here --Shisma (talk)

    ✓ Created leaving a note here as I did change the label and description slightly. John F. Lewis (talk) 09:56, 4 September 2013 (UTC)

    Global Biodiversity Information Facility ID (GBIF)

    DescriptionThe w:Global Biodiversity Information Facility (GBIF) is an international organisation that focuses on making scientific data on biodiversity available via the Internet using web services.
    Data typeString
    Template parameterw:Template:Taxon, w:Template:TaxonIds
    Domainterm / taxon
    Example5963040
    Proposed by--Micru (talk) 13:08, 15 August 2013 (UTC)
    Discussion

    ATTENTION: The id's in the Wikipedia seem not to work, the new ones will have to be imported.

     Support Liné1 (talk) 14:56, 23 August 2013 (UTC)
     Support Danrok (talk) 10:39, 2 September 2013 (UTC)
     Support --Tobias1984 (talk) 09:27, 6 September 2013 (UTC)

    ✓ Done --Tobias1984 (talk) 19:43, 7 September 2013 (UTC)

    World Register of Marine Species identifier (WoRMS)

    DescriptionThe w:World Register of Marine Species (WoRMS) is a database that hopes to provide an authoritative and comprehensive list of names of marine organisms
    Data typeString
    Template parameterw:Template:TaxonIds
    Domainterm / taxon
    Example145548
    Proposed by--Micru (talk) 13:08, 15 August 2013 (UTC)
    Discussion
     Support Liné1 (talk) 14:58, 23 August 2013 (UTC)
     Support Danrok (talk) 10:37, 2 September 2013 (UTC)
     Support --Tobias1984 (talk) 09:36, 6 September 2013 (UTC)

    ✓ Done --Tobias1984 (talk) 19:58, 7 September 2013 (UTC)

    FIPS for US counties (FIPS 6-4)

       Done: FIPS 6-4 (P882) (Talk and documentation)
    DescriptionFIPS code for US counties per former FIPS 6-4 standard, see Federal Information Processing Standard (Q917824). See also: FIPS 55-3 (locations in the US) (P774)
    Data typeString
    Domainplaces: US counties
    Allowed values\d\d\d: see state pages available on en:Lists of counties in the United States
     Support would be useful for bots among other uses to identify a county. Aude (talk) 07:52, 24 August 2013 (UTC)
     Comment Seems ready for creation. --  Docu  at 19:05, 6 September 2013 (UTC)

    FIPS 5-2 for US states and other associated areas

       Done: no label (P883) (Talk and documentation)
    DescriptionFIPS code for US states (numeric or alpha) per former FIPS 5-2 standard, see Federal Information Processing Standard (Q917824). See also: FIPS 55-3 (locations in the US) (P774)
    Data typeString
    Domainplaces: US states and certain other associated areas
    Allowed values\d\d or \D\D: see en:Federal Information Processing Standard state code
     Support Aude (talk) 07:53, 24 August 2013 (UTC)
     Support Danrok (talk) 13:59, 4 September 2013 (UTC)


     Comment Seems ready for creation. --  Docu  at 19:07, 6 September 2013 (UTC)


    Statistical name / /

       Not done
    DescriptionName of location according to Statistical organisations.
    Data typeString
    Example 1MISSING
    Example 2MISSING
    Example 3MISSING
    Sourcehttp://www.scb.se/Statistik/MI/MI0811/2010A01/Tabell_1_2010_web_v2.xls
    •  Comment I think it is necessary to have a property for any codified, official designation or name assigned by an organization, provided the designation or naming system meets notability guidelines. However, I think this is best done with discrete properties for each system, with statements added directly as needed. An example of this is airports, which have both an official ICAO airport code and an IATA airport code. Each is its own property, instead of say a more generic 'official airport code' with qualifiers or such. I would propose that if Statistics Sweden place names are significant enough to warrant including in statements, that we ought to simply make the property 'Statistics Sweden place name' or some such that is specific to that purpose. That will make it very easy to link to infoboxes and define what should be entered in statements without having to add extra qualifiers. Joshbaumgartner (talk)
     Oppose. Use 'official name' with qualifier 'authority' => '<name of statistical organisation>'. Filceolaire (talk) 15:06, 17 August 2013 (UTC)
    It's nothing official at all with the names of minor urban areas and holiday and weekend homes. But I guess it would do with the proposed #controlled place name proposed above. -- Lavallentalk(block) 15:42, 17 August 2013 (UTC)
    Marking this as "not done". -- Lavallentalk(block) 07:06, 7 September 2013 (UTC)

    State Water Register Code (Russia)/ код ГВР

    DescriptionBody water identification code
    Data typeString
    Template parameterru:Шаблон:Водный реестр России Код
    Domainреки России
    ExampleVoyevolikhan (Q4114311) <код ГВР> 17040200112117600008474
    Format and edit filter validation23 цифры
    Sourceкарточки, сама база
    Robot and gadget jobsWikidata:Database reports/Constraint violations
    Proposed by— Ivan A. Krestinin (talk)
    Discussion
    •  Support. This geographical code identifies rivers and some other water bodies in Russia. --Emaus (talk) 21:45, 13 July 2013 (UTC)
    •  Wait Can we create an unique property for the different national classifications instead of different properties for each natioanl code ? Snipre (talk) 12:50, 29 July 2013 (UTC)
      • It is hard to manage one property for different databases. For example for infobox ru:Шаблон:Водный реестр России we need only ГВР-code, not any other codes. But one river can be registered in many databases. Naming of mixed property is problem ("river's code" is not descriptive). Different databases have different ID's format, different domain (for constrains check). They are managed by different organizations, so different URL is needed. — Ivan A. Krestinin (talk) 13:23, 29 July 2013 (UTC)
        • A qualifier can do the difference between the different national codes, something like national office of statistic where you can put the country or the national office if you have an item for it. The label of the property is not a real problem, something like property:"national code of water body" ->230755 17040200112117600008474, qualifier:"national office of statistic" ->Russia. For the format I don't see an issue: most of statistical data can be found from tables and can be added by bot reducing the problem of manual addition in the db. Once the data is added, the format control is not necessary and if you really want to check vandalism you can define one bot which can check all formats according to their qualifier. If we are working with bots there are no big problems concerning different databases or different formats. And differents sources are not a problem: for most properties you have to deal with differents sources. Snipre (talk) 14:11, 29 July 2013 (UTC)
          • Qualifier is bad way for this case: every time then you specify ГВР-code you need additionally specify qualifier. You can forget to do this, you can specify invalid item or property in qualifier. Qualifiers are problem for bots too because its make bot code more complex. Qualifier makes infobox code more complex too. This makes Wikidata gadgets more complex. What benefits are on this way? We will have many manual work too because there is no table with columns: Wikidata Q-code and ГВР-code. We have only one source: Wikipedia articles, but its contain many errors and missed data that need be fixed manually. Databases (both Wikidata and external databases) are not static objects. They are changed from time to time (bugfix, changes in real world and etc.). We need check data consistence continuously, not once. — Ivan A. Krestinin (talk) 14:55, 29 July 2013 (UTC)
            • Did you already program ? If not, here is a small explanation: qualifier in programming language is just an additional condition to an existing query or to simplify a query inside a query. If you know how to program a query, it is not difficult to create a new one. For data import qualifier is just a second action after creating the claim with the value, one or two code lines, not very complex. And sorry but sayinf that qualifiers are a problem for infobox is just forgetting the reality: with your proposition you create one infobox per country so you for you 200-250 infoboxes are less complex than 5-10 code lines ? Especially when 99% of the infobox content is the same. Then for the rest of your comment they are no differences between one system with hundreds of specific properties or another with 2 general properties: the q-list has to done once. Data check is not a problem even with only 2 properties: you just have to extend the existing check bots. Snipre (talk) 17:22, 29 July 2013 (UTC)
            • We can even keep the existing template for format constraints and extend the current code from {{Constraint:Format|pattern=\d\d\d\d\d\d\d\d\d\d\d}} to {{Constraint:Format|qualifier=Russia|pattern=\d\d\d\d\d\d\d\d\d\d\d|qualifier=Sweden|pattern=\d\d\d\\-\d\d\d\d\d|qualifier=France|pattern=\[A-Z]\[A-Z]\d\d}}. The complexity is just the creation of a small table at the beginning and to add a line in the code to lookup for the corresponding pattern according to the qualifier before the check of the correspondance between the value and the pattern. Again this implies some additional code lines but you will do that once and this will save a lot time corresponding to the search of the specific property in a list composed of all national codes with their corresponding country. Snipre (talk) 17:40, 29 July 2013 (UTC)
              • Are you want create infobox that will show any new database without infobox modification? I think this is not very good idea. Every database ID must be wikified with specific way. For example ГВР ID is very long, it need spitted row in infobox (see ru:Шаблон:Водный реестр России). Every ID need specific language-dependent short-name. Every ID need specific URL for wikification, for example [http://vwo.osm.rambler.ru/?page=findname&name=17040200112117600008474 17040200112117600008474] for ГВР. There are historical/deprecated databases, they may be interesting for example in ru-wiki and not interesting in es-wiki. These are the reasons why every new database need be added (or not added) to infobox manually. No need many infoboxes, we need one river infobox per xx-wiki. This infobox will specify database (property) set and visualization parameters per every property. This schema can be realized using qualifiers instead of property, but implementation with qualifiers is more complex. — Ivan A. Krestinin (talk) 18:31, 29 July 2013 (UTC)
                • I really don't see where you see problems: if your code can handle different properties for the water body identification code, it can do the same work with qualifier. A loop with if and elseif can do the work very easily.
    Example:
    ...
    qualifier_wikidata = XX
    value_wikidata = YY
    if qualifier_wikidata == Russia then
    link_infobox = www.aaa.ru
    title_infobox = State Water Register Code
    elseif qualifier_wikidata == Sweden then
    link_infobox = www.bbb.sw
    title_infobox = VISS ID
    else
    ...
    end
    ...
    {{title_infobox|[link_infobox value_wikidata]}} (very simplified code but lua is doing that job very well) Snipre (talk) 15:41, 30 July 2013 (UTC)


    origin of the watercourse (en)

    Descriptionmain source of a river or stream
    Data typeItem
    Template parameter"source" in en:template:geobox, "origin" in en:template:Infobox River
    Domainplace
    Allowed valuesnot limited
    Examplecould be lakes (e.g. en:Columbia Lake, source of en:Columbia River), glaciers and icefields (e.g. en:Columbia Icefield, source of en:Athabasca River), mountain range (e.g. en:Andes Mountains source of en:Amazon River). The property would be analogous to Property:P403 (mouth of the watercourse)
    Sourceinfobox
    Proposed byAude (talk) 02:29, 30 May 2013 (UTC)
    Discussion
    Don't you mean headwaters? --Rschen7754 05:21, 30 May 2013 (UTC)
    Yes, that works. Some of the enwiki infoboxes link to en:River source for that parameter. Aude (talk) 07:56, 30 May 2013 (UTC)
    For some, "Source confluence" is used like for en:Saskatchewan River. The values would be en:South Saskatchewan River and en:North Saskatchewan River It is not exactly the same infobox parameter in that case. Not sure we would want it to be a different property? or same property, perhaps with a qualifier or something? Aude (talk) 08:03, 30 May 2013 (UTC)
    en:Peace River (Canada) has primary and secondary source. I think qualifiers would work for that. Aude (talk) 08:07, 30 May 2013 (UTC)
     Support دوستدار ایران بزرگ (talk) 10:29, 3 June 2013 (UTC)

    IPA (en)

    Descriptionsee m:Wikidata/Notes/Future#Wiktionary
    Data typeString
    Proposed byGZWDer (talk) 10:23, 18 June 2013 (UTC)
    Discussion

    ✓ Done --Jakob (Scream about the things I've broken) 00:55, 12 September 2013 (UTC)

    Code of nomenclature

    Descriptionthe Code of nomenclature that governs the names for this taxon
    Data typeItem
    Domainterm
    Allowed values
    Proposed byBrya (talk) 16:53, 17 September 2013 (UTC)

    Motivation: this is not included in any Wikipedia infoboxes, and need not ever be. Its use would primarily be for internal use, for putting together a taxobox generated from Wikidata. The reason for it would be to indicate what Code applies to this particular taxon, as this cannot be reliably read from its taxonomic position (not for the small stuff). For example the Cyanobacteria taxonomically are prokaryotes but their nomenclature is governed by the Code for algae, fungi and plants. The new property would not need to be used in many items (once parent taxon (P171) is fully implemented). (There are five Codes; this does not include the one for orchids, which presumably is no longer used. In a sense, for names of cultivated plants two Codes apply simultaneously.) - Brya (talk) 16:53, 17 September 2013 (UTC)

     Support But datatype should be item. --Succu (talk) 17:25, 17 September 2013 (UTC)

     Support datatype item linking to the existing items of Codes like for example International Code of Zoological Nomenclature (Q13011).  — Felix Reimann (talk) 17:48, 17 September 2013 (UTC)

    ✓ Done --Jakob (Scream about the things I've broken) 19:17, 3 October 2013 (UTC)

    Retrieved from "https://www.wikidata.org/w/index.php?title=Wikidata:Property_proposal/Archive/13&oldid=1494178114"