Shortcuts: WD:PP/GEN, WD:PP/Generic

Wikidata:Property proposal/Generic

From Wikidata
Jump to navigation Jump to search


Property proposal: Generic Authority control Person Organization
Creative work Place Sports Sister projects
Transportation Natural science Lexeme

See also[edit]

This page is for the proposal of new properties.

Before proposing a property

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

Creating the property

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

On this page, old discussions are archived. An overview of all archives can be found at this page's archive index. The current archive is located at 2018/07.

Contents

Generic properties[edit]

SNOMED CT identifier[edit]

   Under discussion
Descriptionidentifier in the SNOMED CT catalogue codes for diseases, symptoms and procedures
Data typeExternal identifier
Domainhttps://www.wikidata.org/wiki/Q19887775
Allowed unitsthere are not units, just an identifier
Examplehttp://snomed.info/id/64859006 (osteoporosis), http://snomed.info/id/267718000 (age related macular degeneration)
Sourcehttps://en.wikipedia.org/wiki/SNOMED_CT and https://www.wikidata.org/wiki/Q1753883
Planned uselink diseases with SNOMED CT terms
Formatter URLhttp://snomed.info/id/$1
See alsoICD-10 identifier (https://www.wikidata.org/wiki/Property:P494), ICD-9 identifier

Motivation

SNOMED CT is a well established terminology. It has existed since 1965. Since 2007 it changed legal form to be an international standard development organization. There are existing properties for ICD 9 and ICD 10 and SNOMED CT is very similar to those. Example wikipedia term where this property could be used would be https://en.wikipedia.org/wiki/Macular_degeneration or https://en.wikipedia.org/wiki/Osteoporosis

The infobox template relevant to this property is https://en.wikipedia.org/wiki/Template:Infobox_medical_condition The identifier must be a number. (see https://confluence.ihtsdotools.org/display/DOCTIG/3.1.4.2.+Component+features+-+Identifiers )

Wuser6 (talk) 03:52, 14 April 2018 (UTC)

Discussion

  • Pictogram voting comment.svg Comment It is not sufficient, because we would like to add it to the medical condition info box and in order to do that having it linked the same way as ICD is the only way to have that advanced functionality. Wuser6 (talk) 15:04, 3 May 2018 (UTC)
  • Symbol support vote.svg Support, although I don't know well about the license of SNOMED CT... --Okkn (talk) 03:47, 19 July 2018 (UTC)

donation platform[edit]

   Under discussion
Descriptionplace to make donations for this person or project
Representsdonation (Q1124860)
Data typeItem
Example
Expected completenessalways incomplete (Q21873886)

Motivation

My idea is that this would work similarly to website account on (P553). I'm not entirely sure how to handle self-hosted donations platforms, such as Wikimedia's, so the third example given is tentative. Any suggestions? NMaia (talk) 12:32, 21 April 2018 (UTC)

Discussion

  • Pictogram voting comment.svg Comment @Ivanhercaz: For self-hosted donation platforms we can create an item with the label "self-hosted service".--Micru (talk) 07:44, 25 May 2018 (UTC)
  • Symbol support vote.svg Support Robin van der Vliet (talk) (contribs) 10:16, 26 May 2018 (UTC)
  • Symbol oppose vote.svg Oppose P553 or a dedicated property can do.
    --- Jura 06:46, 29 May 2018 (UTC)
  • Symbol oppose vote.svg Oppose better think deeper about how to model donation information in general: what information is required, e.g. where to find information about donation, which account to donate to (bank account, donation platform...), whether donations could be tax-reducible... Some of this information can already be modeled with existing properties. New properties and/or qualifiers might make sense but this particular proposal is not convincing. -- JakobVoss (talk)

cryptocurrency address[edit]

   Under discussion
Descriptionaddress for this project or organization's cryptocurrency wallet
Representscryptocurrency (Q13479982)
Data typeExternal identifier
Domainprojects and organizations
Example
Sourcehttps://en.bitcoin.it/wiki/Donation-accepting_organizations_and_projects
Expected completenessalways incomplete (Q21873886)

Motivation

Similar to Property proposal/donation platform, this is valuable for donations. We probably need tight controls on this to, eg. spot new users changing this statement. NMaia (talk) 12:59, 21 April 2018 (UTC)

Discussion

  • Pictogram voting comment.svg Comment @NMaia: Please make examples correct links David (talk) 14:39, 21 April 2018 (UTC)
    • Which link is incorrect? NMaia (talk) 15:45, 21 April 2018 (UTC)
      • For your first example, Firefox reports "The address wasn't understood". Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 19:31, 2 May 2018 (UTC)
        • You need a program that can open links like that, like a bitcoin wallet. This is a similar scheme to 'mailto'. I took the link directly from https://f-droid.org NMaia (talk) 14:05, 3 May 2018 (UTC)
  • Symbol support vote.svg Support But, is a link with 'bitcoin:' scheme valid? Would be better using a HTTP link like https://blockchain.info/address/15u8aAPK4jJ5N8wpWJ5gutAyyeHtKX5i18? --Giovanni Alfredo Garciliano Díaz diskutujo 22:06, 1 May 2018 (UTC)
  • Symbol oppose vote.svg Oppose this information is useless because it cannot be trusted. We would need to add a big warning sign not to send money to this address without having checked at the organization. A cryprocurrency account is different to similar information (e.g. traditional bank account, street address...) because there is no way to withdraw a transfer -- JakobVoss (talk) 09:10, 16 June 2018 (UTC)
    Like all statements, reliable references would be necessary to be sure of its accuracy. I don't see how this is an argument against having the property. --Yair rand (talk) 18:28, 16 July 2018 (UTC)

has program committee member[edit]

   Under discussion
Data typeItem
Domainscientific event (Q52260246)
Allowed valueshuman (Q5)
ExampleWiki Workshop 2018 (Q47035167)Miriam Redi (Q43372605) [1]
Expected completenessalways incomplete (Q21873886)
See alsoreviewed by (P4032)

Begrundelse

Scientific meetings (conferences/workshops) has a group of researchers that determine which contributions (articles/abstracts/presentations/demos) that will be accepted to the meeting. This is usually called the program committee. For modeling scientific events a property catching this relationship is wanted. Alternatively one could establish a new item for the program committee and declare a person to be a member of that item. However then we would need another property to link scientific meeting Wikidata items to program committee Wikidata items. Alternatively, one could have the inverse property, on person item pages that directly links to the scientific meeting. Program commmitees might be from about 10 to over 1'000 members. — Finn Årup Nielsen (fnielsen) (talk) 10:55, 28 April 2018 (UTC)

See the inverse property suggestion at Wikidata:Property proposal/is program committee member of.

Discussion

  • Symbol support vote.svg Support David (talk) 10:49, 29 April 2018 (UTC)
  • Symbol support vote.svg Support John Samuel 10:05, 1 May 2018 (UTC)
  • Pictogram voting comment.svg Comment both properties have been supported and marked as ready but at a quick glance it is not clear to me whether the proposer and supporter want both properties to be created, or should we just pick one? − Pintoch (talk) 07:22, 17 May 2018 (UTC)
@Fnielsen: ^ − Pintoch (talk) 09:06, 26 May 2018 (UTC)

Maintained by WikiProject[edit]

   Under discussion
DescriptionLink to WikiProject that maintain a property
Data typeItem
Domainproperties
Allowed valuesWikiProject (Q21025364)
Exampleencoded by (P702)WikiProject Molecular and Cellular Biology (Q15884967)
Planned usesplit Wikidata:Database reports/Constraint violations/Mandatory constraints/Violations and other reports by projects
Expected completenessalways incomplete (Q21873886)
Robot and gadget jobsKrBot (talkcontribslogs)
See alsoWikidata project (P4570)

Motivation

Reports like Wikidata:Database reports/Constraint violations/Mandatory constraints/Violations are too long. Project-related lists will be more efficient. — Ivan A. Krestinin (talk) 09:48, 29 April 2018 (UTC)

Discussion

  • Symbol support vote.svg Support better than Wikidata project (P4570) David (talk) 10:41, 29 April 2018 (UTC)
  • Pictogram voting comment.svg Comment If doing any kind of automated things based on this property data (e.g. posting report to talk page, etc), I think we need to specify language edition. Because each projects are working generally independently. So what do you think about using qualifier like this...? --Was a bee (talk) 12:51, 29 April 2018 (UTC)
Maintained by Wikiproject
Normal rank WikiProject Molecular and Cellular Biology Arbcom ru editing.svg edit
of English Wikipedia
of French Wikipedia
of Wikidata
▼ 0 reference
+ add reference
+ add value
  • I will use the property inside Wikidata project only for now. Your suggestion is good if it will be used for another projects. — Ivan A. Krestinin (talk) 19:23, 29 April 2018 (UTC)
  • Oh I see. This would be good and useful property. Thank you for answer. Symbol support vote.svg Support --Was a bee (talk) 06:25, 30 April 2018 (UTC)

GNOME Wiki ID[edit]

   Not done
Descriptionentry in GNOME Wiki website for an application or project
RepresentsGNOME Wiki (Q29605393)
Data typeExternal identifier
Domainsoftware
Example
Sourcehttps://wiki.gnome.org/
Planned useIntegrate in the software infoboxes
Number of IDs in source278
Expected completenessalways incomplete (Q21873886), GNOME will make more apps in the future
Formatter URLhttps://wiki.gnome.org/$1
Robot and gadget jobsNone
See alsoFree Software Directory entry (P2537)

Motivation

I think this property is an useful data, different from official website (P856), for example: Gtkmm (Q284796) has official website (P856) value: https://www.gtkmm.org/, and we could have a GNOME Wiki Id property, with a possible value: https://wiki.gnome.org/Projects/gtkmm --Giovanni Alfredo Garciliano Díaz diskutujo 22:56, 1 May 2018 (UTC)

Discussion

  • @Liuxinyu970226: I didn't know I can do that, but reading the page, I'm not sure if is a good idea create a proposal, because I'm not sure about the license of the contents, and I think that 300 items are insufficient for a new interwiki prefix.

 Not done--Micru (talk) 17:00, 17 July 2018 (UTC)

visible by means of[edit]

   Under discussion
Descriptionitems of interest can be visible through other items (e.g. webcams)
Data typeItem
Allowed valuestype of linked items: Q template
Examplea water well such as Mosaikbrunnen (Q27229889) might be live-visible on a web cam such as NZZ WebCam (Q53678107)
Planned useafter the WVZ data set import (https://www.wikidata.org/wiki/Q53629101), we want to mark the fountains that are visible live on the webcams of the city
See alsooffers view on (P3173), webcam page URL (P4238)

Motivation

When people want to see an item of interest real time through the internet, this gives them a hint how to do so. Another application may be tourist binoculars available in many city- or mountain-viewpoints.  – The preceding unsigned comment was added by Ralfhauser (talk • contribs) at 03:19, May 18, 2018‎ (UTC).

"offers view on" (P3173) appears to be the reciprocal approach.

Probably, there is yet another property needed "in focus of URL" because the webcam URL is only likely to give access to the webcam, but some webcams hopefully allow to specifiy by means of an url also what (i.e. which direction, focus, zoom) they should point

Discussion

production website[edit]

   Under discussion
DescriptionAn official page of a television series hosted by the network or production company.
Data typeURL
Template parameter"production website" in en:template:infobox television
Domainproperty
ExampleMy Mister (Q43111245)http://www.chorokbaem.com/main/ko/sub04_02_31.html?xid=4&subxid=2
See alsoofficial website (P856)

Motivation

Production website is used in the English infobox. It would be nice to be able to link it to other languages Wikipedia pages just like official website (P856). CherryPie94 (talk) 12:27, 18 May 2018 (UTC)

Discussion

Do you have an example where it would be different from official website (P856)? Perhaps just a qualifier on official website (P856) would take care of this? ArthurPSmith (talk) 17:34, 18 May 2018 (UTC)
If we are to link it to Wikipedia infobox it would not work. Currently, the official website is migrated from Wikidata to Englis Wikipedia, but since there is no property for the production website, that can't be done. https://en.wikipedia.org/wiki/My_Mister#External_links This TV series has 1 official link, and 2 links to the production company pages about the TV series. CherryPie94 (talk) 10:42, 20 May 2018 (UTC)
Symbol support vote.svg Support Ok, I was mainly just looking for the property template to be filled out, I added your example. ArthurPSmith (talk) 15:01, 21 May 2018 (UTC)
Symbol oppose vote.svg Oppose the proposal lack more examples, domain, infobox parameter, cardinality (can it have multiple values?) etc. URL (P2699) with a qualifier could be used, couldn't it? -- JakobVoss (talk) 06:22, 16 June 2018 (UTC)

Political coalition[edit]

   Under discussion
Descriptionagreement for cooperation between different political parties
Representspolitician (Q82955)
Data typeItem
ExampleDilma Rousseff (Q40722)position held (P39)President of goku (Q5176750) → Political coalition = For Brazil to keep on changing (Q5466690)
See alsoparliamentary group (P4100)

Motivation

I'm involved in a project of strutured narrative about brazilian elections that I think it will be useful to improve elections items at Wikidata. The database of the official electoral institutions can provide a lot of information. Scrap and bring this data is part of the plan. A political coalition is an agreement for cooperation between different political parties. In a parlamentary item, besides party, it would be great to have the coalition that politician was involved while the electoral process. Ederporto (talk) 01:19, 20 May 2018 (UTC)

Discussion

  • Pictogram voting comment.svg Comment position held (P39) statement tend to be overloaded with qualifiers. Maybe an item for each coalition government works better.
    --- Jura 17:57, 20 May 2018 (UTC)
@Jura1: Can you be more clear? I didn't get it. Thanks, Ederporto (talk) 23:01, 20 May 2018 (UTC)
  • Symbol support vote.svg Support David (talk) 12:45, 26 May 2018 (UTC)
  • BA candidate.svg Weak oppose. I'm not sure this is the best way to model this. I think we need to look at a broader set of political coalitions and how they work across countries, and figure out a setup that works as widely as possible. --Yair rand (talk) 19:43, 27 June 2018 (UTC)
  • Symbol support vote.svg Support --Giovanni Alfredo Garciliano Díaz diskutujo 18:28, 30 June 2018 (UTC)
  • Symbol support vote.svg Support. In the Brazilian case, this refers to electoral coalitions, an object of our electoral system. I understand this applies elsewhere. Joalpe (talk) 01:27, 8 July 2018 (UTC)

sense for this name[edit]

   Not done
Descriptionsense of a lexeme corresponding to name
Data typeSense (not available yet)
ExampleWarsaw (Q270) native label (P1705) "Warszawa" → Warszawa/capital of Poland

Motivation

Not sure how to do this. (Add your motivation for this property here.)
--- Jura 15:22, 13 May 2018 (UTC)

Discussion

It sounds like you are trying to create an inverse of item for this sense (P5137) (which you created though we can't use it yet)? Or is this somehow different (can you clarify)? In any case, I think the inverse direction (which P5137 may already cover) is the better one here, otherwise you'll have one statement per language on each place item. ArthurPSmith (talk) 14:48, 14 May 2018 (UTC)
  • I'm trying to figure out how to solve last year's usecase. I'm not sure if P5137 would be sufficient. Maybe we could try an equivalent of statement is subject of (P805). This could be used as a qualifier for a statement such as 'native label = "Warszawa" '.
    --- Jura 15:12, 14 May 2018 (UTC)
  • I updated this accordingly.
    --- Jura 12:22, 15 May 2018 (UTC)

If I understand correctly, this is intended to connect a Statement on an Item to a Lexeme using a qualifier. The use case makes sense to me, but if I understand the structure of this page correctly, this request is misplaced: this section appears to be for Properties to be used on Senses. The proposed Property refers to a Sense, but would be used as a Qualifier on a Statement (supposedly on Items), on on Senses. So the request should probably be at Wikidata:Property_proposal/Generic. -- Duesentrieb (talk) 11:24, 24 May 2018 (UTC)

 Not done --Micru (talk) 17:00, 17 July 2018 (UTC)

number of rocket stages[edit]

   Not done
Descriptionnumber of stages for a rocket
Representsrocket stage (Q4809)
Data typeQuantity
Domainrocket (Q41291)
Allowed unitspositive integers
ExampleSputnik (Q1393751) -> 2

Motivation


Discussion

Ideally this would have a less unwieldy name like "number of stages", although I'm afraid people would then start adding it to stuff like 2018 Tour de France (Q28859163).--Reosarevok (talk) 19:34, 9 June 2018 (UTC)
Symbol oppose vote.svg Oppose has parts of the class (P2670) with an item like "rocket stage of Sputnik" and quantity (P1114) would be a better way to specify this relationship. The proposed property is too specific. ChristianKl❫ 14:05, 14 June 2018 (UTC)

 Not done --Micru (talk) 16:58, 17 July 2018 (UTC)

reference has role[edit]

   Ready Create
Descriptionrole, or specific nature, of the given reference
Representsreference (Q121769)
Data typeItem
Domainreferences
Allowed valueslimited list of allowed values
ExampleAS PART OF REFERENCE → first description (of a taxon) (Q1361864)
Robot and gadget jobsconvert existing uses of P31 as a reference to use the new property
See also

Motivation[edit]

We currently have about 50,000 cases where instance of (P31) is used as a property in a reference, rather than as a main statement. See queries: tinyurl.com/y78odkdu (counts of values), tinyurl.com/y8owabzc (examples). The use on e.g. Q101538#P225 is typical.

In my opinion, use of P31 in this way is ugly and confusing -- IMO it would be better if P31 was only used for its main purpose, as a direct statement on an item giving its nature.

Use of P31-on-references is similar to the way P31 once used also to be used as a qualifier. But those uses have now everywhere been removed and replaced with subject has role (P2868) and object has role (P3831).

P31-on-references is currently doing some important work. In particular, the #1 value of P31-on-references, first description (of a taxon) (Q1361864), to be able to indicate that the reference in question contained the first description and definition of a taxon is extremely valuable and important to be able to highlight for taxonomic references.

To me it therefore makes sense to propose a new drop-in replacement "reference has role" for P31-on-references, as a specific property to take over this function, which is different from the normal use of P31; and which would allow a constraint to limit acceptable values to an agreed controlled vocabulary. -- Jheald (talk) 14:30, 10 June 2018 (UTC)

Discussion[edit]

99of9
Abbe98
Achim Raschka (talk)
Brya (talk)
Dan Koehl (talk)
Daniel Mietchen (talk)
Delusion23 (talk)
Faendalimas
FelixReimann (talk)
Infovarius (talk)
Joel Sachs
Josve05a (talk)
Klortho (talk)
Lymantria (talk)
Mellis (talk)
Michael Goodyear
MPF
Nis Jørgensen
Peter Coxhead
PhiLiP
Andy Mabbett (talk)
Plantdrew
Prot D
pvmoutside
Rod Page
Soulkeeper (talk)
Strobilomyces (talk)
Tinm
Tom.Reding
Tommy Kronkvist (talk)
TomT0m
Tubezlob
Pictogram voting comment.svg Notified participants of WikiProject Taxonomy -- Jheald (talk) 14:56, 10 June 2018 (UTC)

  • Symbol support vote.svg Support. Appears to me, a relatively inexperienced Wikidata-er, to fill a niche role. If/when created, could instance of (P31) be software-restricted from being placed in references, to avoid confusion & accidental placement? —Tom.Reding (talk) 15:24, 10 June 2018 (UTC)
The software wouldn't completely prevent it, but it would register a constraint violation, and place a warning error sign next to it. Jheald (talk) 19:52, 10 June 2018 (UTC)
Pictogram voting comment.svg Comment - This is not an isolated proposal: publication in which this scientific name was established also deals with this issue, but proposes to move this to a statement. Since there are so many cases for this, and likely to become more, a separate property (making this a statement) seems well justified. The qualifier "first description (of a taxon) (Q1361864)," looks quite awkward to me (also wrong: it is the establishing of a name that matters here, not the description): if there are three references listed, will the software that reads in data be able to determine what reference this qualifier belongs to? A separate property would make this unnecessary. - Brya (talk) 17:12, 10 June 2018 (UTC)
@Brya: I don't see the two proposals as necessarily in conflict. Firstly, there are other reasons why one might want to annotate a reference: establishing a taxon is only one example. Secondly, even if there was a separate statement for when the scientific statement was established, one might still want to note of a reference that it was the originating paper, or the statement that redefined the taxon, or some other notable thing about the paper. But it would be a good thing to get rid of the current P31s.
As to your technical question, the annotation becomes part of the reference (as the present uses of P31 do). It is therefore uniquely associated with a single reference, just as much as the properties "stated in" or "volume" or "page" would be. There is no danger of crosstalk with any other reference. Jheald (talk) 19:52, 10 June 2018 (UTC)
Yes, on this last point, I had realized that the danger of software reading it out wrong was quite limited. It will still be confusing to the reader. - Brya (talk) 16:41, 11 June 2018 (UTC)
Hi Brya, I think this proposal makes queries like that a little bit more understandable. I'm not really happy with the creation of publication in which this taxon name was established (P5326). --Succu (talk) 19:10, 25 June 2018 (UTC)
Hi Succu, I understand that switching to publication in which this taxon name was established (P5326) would involve a lot of edits (some fifty thousand items being involved). But there is an even larger number of items involved which don't yet have an original publication attached (much, much larger), so it is worth taking time to reconsider before taking on that larger number. Having a property like P5326 is much more user-friendly. - Brya (talk) 05:31, 26 June 2018 (UTC)
This add (made by Jheald) would be a perfect usage of type of reference (P3865). For my concerns please see below (type <> role). --Succu (talk) 21:45, 4 July 2018 (UTC)

mathematical concept defining formula[edit]

   Not done
Descriptionmathematical formula representing the definition of a mathematical concept
Data typeMathematical expression
Domaininstances and subclasses of mathematical concept (Q24034552)
Exampleabsolute value (Q120812)
absolute value (Q120812)
See alsodefining formula (P2534)

Motivation

defining formula (P2534) allows to add the formula that defines a mathematical statement, but currently there isn't a property to add the formula that defines a mathematical concept. Malore (talk) 18:00, 10 June 2018 (UTC)

Discussion

Opensofias
Tobias1984
Micru
Arthur Rubin
Cuvwb
TomT0m
Tylas
Physikerwelt
Lymantria
Bigbossfarin
Infovarius
Helder
PhilMINT
Malore
Pictogram voting comment.svg Notified participants of WikiProject Mathematics

  • Symbol support vote.svg Support David (talk) 16:21, 14 June 2018 (UTC)
  • Symbol oppose vote.svg Oppose per Arthur, just use defining formula (P2534) - feel free to broaden its description and usage instructions to reflect that. − Pintoch (talk) 13:50, 15 June 2018 (UTC)

 Not done --Micru (talk) 16:57, 17 July 2018 (UTC)

mathematical concept definition[edit]

   Not done
Descriptiondefinition of a mathematical concept in natural language
Data typeMultilingual text (not available yet)
Domaininstance or subclass of mathematical concept (Q24034552)
Exampleabsolute value (Q120812) → "unsigned" portion of a number
absolute value (Q120812) → distance of a number from zero

Motivation

It's the same of "mathematical concept defining formula" but expressed in natural language instead of mathematical expression.

It differs from the item description because the latter should be a short sentence used only to identify the item. Another difference is that a mathematical concept can have multiple definitions.

It should contain as few symbols as possible to be comprehensible by everyone. Malore (talk) 18:27, 10 June 2018 (UTC)

Discussion

Opensofias
Tobias1984
Micru
Arthur Rubin
Cuvwb
TomT0m
Tylas
Physikerwelt
Lymantria
Bigbossfarin
Infovarius
Helder
PhilMINT
Malore
Pictogram voting comment.svg Notified participants of WikiProject Mathematics

Symbol oppose vote.svg Oppose Sorry, but for me is exactly the same as the description. The Wikipedia article fills the function of disambiguate the possible interpretations or definitions of a formula. The item exists to show the metadata about the formula, not its interpretation, if someone is curious about the possible meanings of it, they should go to the Wikipedia article. Good contributions, Ederporto (talk) 23:48, 10 June 2018 (UTC)

Also, this is so subjective. The quantity of symbols does not ensures the unserstanding, the choice of words is more dangerous than the use of symbols. Ederporto (talk) 23:53, 10 June 2018 (UTC)

Symbol oppose vote.svg Oppose this is what the description field is for. Also multilingual text (data type) does not exist. ArthurPSmith (talk) 18:35, 11 June 2018 (UTC)

@ArthurPSmith: They have differentt goals. The goal of the description field is to distinguish the item from similar ones, while the goal of this property is to give all the definitions of the concept. It is the same of "mathematical concept defining formula" (the other property I proposed) but in natural language instead of symbols. --Malore (talk) 21:41, 11 June 2018 (UTC)

Symbol oppose vote.svg Oppose Wikidata is designed to store structured information, definitions of concepts in natural language are not structured. Descriptions can be used for that. − Pintoch (talk) 13:52, 15 June 2018 (UTC)

@Pintoch: I agree with you that Wikidata should store structured content, and maybe this property is not appropriate, but I think it would serve a different function than descriptions. In my opinion, descriptions (like aliases) are for identify items, not for define them, because otherwise they would need to be sourced.--Malore (talk) 02:19, 3 July 2018 (UTC)

Symbol oppose vote.svg Oppose -- JakobVoss (talk) 06:13, 16 June 2018 (UTC)

 Not done --Micru (talk) 16:56, 17 July 2018 (UTC)

API endpoint[edit]

   Under discussion
Descriptionbase URL of a web service
Data typeURL
Domaindata set (Q1172284), web service (Q193424)
Example 1Wikidata (Q2013)https://www.wikidata.org/w/api.php (no standard protocol)
Example 2Library of Congress (Q131454) → "unknown"
qualifier described at URL (P973) https://libraryofcongress.github.io/data-exploration/
Example 3Library of Congress (Q131454)http://lx2.loc.gov:210/LCDB
qualifier protocol (P2700) Search/Retrieve via URL (Q337367)
Example 4GitHub (Q364)https://api.github.com/graphql
qualifier protocol (P2700)
qualifier described at URL (P973) https://developer.github.com/v4/
Example 5GitHub (Q364) API → https://api.github.com (no standard protocol)
qualifier file format (P2701) JavaScript Object Notation (Q2063)
Sourcewebsites of each item and third-party directories such as https://www.programmableweb.com/apis/directory
See alsoSPARQL endpoint (P5305), feed URL (P1019), URL (P2699)

Motivation

Specify API endpoints to access databases via web services. Standard protocols can be added with qualifier protocol (P2700) and link to API documentation with qualifier described at URL (P973). This property was also discussed as part of Wikidata:Property proposal/SPARQL endpoint. API endpoints can already be specified with URL (P2699) and qualifier protocol (P2700) but many endpoints don't follow a standard protocol and it's more convenient to query endpoints without qualifier. -- JakobVoss (talk) 06:58, 16 June 2018 (UTC)

Discussion

Symbol support vote.svg Support (but please don't support your own proposal - it makes it clearer to assess at a glance if there is consensus) − Pintoch (talk) 08:23, 18 June 2018 (UTC)
Symbol support vote.svg Support ArthurPSmith (talk) 14:44, 18 June 2018 (UTC)
Symbol oppose vote.svg Oppose duplicates the existing property proposed at Wikidata:Property proposal/Archive/48#P2699. I don't think it can work work as intended by the proposer ("it's more convenient to query endpoints without qualifier."). Maybe it's just that the use case isn't specified.
--- Jura 06:15, 19 June 2018 (UTC)
This makes no sense to me: you just argued the opposite at Wikidata:Property proposal/SPARQL endpoint -- JakobVoss (talk) 21:07, 20 June 2018 (UTC)
  • I don't think I did, but it's possible that I just don't understand your usecase. As you haven't given it, that seems normal. So what do you want to do with this property that you can't do with the one proposed for the same at Wikidata:Property proposal/Archive/48#P2699. Please include a sample query and application.
    --- Jura 04:05, 21 June 2018 (UTC)
Symbol support vote.svg Support - Bit sad that we already have SPARQL endpoint (P5305), because this seems to be much more versatile. Husky (talk) 19:20, 19 June 2018 (UTC)
Symbol support vote.svg Support - I actually like that we have SPARQL endpoint (P5305) as well, because I think that a SPARQL endpoint has particularly strong relevance for people working with Wikidata. But I do think this property is a useful distinction over generic URL (P2699) -- an API for data extraction is a very specific sort of URL, that it is useful to separate from other sorts of URLs the site may offer; and the API URL statements are already going to be quite complicated, with quite a lot of potential qualifiers flying around. It's a lot cleaner to be able to consider them separately, without them being muddled together with all sorts of other URLs, with all sorts of other role-specific qualifiers. Jheald (talk) 21:05, 19 June 2018 (UTC)
  • Symbol oppose vote.svg Oppose As noted above, this duplicates URL (P2699), whose documentation should be clarified. It may, though, be useful to have a new property with an $1 component. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 10:23, 20 June 2018 (UTC)
@Pigsonthewing: More accurately, it's a specialisation of P2699 rather than a duplication. This property is proposed to segregate off a specific subset of things currently loaded on the reserve backstop property URL (P2699). Jheald (talk) 11:06, 20 June 2018 (UTC)

type of water supply[edit]

   Under discussion
Representsfour different 'types of water' are specified by the data set data set (Q1172284) fountainsWVZ (Q53629101) that are provided by a fountain.
Data typeItem
Allowed valuesWater distribution pipe network (Q53633635) , own water supply (Q53634173) , groundwater (Q161598) , spring water (Q1881858)
Example 1Mosaikbrunnen (Q27229889)Water distribution pipe network (Q53633635)
Example 2Fountain at the Zurich Children's hospital (Q55170700)
Example 3Othmar-Schoeck-Foutain (Q27229997)

Description

For any fountain, it is interesting what type of water it supplies. Also, this is a column in the original data set and we would not want to loose this information upon import. (Will make type of water (Q53673519) obsolete) Ralfhauser (talk) 11:50, 16 June 2018 (UTC)

As of July 1, 2018 approx 1'200 fountains imported from the dataSet fountainsWVZ (Q53629101), i.e. ( public water well (Q53628296), water well (Q43483), drinking fountain (Q1630622)) are the type of items this property will be used on.

Discussion

Symbol support vote.svg Support This property will be useful to indicate the type of water (e.g., spring water, tap water) that we get in the data set that we would like to import from Open Data Zurich into Wikidata [https://github.com/opendata-zurich/wikidata/tree/master/fountains]. Cristina Sarasua (talk) 11:59, 16 June 2018 (UTC)

Symbol support vote.svg Support The type of water is a relevant piece of information, because e.g. groundwater has more minerals than water from the distribution mains. Matthew (talk) 12:18, 16 June 2018 (UTC)

Symbol support vote.svg Support I'm working for the City of Zurich and think that this property would be really useful +1 Marco Sieber (talk) 12:18, 16 June 2018 (UTC)

Pictogram voting comment.svg Comment The examples as supplied are not valid - please follow the example pattern shown with both a subject item and (for item datatype) a value item for each example. ArthurPSmith (talk) 14:47, 18 June 2018 (UTC)
Sorry for putting the allowed values into the examples. Is it better now ?
Thanks - You don't need all the text - I've adjusted it to our standard example format. ArthurPSmith (talk) 18:06, 23 June 2018 (UTC)

Pictogram voting comment.svg Comment This is type of water supply, rather than type of water, I think. It seems very specific. All the best: Rich Farmbrough10:31, 20 June 2018 (UTC).

It seems to be kind of both, but I have no problem calling the property "type of water supply" if the community prefers
  • Symbol oppose vote.svg Oppose. I don't get it. The proposal is badly formatted. Thierry Caro (talk) 11:12, 22 June 2018 (UTC)
Hi Thierry, with the help of Arthur, I hope it is now clearer. If not, what points would you like to have expanded ?  – The preceding unsigned comment was added by Ralfhauser (talk • contribs) at 12:24, June 25, 2018‎ (UTC).
@Thierry Caro: ArthurPSmith (talk) 18:26, 25 June 2018 (UTC)
  • Is this only for fountains? It could be used for entire cities, for instance. What about that? Thierry Caro (talk) 09:57, 2 July 2018 (UTC)

Symbol support vote.svg Support This property might be interesting for some users, as different water types have different tastes. Axel (talk) 08:57, 29 June 2018 (UTC)

Pictogram voting comment.svg Comment it would be good to have:

  • a description
  • other examples
  • the type of item this property is expected to be used on

Pintoch (talk) 17:48, 2 July 2018 (UTC)

@Ralfhauser: removing the "ready" flag - feel free to add it back once the proposal template has been completed − Pintoch (talk) 14:02, 5 July 2018 (UTC)

@Pintoch: is it now better and "ready" can be added back?

Harmonized System Code[edit]

Descriptioncode in the Harmonized System for a category of object traded internationally
RepresentsHarmonized System Code (Q55237506)
Data typeString
Domainobject (Q488383)
Allowed valuesregex: \d{2}(\d{2}){0,2}
Example 1beer (Q44) → 2203
Example 2oscilloscope (Q174320) → 903020
Example 3cigarette (Q1578) → 240220
Example 4citrus fruit (Q2574750) → 0805
SourceUN Comtrade Commodity Classifications (also see Harmonized Commodity Description and Coding Systems (HS))
Number of IDs in source~39000
Expected completenesseventually complete (Q21873974)

Motivation

Codes within the Harmonized System are used globally to classify goods, products and objects for customs purposes when they are traded internationally between country borders. The Harmonized System is a taxonomy where each level in the taxonomoy is assigned a code. The World Customs Organization maintains this system on behalf of the 200+ member countries, so the applicability of these codes is very global and widely adopted. Dhx1 (talk) 14:46, 28 June 2018 (UTC)

Discussion

  • Pictogram voting comment.svg Comment Since it is described as a "category" or to "classify" things, can you describe whether you expect it to satisfy the uniqueness constraint we expect of identifiers (there should never be two items with the same value)? ArthurPSmith (talk) 17:56, 28 June 2018 (UTC)
  • Pictogram voting comment.svg Comment @ArthurPSmith: I forgot that rule about external-id! I've changed the data type to string instead as this is more appropriate. Dhx1 (talk) 01:06, 30 June 2018 (UTC)
  • Symbol support vote.svg Support Ok, this makes sense then, thanks. ArthurPSmith (talk) 01:44, 30 June 2018 (UTC)
  • Symbol support vote.svg Support David (talk) 09:29, 30 June 2018 (UTC)

@ديفيد عادل وهبة خليل 2, ArthurPSmith, Dhx1: ✓ Done: Harmonized System Code (P5471). − Pintoch (talk) 08:05, 17 July 2018 (UTC)

reference properties[edit]

   Under discussion
Descriptionreference properties
Data typeProperty
Domainqualifier for citation needed constraint (Q54554025)
Allowed valuesproperties from {{Reference properties}}
Example 1social classification (P3716)citation needed constraint (Q54554025) → Reference properties → stated in (P248), reference URL (P854)
Example 2MISSING
Example 3MISSING
Planned useadd the qualifier to all citation needed constraint (Q54554025) usages
Robot and gadget jobsconstraints check bots and tools are need to be improved

Motivation

see Wikidata_talk:WikiProject_property_constraints#New constraint type: citation needed. — Ivan A. Krestinin (talk) 21:52, 29 June 2018 (UTC)

Discussion

  • What about all other properties including introduced in the future? — Ivan A. Krestinin (talk) 21:07, 1 July 2018 (UTC)
    • If the reference can be any property with an external id, the list would get endless. Not sure if the constraint would be used for properties were "imported from" is sufficient.
      --- Jura 15:47, 2 July 2018 (UTC)
  • Symbol oppose vote.svg Oppose Honestly, I'm not enthusiastic about this approach. We would repeat the same lists of reference properties in almost all the properties with the citation needed constraint (Q54554025). This model would be terribly redundant and hard to maintain. The mandatory reference properties could be defined once in one place; for example, as a statement on citation needed constraint (Q54554025). --abián 12:50, 1 July 2018 (UTC)
  • Different properties can have different requirements to sources. For example "imported from" is good for external identifier property, but is not enough for many others. — Ivan A. Krestinin (talk) 21:07, 1 July 2018 (UTC)
  • From my point of view, external identifiers directly shouldn't have this constraint since they're references by themselves, their verifiability is inherent. References for external identifiers should be possible but not mandatory. --abián 23:40, 1 July 2018 (UTC)
  • I did not suggest to make such constraints mandatory. But its are needed to control data integrity, describe completeness of dataset, fix vandalism and etc. One of interesting cases is external ID property without formatter URL. — Ivan A. Krestinin (talk) 08:23, 2 July 2018 (UTC)
  • Symbol support vote.svg Support I'm sympathetic to Abián's approach above, but I think in the case of constraints it actually is useful to have them explicitly defined on each property, even if that's a lot of duplication. So I think this property would be useful. ArthurPSmith (talk) 17:12, 2 July 2018 (UTC)
  • Symbol support vote.svg Support let's see how it goes.
    --- Jura 12:07, 3 July 2018 (UTC)
  • Symbol oppose vote.svg Oppose all statements except of external identifiers should have a reference with either stated in (P248) or reference URL (P854). There is no need to repeat that on each property page. --Pasleim (talk) 16:35, 3 July 2018 (UTC)
  • Symbol oppose vote.svg Oppose per Abián. If we are making changes to this constraint, I would expect that such properties is defined globally (for instance as part of the WikibaseQualityConstraints configuration), not individually for each use of the property constraint. − Pintoch (talk) 16:29, 4 July 2018 (UTC)
  • Symbol oppose vote.svg Oppose in the way it is currently proposed this seems to be redundant. We're probably better of defining what a good citation is (stated in + link + timestamp?) and a bad one (imported from Wikimedia project (P143) / Wikimedia import URL (P4656)) and use that for the next iteration of this constraint. Multichill (talk) 19:04, 4 July 2018 (UTC)

property definition in SPARQL[edit]

   Under discussion
DescriptionSPARQL definition for a possible calculated property. Format: include ?item and ?value
Data typeString
Allowed valuesmust include ?item and ?value
Example
  • ISBN-13 without dashes (Q55237971)?item wdt:P212 ?p212 . BIND(REPLACE(?p212, "-", "") AS ?value)
  • <country of birth (new item)> → ?item wdt:P19/wdt:P17 ?value
  • <year of birth (new item)> → ?item wdt:P569 ?dob . BIND(YEAR(?dob) as ?value)

Motivation

If the feature even becomes available, these can be used for definition. In the meantime, these can be used to build queries.
--- Jura 06:06, 30 June 2018 (UTC)

Discussion

Pictogram voting comment.svg Comment I think this idea is very interesting. I have two questions regarding this model:

  1. Is it possible to get the ISBN-13 without dashes (Q55237971) value of DSM-5 (Q3064664), for example, in Wikidata Query Service by using the Sandbox-String (P370) in ISBN-13 without dashes (Q55237971), at this time? Or is it required an external tool to build queries?
  2. As this property stores only string values, it will be difficult to find available calculated properties from the original properties, such as ISBN-13 (P212) in this case. Isn't there a need for a property or a qualifier to specify which properties are used to calculate?

Thank you, --Okkn (talk) 04:56, 6 July 2018 (UTC)

  • Thanks for your interesting questions.
    For (1), I think it's possible to do this, either similar to the (indirect) queries on Property_talk:P4316#Sample_query, or (after editing) with the query built through the formatter url on specific items. Maybe there is also some way to construct the queries directly (I would be interested to learn about).
    For (2), I had thought about this too. Eventually, I think we should also link the properties being used in one way or the other from Q55237971.
    --- Jura 05:11, 6 July 2018 (UTC)
    • Symbol support vote.svg Support Ok, I also want this proeprty. But I'm not sure the name is appropriate. What you call "calculated property" is not a Wikidata property (Q18616576). The name of "property definition" gives the impression that the subject of this property is Wikidata property (Q18616576). Isn't the "calculated property" something like a formatter? Of course I understand it is not restricted to string data type... --Okkn (talk) 15:49, 6 July 2018 (UTC)
    • It's currently mentioned at Help:Data_type#Calculated_property (disclaimer: I added it). Supposedly, there are various ways of implementing this: maybe as some shortcut when writing queries or triples directly generated from existing properties. In any case, I think the definition would need to be stored some place. Initially, I thought this could be added to property entities and labeled "calculated property", but there might be several properties that could apply. So the current proposal. If there are better labels, that would be good. We can also change it later if it's problematic. Maybe "SPARQL" should already be in the label.
      --- Jura 07:27, 7 July 2018 (UTC)
  • Symbol oppose vote.svg Oppose I see no advantage for this property compared to just adding this code snipped to a SPARQL query help page. --Pasleim (talk) 05:53, 8 July 2018 (UTC)
  • Pictogram voting comment.svg Comment I think this would benefit much more upstream discussion with the community and the dev team. If there is no commitment from WMDE to integrate that somehow, this property might not be desirable: users could expect that it is reflected in the Wikidata query service, or it might encourage people to run wasteful SPARQL queries on their own to simulate that functionality. What is really the problem you are trying to solve? More examples of use cases should be gathered. For instance, the requirement that the SPARQL fragment uses both "?item" and "?value" seems to be made up for your own needs, but would not necessarily be generic enough for other use cases. There is a lot of previous work on rule-based inference in RDF stores, which are generally more principled. Marking as not ready. − Pintoch (talk) 13:27, 8 July 2018 (UTC)
    • If you prefer "?s" and "?o" as variables, that is fine for me. I think in Wikidata, we generally uses "?item" (and possible "?value" for "?o"). If there are other suggestions, I'd be most interested. This is the first time I hear that we should discourage people to use SPARQL.
      --- Jura 13:38, 8 July 2018 (UTC)
    • Pictogram voting comment.svg Comment I have tried writing a "wasteful" SPARQL query, which generates a SPARQL query to resolve a calculated property. --Okkn (talk) 15:23, 8 July 2018 (UTC)
  • Pictogram voting comment.svg Comment @Lymantria: There are several unresolved issues in the above discussion, I don't see why you marked as ready? I've removed that status. The concerns I have are: (1) the name of this proposed property is confusing, (2) I would like to see a handful more examples of how it would be used (are we setting a standard for the parameter names as suggested in the description? Also see Pintoch's comment above), including issues of handling more complex calculations that may involve qualifiers etc. (if that is part of this proposal) (3) Pasleim's comment above was responded to by Jura with an oblique reference (not directly related to this discussion at all, other than constructing a sparql query in SPARQL). I'd like to see an actual concrete example where that could be helpful for this purpose - is there some category of calculated properties like this that you might search across several of them in such a way that it would be helpful to have SPARQL do the construction, rather than just cutting and pasting in the code for one calculated property you are looking at? If it's just the latter that would be used, then I think better to paste such SPARQL code on the discussion page of the item in question, as an example of how you would do it in wikidata. ArthurPSmith (talk) 18:10, 13 July 2018 (UTC)
  • @Okkn: I updated the property name above given the preceding comment. I hope this is still acceptable to you.
    Not sure what to add say to the suggestion to store data in an unstructured way on talk pages .. obviously, some users do prefer talk pages and hardly ever venture into adding structured data.
    --- Jura 05:39, 15 July 2018 (UTC)
    • Okkn said "The name of "property definition" gives the impression that the subject of this property is Wikidata property (Q18616576).", which was my main concern - adding the "in SPARQL" is helpful, but I think the word "property" needs to be removed since the domain is not properties but items. Just "definition in SPARQL" would probably be fine. I really would like to see a concrete example where you think you could make use of this within a SPARQL context. Structured databases are useful when you need a machine to do stuff with them, but I have a hard time seeing what a machine would do with the values of this property, that's why a real example would be important. ArthurPSmith (talk) 14:17, 16 July 2018 (UTC)

abuse filter ID[edit]

   Under discussion
Descriptionnumber of an abuse filter related to this property
RepresentsWikipedia:Edit filter (Q4582485)
Data typeExternal identifier
Template parameter|filter= in {{Property documentation}}
Domainproperties
Allowed values[1-9]\d{0,2}
Example 1Twitter username (P2002)96
Example 2place of marriage (P2842)87
Example 3sex or gender (P21)78
Example 4sex or gender (P21)67
Example 5software version (P348)61
Sourcehttps://www.wikidata.org/wiki/Special:AbuseFilter
Number of IDs in source103
Expected completenesseventually complete (Q21873974)
Formatter URLhttps://www.wikidata.org/wiki/Special:AbuseFilter/$1

Motivation

To have a better organization of the filters and to stop using {{Property documentation}} parameters. abián 11:12, 30 June 2018 (UTC)

Discussion

  • Symbol oppose vote.svg Oppose I think it would be better to model this by creating an item for each filter, and using properties to describe its scope and purpose. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 12:38, 2 July 2018 (UTC)
    • I like your idea too. :-) --abián 13:08, 2 July 2018 (UTC)
  • Pictogram voting comment.svg Comment I think the goal (and my wish) is to turn off abuse filters specific to certain properties as soon as contraints are well integrated with recent changes and input interface. Then, we won't need them anymore. Matěj Suchánek (talk) 08:50, 3 July 2018 (UTC)
    • Sadly, I'm not sure the development team wants the quality extensions to prevent edits or to show warnings as abuse filters do (and, as far as I know, there are no signs to believe they're going to implement these possibilities in the near future), but that's my wish as well. Nonetheless, I also admit that the community isn't managing constraints well: endless lists of exceptions, unjustified constraints to simply generate reports (instead of using the Query Service or Listeria with that purpose), additions and removals of constraints by editors who individually consider the current number of violations too high or too low, etc. --abián 09:59, 3 July 2018 (UTC)
  • Pictogram voting comment.svg Comment There don't seem to be plenty of these. Most aren't specific to properties and some not even viewable by people like me (e.g. Special:AbuseFilter/5).
    --- Jura 11:43, 9 July 2018 (UTC)

perfume note[edit]

   Under discussion
Descriptionthe note of a perfume
Representsno label (Q55315285)
Data typeItem
Template parameter"notes" in en:Template:Infobox Fragrance, "notes" in fr:Modèle:Infobox Parfum
Domainperfumes
Example 1Habanita (Q3125263)vanilla (Q13241)
Example 2no label (Q3393810)Coriandreae (Q15513308)
Example 3Femme (Q3068231)Coriandreae (Q15513308)
Planned useHarvesting from fragrance infoboxes
Expected completenesseventually complete (Q21873974)

Motivation

Improving perfume support. Next step is top_note, heart_note and base_note, stored in the en infobox. Teolemon (talk) 15:24, 1 July 2018 (UTC)

Discussion

  • Symbol support vote.svg Support. Perhaps the value items should be "instances of note"? Also potentially useful for beers/wines etc. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 12:56, 2 July 2018 (UTC)
    • Yes, good idea :-) Teolemon (talk) 21:10, 6 July 2018 (UTC)

CJKV variant character[edit]

DescriptionEquivalent forms of Han characters used in different regions
RepresentsZ-variant (Q8062847)
Data typeItem
DomainCJKV character
Allowed valuesinstance of CJK character (Q53764732)
Example 1(Q54879263)("") → 擧 ("") (writing system (Q8192): Kyūjitai (Q1147857))
Example 2(Q54879263)("") → 举 ("") (writing system (Q8192): simplified Chinese characters (Q185614))
Example 3(Q54879263)("") → 舉 ("") (writing system (Q8192): traditional Chinese characters (Q178528))
Example 4(Q54872784)("") → 溫 ("") (writing system (Q8192): traditional Chinese characters (Q178528), Kyūjitai (Q1147857))
Example 5(Q54872914)("") → 汉 ("") (writing system (Q8192): simplified Chinese characters (Q185614))
Example 6(Q54879672)("") → 杀 ("") (writing system (Q8192): simplified Chinese characters (Q185614))
Example 7(Q54881859)("") → 巢 ("") (writing system (Q8192): Kyūjitai (Q1147857))
SourceWikipedia:Z-Variant; Unicode (kZVariant): https://www.unicode.org/reports/tr38/index.html#kZVariant
Planned useLinking corresponding shinjitai/kyūjitai/traditional Chinese/simplified Chinese/Variant Chinese characters with one another.
Expected completenesseventually complete (Q21873974)
See alsotraditional Chinese characters (Q178528),simplified Chinese characters (Q185614),Kyūjitai (Q1147857),Shinjitai (Q1055887),Extended shinjitai (Q5421905),Hanja (Q485619),Chu Nom (Q875344),Xin Zixing (Q8044489),Variant Chinese character (Q837611),Sawndip (Q923677)

Abstract

The proposed property is designed to link equivalent Han characters used in different regions that are encoded under different codepoints in Unicode. It is inspired by the kZVariant property present in the Unihan database but attempts to improve on it by describing how the characters are related to one another.

Motivation

As of July 2018, up to 1016 items with the description "CJK (hanzi/kanji/hanja) character" have been created. Upon closer inspection, most of these characters belong to the set of Kyōiku kanji and are unique. However, two Han characters which are semantically related, (Q54552723)("") and (Q3594925)("") have been created with no indication of their relationship with one another. The former is a Japanese shinjitai while the latter is a simplified Chinese character, both of which are related by their kyūjitai/traditional form "". A property is needed to indicate this relationship. KevinUp (talk) 01:02, 3 July 2018 (UTC)

Discussion

  • Symbol support vote.svg Support Variant Han characters should be linked to each other. Okkn (talk) 18:16, 3 July 2018 (UTC)
  • @Was a bee, Deryck Chan, NMaia, VIGNERON, Stevenliuyi: Any thoughts? --Okkn (talk) 18:29, 3 July 2018 (UTC)
  • Symbol support vote.svg Support BTW, I noticed that the kyūjitai/traditional Chinese character “樂” (U+6A02) has the same form as hanja U+F914, U+F95C and U+F9BF. The three hanja characters are actually one character with different pronunciations (heteronym (Q875690)). Should we create one item or four different items in this case? If we create separate items, should we also use this property to link them? --Stevenliuyi (talk) 22:06, 3 July 2018 (UTC)
    • If separated four items were created for 樂, they can be linked using this property. However, at this time, I think we don't have to separate them. --Okkn (talk) 05:40, 4 July 2018 (UTC)
      • Hi. "" is a rare exception of a single character being split into four codepoints due to different pronunciations. The codepoints U+F914, U+F95C and U+F9BF belong to CJK Compatibility Ideographs (Q2493848). Unfortunately, it is not possible to create new items for them because the compatibility forms will convert back to its main ideograph after being created. An example of how compatibility forms are dealt with can be seen here: (Q54879672) and (Q54872914). KevinUp (talk) 11:58, 4 July 2018 (UTC)
  • Tentative Symbol support vote.svg Support, and I think the qualifier should be writing system (P282)? Deryck Chan (talk) 22:58, 3 July 2018 (UTC)
  • Symbol support vote.svg Support Support this. By the way, all Han characters have counterpart in different languages? Although I don't know well about diversity of Han characters, if there are characters which exist only in certain language, how about using, for example, "no equivalent" to show such fact. --Was a bee (talk) 22:07, 4 July 2018 (UTC)
  • Symbol support vote.svg Support Jc86035 (talk) 11:42, 6 July 2018 (UTC)

@KevinUp, Stevenliuyi, Deryck Chan, Was a bee, Jc86035: ✓ Done: CJKV variant character (P5475) --Okkn (talk) 17:47, 18 July 2018 (UTC)

GlyphWiki ID[edit]

   Done. GlyphWiki ID (P5467) (Talk and documentation)
Descriptionidentifier of GlyphWiki, in which glyphs of Han characters are managed
RepresentsGlyphWiki (Q28684738)
Data typeExternal identifier
Domaininstance of Chinese character (Q53764738)
Example 1(Q4025820)u4e00-j
Example 2(Q54872914)ufa47 (writing system (P282): traditional Chinese characters (Q178528), Kyūjitai (Q1147857))
Example 3(Q54872914)u6f22-j (writing system (P282): Shinjitai (Q1055887))
Example 4(Q54879255)ufa38 (writing system (P282): traditional Chinese characters (Q178528), Kyūjitai (Q1147857))
Example 5(Q54879255)u5668 (writing system (P282): Shinjitai (Q1055887))
Sourcehttp://en.glyphwiki.org/wiki/GlyphWiki:MainPage
Number of IDs in sourcemore than 310,000
Expected completenessalways incomplete (Q21873886)
Formatter URLhttp://en.glyphwiki.org/wiki/$1

Motivation

Recently we have created stroke count (P5205) and radical (P5280), and now we are trying to represent Han characters as items. However, glyphs of Han characters are sometimes different by writing systems, by countries, or by fonts. GlyphWiki is a wiki of glyph (Q36975), and every one can use freely(, although public domain license is not explicitly presented). By linking to this site, other people will be able check which glyph the stroke count (P5205) or radical (P5280) claim describes. --Okkn (talk) 07:18, 6 July 2018 (UTC)

Discussion

@KevinUp: Do you have any thoughts? --Okkn (talk) 16:38, 6 July 2018 (UTC)

Symbol support vote.svg Support At the moment we are unable to represent the glyph shape of Han characters in data form, hence a property is needed for it. Although alternatives such as a system using Ideographic Description Characters exist, where Han characters can be broken down and represented by their constituent characters, this system is prone to errors and not all characters can be represented by it. By linking to GlyphWiki, users can check the composition of each character and visually identify the difference between glyphs used in different regions. KevinUp (talk) 18:03, 6 July 2018 (UTC)
  • Symbol support vote.svg Support David (talk) 14:50, 7 July 2018 (UTC)

@KevinUp, ديفيد عادل وهبة خليل 2, Okkn: ✓ Done: GlyphWiki ID (P5467). − Pintoch (talk) 07:48, 17 July 2018 (UTC)

@Pintoch: Thanks for creating this new property. Now we can start using it. KevinUp (talk)

artist-info artist ID[edit]

DescriptionIdentifier in the artist-info artist database of exhibition records
Representsartist-info (Q55344434)
Data typeExternal identifier
Domainhuman (Q5)
Allowed values[0-9]\d+
Allowed unitsno units
Example 1Richard Serra (Q321245)31766
Example 2Otto Dix (Q153104)8201
Example 3Marina Abramović (Q47496)73
Sourcehttps://www.artist-info.com
Planned useAdding artist-info artist Id to artist Statements
Number of IDs in source182800
Expected completenessalways incomplete
Formatter URLhttps://www.artist-info.com/users/artsitpublicpage/$1
Robot and gadget jobsNo bots or gadgets
See alsoRKDartists ID (P650), ULAN ID (P245), Artnet artist ID (P3782), artist-info curator ID (P5488)

Motivation

This new Wikidata property for Wikidata property for authority control for people (Q19595382) would allow a better coverage of the arts (Q2018526).
Identifying artists, curators and exhibition places ('location') through exhibition records has the quality of a reliable authority control.
As exhibitions are fundamental to the discourse in Modern and Contemporary Art, making them searchable with artist-info.com enables new possibilities for research and analytics.
It is different to authority control for people based on auction, library, dictionary (e.g. ThiemeBecker, Bénézit, Oxford) or artwork collection records (museums).
We are documenting with artist-info.com solo- and group-exhibitions at exhibition venues (galleries, museums, non-profit) with all participating artists and if possible with the curator from 1880 up to the present, worldwide.
Our sources are exhibition catalogs, archives, and ephemera. The interactive exhibition histories of artist-info show the relational structure and profiles of artists, curators and exhibition venues alike.
We include links to Wikipedia pages of artists, curators and locations on the related artist-info pages (10.431 as of July 8, 2018) for more biographical information as well as an authority control link to VIAF (includes Wikidata) and WorldCat (VIAF or LCCN based) for library holding information (14.108 as of July 8, 2018).
We publish our groundbreaking research based on exhibition records on www.artist-info.com/blog/
The database was started 1993 and first published on the Internet in November 1996. You find as of July 8, 2018: 182.800 artists, 7.504 curators, 12.285 venues in 1.500 cities in 163 countries, 212.501 exhibitions (680.844 edges).
Access to all artist-info.com artist, curator and exhbition venue pages is free (no registration, no charges).
THHAP (talk) 10:07, 8 July 2018 (UTC)

Discussion

  • @Pintoch: Thank you for your advice. Example 1, 2, 3 is corrected. THHAP (talk) 12:12, 18 July 2018 (UTC)

@ديفيد عادل وهبة خليل 2, THHAP, Pintoch: ✓ Done: artist-info artist ID (P5489). − Pintoch (talk) 09:01, 19 July 2018 (UTC)

artist-info curator ID[edit]

DescriptionIdentifier in the artist-info curator database of exhibition records
Representsartist-info (Q55344434)
Data typeExternal identifier
Domainhuman (Q5)
Allowed values[0-9]\d*
Allowed unitsno units
Example 1Harald Szeemann (Q115816)220302
Example 2Alfred H. Barr (Q711362)246840
Example 3Klaus Biesenbach (Q87928)220614
Sourcehttps://www.artist-info.com
Planned useAdding artist-info curator Id to artist-info (Q55344434) Statements.
As Identifier property on a Wikidata curator page
Number of IDs in source7504
Expected completenessalways incomplete
Formatter URLhttps://www.artist-info.com/users/curatorpublicpage/$1
Robot and gadget jobsNo bots or gadgets
See also

Motivation

This new Wikidata property for Wikidata property for authority control for people (Q19595382) would allow a better coverage of the arts (Q2018526).
Identifying artists, curators and exhibition places ('location') through exhibition records has the quality of a reliable authority control.
As exhibitions are fundamental to the discourse in Modern and Contemporary Art, making them searchable with artist-info.com enables new possibilities for research and analytics.
It is different to authority control for people based on auction, library, dictionary (e.g. ThiemeBecker, Bénézit, Oxford) or artwork collection records (museums).
We are documenting with artist-info.com solo- and group-exhibitions at exhibition venues (galleries, museums, non-profit) with all participating artists and if possible with the curator from 1880 up to the present, worldwide.
Our sources are exhibition catalogs, archives, and ephemera. The interactive exhibition histories of artist-info show the relational structure and profiles of artists, curators and exhibition venues alike.
We include links to Wikipedia pages of artists, curators and locations on the related artist-info pages (10.431 as of July 8, 2018) for more biographical information as well as an authority control link to VIAF (includes Wikidata) and WorldCat (VIAF or LCCN based) for library holding information (14.108 as of July 8, 2018).
We publish our groundbreaking research based on exhibition records on www.artist-info.com/blog/
artist-info database was started 1993 and first published on the Internet in November 1996. You find as of July 8, 2018: 182.800 artists, 7.504 curators, 12.285 venues in 1.500 cities in 163 countries, 212.501 exhibitions (680.844 edges).
Access to all artist-info.com artist, curator and exhbition venue pages is free (no registration, no charges).
THHAP (talk) 10:14, 8 July 2018 (UTC)

Discussion

*@Pintoch: Thank you for your advice. Example 1, 2, 3 is corrected. THHAP (talk) 12:11, 18 July 2018 (UTC)

@ديفيد عادل وهبة خليل 2, THHAP, Pintoch: ✓ Done: artist-info curator ID (P5488). − Pintoch (talk) 08:59, 19 July 2018 (UTC)

artist-info location ID[edit]

DescriptionIdentifier in the artist-info location database of exhibition records
Representsartist-info (Q55344434)
Data typeExternal identifier
DomainCommercial, non-commercial, institutional Entity code (Q?), Wikidata property related to art (Q27918607)
Allowed values[0-9]\d+
Allowed unitsno units
Example 1Kestnergesellschaft (Q565375)56
Example 2White Columns (Q12072840)2110
Example 3Louisiana Museum of Modern Art (Q1410617)5929
Example 4Gallery van Diemen (Q28835258)19393
Sourcehttps://www.artist-info.com
Planned useAdding artist-info location Id to artist-info (Q55344434) Statements.
As Identifier property on a Wikidata exhibition venue page (Gallery, Museum, Non-Profit, Collector/Foundation).
Number of IDs in source12285
Expected completenessalways incomplete
Formatter URLhttps://www.artist-info.com/users/publicpagegallery/$1, https://www.artist-info.com/users/publicpagemuseum/$1, https://www.artist-info.com/users/publicpagenonprofit/$1, https://www.artist-info.com/users/publicpagecollector/$1
Robot and gadget jobsNo bots or gadgets
See alsoRKDartists ID (P650), ULAN ID (P245), Artnet artist ID (P3782), artist-info curator ID (P5488), artist-info artist ID (P5489)

Motivation

This new Wikidata property for authority control for art location (art gallery, art museum, art non-profit, foundation) (Q?) would allow a better coverage of the arts (Q2018526).
Identifying artists, curators and exhibition places ('location') through exhibition records has the quality of a reliable authority control.
As exhibitions are fundamental to the discourse in Modern and Contemporary Art, making them searchable with artist-info.com enables new possibilities for research and analytics.
It is different to authority control for people based on auction, library, dictionary (e.g. ThiemeBecker, Bénézit, Oxford) or artwork collection records (museums).
We are documenting with artist-info.com solo- and group-exhibitions at exhibition venues (galleries, museums, non-profit) with all participating artists and if possible with the curator from 1880 up to the present, worldwide.
Our sources are exhibition catalogs, archives, and ephemera. The interactive exhibition histories of artist-info show the relational structure and profiles of artists, curators and exhibition venues alike.
We include links to Wikipedia pages of artists, curators and locations on the related artist-info pages (10.431 as of July 8, 2018) for more biographical information as well as an authority control link to VIAF (includes Wikidata) and WorldCat (VIAF or LCCN based) for library holding information (14.108 as of July 8, 2018).
We publish our groundbreaking research based on exhibition records on www.artist-info.com/blog/
artist-info database was started 1993 and first published on the Internet in November 1996. You find as of July 8, 2018: 182.800 artists, 7.504 curators, 12.285 venues in 1.500 cities in 163 countries, 212.501 exhibitions (680.844 edges).
Access to all artist-info.com artist, curator and exhbition venue pages is free (no registration, no charges).
THHAP (talk) 10:17, 8 July 2018 (UTC)

Discussion

*@Pintoch: Thank you for your advice. Example 1, 2, 3, 4 is corrected. THHAP (talk) 12:10, 18 July 2018 (UTC)

@ديفيد عادل وهبة خليل 2, THHAP, Pintoch: ✓ Done: artist-info location ID (P5490). − Pintoch (talk) 09:03, 19 July 2018 (UTC)

NATO Stock Number[edit]

   Under discussion
Description13-digit numeric code identifying an object used by NATO member country armed forces
RepresentsNATO Stock Number (Q357602)
Data typeExternal identifier
DomainQ17553950
Allowed values\d{4}-\d{2}-\d{7}
Example 1desk (Q1064858)7110-01-482-1192
Example 2bed (Q42177)7105-01-482-1206
Example 3TACLANE-FLEX, 1Gbps (Q55236915)5810-01-659-9037
Example 4M1 Abrams (Q173684)2350-01-087-1095
Example 5Super Hornet (Q223318)1510-01-578-1741
Example 6Super Hornet (Q223318)1510-66-158-1214
Example 7B-2 Spirit (Q180285)1510-01-514-6555
Example 8F-35A Lightning II (Q17519093)1510-01-660-1118
Example 9EA-18G Growler (Q890185)1510-01-648-1513
Example 10MQ-1C Grey Eagle (Q387188)1550-01-619-2239
Example 11MQ-1C Grey Eagle (Q387188)1550-01-648-0888
Example 12MQ-9 Reaper (Q816695)1550-15-193-5739
SourceVarious online databases, manufacturer specification sheets and websites
https://www.nsncenter.com/
External linksUse in sister projects: [de][en][es][fr][it][ja][ko][nl][pl][pt][ru][sv][vi][zh][commons][species][wd].
Expected completenesseventually complete (Q21873974)
Formatter URLhttps://www.nsncenter.com/NSN/$1

Motivation

NATO Stock Numbers (NSNs) are used by NATO member country armed forces for identifying materiel (equipment, spare parts, components, etc) which can be ordered through military supply chains. With an NSN, public databases can be searched to retrieve manufacturer details, pricing, information on hazardous substances, some technical specification details and numerous other details. Dhx1 (talk) 13:09, 10 July 2018 (UTC)

Discussion

description of glyph[edit]

   Under discussion
Descriptiondescription of a specific glyph.
Data typeMultilingual text (not available yet)
Domainitem if individual characters are represented by items
Example 1🔗 (Q55522849) → two or three interlocked chain links (English)
Example 2MISSING
Example 3MISSING
Robot and gadget jobsNo

Motivation

This provides a visual description of a specific symbol. GZWDer (talk) 12:29, 14 July 2018 (UTC)

Discussion

  • Pictogram voting comment.svg Comment multilingual text does not exist as a datatype. Why wouldn't you just put this into the description of the item? ArthurPSmith (talk) 13:59, 16 July 2018 (UTC)
  • For example the character "⌛" can be described as "an hourglass", but it is clearly not suitable for description as it is confusing. See wikt:Wiktionary:Votes/2016-08/Description.--GZWDer (talk) 17:10, 16 July 2018 (UTC)
    • I don't see that that discussion supports your claim that it is "clearly not suitable for description". The discussion seemed to be on the issue of senses, not of describing the glyph, and of course it was in Wiktionary, not Wikidata so the meaning of "description" is not clearly identical. In Wikidata we have now 🍑 (Q55424107) which is described as "peach emoji" in English. "hourglass emoji" or "glyph in the form of an hourglass" seems fine as descriptions to me. That's what the description field is for, and we shouldn't be adding new properties that serve essentially the same purpose. ArthurPSmith (talk) 17:59, 17 July 2018 (UTC)
  • Symbol oppose vote.svg Oppose. A natural-language text description is not structured data. --Yair rand (talk) 18:20, 16 July 2018 (UTC)
  • Symbol oppose vote.svg Oppose per Yair. Mahir256 (talk) 20:36, 17 July 2018 (UTC)

Unicode block[edit]

   Under discussion
DescriptionUnicode block that a character is in
RepresentsUnicode block (Q3512806)
Data typeItem
Domainitem for Unicode characters
Example 1🔗 (Q55522849)Miscellaneous Symbols and Pictographs (Q2494135)
Example 2(Q3594993)CJK Unified Ideographs (Q994386)
Example 3MISSING
Expected completenesseventually complete (Q21873974)
Robot and gadget jobsYes

Motivation

This information is important for individual Unicode characters.GZWDer (talk) 12:37, 14 July 2018 (UTC)

Discussion

Symbol support vote.svg Support Mahir256 (talk) 23:00, 14 July 2018 (UTC)

artist-info exhibition ID[edit]

   Under discussion
DescriptionIdentifier in the artist-info database for exhibition records
Data typeExternal identifier
DomainWikidata property for authority control for people (Q19595382), Wikidata property related to art (Q27918607)
Allowed values[a-zA-Z0-9-]+-Id[0-9]\d+
Allowed unitsno units
Example 1Armory Show (Q688909)69th-Regiment-Armory-Id363342
Example 2Live in your Head: When Attitudes Become Form (Q21661998)Kunsthalle-Bern-Id317396
Example 3This Is Tomorrow (Q3018307)Whitechapel-Art-Gallery-Id327043
Sourcehttps://www.artist-info.com, artist-info (Q55344434)
Planned useAdding artist-info location Id to artist-info (Q55344434) Statements.
For 79 of 528 exhibitions, which are related to art-exhibition (Q667276), artist-info knows all participating artists, which the wikidata entry doesn't.
As Identifier property on a Wikidata art-exhibition page
Example: Adding artist-info exhbition ID as Identifier to Armory Show (Q688909), to find all artists of this seminal exhibition and the many hundred other exhibitions 1880 – today of these artists.
Number of IDs in sourceartist-info.com exhibition database knows 212.560 (54.395 group-exhibitions, 158.165 solo-exhibitions) always with the complete list of participating artists, from 1880 up to the present, in 12.292 venues, in 1.500 cities in 163 countries.
Expected completenessalways incomplete
Formatter URLhttps://www.artist-info.com/users/exhibition/$1-$2
Robot and gadget jobsNo bots or gadgets
See alsoartist-info.com is the only database which provides the key information 'all artists/exhibition' for art exhibitions. Examples for artists are

Motivation

See as well artist-info artist ID, artist-info curator ID, artist-info location ID proposal motivation.
As artist-info.com is the only database which 'all artists/exhibition' for art exhibitions I would like to add this property proposal in addition to artist-info artistID, curator ID, and location ID, too.
Not only that this informatin is missing in artist CVs, gallery, museum, or non-profit exhibition histories, the unique artist-info.com advantage is our artist-database, identifying artists always with her/his ID regardless which exhibition.
Access to all artist-info.com artist, curator and exhbition venue pages is free (no registration, no charges). THHAP (talk) 15:34, 14 July 2018 (UTC)

Discussion

  • Symbol support vote.svg Support David (talk) 11:13, 16 July 2018 (UTC)

date of release[edit]

   Under discussion
Descriptionthe date that something became available to a wider audience in some way
Representspublication (Q732577), sort of
Data typePoint in time
Domainartificial entity (Q16686448)?
Example 1Portal 2 (Q279446) → 19 April 2011
Example 2MISSING
Example 3MISSING
Planned useI'm not doing this for myself; that's not how it's supposed to work
See alsopublication date (P577)

Motivation

Yes, I know, publication date (P577) already exists.

publication date (P577) is currently used for both real dates (when the secondary sources say a film was released) and made-up dates (the date on the cover of the magazine, which is actually incorrect because half the articles were published on their website the month before). This property would be for the real dates. This would be useful for data analysis, information published in magazines and journals (see my comments at Wikidata:Project chat#Modelling a publication schedule), and biological classification (see EncycloPetey's comments at Wikidata:Project chat#publication date vs inception (in general)). In short, having the actual date information was disseminated instead of a made-up date is useful sometimes because one of them is factual, and occasionally some other information (like the naming of a species) depends on the small difference between those dates.

This would replace or duplicate publication date (P577) where it is verified with secondary sources that the date is real, and would be added alongside publication date (P577) where it is verified that the stated date is not real. Jc86035 (talk) 17:28, 16 July 2018 (UTC)

Discussion

I question what is meant by "real" dates here. publication date (P577) is necessary for the stated date of publication of a work even if the stated date is not the actual date. While issues of priority in biological classification rely upon the actual releases date, bibliographical needs require the stated date of publication printed on the materials. We can't says that one property supplants the other. --EncycloPetey (talk) 17:41, 16 July 2018 (UTC)

@EncycloPetey: For brevity and at the risk of making the proposal seem a bit incoherent, a "real" date for the purposes of those two paragraphs is one which is set in reality – the "actual" release date. I misused "supplant"; I meant "supplement". Jc86035 (talk) 17:45, 16 July 2018 (UTC)

Ideographic description sequences[edit]

   Under discussion
Descriptiona way to describe Han characters
Data typeString
Template parameter"ids" in wikt:template:Han char
DomainCJK characters
Allowed valuesSequence of Han characters and ⿰⿱⿲⿳⿴⿵⿶⿷⿸⿹⿺⿻
Example 1(Q3595029) -> ⿱⻗彐
Example 2(Q3594965) -> ⿱⿳亠丷冖巾
Example 3(Q3594998) -> ⿰氵每 (China, Hong Kong, Taiwan, South Korea, Vietnam); ⿰氵毎 (Japan)
Sourcehttp://www.babelstone.co.uk/CJK/IDS.TXT
Number of IDs in source87887 as of Unicode 11, minus indecomposible characters
Expected completenesseventually complete (Q21873974) for encoded characters
Robot and gadget jobsYes

Motivation

This is a way to represent characters, especially unencoded characters like taito (Q7676480). Note we need a qualifier for example 3. GZWDer (talk) 17:48, 16 July 2018 (UTC)

Discussion

  • Pictogram voting comment.svg Comment @GZWDer: Ideographic description sequences is useful to describe the glyphs of Han characters. However, I think, in Wikidata, we should store this kind of data as items (with a qualifier series ordinal (P1545)), rather than strings. By doing so, we can easily generate the composition trees of Han characters. What do you think? --Okkn (talk) 18:06, 16 July 2018 (UTC)
  • @Okkn: Note the representation is an ordered tree, not a sequence. for example ⿱⿳亠丷冖巾 means ⿱(⿳亠丷冖)巾.--GZWDer (talk) 18:09, 16 July 2018 (UTC)
    • @GZWDer: I know that. But the sequence for the "箱", for example, is "⿱⺮相", not "⿱⺮(⿰木目)", right? Or both two sequences should be stored in this property?--Okkn (talk) 18:17, 16 July 2018 (UTC)
      • A character may have more than one ideographic description sequences, but the shortest possible Ideographic Description Sequence is preferred. Note Unicode Standard does not define equivalence for two Ideographic Description Sequences that are not identical. See page 424 of [2].--GZWDer (talk) 18:23, 16 July 2018 (UTC)
      • Note ideographic description sequences are Prefix notation (Q214510) and brackets never appear in sequences.--GZWDer (talk) 18:25, 16 July 2018 (UTC)
        • I know IDSes. Ok, I also think we should only store the shortest one. In that case, shouldn't we link from "箱" to "相" or from "相" to "木"? I want to draw a tree like Figure 1 on the page 131 of [3]. --Okkn (talk) 18:33, 16 July 2018 (UTC)
        • Examples of representing IDSes as structured data are shown below. This property can be a subproperty of part of (P361). --Okkn (talk) 20:10, 16 July 2018 (UTC)

For "箱":

IDSes
Normal rank Arbcom ru editing.svg edit
series ordinal 1
▼ 0 reference
+ add reference
Normal rank ⺮ (item not yet created) Arbcom ru editing.svg edit
series ordinal 2
▼ 0 reference
+ add reference
Normal rank Arbcom ru editing.svg edit
series ordinal 3
▼ 0 reference
+ add reference
+ add value

For "相":

IDSes
Normal rank Arbcom ru editing.svg edit
series ordinal 1
▼ 0 reference
+ add reference
Normal rank Arbcom ru editing.svg edit
series ordinal 2
▼ 0 reference
+ add reference
Normal rank Arbcom ru editing.svg edit
series ordinal 3
▼ 0 reference
+ add reference
+ add value
Then we will create a lot of items about Han character components. (Yes, [4] includes unencoded components.) How to deal with things like ⿰氵每 (China, Hong Kong, Taiwan, South Korea, Vietnam); ⿰氵毎 (Japan)?--GZWDer (talk) 21:57, 16 July 2018 (UTC)
If we import all Han characters encoded in Unicode 11, the number of components is much lower than that. I think that it's not particularly a problem. Also, in some environment, even the encoded components can't be displayed correctly. So using items brings considerable benefits to everyone.
Variations can be represented as follow:
IDSes
Normal rank Arbcom ru editing.svg edit
series ordinal 1
▼ 0 reference
+ add reference
Normal rank Arbcom ru editing.svg edit
series ordinal 2
▼ 0 reference
+ add reference
Normal rank Arbcom ru editing.svg edit
series ordinal 3
writing system traditional Chinese characters
simplified Chinese characters
Kyūjitai, Hanja, etc...
▼ 0 reference
+ add reference
Normal rank Arbcom ru editing.svg edit
series ordinal 3
writing system Shinjitai
▼ 0 reference
+ add reference
+ add value
I'm not sure whether the common parts ( and 氵) should be duplicated or not. --Okkn (talk) 05:55, 17 July 2018 (UTC)

Cangjie input[edit]

   Under discussion
DescriptionThe cangjie input code for the character
RepresentsCangjie input method (Q1033196)
Data typeString
Template parameter"canj" in wikt:template:Han char
DomainHan characters
Allowed values[A-Y]{1,5}
Example 1(Q3595029) -> MBSM
Example 2(Q3594965) -> YBLB
Example 3(Q3594998) -> EOWY
SourceUnihan database
Robot and gadget jobsYes

Motivation

This is an common input method of Chinese characters. GZWDer (talk) 18:06, 16 July 2018 (UTC)

Discussion

  • Symbol support vote.svg Support --Okkn (talk) 19:04, 16 July 2018 (UTC)
  • Symbol support vote.svg Support NMaia (talk) 17:57, 17 July 2018 (UTC)
  • Symbol support vote.svg Support Mahir256 (talk) 20:36, 17 July 2018 (UTC)

four-corner method[edit]

   Under discussion
DescriptionThe four-corner code(s) for the character.
RepresentsFour-Corner Method (Q2303847)
Data typeString
Template parameter"four" in wikt:template:Han char
DomainHan characters
Allowed values\d{5}
Example 1(Q3595029) -> 10177/10174
Example 2(Q3594965) -> 00227
Example 3(Q3594998) -> 38157
SourceUnihan database
Robot and gadget jobsYes

Motivation

Note the four-corner method includes the fifth number which is optional in searching. Unihan database represent it as XXXX.X. I don't know whether the dot is needed.GZWDer (talk) 18:16, 16 July 2018 (UTC)

Discussion

  • Symbol support vote.svg Support --Okkn (talk) 19:04, 16 July 2018 (UTC)
  • Symbol support vote.svg Support NMaia (talk) 17:56, 17 July 2018 (UTC)

Hangul of a Chinese character[edit]

   Under discussion
DescriptionThe modern Korean pronunciation(s) for this character in Hangul
RepresentsHangul (Q8222)
Data typeItem
DomainHan characters
Example 1(Q3595029) -> <item for 설>
Example 2(Q3594965) -> <item for 제>
Example 3(Q3594998) -> <item for 해>
Example 4樂 -> 1. 악; 2. 락 (North Korea), 낙 (South Korea); 3. 요
SourceUnihan database
Robot and gadget jobsYes

Motivation

This is another important information of Han character.GZWDer (talk) 19:29, 16 July 2018 (UTC)

Discussion

  • Symbol support vote.svg Support The solusion using items seems good to me. --Okkn (talk) 06:17, 17 July 2018 (UTC)
  • Symbol support vote.svg Support NMaia (talk) 17:55, 17 July 2018 (UTC)

Eumhun[edit]

   Under discussion
Descriptionan (often native Korean) word indicating a Han character's meaning. Only used as a qualifier of Hangul property (see above).
Representseumhun (Q20851511)
Data typeMISSING
DomainHan characters
Example 1(Q3595029) -> 눈
Example 2(Q3594965) -> 임금
Example 3(Q3594998) -> 바다
Example 4樂 -> 1. 노래 (for 악); 2. 즐길 (for 락 and 낙); 3. 좋아할 (for 요) Note: 즐길 is an inflected form of 즐기다
Example 5涴 -> 물 굽이쳐 흐를

Motivation

Note I don't know what's the correct datatype - the eumhun may consist more than one word.--GZWDer (talk) 19:47, 16 July 2018 (UTC)

Discussion

  • Pictogram voting comment.svg Comment I'm not familiar with Hangul, but this kind of data should be represented as the datatype of Lexeme, or its Sense, right? --Okkn (talk) 06:24, 17 July 2018 (UTC)

Extra granulated item[edit]

   Under discussion
DescriptionExtra granulated item
RepresentsWikimedia page outside the main knowledge tree (Q17379835)
Data typeItem
Example 1Abbotsbury (Q306685)Abbotsbury (Q24665923)
Example 2Melle (Q20177)Melle (Q30027441)
Example 3UFO (Q225344)Ufo (Q12340062)
Planned usemainly for Ljsbot articles that make an unusual distinction
Robot and gadget jobsBots can start by changing from duplicate or said to be the same.
See alsosaid to be the same as (P460)

Motivation

So that over granular item aren't marked as Wikimedia duplicated page (Q17362920) or said to be the same as (P460), see User talk:Jheald#Lsjbot and Wikimedia duplicated page and search the project chant for cebwiki. This avoids cluttering them up with the "complete" duplicates. While it is clear in this example one if for the settlement and one for the unit, most other projects just have 1 article. Lucywood (talk) 20:25, 16 July 2018 (UTC)

Discussion

  • Pictogram voting comment.svg Comment I think I understand the intent here, but I'm not sure how this really improves the situation - is the idea to have some mechanism for distinguishing items we might want to keep from duplicate items that are basically irrelevant that we should try to remove (by merging on cebwiki for instance)? We do have things like facet of (P1269) or part of (P361) if one is somehow contained in the other. ArthurPSmith (talk) 17:53, 17 July 2018 (UTC)

lexeme of property constraint[edit]

   Under discussion
Descriptionqualifier to define a property constraint in combination with P2302
Data typeLexeme
Examplesimilar to P2305
See alsoitem of property constraint (P2305): qualifier to define a property constraint in combination with P2302

exception to constraint (lexeme)[edit]

   Under discussion
Descriptionlexeme that is an exception to the constraint, qualifier to define a property constraint in combination with P2302
Data typeLexeme
Examplesimilar to P2303
See alsoexception to constraint (P2303): item that is an exception to the constraint, qualifier to define a property constraint in combination with P2302

Motivation

Lucas Werkmeister (WMDE) – work account, mainly for development discussions
Jarekt - mostly interested in properties related to Commons
User:MisterSynergy
John Samuel
Sannita
Yair rand
Jon Harald Søby
Pasleim
Jura
PKM
ChristianKl
Sjoerddebruin
Salgo60
Fralambert
Manu1400
Was a bee
Malore
Ivanhercaz
Peter F. Patel-Schneider
Pizza1016
Pictogram voting comment.svg Notified participants of WikiProject property constraints

Supposedly we would need to adapt to the new namespace. Forms might need the same. Feel free to add above.
--- Jura 09:13, 27 April 2018 (UTC)

Discussion

Pictogram voting comment.svg Comment a lexeme version of exception to constraint (P2303) could make sense, but do you have any uses in mind for “lexeme of property constraint”? Lexemes as constraint parameters? --Lucas Werkmeister (WMDE) (talk) 13:26, 27 April 2018 (UTC)

relative date[edit]

   Under discussion
Descriptionsigned time difference between two entities, the other entity being the one indicated by the [ID OF THE OTHER PROPERTY] statement with the same rank and qualifiers (negative value indicates the other entity occurs later)
Data typeNumber (not available yet)
Allowed unitsany time units
Example 1Easter − 47 days (Q14914941) → −47 days
Example 2MISSING
Example 3MISSING
Planned useaddition to the Easter ±n days items
See alsopoint in time (P585), [ID OF THE OTHER PROPERTY]

Motivation

See the section below; this property does not make any sense without the other. Jc86035 (talk) 08:36, 19 July 2018 (UTC)

relative dates are relative to[edit]

   Under discussion
Descriptionthe entity with which [ID OF THE OTHER PROPERTY], with the same rank and qualifiers, indicates a time difference
Data typeItem
Allowed valuesitem that has a point in time, or item with a Wikidata property (P1687) statement (in reference to the statement(s) for that property)
Example 1Easter − 47 days (Q14914941)date of Easter (Q51224536)
Example 2MISSING
Example 3MISSING
Planned useaddition to the Easter ±n days items
See alsopoint in time (P585), [ID OF THE OTHER PROPERTY]

Motivation

Currently the items listed at Help:Easter related dates are not actually formally linked. This and future subproperties could be useful for other recurring things like record charts, but I didn't want to propose lots of relative equivalents to existing date properties without any consensus that there should be relative date properties. The reasons two properties are needed are because two different value datatypes are needed (the time and the other item), and to ensure that relationships can also be stated with both properties as qualifiers. Jc86035 (talk) 08:36, 19 July 2018 (UTC)

Discussion