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/09.

Contents

Generic properties[edit]

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)

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)

See: Wikidata:Properties_for_deletion#Wikidata_project_(P4570).--Micru (talk) 20:58, 1 August 2018 (UTC)

  • Symbol support vote.svg Support. This allows the relationship represented by Wikidata project (P4570) to be broadened to all WikiProjects. I agree that the link between a topic item and a WikiProject that works on the topic should have its own property, separate from those about other technical literature. Deryck Chan (talk) 10:28, 2 August 2018 (UTC)
  • Pictogram voting comment.svg Comment marginally related: soon Listeria should be able to generate constraint violation reports.
    --- Jura 16:39, 2 August 2018 (UTC)

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)
@CherryPie94: Do you think you could provide the requested information? --abián 16:09, 31 August 2018 (UTC)

reference has role[edit]

   Under discussion
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)
Faendalimas
FelixReimann (talk)
Infovarius (talk)
Joel Sachs
Josve05a (talk)
Klortho (talk)
Lymantria (talk)
MargaretRDonald
Mellis (talk)
Michael Goodyear
MPF
Mr. Fulano (talk)
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)

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)
  • Symbol support vote.svg Support. ··· 🌸 Rachmat04 · 07:52, 7 August 2018 (UTC)
  • Symbol support vote.svg Support API endpoints are offered by web services to interact with or extract information, and it's specialized as feed URL or SPARQL endpoint --Sabas88 (talk) 12:52, 4 September 2018 (UTC)
  • Symbol support vote.svg Support Worldm99 (talk) 08:36, 18 September 2018 (UTC)

perfume note[edit]

   Done. perfume note (P5872) (Talk and documentation)
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)
  • Symbol support vote.svg Support how about a general property for smell Nepalicoi (talk) 12:29, 17 September 2018 (UTC)

@Nepalicoi, Teolemon, Pigsonthewing: ✓ Done: perfume note (P5872). − Pintoch (talk) 21:34, 20 September 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)

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)
    The intention here is mainly for items that we generally don't have 2 separate items for but we have to because 1 project makes a distinction (like the UFO DAB page for example). It wasn't just to get rid of ceb articles, of which many should be kept but some are non notable or even don't really exist. Lucywood (talk) 11:43, 2 August 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
Ogoorcs
CennoxX
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)
  • Cold you add these constraint to some property? This makes debugging more simple. — Ivan A. Krestinin (talk) 07:24, 30 July 2018 (UTC)
  • I implemented these constraints, but have no time to execute full testing. Please notify me if something goes wrong. The nearest update is in progress already. It will fail with "unsupported constraint" error. The next update must produce appropriate result. — Ivan A. Krestinin (talk) 12:38, 30 July 2018 (UTC)
Also, why are the labels of those constraint types so inconsistent both with each other (“lexeme requires” vs. “required by this lexeme”) and with all other constraint types (typically end in “… constraint”)? --Lucas Werkmeister (WMDE) (talk) 13:07, 30 July 2018 (UTC)
  • @Ivan A. Krestinin, Lucas Werkmeister (WMDE): Thanks! I will check the reports once updated.
    (a) For both, I think several values should be possible, especially as they can easily evolve. In the meantime, I also added the second constraint to Han character in this lexeme (P5425) with two values.
    (b) The check could easily apply to statements added on forms (or senses once available). It might take some time to dig up samples.
    The labels should indeed be improved, especially as all other values include "constraint" in the English label ;)
    --- Jura 13:38, 30 July 2018 (UTC)
  • ✓ it works! on constraint reports. There are currently five properties using it. Thanks.
    --- Jura 23:33, 2 August 2018 (UTC)

relative time[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)

reference time[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 time 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

Pictogram voting comment.svg Comment I think it should be a qualifier of your proposing "relative time" property, because there can be mulitiple relative date in one item. And the name can be simply "reference date". --Okkn (talk) 02:16, 20 July 2018 (UTC)

Why not use the general property relative to (P2210)?--GZWDer (talk) 09:40, 20 July 2018 (UTC)
@GZWDer, Okkn: If relative to (P2210) were used, it wouldn't be possible to use relative date/time properties as qualifiers themselves, because qualifiers can't have their own qualifiers. I would be fine with calling the second property "reference date"/"reference time". If there are multiple "relative times", then presumably they are distinguished using properties, qualifiers and rank, so there could be one matching "reference time" for each statement or qualifier; if a "relative start time" property were to be created, it would need a matching "start time reference time". Jc86035 (talk) 11:39, 20 July 2018 (UTC)
  • I think "time index" works fine for this.
    --- Jura 16:22, 5 August 2018 (UTC)
  • Symbol oppose vote.svg Oppose Nepalicoi (talk) 13:04, 17 September 2018 (UTC)

copyright status[edit]

   Under discussion
Descriptioncopyright status for any work of art or intellectual creation
Representscopyright status (Q50424085)
Data typeItem
DomainAll elements under creative work (Q17537576) e.g. photograph (Q125191), painting (Q3305213), literary work (Q7725634), etc.
Allowed valuespublic domain (Q19652) / copyrighted (Q50423863)
Example 1Atomic Cloud Rises Over Nagasaki (Q55437339)public domain (Q19652)
Example 2One Thousand and One Nights (Q8258)public domain (Q19652)
Example 3Guernica (Q175036)copyrighted (Q50423863)
Example 4Mona Lisa (Q12418)public domain (Q19652)
Example 5Gutenberg Bible (Q158075)public domain (Q19652)
Example 6Harry Potter and the Philosopher's Stone (Q102438)copyrighted (Q50423863)

Motivation

Currently license (P275) is used, but public domain (Q19652) is not a license. Neither is copyrighted (Q50423863). There was a failed proposal before: Wikidata:Property proposal/Archive/48#Copyright status. There is also a (stalled) discussion on Wikidata talk:WikiProject sum of all paintings#Shall we introduce properties indicating copyright status. Yann (talk) 15:27, 19 July 2018 (UTC)

Discussion[edit]

Multichill (talk) 11:28, 8 August 2014 (UTC), focus on the Netherlands Husky (talk) 11:38, 8 August 2014 (UTC) - Cool, i'd like to focus on building tools to visualise progress. Spinster (talk) 07:00, 9 August 2014 (UTC) Happy to help with manual finetuning that can't be done by bots, and anything else on the 'soft/wet' side of this project. I'm dreaming of complete artists' oeuvres on Wikidata! Rich Farmbrough (talk) Time to learn2Wikidata Jheald (talk) 12:33, 17 August 2014 (UTC) Kippelboy (talk) 07:01, 21 August 2014 (UTC) (Focus on Catalan paintings (subdivision of Spain) Mushroom (talk) 12:27, 21 August 2014 (UTC) Jane023 (talk) 09:11, 3 October 2014 (UTC) work on Dutch 17th-century paintings and landscapes of Haarlem; Most recently, the sum of all "attributed" paintings by Frans Hals, which is nearly done Missvain (talk) 18:51, 18 October 2014 (UTC) (talk) 13:27, 15 November 2014 (UTC) Zolo (talk) 14:57, 23 November 2014 (UTC) Beat Estermann (talk) 10:33, 3 December 2014 (UTC) (Focus on Swiss heritage institutions) Vladimir Alexiev (talk) 15:07, 23 January 2015 (UTC) KRLS (talk) 11:26, 11 February 2015 (UTC) (Focus on Catalan area museums) DivadH (talk) 11:35, 1 March 2015 (UTC) ,happy to help out with any questions in regards to the Europeana API, how to best query it, and/or our metadata Xcia0069 (talk) 11:49, 8 March 2015 (UTC), Work on data related to Gianlorenzo Bernini and Artemisia Gentileschi. Work at Europeana too ! Susannaanas (talk) 07:29, 9 March 2015 (UTC) Wittylama (talk) 17:29, 20 March 2015 (UTC) Fabrice Florin (talk) 02:35, 26 June 2015 (UTC) I can help in California later this year. Vaughn88 (talk) 15:58, 15 July 2015 (UTC) I can help! Raymond Ellis (talk) 19:31, 17 August 2015 (UTC) Hsarrazin (talk) 14:11, 29 August 2015 (UTC) - will give a hand with Creators and AC :) louis-garden (talk) 14:21, 31 August 2015 (UTC) for italian paintings (XIIe-XVIIe) Olivier (talk) 21:46, 8 September 2015 (UTC) Kopiersperre (talk) 11:33, 20 November 2015 (UTC) ProtoplasmaKid (talk) 03:49, 23 February 2016 (UTC) Micru (talk) 11:19, 29 February 2016 (UTC) Stuart Prior (WMUK) (talk) 11:04, 28 April 2016 (UTC) Hannolans (talk) 23:14, 22 October 2016 (UTC) Geraki (talk) 09:52, 24 October 2016 (UTC) (Focus on Greece) PatHadley (talk) 12:16, 3 January 2017 (UTC) MartinPoulter (talk) 14:54, 11 January 2017 (UTC) Working to get data from the University of Oxford (Q34433) and its component institutions shared on Wikidata. Pablísima (talk) 18:07, 8 February 2017 (UTC) Carl Ha (talk) 22:10, 9 February 2017 (UTC) Marsupium (talk) 19:44, 22 May 2017 (UTC) Mauricio V. Genta (talk) 16:15, 26 June 2017 (UTC) Shani Evenstein (talk) 10:26, 26 July 2017 (UTC) Nasty nas (talk) 07:45, 24 August 2017 (UTC) Bodhisattwa (talk) 14:28, 28 October 2017 (UTC) Joalpe (talk) 18:39, 9 November 2017 (UTC) Fuzheado (talk) 18:33, 30 November 2017 (UTC) Sarasays (talk) 20:00, 1 December 2017 (UTC) Thierry Caro (talk) 07:30, 9 December 2017 (UTC) John Samuel 18:29, 21 December 2017 (UTC) Jklamo (talk) 12:06, 31 December 2017 (UTC) Reosarevok (talk) 10:28, 15 February 2018 (UTC), focus on Estonia Ambrosia10 (talk) 19:48, 19 February 2018 (UTC) Subsublibrary (talk) 03:17, 22 February 2018 (UTC) Martingggg (talk) 07:00, 22 February 2018 (UTC), focus on Argentine and Hispanic America Kruusamägi (talk) 16:42, 13 March 2018 (UTC), focus on Estonia SIryn (talk) 10:36, 9 June 2018 (UTC) Jarekt (talk) 13:49, 7 September 2018 (UTC), focus on moving metadata from Commons to Wikidata Pictogram voting comment.svg Notified participants of WikiProject sum of all paintings - Aubrey
Viswaprabha (talk)
Micru
Tpt
EugeneZelenko
User:Jarekt
Maximilianklein (talk)
Don-kun
VIGNERON (talk)
Jane023 (talk) 08:21, 30 May 2013 (UTC)
Alexander Doria (talk)
Ruud 23:15, 24 June 2013 (UTC)
Kolja21
arashtitan
Jayanta Nath
Yann (talk)
John Vandenberg (talk) 09:14, 30 November 2013 (UTC)
JakobVoss
Danmichaelo (talk) 19:30, 16 February 2014 (UTC)
Ravi (talk)
Mvolz (talk) 08:21, 20 July 2014 (UTC)
Hsarrazin (talk) 07:56, 9 August 2014 (UTC)
Accurimbono
Mushroom
PKM (talk) 19:58, 10 October 2014 (UTC)
Revi 16:54, 29 November 2014 (UTC)
Giftzwerg 88 (talk) 23:36, 1 January 2015 (UTC)
Almondega (talk) 00:17, 5 August 2015 (UTC)
maxlath
Jura to help sort out issues with other projects
Epìdosis
Skim (talk) 13:52, 24 June 2016 (UTC)
Marchitelli (talk) 12:29, 5 August 2016 (UTC)
BrillLyle (talk) 15:33, 26 August 2016 (UTC)
Alexmar983 (talk) 23:53, 28 August 2016 (UTC)
Finn Årup Nielsen (fnielsen) (talk) 10:44, 29 August 2016 (UTC)
Chiara (talk) 14:15, 29 August 2016 (UTC)
Thibaut120094 (talk) 20:31, 14 September 2016 (UTC)
Ivanhercaz | Discusión Plume pen w.png 15:30, 31 October 2016 (UTC)
YULdigitalpreservation (talk) 17:35, 10 November 2016 (UTC)
User:Jc3s5h
PatHadley (talk) 21:51, 15 December 2016 (UTC)
Erica (ohmyerica) (talk) 19:26, 1 January 2017 (UTC)
User:Timmy_Finnegan
Mauricio V. Genta (talk) 05:38, 12 March 2017 (UTC)
Sam Wilson 09:24, 24 May 2017 (UTC)
Sic19 (talk) 22:25, 12 July 2017 (UTC)
Andreasmperu
MartinPoulter (talk) 09:21, 20 July 2017 (UTC)
ThelmadatterThelmadatter (talk) 01:11, 13 September 2017 (UTC)
Zeroth (talk) 15:01, 16 September 2017 (UTC)
Emeritus
Ankry
Beat Estermann (talk) 20:07, 12 November 2017 (UTC)
Shilonite - specialize in cataloging Jewish & Hebrew books
Elena moz
Oa01 (talk) 10:52, 3 February 2018 (UTC)
Maria zaos (talk) 11:39, 25 March 2018 (UTC)
Wikidelo (talk) 13:07, 15 April 2018 (UTC)
Mfchris84 (talk) 10:08, 27 April 2018 (UTC)
Mlemusrojas (talk) 3:36, 30 April 2018 (UTC)
salgo60 Salgo60 (talk) 12:42, 8 May 2018 (UTC)
Dick Bos (talk) 14:35, 16 May 2018 (UTC)
Marco Chemello (BEIC) (talk) 07:26, 30 May 2018 (UTC)
Harshrathod50
 徵國單  (討論 🀄) (方孔錢 💴) 14:35, 20 July 2018 (UTC)
Alicia Fagerving (WMSE)
Louize5 (talk) 20:05, 11 September 2018 (UTC)
Pictogram voting comment.svg Notified participants of WikiProject Books - User:Zolo
Jane023 (talk) 08:50, 30 May 2013 (UTC)
User:Vincent Steenberg
User:Kippelboy
User:Shonagon
Marsupium (talk) 13:46, 18 October 2013 (UTC)
GautierPoupeau (talk) 16:55, 9 January 2014 (UTC)
Multichill (talk) 19:13, 8 July 2014 (UTC)
Susannaanas (talk) 11:32, 12 August 2014 (UTC) I want to synchronize the handling of maps with this initiative
Mushroom (talk) 00:10, 24 August 2014 (UTC)
Jheald (talk) 17:09, 9 September 2014 (UTC)
Spinster (talk) 15:16, 12 September 2014 (UTC)
PKM (talk) 21:16, 8 October 2014 (UTC)
Vladimir Alexiev (talk) 17:12, 7 January 2015‎ (UTC)
Sic19 (talk) 21:12, 19 February 2016 (UTC)
Wittylama (talk) 13:13, 22 February 2017 (UTC)
Armineaghayan (talk) 08:40, 10 March 2017 (UTC)
Hannolans (talk) 18:36, 16 April 2017 (UTC)
User:Martingggg
Zeroth (talk) 02:21, 4 June 2018 (UTC)
User:7samurais
User:mrtngrsbch
Pictogram voting comment.svg Notified participants of WikiProject Visual arts --Hsarrazin (talk) 11:50, 25 July 2018 (UTC)

  • Pictogram voting comment.svg Comment I think there's a little too much overlap with license (P275) here, and essentially this is just adding a Boolean field to that, which isn't terribly helpful in my opinion. Also in general we have avoided "status"-like properties as they inherently have a present-time bias, but time passes and "status" changes, which necessitates updates to every such property as time goes by. I think better than a "status" would be a date property - "copyright expiry date" perhaps (which may need to be qualified by jurisdiction). I would support a date-related property for this. ArthurPSmith (talk) 18:52, 19 July 2018 (UTC)
  • There is overlap only because license (P275) is badly used. In many cases, as examples I cited above, license (P275) is absolutely not suitable to indicate the copyright status. A license indicates rights or permission given by the copyright owner. It should not be used when there isn't any copyright owner, or worse, for elements created before the concept of copyright was created. "copyright expiry date" would be a qualifier of the proposed property, but the date is often unknown, and/or irrelevant. Examples: what date would you use for One Thousand and One Nights (Q8258) or Mahabharata (Q8276)? As for the changing state of a status, we need a way to update automatically some data (with a bot?) when the status changes. Incompleteness of the system should not be a reason not to create a useful property, otherwise we are blocked in a chicken-and-egg circle. Regards, Yann (talk) 08:38, 20 July 2018 (UTC)
  • You could use the same date as the publication date for old works, for example "10. century" for One Thousand and One Nights (Q8258). However, copyright generally applies not to the work as a whole but to particular editions or translations - Le Mille ed una Notti (Q18913375) was published in 1852 so the copyright expiry for that (or another edition in the language of your choice) is probably a more relevant question. Automatically changing a status doesn't address the issue of how one can use the database to determine copyright status at a particular point in time (before or after present), so a date-based property is more generally useful than a status one. ArthurPSmith (talk) 18:51, 20 July 2018 (UTC)
  • I agree with Yann, a date-based property needs computation (which is totally useless for old works, which could just be indicated as Public Domain). Also, "copyright expiry date" is alright for US-type "copyright", but is not applicable for works by still living people according to EU regulations or '"author's rights". A status type like "Author's death+70 year" would be clearer, and allow for automatic retrieving of the authors P570, when they are added. Also, if regulations change (to prolong the delay) it would be easier to apply to all authors concerned by it. It would be very useful for wikisource to easily know which writers rise to Public Domain every January 1st. --Hsarrazin (talk) 09:21, 25 July 2018 (UTC)
Pictogram voting comment.svg Comment Will we mark the individual copyright status of the work for each and every country? Laws differ considerably in each nation.
We'd also have to have a means of differentiating the status of content within a volume. Sometimes the text is in public domain, but the illustrations are still under copyright. Or a volume may contain multiple works, some of which are under copyright and some of which are not. Sometimes the primary work is free of copyright, but the annotations, or the introduction are copyrighted. We'd have to have a system that indicates the status of individual components of a work before we can handle copyright issues. --EncycloPetey (talk) 14:41, 25 July 2018 (UTC)
of course, you can put the copyright status on work items, instead of the "book" item. Thus, allowing to know the status of each part. But not all editions are composite. Most are single works. and you do not "have to"... it would "allow to" which is quite different. --Hsarrazin (talk) 17:11, 27 July 2018 (UTC)
« Most are single works. » Is it? Composition is quite common, paratext being the most common editing. For instance, most recent editions have a cover who are works with their own rights. And translation are edition (per FRBR at least) who have a translator with -again- its own rights. Their is a lot of other examples. If we create this property, I feel it would be easier to put it only on editions and not on works.
I totally agree for the "allow to" and not "have to", indicating the status of text in French according to laws of France, Canada, Belgium, Switzerland and other francophone country make sense and could be useful/relevant, adding the status of a text in Japanese according to the law of Lichtenstein could be done if needed but doesn't have to.
Cheers, VIGNERON (talk) 21:09, 30 July 2018 (UTC)
I still have a major concern about updating (document entering or leaving the public domain). How this property could deal with it? Cdlt, VIGNERON (talk) 21:09, 30 July 2018 (UTC)

⧼Vote⧽[edit]

Symbol strong support vote.svg Strong support --Hsarrazin (talk) 09:58, 25 July 2018 (UTC)

  • Symbol oppose vote.svg Oppose Implementation does not allow marking which locations have a particular copyright status. A book may be under copyright in the UK, but not in the US. Or may be PD in Canada, but copyrighted in the US. It is also possible that individual portions of a book are copyrighted, such as the illustrations, the annotations, or the introduction, while the main text is free of copyright. We also need to be able to mark the status of individual poems within a collected volume, or the individual stories in a magazine. Sometimes a work is in public domain, but a translation of that work is not. We can't handle all these situations under the current proposal. A great deal of work will be required first. --EncycloPetey (talk) 14:49, 25 July 2018 (UTC)
    • Maybe I'm missing something, but all the things you listed seem possible with this proposal: For the location, use applies to jurisdiction (P1001) as a qualifier. When it only applies to a part of the work, use applies to part (P518) as a qualifier. Translations, individual poems and individual stories in a magazine would already need their own items anyway to enter titles, authors, creation dates, etc - the copyright status can be added the individual items. - Nikki (talk) 15:20, 25 July 2018 (UTC)
      • Re: "can be added the individual items": You're missing how WikiProject:Books has book data items structured. A magazine is a simple example compared to a book. If we have a book containing 12 short stories, that's a minimum of 26 data items, provided the book has only a single edition: there will be one data item for the "work", one for each story as a "work", and one additional data item each for the particular "edition" of the book and story. For each additional edition, there will be an additional 13 data items. Can we be sure that the copyright status will be the same for the editions as for the original work? No. Each edition can have editorial changes that warrant a separate copyright status. Each edition can have a foreword, introduction, or notes that are copyrighted. Each edition can have new illustrations that are copyrighted.
      • When we add new items to Wikisource, it often involves long and complicated research for a single edition and a community discussion to decide whether a particular work is (a) copyrighted in the US, and (b) copyrighted in its country of origin. To add every individual nation's copyright status on top of that will generate millions of discussions to resolve and track.
      • For a novel that was serialized in a magazine initially, then published as a book in the US/UK simultaneously, then multiple additional editions, we have to track the status of the original story separately from each and every edition, because each edition may or may not have additional copyrighted material, and we have to have the copyright status on every individual edition, with no guarantee that they are the same. And for a poem, there won't be just one data item; there will be a data item for each and every time that poem was published, each of which will have individual copyright status depending on when and where it was published and whether or not that edition had editorial changes, notes, or other associated material that falls under copyright. Popular poems can run into the hundreds of different editions to track. And once you add to that the translations and any illustrations that may or may not have appeared under the edition, I don't see how we can hope to track it all.
      • And Wikiproject:Books is now in a discussion to decide what data structure we need for our purposes, so we don't even have a set model yet on which to add copyright status.
      • And once the copyright status is added, is it a static value? No. The copyright status is time dependent, and subject to changes in law. The current proposal offers no means to track changes that happen as the result of the passage of time, or to indicate which law and what registration affects the current status. --EncycloPetey (talk) 17:11, 25 July 2018 (UTC)
        • None of these is a valid reason not to create this property. Anyway it is not just because it can't be used in some cases, that it should not be created, as it is useful in other cases. Regards, Yann (talk) 10:38, 26 July 2018 (UTC)
          • It is a valid reason if the proposal is not designed to handle these situations, and the proposal clearly isn't capable of doing so. The proposal is a naive implementation that assumes a single data item for a book, with two possible settings. The situations I've described cannot be handled under the proposal as it was submitted. A proposal that purports to handle copyright status, that isn't even designed to handle a book is not going to be useful, and will create more problems than it solves. The proposal should be voted down, and a new proposal that can handle the needs of Wikidata should be drafted. --EncycloPetey (talk) 14:29, 26 July 2018 (UTC)
            • The proposition is not a 2-possible settings one. It allows for adding specific qualifiers for specific values, and to create more possible values than "copyrighted" or "public domain". Moreover, it allows for adding info on "work" items, not only on "edition" items. The mere notion of "book" items is a nightmaire chimera, that should be divided into the previous two types of items. Being able to know, for each "work" whether it is or not PD, is a progress to being able to know if a specific edition is or not, considering each part, including foreword, preface, etc. could have the info "as a work". --Hsarrazin (talk) 16:07, 27 July 2018 (UTC)
              • I'm looking at the proposal as it's given above. All six examples have only one of two values, and that's all. The proposal lists only two allowed values, so it is clearly a two-settings proposal. I'm evaluating the proposal as it is stated, not as I imagine it might be and not as other people imagine it might be. I cannot evaluate people's imagination, only the proposal as it was stated. --EncycloPetey (talk) 18:57, 27 July 2018 (UTC)
  • Symbol oppose vote.svg Oppose per EncycloPetey. Mahir256 (talk) 17:31, 25 July 2018 (UTC)
  • Symbol oppose vote.svg Opposechanged to Pictogram voting comment.svg Comment isn't public domain date (P3893) enough and even better as more perennial (per EncycloPetey (talkcontribslogs) last point). Cdlt, VIGNERON (talk) 17:41, 27 July 2018 (UTC)
    • Pictogram voting comment.svg Comment @VIGNERON: for old work (19th century of before), you would need to give a date which means nothing, or would be difficult to compute. how would you propose to do in those cases ? --Hsarrazin (talk) 19:48, 27 July 2018 (UTC)
      • @Hsarrazin: why would the date means nothing? or why would it means more (or less) than the proposed property? And old publications are obviously in the public domain (except for few strange cases like Peter Pan or posthumous editions). My concern is that for edition entering in the public domain now, it would means that we would need to monitor and change the data on thousands of items, meanwhile a date doesn't have to be changed (again, with exceptions). By the way, "work" is not really an appropriate term here, a work is intangible so it's never under copyright law, legally it's never under copyright or in the public domain, only publications are. Cdlt, VIGNERON (talk) 20:33, 27 July 2018 (UTC)
@VIGNERON: I disagree with you about work. You know as well as me that in French (and European) law, works are protected from their inception, whether they are published or not. And that the period of protection does not run from edition, but from the death of the author. When a work is PD, all its editions (if there is not added work, translation, illustration, etc.) is automatically PD too ^^ --Hsarrazin (talk) 20:42, 27 July 2018 (UTC)
@Hsarrazin: Well, law is complicated. It depends on what we call "work" and "inception", as long as it is intangible (for instance still in someone mind), it's not protected (idea are free), but true as soon as it's written down (published or not) it's protected. The duration of protection is not always PMA, not even in France (it's not the case for posthumous works for instance). And no, not all editions of a "PD work" are automatically PD (not if there is addition or modifications). Anyway, why not just use public domain date (P3893)? (especially as it can be in the future, which could be very useful for Wikisources ;) ) Cdlt, VIGNERON (talk) 21:47, 27 July 2018 (UTC)
  • and using "no value" (combined with public domain date (P3893)) for those works that were never under copyright? strakhov (talk) 16:58, 30 July 2018 (UTC)
  • @Strakhov: yes, it could work. That said, qualifiers would still be needed. Cdlt, VIGNERON (talk) 19:13, 30 July 2018 (UTC)
  • @Strakhov: While I initially thought it could work, I see 3 problems with that: 1. "no value" means "there is no value for the date of accession to public domain", and is not equivalent to "being in the public domain". It can be interpreted as "it will never enter in the public domain". 2. Copyright is quite complex, and determining if a document is in the public domain today is sometimes complicated. Knowing when it entered the public domain is even worse, and useless as a practical matter. I don't see any reason to make things even more difficult than they are. 3. If the author is still alive, we can't give a date when the work will enter in the public domain. Regards, Yann (talk) 19:18, 30 July 2018 (UTC)
Symbol oppose vote.svg Oppose better to extend license (P275) usages instead. --Liuxinyu970226 (talk) 10:40, 31 July 2018 (UTC)
@Liuxinyu970226: do you mean inputing public domain (Q19652) in license (P275) ? - this value would have to be explicitely authorized, then, and a redefinition of license (P275) to be accepted. --Hsarrazin (talk) 11:39, 31 July 2018 (UTC)
@Hsarrazin: By simply searching "Q19652" I found 845 items that are having license (P275)  public domain (Q19652) e.g. Mahabharata (Q8276). --Liuxinyu970226 (talk) 11:42, 31 July 2018 (UTC)
indeed, but this is not considered proper for now, see this discussion — what counts for me is that it is possible to use this value somewhere. If it was agreed to extend and rename P275, it would be ok for me :) --Hsarrazin (talk) 12:01, 31 July 2018 (UTC)
I proposed a more generic property: Wikidata:Property proposal/legal status.--GZWDer (talk) 10:50, 2 August 2018 (UTC)
Symbol oppose vote.svg Oppose I like GZWDer's legal status as it's more generic --Sabas88 (talk) 13:08, 5 August 2018 (UTC)
  • Symbol support vote.svg Support Clarifies existing data. "Legal status" is incredibly vague, it could mean anything from immigration statuses to tax statuses. The only think I would change is that this property should be called "intellectual property status" or something like that.Mr. Guye (talk) 19:03, 29 August 2018 (UTC)

sense for this name[edit]

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

Note: Sense datatype is not available yet

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)

  • @Micru: can you add an explanation?
    --- Jura 11:05, 24 July 2018 (UTC)
  • @Jura1: As you can see above there was no support for this proposal, and the conversation stalled. --Micru (talk) 14:12, 24 July 2018 (UTC)
  • I think there is. It's just that senses aren't available.
    --- Jura 14:17, 24 July 2018 (UTC)
    • I reopened it. The point raised by @Duesentrieb: had been addressed. I think it's good to include this in both.
      --- Jura 11:48, 25 July 2018 (UTC)
Symbol oppose vote.svg Oppose until it can be shown that item for this sense (P5137) is insufficient for a real usecase. The motivation for this property doesn't actually make a case for why this is needed, and since we don't have senses yet, let alone the ability to query lexemes or use the data in other projects, it seems too premature to be sure it's needed anyway. - Nikki (talk) 10:36, 10 August 2018 (UTC)
  • This is silly. We were asked to propose properties provided that lexemes/forms/senses will be available.
    --- Jura 10:39, 10 August 2018 (UTC)
    The way property proposals work is that the proposer has to convince others that the property being proposed should be added. Some properties will obviously be necessary and that can be demonstrated in advance. If you think this one is also clearly necessary, then it's up to you to show that it is. Dismissing my comment as "silly" is not going to suddenly make me think that this is needed. - Nikki (talk) 13:41, 10 August 2018 (UTC)
    • I'm not really interested in convincing you, as you argue that properties for senses are premature .. It's just not relevant as we seek to formulate proposals in advance.
      --- Jura 13:45, 10 August 2018 (UTC)

expiration date[edit]

   Under discussion
Descriptiondate after which an item will no longer be in effect, date on which it arrives at its theoretical term
Data typePoint in time
Domainany
Allowed valuesany, generally > date of publication of reference/source
ExampleSaab 340 c/n 269 (Q29479553) aircraft registration (P426) "N902AE" → 30 April 2020
Planned usereplace end time (P582) where needed
See also

Motivation

Currently we get some crystal ball values in P582, at least if it's understood as providing the actual end date. (Add your motivation for this property here.)
--- Jura 09:22, 27 July 2018 (UTC)

Discussion

legal status[edit]

   Under discussion
Descriptionlegal status of an entity
Data typeItem
Example 1One Thousand and One Nights (Q8258)public domain (Q19652) (from Wikidata:Property proposal/copyright status)
Example 2Guernica (Q175036)copyrighted (Q50423863) (from Wikidata:Property proposal/copyright status)
Example 3Richey Edwards (Q436648)death in absentia (Q693726) (since Nov 23, 2008)
Example 4Virtue Party (Q1399162)ban (Q621608) (since Jun 22, 2001) - Note we possibly need a new item "banned"
Example 5Julian Assange (Q360) → under arrest warrant (November 2010 - 19 May 2017; applies to jurisdiction (P1001)=Sweden (Q34))
These following three examples are additional usage of the property, and probably do not meet the final property scope:
Example 6Jundallah (Q1048651)terrorist organization (Q17127659) (applies to jurisdiction (P1001)=United States of America (Q30)) - This may replace designated as terrorist by (P3461), but I don't know whether it is appropriate
Example 7same-sex marriage (Q17422)civil union (Q41075) (applies to jurisdiction (P1001)=Germany (Q183)) - see Wikidata:Property proposal/Same-sex marriage
Example 8acetaminophen (Q57055)General sales list (UK) (Q26715239) (applies to jurisdiction (P1001)=United Kingdom (Q145)) - possibly reuse the current property of legal status (medicine) (P3493)

Motivation[edit]

This is a more general property than Wikidata:Property proposal/copyright status. Note I have include many possible usage of this property, but I also think this proposal in current form is a bit vague (probably not all are appropriate to be represented in one property) and needs further discussion. GZWDer (talk) 10:49, 2 August 2018 (UTC)

Discussion[edit]

  • Symbol support vote.svg Support In this more general form it actually makes a lot of sense to me. Thanks for proposing it! ArthurPSmith (talk) 17:48, 3 August 2018 (UTC)
  • Symbol support vote.svg Support Could it also be used for disputed territories --Sabas88 (talk) 13:03, 5 August 2018 (UTC)
  • Symbol oppose vote.svg Oppose. This is far too broad and ambiguous, and could lead to statements that can't be reliably interpreted. Additionally, many such items would certainly develop too many statements, as every single jurisdiction would need a separate statement in the item. A generic "legal-related has-attribute" is problematic. For some of these issues, I'd favor a more precise (but not unnecessarily specific) property to be used from the item for the law/ruling/executive order/resolution that set the status. For many of the person-related ones, use significant event (P793). "Legal status" is bad modelling. --Yair rand (talk) 03:29, 7 August 2018 (UTC)
  • Comment, I'm not sure about this one... I can see the value of a Property that is flexible and can handle edge cases and obscure circumstances that don't really have a precise-definition property. However, that could also make it more confusing and thus create difficulty rather than simplicity. For example, a person could theoretically have several simultaneous 'legal status' statements about all sorts of different things: legal status -> Married; legal status -> Adopted; legal status -> missing presumed dead; legal status -> bankrupt; legal status -> on parole; legal status -> stateless.... Wittylama (talk) 11:11, 8 August 2018 (UTC)
  • Symbol oppose vote.svg Oppose we already have dedicated properties for some of the uses cases. If other proposals are too broad to be edited efficiently, I doubt this would work out for this one. It seems that the proposer doesn't intend to use it anyways ..
    --- Jura 16:17, 10 August 2018 (UTC)
  • Symbol oppose vote.svg Oppose Strong oppose. As I said on the copyright proposal, this is ludicrously vague. There are so many different things that are referred to as legal statuses; immigration status, status of legislation, marital status, many different tax statuses, customs status, etc. Mr. Guye (talk) 19:11, 29 August 2018 (UTC)
    • We should create properties for many of the examples. Mr. Guye (talk) 19:12, 29 August 2018 (UTC)

Morse code[edit]

   Under discussion
Descriptioncode for a letter or number
Representsmorse code (Q79897)
Data typeExternal identifier
Domainitems for letters and numbers
Allowed values[.-]++
Example 1A (Q9659).-
Example 2E (Q9907).
Example 3H (Q9914)....
Example 4I (Q9893)..
Example 55 (Q203).....
Planned useadd to relevant items

Motivation[edit]

(Add your motivation for this property here.)
--- Jura 00:34, 11 August 2018 (UTC)

Discussion[edit]

  • @Jura1:The examples are unclear and not IDs! --David (talk) 08:50, 11 August 2018 (UTC)
    • They should match the regex. If you have suggestions for a better formatting, I'm interested. The code should uniquely identify a letter/number, thus the choice of external-id.
      --- Jura 09:11, 11 August 2018 (UTC)
  • Symbol support vote.svg Support Symbol oppose vote.svg Oppose (intended to forestall this property's creation per Arthur's comments; will come back to this with more detail after some thought Mahir256 (talk) 20:59, 21 August 2018 (UTC)) @Jura1: even the generic motivations that User:Thierry Caro gives for his property proposals are immensely better than no express motivation given at all. Mahir256 (talk) 18:28, 11 August 2018 (UTC)
    • Somehow I followed GZW's sample. As any property I propose, I intend to add it to the relevant items. (I just added that in the proposal above).
      --- Jura 19:18, 11 August 2018 (UTC)
  • Pictogram voting comment.svg Comment I support the property, but the choice of datatype is exotic. Is the usage only for letters and digits? Not for any phrases or signals such as SOS? That affects the choice of datatype. I also appreciate writing it out. Will support after. – Susanna Ånäs (Susannaanas) (talk) 04:59, 12 August 2018 (UTC)
  • Symbol support vote.svg Support I guess it's all there already. – Susanna Ånäs (Susannaanas) (talk) 10:45, 12 August 2018 (UTC)
  • Pictogram voting comment.svg Comment (edited - see below) too few items would benefit from this property. It could be an interesting property (like a transcription) for lexemes perhaps though. ArthurPSmith (talk) 13:51, 13 August 2018 (UTC)
    • No need. With this property on items, it could be calculated.
      --- Jura 12:15, 18 August 2018 (UTC)
      • Alternatively, one could use code (P3295) with qualifier encoding (P3294) as for example in [1]. --Pasleim (talk) 18:31, 19 August 2018 (UTC)
      • Didn't notice the values. Yes. A dedicated property would make it easier to ensure that they are unique and we don't miss some of them.
        --- Jura 20:29, 19 August 2018 (UTC)
    • @ArthurPSmith: With an import of Chinese characters coming along, and the existence of Chinese telegraph code (Q5100952), I'm not so sure about "too few"; also it'd be interesting to use this property for importing the contents of various telegraph code books somehow. Mahir256 (talk) 14:14, 20 August 2018 (UTC)
  • Symbol support vote.svg Support (Second thoughts. Lymantria (talk) 05:42, 22 August 2018 (UTC)) The possible use extends the (indeed) limited items it directly applies to, as it can be a calculated property for words, longer codes, etc. Lymantria (talk) 16:35, 20 August 2018 (UTC)
Pictogram voting comment.svg Comment @Jura1, Lymantria, Mahir256, Pasleim: So two more things that I feel need to be clarified here:
  • Are the spaces in the code significant? The regex (which as written is invalid by the way - the '-' should be first) allows space, dot, and dash characters. In the examples above there is a space between each dot or dash. I would have thought that, if anything, spaces should only appear between distinct character codes (for example if we are to add them for Chinese telegraph codes, you would need a space between the codes for each digit). Is there a standard that can be referenced to describe how this is traditionally done in plain text? To call it an "external id" we need to have a single universally agreed string format for the codes, you can't have various alternatives with different spacings etc.
  • We really need to pin down the domain. The international standard (ITU) Morse code only applies to the (capital) letters A-Z and digits 0-9. Do we intend to allow other characters or not? The enwiki page lists various extensions for punctuation and accented characters. Chinese has been suggested here, presumably a qualifier would be required to indicate the upper encoding. Are there other cases like this?
I think I could support it if it applied to significantly more than just the 36 standard ITU characters, but the proposal so far isn't clear on either of these questions. ArthurPSmith (talk) 20:33, 20 August 2018 (UTC)
  • No worries. I noted your oppose earlier about the proposal in its present form. Chinese telegraph codes wont work with the proposal in it's present form and they shouldn't.
    --- Jura 21:34, 20 August 2018 (UTC)
Ok, Symbol oppose vote oversat.svg Strong oppose then. But even so, you still haven't addressed the first question just above - why do you allow space in the regex (and have spaces in your examples) if you don't intend to allow this to be applied to anything other than the 36 characters? No morse code converter that I can find on the internet translates single characters to strings that have spaces, they are simple spaceless '...', '.-', etc. with the space character used to separate the code for one letter from another in a multi-letter string. ArthurPSmith (talk) 20:11, 21 August 2018 (UTC)
  • Pictogram voting comment.svg Comment thanks for your feedback. I think there is sufficient support for this property to be created. I don't see a point in including [0-9] for Chinese codes, but except the opposer, I don't think any does. If there are problems with implementing it, we can discuss it later/improve the format.
    --- Jura 20:21, 21 August 2018 (UTC)
    • @Jura1: you are being overeager with a poorly prepared proposal. @Mahir256, ديفيد عادل وهبة خليل 2, Susannaanas, Pasleim, Lymantria: this is CLEARLY not ready as far as I can see, can one of you please comment in regard to the issues I've raised. And note that a very simple SPARQL query already returns the Morse code values for the letters (MINUS the spaces Jura inserted) - See tinyurl.com/y75euhhh . ArthurPSmith (talk) 20:32, 21 August 2018 (UTC)
      • I think that just illustrates the need for a separate property. We don't want Wikidata to be website with half the list.
        --- Jura 20:39, 21 August 2018 (UTC)
        • @Jura1: I was slightly disappointed that you didn't react to the spaces-question by ArthurPSmith, but I see below you have removed the spaces in the proposal. Thanks for that. Perhaps you could enlighten ArthurPSmith and myself to show benefit of this proposal in the use of for instance racon signal (P3994), as the signals this property is about are in fact morse codes. Initially I thought your proposal would allow us to add the morse code as qualifier to values of this property, that would make sense to me. I'm starting to doubt about the usefulness. Lymantria (talk) 05:40, 22 August 2018 (UTC)
            • @Lymantria: It's a point that was there from the beginning and had been discussed, we could continue to debate if the spaces should be there, small, smaller, large, etc. Anyways, with this property, a query should allow to convert the P3994 value to Morse. If the current list wasn't incomplete and we had checks in place to ensure it's robustness, it could also be done with the P3295/4 version. Unfortunately the current approach is somewhat unsatisfactory.
              Chinese codes could use the same to convert into Morse signals.
              --- Jura 05:49, 22 August 2018 (UTC)
              • @Jura1: What I was thinking of is
                < Ölands södra grund (Q10727264) View with Reasonator View with SQID > racon signal (P3994) View with SQID < OE >
                morse search < --- . >
                . Seems not intended by your proposal (and needs a space in the regex). Lymantria (talk) 05:55, 22 August 2018 (UTC)
                • @Lymantria: Yes, I understood that. For simple lookup. it might be easier to link the items with the code. If there is interest, we could have another property that transcribes texts into morse.
                  --- Jura 06:10, 22 August 2018 (UTC)
  • Pictogram voting comment.svg Comment we need to find a way to improve the current, clearly unsatisfying situation. I simplified the string format @Lymantria, Mahir256, Susannaanas: what do you think? Do you still support it?
    --- Jura 03:55, 22 August 2018 (UTC)
    • Change to Symbol neutral vote.svg Neutral for now, see above. Lymantria (talk) 05:40, 22 August 2018 (UTC)
  • Pictogram voting comment.svg Comment I see no big reason to object, it's better now. I'd rather be Symbol neutral vote.svg Neutral and let someone with clear objection or support voice out. – Susanna Ånäs (Susannaanas) (talk) 11:09, 22 August 2018 (UTC)
  • Symbol support vote.svg Support Worldm99 (talk) 12:39, 19 September 2018 (UTC)

Qualifiers for locations within pdfs, djvu etc[edit]

preface page number[edit]

(added 6 December 2017 (UTC))

   Under discussion
Descriptionqualifier to indicate the number of the page of a document in which the first page of a preface is located
Data typeQuantity
DomainCommons documents (pdf, djvu etc), URLs to pdfs/djvu
Allowed valuesnumbers
Example

table of contents page number[edit]

(added 15:42, 6 December 2017 (UTC))

   Under discussion
Descriptionqualifier to indicate the number of the page of a document in which the first page of the table of contents is located
Data typeQuantity
DomainCommons documents (pdf, djvu etc), URLs to pdfs/djvu
Allowed valuesnumbers
Example

alphabetical index page number[edit]

(added 15:42, 6 December 2017 (UTC))

   Under discussion
Descriptionqualifier to indicate the number of the page of a document in which the first page of the alphabetical index is located
Data typeQuantity
DomainCommons documents (pdf, djvu etc), URLs to pdfs/djvu
Allowed valuesnumbers
Example

persons index page number[edit]

(added 15:42, 6 December 2017 (UTC))

   Under discussion
Descriptionqualifier to indicate the number of the page of a document in which the first page of the index of names of people is located
Data typeQuantity
DomainCommons documents (pdf, djvu etc), URLs to pdfs/djvu
Allowed valuesnumbers
Example

place name index page number[edit]

(added 15:42, 6 December 2017 (UTC))

   Under discussion
Descriptionqualifier to indicate the number of the page of a document in which the first page of the index of names of geographic place names is located
Data typeQuantity
DomainCommons documents (pdf, djvu etc), URLs to pdfs/djvu
Allowed valuesnumbers
Example

table of illustrations page number[edit]

(added 15:42, 6 December 2017 (UTC))

   Under discussion
Descriptionqualifier to indicate the number of the page of a document in which the first page of the table of illustrations is located
Data typeQuantity
DomainCommons documents (pdf, djvu etc), URLs to pdfs/djvu
Allowed valuesnumbers
Example

end notes page number[edit]

(added 6 December 2017 (UTC))

   Under discussion
Descriptionqualifier to indicate the number of the page of a document in which the first page of end notes is located
Data typeQuantity
DomainCommons documents (pdf, djvu etc), URLs to pdfs/djvu
Allowed valuesnumbers
Example

glossary page number[edit]

(added 6 December 2017 (UTC))

   Under discussion
Descriptionqualifier to indicate the number of the page of a document in which the first page of the glossary is located
Data typeQuantity
DomainCommons documents (pdf, djvu etc), URLs to pdfs/djvu
Allowed valuesnumbers
Example

bibliography page number[edit]

(added 6 December 2017 (UTC))

   Under discussion
Descriptionqualifier to indicate the number of the page of a document in which the first page of the glossary is located
Data typeQuantity
DomainCommons documents (pdf, djvu etc), URLs to pdfs/djvu
Allowed valuesnumbers
Example

appendix page number[edit]

   Under discussion
Descriptionqualifier to indicate the number of the page of a document in which the first page of a appendix is located
Data typeQuantity
DomainCommons documents (pdf, djvu etc), URLs to pdfs/djvu
Allowed valuesnumbers
Example

title or cover page number[edit]

   Under discussion
Descriptioncreated as title page number (P4714) qualifier to indicate the number of the page of a document in which the title page is located
Data typeQuantity
Template parameter"Cover image", in Wikisource indexes
DomainCommons documents (pdf, djvu etc), URLs to pdfs/djvu
Allowed valuesnumbers
ExampleFile:Relatório ao governador do estado de Alagoas (1929-1930).pdf4
Motivation

This is useful for Wikisource and the upcoming integration of Wikibase into Commons. ~nmaia d 18:17, 27 July 2017 (UTC)

  • Given some of the comments below, rephrased the initial proposal for a "cover page" property as a qualifier for pdf/djvu files and completed it with a few other qualifiers that can (if applicable), but don't have to be used. Datatype "number" should be quantity. These could be used independently of Commons.
    --- Jura 16:24, 6 December 2017 (UTC)
Discussion

Aubrey
Viswaprabha (talk)
Micru
Tpt
EugeneZelenko
User:Jarekt
Maximilianklein (talk)
Don-kun
VIGNERON (talk)
Jane023 (talk) 08:21, 30 May 2013 (UTC)
Alexander Doria (talk)
Ruud 23:15, 24 June 2013 (UTC)
Kolja21
arashtitan
Jayanta Nath
Yann (talk)
John Vandenberg (talk) 09:14, 30 November 2013 (UTC)
JakobVoss
Danmichaelo (talk) 19:30, 16 February 2014 (UTC)
Ravi (talk)
Mvolz (talk) 08:21, 20 July 2014 (UTC)
Hsarrazin (talk) 07:56, 9 August 2014 (UTC)
Accurimbono
Mushroom
PKM (talk) 19:58, 10 October 2014 (UTC)
Revi 16:54, 29 November 2014 (UTC)
Giftzwerg 88 (talk) 23:36, 1 January 2015 (UTC)
Almondega (talk) 00:17, 5 August 2015 (UTC)
maxlath
Jura to help sort out issues with other projects
Epìdosis
Skim (talk) 13:52, 24 June 2016 (UTC)
Marchitelli (talk) 12:29, 5 August 2016 (UTC)
BrillLyle (talk) 15:33, 26 August 2016 (UTC)
Alexmar983 (talk) 23:53, 28 August 2016 (UTC)
Finn Årup Nielsen (fnielsen) (talk) 10:44, 29 August 2016 (UTC)
Chiara (talk) 14:15, 29 August 2016 (UTC)
Thibaut120094 (talk) 20:31, 14 September 2016 (UTC)
Ivanhercaz | Discusión Plume pen w.png 15:30, 31 October 2016 (UTC)
YULdigitalpreservation (talk) 17:35, 10 November 2016 (UTC)
User:Jc3s5h
PatHadley (talk) 21:51, 15 December 2016 (UTC)
Erica (ohmyerica) (talk) 19:26, 1 January 2017 (UTC)
User:Timmy_Finnegan
Mauricio V. Genta (talk) 05:38, 12 March 2017 (UTC)
Sam Wilson 09:24, 24 May 2017 (UTC)
Sic19 (talk) 22:25, 12 July 2017 (UTC)
Andreasmperu
MartinPoulter (talk) 09:21, 20 July 2017 (UTC)
ThelmadatterThelmadatter (talk) 01:11, 13 September 2017 (UTC)
Zeroth (talk) 15:01, 16 September 2017 (UTC)
Emeritus
Ankry
Beat Estermann (talk) 20:07, 12 November 2017 (UTC)
Shilonite - specialize in cataloging Jewish & Hebrew books
Elena moz
Oa01 (talk) 10:52, 3 February 2018 (UTC)
Maria zaos (talk) 11:39, 25 March 2018 (UTC)
Wikidelo (talk) 13:07, 15 April 2018 (UTC)
Mfchris84 (talk) 10:08, 27 April 2018 (UTC)
Mlemusrojas (talk) 3:36, 30 April 2018 (UTC)
salgo60 Salgo60 (talk) 12:42, 8 May 2018 (UTC)
Dick Bos (talk) 14:35, 16 May 2018 (UTC)
Marco Chemello (BEIC) (talk) 07:26, 30 May 2018 (UTC)
Harshrathod50
 徵國單  (討論 🀄) (方孔錢 💴) 14:35, 20 July 2018 (UTC)
Alicia Fagerving (WMSE)
Louize5 (talk) 20:05, 11 September 2018 (UTC)
Pictogram voting comment.svg Notified participants of WikiProject Books.

  • Symbol support vote.svg Support --Jarekt (talk) 19:37, 27 July 2017 (UTC)
  • Symbol support vote.svg Support --Mauricio V. Genta (talk) 20:37, 27 July 2017 (UTC)
  • Pictogram voting question.svg Question Is this a qualifier for either Wikisource index page (P1957) or scanned file on Wikimedia Commons (P996)? It seems that as a property on its own it has to refer to some particular edition or scan of a book. Sam Wilson 00:44, 28 July 2017 (UTC)
    • Neither, this would be used directly as a statement for a document file on Commons. Or for specific editions with Wikidata entries, like you mentioned. ~nmaia d 02:04, 28 July 2017 (UTC)
      • But individual files on Commons don't get individual WD items. For example, The Nether World (Q23308118) has three scanned files and therefore 3 cover pages. How would this property be used for that sort of item? (Sorry if I'm misunderstanding things.) Sam Wilson 07:53, 28 July 2017 (UTC)
        • Correct, but Commons is getting a Wikidata backend very soon, which means files will be able to be described using our properties; it's not common but possible that this property can be used on Wikidata too, in a specific edition of a work, when the accompanying pdf is present. Regarding your second question, The Nether World (Q23308118) has three covers because it has three volumes: we can add this property to each volume on Commons, to make it more accurate. In my opinion, using image (P18) with page(s) (P304) is not a very satisfying solution, as it doesn't necessarily make it clear to reusers that it's the cover image being shown. ~nmaia d 11:14, 28 July 2017 (UTC)
  • Pictogram voting question.svg Question Is this a statement for direct cover image from c:Category:Book covers category? Skim (talk) 07:03, 28 July 2017 (UTC)
    • No, I've reworded the label according to @Maxlath's suggestion to make it clearer (thanks!) ~nmaia d 11:14, 28 July 2017 (UTC)
  • Pictogram voting question.svg Question Could the property label be more explicit? Something like "cover page number"? As such, I first thought this property was to link to the media file displaying the cover image. -- Maxlath (talk) 08:57, 28 July 2017 (UTC)
    • Done, cheers! ~nmaia d 11:14, 28 July 2017 (UTC)
I also thought that would be a commons file. We also do need "cover page number" for PDF/DjVu files, but that should be a qualifier of scanned file on Wikimedia Commons (P996) as even 2 different scans of the same book might be off by a page or two. This property does not make sense if not paired up with a specific file. --Jarekt (talk) 16:35, 28 July 2017 (UTC)
Pictogram voting question.svg Question Is it somewhere documented that the Wikibase backend for Commons will use the same properties as Wikidata? My current understanding was that it will have its own properties. --Pasleim (talk) 19:29, 28 July 2017 (UTC)
Ah, in that case it seems this property would be most useful in Commons. However some people here in the discussion see value in it as a qualifier, so I'll leave it up to them to argue for it. ~nmaia d 16:08, 15 October 2017 (UTC)
Pictogram voting question.svg Question An other possibility for the range would be to have something like "my book cover.jpg" or "my book.djvu/2". But the second syntax is not supported yet by the "commons media" datatype (but it should be possible to add support of it). Tpt (talk) 20:24, 28 July 2017 (UTC)
  • Symbol support vote.svg Support if this a a qualifier for the scanned file on Wikimedia Commons (P996) property. It would have not meaning in another context... --Hsarrazin (talk) 15:53, 30 July 2017 (UTC)
    • Symbol support vote.svg Support in this case too. Skim (talk) 05:41, 31 July 2017 (UTC)
  • Pictogram voting comment.svg Comment why shouldn't this be stored directly at Commons?
    --- Jura 15:28, 16 August 2017 (UTC)
  • because Commons is not the main user, but wikisource(s) ? --Hsarrazin (talk) 16:11, 16 August 2017 (UTC)
    • I don't think Commons Wikibase wont be accessible from Wikisource.
      --- Jura 16:45, 16 August 2017 (UTC)
  • Symbol support vote.svg Support ديفيد عادل وهبة خليل 2 (talk) 20:01, 1 October 2017 (UTC)
  • Symbol oppose vote.svg Oppose I've marked this as not ready and I don't believe it will work in wikidata until I actually see a concrete example of an item where this property could be added, or a statement where it could be used as a qualifier. The example in the current proposal is invalid - the "File" linked is not a wikidata item with a Q ID. ArthurPSmith (talk) 18:27, 11 October 2017 (UTC)
  • I agree with ArthurPSmith that it would be nice to have a proper example. ChristianKl (talk) 15:28, 15 October 2017 (UTC)

Aubrey
Viswaprabha (talk)
Micru
Tpt
EugeneZelenko
User:Jarekt
Maximilianklein (talk)
Don-kun
VIGNERON (talk)
Jane023 (talk) 08:21, 30 May 2013 (UTC)
Alexander Doria (talk)
Ruud 23:15, 24 June 2013 (UTC)
Kolja21
arashtitan
Jayanta Nath
Yann (talk)
John Vandenberg (talk) 09:14, 30 November 2013 (UTC)
JakobVoss
Danmichaelo (talk) 19:30, 16 February 2014 (UTC)
Ravi (talk)
Mvolz (talk) 08:21, 20 July 2014 (UTC)
Hsarrazin (talk) 07:56, 9 August 2014 (UTC)
Accurimbono
Mushroom
PKM (talk) 19:58, 10 October 2014 (UTC)
Revi 16:54, 29 November 2014 (UTC)
Giftzwerg 88 (talk) 23:36, 1 January 2015 (UTC)
Almondega (talk) 00:17, 5 August 2015 (UTC)
maxlath
Jura to help sort out issues with other projects
Epìdosis
Skim (talk) 13:52, 24 June 2016 (UTC)
Marchitelli (talk) 12:29, 5 August 2016 (UTC)
BrillLyle (talk) 15:33, 26 August 2016 (UTC)
Alexmar983 (talk) 23:53, 28 August 2016 (UTC)
Finn Årup Nielsen (fnielsen) (talk) 10:44, 29 August 2016 (UTC)
Chiara (talk) 14:15, 29 August 2016 (UTC)
Thibaut120094 (talk) 20:31, 14 September 2016 (UTC)
Ivanhercaz | Discusión Plume pen w.png 15:30, 31 October 2016 (UTC)
YULdigitalpreservation (talk) 17:35, 10 November 2016 (UTC)
User:Jc3s5h
PatHadley (talk) 21:51, 15 December 2016 (UTC)
Erica (ohmyerica) (talk) 19:26, 1 January 2017 (UTC)
User:Timmy_Finnegan
Mauricio V. Genta (talk) 05:38, 12 March 2017 (UTC)
Sam Wilson 09:24, 24 May 2017 (UTC)
Sic19 (talk) 22:25, 12 July 2017 (UTC)
Andreasmperu
MartinPoulter (talk) 09:21, 20 July 2017 (UTC)
ThelmadatterThelmadatter (talk) 01:11, 13 September 2017 (UTC)
Zeroth (talk) 15:01, 16 September 2017 (UTC)
Emeritus
Ankry
Beat Estermann (talk) 20:07, 12 November 2017 (UTC)
Shilonite - specialize in cataloging Jewish & Hebrew books
Elena moz
Oa01 (talk) 10:52, 3 February 2018 (UTC)
Maria zaos (talk) 11:39, 25 March 2018 (UTC)
Wikidelo (talk) 13:07, 15 April 2018 (UTC)
Mfchris84 (talk) 10:08, 27 April 2018 (UTC)
Mlemusrojas (talk) 3:36, 30 April 2018 (UTC)
salgo60 Salgo60 (talk) 12:42, 8 May 2018 (UTC)
Dick Bos (talk) 14:35, 16 May 2018 (UTC)
Marco Chemello (BEIC) (talk) 07:26, 30 May 2018 (UTC)
Harshrathod50
 徵國單  (討論 🀄) (方孔錢 💴) 14:35, 20 July 2018 (UTC)
Alicia Fagerving (WMSE)
Louize5 (talk) 20:05, 11 September 2018 (UTC)
Pictogram voting comment.svg Notified participants of WikiProject Books @NMaia: Can you provide an example? ChristianKl (talk) 21:54, 3 November 2017 (UTC)

Throughout the discussions I was convinced this was more suitable as a Commons property, but since others saw potential in it, I let the discussion happen on its own. ~nmaia d 21:05, 4 November 2017 (UTC)
  • Symbol oppose vote.svg Oppose in its current form, but if this were to be a qualifier for scanned file on Wikimedia Commons (P996) and were renamed "title page number" as that seems to be what it's actually representing. A "cover page" I think is the actual cover of a book, whereas this is (I think) about the title page (Q1339862). Sam Wilson 01:59, 6 November 2017 (UTC)
  • Symbol support vote.svg Support as title page number qualifier for scanned file on Wikimedia Commons (P996). It should be possible to get this information from statements here. Additional qualifiers for table of contents, place name index, etc. would be helpful.
    --- Jura 08:39, 28 November 2017 (UTC)
  • @Jura1: If you support it in that form, can you provide an example of how you would want it to be used and edit the description to express the new scope? ChristianKl () 14:30, 6 December 2017 (UTC)
    • sure, I added above accordingly, including some other qualifiers.
      --- Jura 15:42, 6 December 2017 (UTC)
  • Ok, this is now a completely revised proposal for 8(?) new properties; I believe (A) it should start over from scratch to avoid the confusion of the above discussion about a quite different proposal, and (B) all of these seem much more appropriate for discussion as Commons properties rather than as Wikidata properties - on Commons there would be no need to limit these to being just qualifiers. So I'd recommend we table this proposal until the Commons structured data implementation is close, and then introduce these as proposed properties there specifically for Commons. I don't see that they add much useful to have them within Wikidata itself. ArthurPSmith (talk) 20:23, 6 December 2017 (UTC)
  • Pictogram voting comment.svg Comment I'm not really aware of what Commons is doing, intends to do or might eventually have done. It's not really relevant to these proposals. The problem is that Commons and other archives host pdfs and similar files and Wikidata links to them, but these are generally not structured. Some files are transcribed at Wikisource, but not all of them. As we can't do statements on statements, we need specific qualifiers. As the initial proposal was for a title page and the qualifier approach has support, I'm marking the first one as ready.
    --- Jura 20:29, 6 December 2017 (UTC)
  • ✓ Done the first one as title page number (P4714): @NMaia, Jarekt, Mauricio V. Genta, Hsarrazin, Skim, ديفيد عادل وهبة خليل 2: please make good use of it.
    --- Jura 11:36, 3 January 2018 (UTC)
  • Pictogram voting comment.svg Comment Looks like this got accidentally archived.
    --- Jura 06:26, 25 February 2018 (UTC)
  • Pictogram voting comment.svg Comment fixed again.
    --- Jura 13:53, 11 August 2018 (UTC)

value is more specific than[edit]

value is subclass of that of[edit]

   Under discussion
Descriptionthis value is more specific than that of the parent (super)class or broader class; the parent (super)class or broader class has the same property statement, and the relation between this value and the value in the superclass is subclass of (P279) (To be used in a source field)
Data typeItem
Domainany item with subclass of (P279) or part of (P361)
Allowed valuessuperclasses or broader classes of the subject item (subject item is a subclass of (P279) or part of (P361) of the value)
Example 1
(Note that mitral valve disease (Q18557136) is a subclass of heart valve disease (Q1130519), and the P927 value of mitral valve disease (Q18557136) is a subclass of the P927 value of heart valve disease (Q1130519) (mitral valve (Q369939) subclass of (P279) heart valve (Q215620)))
Example 2
(Note that finding by heart auscultation (Q30078856) is a subclass of finding by auscultation (Q30079797), and the P5134 value of finding by heart auscultation (Q30078856) is a subclass of the P5134 value of finding by auscultation (Q30079797) (heart auscultation (Q30078800) subclass of (P279) auscultation (Q779054)))
Example 3
(Note that set of imaginary numbers (Q47310259) is a part of set of complex numbers (Q26851286), and the P2670 value of set of imaginary numbers (Q47310259) is a subclass of the P2670 value of set of complex numbers (Q26851286) (imaginary number (Q9165172) subclass of (P279) complex number (Q11567)))
Example 4
< hydrogen fluoride (Q2468) View with Reasonator View with SQID > has part (P527) View with SQID < fluorine (Q650) View with Reasonator View with SQID >
value is subclass of that of search < hydrogen halide (Q1572088) >

(Note that hydrogen fluoride (Q2468) is a subclass of fluorine (Q650), and the P527 value of hydrogen fluoride (Q2468) is a subclass of the P527 value of hydrogen halide (Q1572088) (fluorine (Q650) subclass of (P279) group 17 (Q19605)))
See alsoWikidata:Property proposal/value is inherited from

value is part of that of[edit]

   Under discussion
Descriptionthis value is more specific than that of the parent (super)class or broader class; the parent (super)class or broader class has the same property statement, and the relation between this value and the value in the superclass is part of (P361) (To be used in a source field)
Data typeItem
Domainany item with subclass of (P279) or part of (P361)
Allowed valuessuperclasses or broader classes of the subject item (subject item is a subclass of (P279) or part of (P361) of the value)
Example 1
(Note that lung cancer (Q47912) is a subclass of respiratory system cancer (Q7315926), and the P927 value of stomach cancer (Q189588) is a part of the P927 value of stomach disease (Q175827) (human lung (Q2640512) part of (P361) respiratory system (Q7891)))
Example 2
(Note that lung lobe development (Q21170946) is a part of lung development (Q14327711), and the P927 value of lung lobe development (Q21170946) is a part of the P927 value of lung development (Q14327711) (pulmonary lobe (Q7259536) part of (P361) lung (Q7886)))
Example 3MISSING
See alsoWikidata:Property proposal/value is inherited from

Motivation[edit]

Wikidata Inheritance Model.svg

In many cases, there are similar tree structures among parallel concepts. These proposed qualifiers are useful to explicitly clarify these relationships, and to check if the relation is broken. See also Wikidata:Property proposal/value is inherited from.

Anandhisuresh (talk) 17:16, 28 February 2018 (UTC)anandhisuresh Tobias1984
Doc James
User:Bluerasberry
Wouterstomp
Gambo7
Daniel Mietchen
Andrew Su
Peter.C
Klortho
Remember
Matthiassamwald
Projekt ANA
Andrux
Pavel Dušek
Was a bee
Alepfu
FloNight
Genewiki123
Emw
emitraka
Lschriml
Mvolz
Franciaio
User:Lucas559
User:Jtuom
Chris Mungall
ChristianKl
Gstupp
Geoide
Sintakso
علاء
Dr. Abhijeet Safai
Adert
CFCF
Jtuom
Lucas559
Drchriswilliams
Okkn
CAPTAIN RAJU
LeadSongDog
Ozzie10aaaa
Sami Mlouhi
Marsupium
Netha Hussain
Abhijeet Safai
ShelleyAdams
Fractaler
Seppi333
Shani Evenstein
Csisc
Pictogram voting comment.svg Notified participants of WikiProject Medicine: These qualifiers are especially useful to describe medical concepts. --Okkn (talk) 15:10, 20 August 2018 (UTC)

As per Pasleim's suggestion, we would deal with this property as a source property, instead of qualifiers. So I chaged the description. --Okkn (talk) 12:20, 12 September 2018 (UTC)

Discussion[edit]

  • Pictogram voting comment.svg Comment I don't see how this adds value to wikidata - it looks like a duplication of information which can be derived from the relationships on the values of these statements. Or maybe I'm missing something here? It seems at the least a confusing way to go about this... ArthurPSmith (talk) 20:11, 20 August 2018 (UTC)
    @ArthurPSmith: Thank you for commenting. For example, lung cancer (Q47912) is a subclass of respiratory system cancer (Q7315926) (pathological condition (cancer) is specified, but affected organ is NOT specified) and lung disease (Q3392853) (pathological condition is NOT specified, but affected organ (lung) is specified).
subclass of
Normal rank respiratory system cancer Arbcom ru editing.svg edit
▼ 0 reference
+ add reference
Normal rank lung disease Arbcom ru editing.svg edit
▼ 0 reference
+ add reference
+ add value
If we have qualifiers "value is subclass/part of that of" and "value is inherited from", the anatomical location (P927) claim in lung cancer (Q47912) can be represented as follow:
anatomical location
Normal rank human lung Arbcom ru editing.svg edit
value is inherited from lung disease
value is part of that of respiratory system cancer
▼ 0 reference
+ add reference
+ add value
By doing so, we can explicitly declare the detailed relationships between the subject class and its superclasses, i.e. everyone can understand why respiratory system cancer (Q7315926) is a broader concepts than lung cancer (Q47912).
Of course if the data are complete, this information can be automatically generated. But practically, data are sometimes missed or changed mistakenly. We can detect not only ①mistakenly removing or changing of P279 claims in the subject class, but also ② mistakenly removing or changing of some inherited values in the superclass, by using these qualifiers. When editing in the superclass, we sometimes fail to notice the existence of subclasses, and in order to resolve interwiki conflicts or to fix the wrong external IDs, we would change some values. These qualifiers prevent us from causing mismatching in P279 claims in the subclasses.
However, we must beware that any bot should not automatically change these qualifiers according to the changes in the superclass. --Okkn (talk) 06:02, 21 August 2018 (UTC)
  • This still seems overly hard to follow - is it really necessary? Pinging the taxonomy project here.. ArthurPSmith (talk) 18:29, 23 August 2018 (UTC)
    • I believe these qualifiers are necessary to actualize high robustness of data and their structures. That is particularly vital for healthcare information, I think. --Okkn (talk) 18:44, 23 August 2018 (UTC)

99of9
Abbe98
Achim Raschka (talk)
Brya (talk)
Dan Koehl (talk)
Daniel Mietchen (talk)
Faendalimas
FelixReimann (talk)
Infovarius (talk)
Joel Sachs
Josve05a (talk)
Klortho (talk)
Lymantria (talk)
MargaretRDonald
Mellis (talk)
Michael Goodyear
MPF
Mr. Fulano (talk)
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

Pictogram voting comment.svg Comment My first impression also is that it looks complicated, and does not seem to be adding new information. It may help in adding robustness, but I can't really say if this would be worth it. Would this be used as a qualifier? - Brya (talk) 04:54, 24 August 2018 (UTC)

  • @Brya: Yes, they would be used as qualifiers. Not only robustness but also the notation of value inheritance (where the value is inherited from, or how the value is updated from superclass), would be added. --Okkn (talk) 06:57, 24 August 2018 (UTC)
    • Couldn't you get much the same effect by just adding "subclass of: " (or whatever is relevant) as a qualifier? - Brya (talk) 11:03, 24 August 2018 (UTC)

Pakistan Railways station code[edit]

   Under discussion
Descriptioncode to identify a railway station operated by Pakistan Railways
Data typeExternal identifier
Template parameter"code" in en:Template:Infobox station
Domainrailway station (Q55488)'s in Pakistan (Q843)
Allowed values[A-Z]+
Example 1Karachi City Station (Q4373381) → KYC
Example 2Peshawar Cantonment railway station (Q7171369) → PSC
Example 3Lahore Junction railway station (Q3695748) → LHR
Example 4Islamabad railway station (Q15228858) → MGLA
Sourcevarious Wikipedia articles and references from the Pakistani government as may be found regarding this property
Planned useadd this to items for stations (especially a great deal which only have sitelinks to urwiki)
Number of IDs in sourceas many as there have been railway stations in Pakistan—around 1200, according to some estimates I found
Expected completenesseventually complete (Q21873974)
Robot and gadget jobsnot yet, though this is surely possible
See alsoIndian Railways station code (P5696), Amtrak station code (P4803), ESR station code (P2815), China railway TMIS station code (P1378)

Motivation[edit]

The presence of this identifier is motivated by similar identifiers for the United States (Amtrak station code (P4803)), Russia/the USSR (ESR station code (P2815)), China (China railway TMIS station code (P1378)), and most recently India (Indian Railways station code (P5696)). Mahir256 (talk) 01:15, 25 August 2018 (UTC)

Discussion[edit]

@Thierry Caro, BukhariSaeed, Obaid Raza: who might find this interesting.

Why can't be used station code (P296) with a qualifier? --Sabas88 (talk) 09:43, 27 August 2018 (UTC)

@Sabas88: If you would like to propose the deletion of the other four properties I mentioned (plus more of the sort), you are welcome to do so, but in the meantime having a separate property for this large collection of stations has its benefits, including the ability to easily define formatter URLs for each country on each country's respective property. Mahir256 (talk) 12:46, 27 August 2018 (UTC)
Symbol oppose vote.svg Oppose for now, if there are reasons that how codes in this country are used in URL schemes, I would change to support. --Liuxinyu970226 (talk) 23:58, 1 September 2018 (UTC)

described in Wikimedia article[edit]

   Under discussion
DescriptionThe topic is described in the specific Wikimedia article in detail (not just mentioned).
Data typeURL
Domainanything
Example 1Eastern Han Dynasty (Q1147037) -> https://en.wikipedia.org/wiki/Han_dynasty#Eastern_Han
Example 2Hussein Onyango Obama (Q15982328) -> https://en.wikipedia.org/wiki/Family_of_Barack_Obama#Hussein_Onyango_Obama
Example 3Place des Carmes (Q24834026) -> https://fr.wikipedia.org/wiki/Places_d%27Avignon#Place_des_Carmes
Example 4Tengwar (Q473725) -> https://de.wikipedia.org/wiki/Tengwar_und_Certar#Tengwar
See alsoglossary entry at Wikipedia (P5178) will be a subproperty

Motivation[edit]

This provides a weak form of sitelinks. As page content may be non-persistent, we probably needs a qualifier to indicate a permanent version. GZWDer (talk) 04:48, 31 August 2018 (UTC)

Discussion[edit]

Pictogram voting comment.svg Comment @GZWDer: This is currently handled to some degree by sitelinks to redirects. Would you intend to replace those sitelinks (which require a workaround to create) with these statements? ArthurPSmith (talk) 18:23, 31 August 2018 (UTC)
@ArthurPSmith: Sometimes they are red links (e.g. fr:Place des Carmes). Another example is en:Lupton family describes a number of people but no pages redirects to this page.--GZWDer (talk) 18:28, 31 August 2018 (UTC)
  • Pictogram voting comment.svg Comment Is there any reason for not using described at URL (P973) instead of creating an entirely new property? Other than that it's a great idea though, ever since not being able to create site links to redirects it's been harder to find whether Wikipedia contains any information on the item or not. Lewis Hulbert (talk) 01:39, 1 September 2018 (UTC)
    • Looks to me like this is intended to explicitly point out the material is covered in wikipedia. That is, it's actually a kind of sub- or weak interwiki, not a generic URL. Circeus (talk) 12:05, 11 September 2018 (UTC)
  • Symbol oppose vote.svg Oppose per Lewis Hulbert, use P973 is good enough, feel free to add this name as alias of that. --Liuxinyu970226 (talk) 00:07, 2 September 2018 (UTC)

subject stated as, predicate stated as[edit]

subject stated as[edit]

   Under discussion
Descriptionhow the subject was given in the source (only use as qualifier)
Data typeString
Example 1Antoine Chazal (Q2853791) Benezit ID (P2843) B00036491 <subject stated as> Antoine Toussaint de Chazal
Example 2(deprecated) Balkans (Q23522) GeoNames ID (P1566) 783759 <subject stated as> Balkan Peninisula
Example 3MISSING
Robot and gadget jobsBot to move all qualifiers stated as (P1932) of identifier properties to this property
See alsostated as (P1932)

predicate stated as[edit]

   Under discussion
Descriptionhow the predicate (property) was given in the source (only use as qualifier)
Data typeString
Example 1So Dear to My Heart (Q2090255) musical conductor (P3300) Ken Darby (Q2316737) <predicate stated as> Vocal director
Example 2MISSING
Example 3MISSING
See alsostated as (P1932), object has role (P3831) (used if there're specific items for this)

Motivation[edit]

Currently stated as (P1932) has description "use as qualifier to indicate how the value was given in the source", but is also used to indicate how subject or predicate was given. It is confusing, so we should split the property, leaving stated as (P1932) for "object stated as" only. GZWDer (talk) 20:31, 6 September 2018 (UTC)

Discussion[edit]

Symbol support vote.svg Support These make sense to me, although there has been some confusion among wikidata users about the terms "subject" and "predicate" so better labels might be helpful (could we say "item" and "property" here?). Also - should this be of type "monolingual string" (specifying a language) rather than just "string"? ArthurPSmith (talk) 19:02, 7 September 2018 (UTC)
If it is a monolingual string stated as (P1932) should be a monolingual string too; though most uses of stated as (P1932) are author names which have no language in itself.--GZWDer (talk) 23:40, 7 September 2018 (UTC)

Bank properties[edit]

See below for the description.

Foreign Transaction Fee[edit]

Descriptionforeign transaction fee applies to payments in foreign currencies
Representsforeign transaction fee (Q55863525)
Data typeQuantity
Domainpayment card (Q1436963)
Example 1American Express Gold Card (Q11285067) → 2 percentage (Q11229) (valid in place: Germany (Q183))
Example 2Amazon.de VISA Card (Q56510643) → 1.75 percentage (Q11229)
Example 3N26 Black (Q56247857) → 0 percentage (Q11229)
See alsoWikidata:Property_proposal/CardProps


Discussion[edit]

Trading Fee[edit]

   Done. trading fee (P5896) (Talk and documentation)
DescriptionA trading fee or brokerage commision is fee charged when buying stock or commodities at exchanges or at a bank
Representsbrokerage commission (Q10460910)
Data typeQuantity
Domaincurrency exchange (Q2002539), Securities account (Q2563572)
Example 1Degiro (Q23680150) → 0.026 percentage (Q11229) + 2 euro (Q4916) (applies to part: Xetra (Q819468), valid in place: Germany (Q183))
Example 2Bitfinex (Q29647473) → 0.2 percentage (Q11229) (applies to part: maker fee (Q55956741) and 0.1 percentage (Q11229) (applies to part: taker fee (Q55956748)
Example 3Flatex Depot (Q56525744) → 5.90 euro (Q4916) applies to part: Xetra (Q819468)
See alsoWikidata:Property_proposal/CardProps


Discussion[edit]

Account Charge / Subscription fee[edit]

DescriptionA monthly/yearly fee for using a service or account
Representsaccount charge (Q56489330)
Data typeQuantity
Domainsubscription service (Q26674207), financial services (Q837171)
Example 1Google Play Music (Q3238917) → 9.99 United States dollar (Q4917) (duration (P2047): 1 month (Q5151); valid in place (P3005): United States of America (Q30))
Example 2N26 Black (Q56247857) → 9.90 euro (Q4916) (duration (P2047): 1 month (Q5151))
Example 3Amazon Prime (Q21086634) → 69 euro (Q4916) (duration (P2047): 1 annum (Q1092296)); 7.99 euro (Q4916) (duration (P2047): 1 month (Q5151)) valid in place: Germany (Q183))
See alsoWikidata:Property_proposal/CardProps, fee (P2555)


Discussion[edit]

borrowing rate[edit]

   Done. borrowing rate (P5898) (Talk and documentation)
Descriptionthe p.a. borrowing/lending rate
Representsborrowing rate (Q1501526)
Data typeQuantity
Domainsubscription service (Q26674207), financial services (Q837171), loan (Q2914547)
Example 1DKB Cash (Q56489310) → 7.50 percentage (Q11229)
Example 2Barclaycard Visa (Q56489433) → 16.99 percentage (Q11229)
Example 3Madagascar (Q1019) → 60 percentage (Q11229) (time:2017,determination method:...) Reference Worldbank
See alsoWikidata:Property_proposal/CardProps


Discussion[edit]

interest rate[edit]

   Done. interest rate (P5899) (Talk and documentation)
DescriptionThe yearly interest rate
Representsborrowing rate (Q1501526)
Data typeQuantity
Domainfinancial services (Q837171)
Example 1DKB Cash (Q56489310) → 0.2 percentage (Q11229) (max amount 100000€)
Example 2N26 Black (Q56247857) → 0 percentage (Q11229)
Example 3Flatex Depot (Q56525744) → -0.4% percentage (Q11229) (start time: 2017)
See alsoWikidata:Property_proposal/CardProps

Discussion[edit]

Motivation[edit]

A foreign transaction fee applies to payments in foreign currencies. It is usually between 0-5%. A trading fee is important for exchanges as well as securities accounts. In respect to the existing properties

  • fee (P2555) (fee or toll payable to use or transit the subject)
  • cost (P2130) (amount of money spent on building or producing an object)
  • price (P2284) (published price listed or paid for a product)

I propose "Account Charge / Subscription fee" because fee (P2555) is quite general and doesn't indicate an ongoing process, a fee one has to pay just to be able to use the service. If most think that fee will do, I'll withdraw it. Another question is how to differentiate between "and" and "either", (ex. Amazon prime can be paid per month OR per year, Degiro charges per transaction 2€ PLUS 0.20%). I'm also not sure about the qualifier "duration", I'm thinking billing cycle (monthly, yearly) would be more precise. What do you think? Germartin1 (talk) 18:07, 8 September 2018 (UTC)

  • Symbol support vote.svg Support All David (talk) 07:18, 9 September 2018 (UTC)
  • Symbol oppose vote.svg Oppose I would use fee (P2555) for the fees, with an appropriate qualifier to link them to an item describing the type of fee. (We might need to create one.) − Pintoch (talk) 14:26, 16 September 2018 (UTC)
  • Symbol support vote.svg Support For all Nepalicoi (talk) 12:28, 17 September 2018 (UTC)

@ديفيد عادل وهبة خليل 2, Nepalicoi, Germartin1, Pintoch: ✓ Done: foreign transaction fee (P5895). − Pintoch (talk) 06:50, 21 September 2018 (UTC)

@ديفيد عادل وهبة خليل 2, Nepalicoi, Germartin1, Pintoch: ✓ Done: trading fee (P5896). − Pintoch (talk) 06:50, 21 September 2018 (UTC)

@ديفيد عادل وهبة خليل 2, Nepalicoi, Germartin1, Pintoch: ✓ Done: account charge / subscription fee (P5897). − Pintoch (talk) 06:51, 21 September 2018 (UTC)

@ديفيد عادل وهبة خليل 2, Nepalicoi, Germartin1, Pintoch: ✓ Done: borrowing rate (P5898). − Pintoch (talk) 06:52, 21 September 2018 (UTC)

@ديفيد عادل وهبة خليل 2, Nepalicoi, Germartin1, Pintoch: ✓ Done: interest rate (P5899). − Pintoch (talk) 06:56, 21 September 2018 (UTC)

tuition fee[edit]

   Done. tuition fee (P5894) (Talk and documentation)
Descriptionthe tuition fee at an educational instition (default duration:1 year, use duration qualifier to specify)
Representstuition payments (Q538104)
Data typeNumber (not available yet)
Domaineducational institution (Q2385804)
Example 1Heidelberg University (Q151510) → 1500€ (duration: 1 semester (Q3955006); applies to part: Non-EU/EEA Citizen (Q56508358))
Example 2Heidelberg University (Q151510) → 650€ (duration: 1 semester (Q3955006); applies to part: second studies (Q243765)
Example 3Harvard University (Q13371) → 46340$ (time: 2018)
Example 4University of Oxford (Q34433) → 9250£ (applies to part: EU/EEA Citizen (Q56508363); time: 2019) reference
Example 5University of Copenhagen (Q186285) → 55000DKK (duration: 1 semester (Q3955006); applies to part: Non-EU/EEA Citizen (Q56508358),computer science (Q21198),Master of Science (Q950900)
Example 6University of Copenhagen (Q186285) → novalue (applies to part: EU/EEA Citizen (Q56508363))
See alsofee (P2555)

Discussion[edit]

semester fee[edit]

   Under discussion
Descriptionsemester fee (6 months) for a university in Germany, Austria, Switzerland
Representssemester fee (Q1386894)
Data typeNumber (not available yet)
Domaineducational institution (Q2385804)
Example 1Heidelberg University (Q151510) → 152.30€ (time: April 2018)
Example 2University of Göttingen (Q152838) → 348.40€ (time: Oct 2018)
Example 3Technical University of Berlin (Q51985) → 306.99€ (start time: April 2018)
See alsofee (P2555)

Motivation[edit]

I'm proposing adding tuition fee and semester fee. These are two different fees. Tuition fee describes the cost for tuition usually as an annual fee for the cost of teaching. Semester fee applies to German universities and covers administrative costs, which mostly do not have tuition fees. German universities may have a tuition fee for non-EU citizens additional to the semester fee. Please see my example. Germartin1 (talk) 13:10, 9 September 2018 (UTC)

Discussion[edit]

  • Symbol support vote.svg Support Both David (talk) 08:27, 10 September 2018 (UTC)
  • Pictogram voting comment.svg Comment Would fee (P2555) with an appropriate qualifier be suitable for this? ArthurPSmith (talk) 13:41, 10 September 2018 (UTC)
Pictogram voting comment.svg Comment @ArthurPSmith: It is possible, but I think fee is too general and as you can see I'm already using a lot of qualifiers with multiple values. Eventually it will become confusing. I think fee is meant for one-time payments (for an entrance or a ferry trip) Germartin1 (talk) 14:29, 10 September 2018 (UTC)
In the original property proposal, it was pointed out by Joshbaumgartner that the scope of this property should be wider than its current descriptions indicate. I agree and I have proposed to do this at Property_talk:P2555.− Pintoch (talk) 11:13, 16 September 2018 (UTC)
  • Symbol support vote.svg Support. ··· Rachmat04 · 02:50, 13 September 2018 (UTC)
  • Pictogram voting comment.svg Comment I also think it would be worth working on generalizing fee (P2555) and creating the appropriate qualifier properties to make its use more precise. This property has already been used on university items to indicate the tuition or application fee, see University of Copenhagen (Q186285) or Harvard University (Q13371) for instance. There are a lot of different types of fees, we probably do not want to create a property for each of them. Typically the "semester fee" proposal seems too country-specific to me. − Pintoch (talk) 11:13, 16 September 2018 (UTC)
Yes, I added those statements, but I realized that I will become to confusing Germartin1 (talk) 15:33, 16 September 2018 (UTC)
  • Pictogram voting comment.svg Comment I support the tuition fees. I agree with User talk:Pintoch since different countries may follow different schemes: yearly, semester, trimester etc. Do we use of (P642) as a scope qualifier? John Samuel (talk) 11:33, 16 September 2018 (UTC)
@Jsamwrites: I agree that of (P642) would be a good qualifier for the type of fee, but I think all universities in the US, Canada, UK, etc. charge on a yearly basis. So which qualifier do you propose for the duration? Germartin1 (talk) 15:33, 16 September 2018 (UTC)
@Germartin1: You can make use of qualifiers like start time (P580) and end time (P582) to specify the validity of duration of fees. John Samuel (talk) 15:48, 16 September 2018 (UTC)
@Jsamwrites: Agreed, but how about the duration (per year, per semester), is duration (P2047) appropriate, i.e. 1 annum, 6 months, 4 months? Germartin1 (talk) 16:01, 16 September 2018 (UTC)
@Germartin1: Yes for specifying the total duration of the fees structure. But if fees structure changes, start time (P580) and end time (P582) can be used (for ancient fee structure). John Samuel (talk) 16:44, 16 September 2018 (UTC)
  • Pictogram voting comment.svg Comment @Germartin1: please do not mark the proposal as ready at this stage, given the ongoing discussion. Changing my comment to an Symbol oppose vote.svg Oppose vote to clarify that.Pintoch (talk) 14:21, 16 September 2018 (UTC)
@Pintoch: I'm sorry I didn't see the additional comments earlier today Germartin1 (talk) 15:11, 16 September 2018 (UTC)
  • Pictogram voting comment.svg Comment @Pintoch:,@ArthurPSmith:,@Jsamwrites: I support the broadening of Property_talk:P2555 fee property, ie. I think application fee should be within Property "fee" with a qualifier "of" "application fee".However, I believe that packing everything under fee will be confusing, because tuition and semester fee can have many values (usually the fee changes every year) and can have a bunch of qualifiers, depending on the year of study, subject, student's nationality, new student/second studies student. Those are already 5 qualifiers (including point of time). Semester fee is country specific, but they're thousands of universities within Germany alone, so I don't understand why it matters. However, if you guys don't agree, I would like to ask you if we can create an example of using the "fee" property, so everyone will know how to use it in future. Another question, is it possible to add statements to a country when for example all public universities have the same fee, using qualifiers "applies to part" "public universities". Germartin1 (talk) 15:33, 16 September 2018 (UTC)
@Pintoch: It's been two days, any more comments? I'd like to conclude this discussion soon. Germartin1 (talk) 12:29, 18 September 2018 (UTC)
@Germartin1: fine with me then. Looks like the first proposal is well supported, still not sure about the second one. But note that "two days" is really not much for property proposals, given the low activity in this area of Wikidata. It is normal that it takes time to build consensus for these sort of properties (identifiers are more straightforward). − Pintoch (talk) 13:13, 19 September 2018 (UTC)


Pintoch
Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits
ArthurPSmith
Vladimir Alexiev (talk)
Toniher
Runner1928
Daniel Mietchen (talk)
Satpal Dandiwal (talk)
danielt998
Sush_0809 (talk)
John Samuel Nomen ad hoc
OdileB(talk)
Ivanhercaz
Mlemusrojas
Jjfloyd
Kippelboy
Germartin1

Pictogram voting comment.svg Notified participants of WikiProject Universities

@ديفيد عادل وهبة خليل 2, ArthurPSmith, Nepalicoi, Germartin1, Pintoch, Worldm99: @Rachmat04: ✓ Done: tuition fee (P5894). − Pintoch (talk) 06:46, 21 September 2018 (UTC)

model item for[edit]

   Under discussion
DescriptionDefines which item is a best practice example of modelling a subject, which is described by the value of this property
Data typeItem
Allowed valuesItems which are classes
Example 1Douglas Adams (Q42)human (Q5)
Example 2Nelson Mandela (Q8023)politician (Q82955)
Example 3Zootopia (Q15270647)animated film (Q202866)
Example 4Mona Lisa (Q12418) -> painting (Q3305213)
Planned useRecord model items for all of the most used classes on Wikidata, then gradually expand over time to include more granular concepts
Expected completenessalways incomplete (Q21873886)
See alsoWikidata :Property proposal/Model item

Motivation[edit]

Defines which item is a best practice example of modelling a subject, which is described by the value of this property. Providing best practice examples linked from the subject will make it much easier for people to understand how to model types of items, especially new people. The main hope is that this will lead to more consistent modelling of items rather than different editors making up their own structure. It will also allow a central place to decide how to model certain kinds of items.

By modelling this within the structure of Wikidata rather than in Wikiprojects the structure is multilingual. Also looking at where the model item refers to the concept we can run a standard query that will work for most cases to find all the items that the model applies to, this is not limited to ‘instance of’. This could be used to check which items do and do not have high importance statements, e.g authors without a date of birth.

This could later be complemented with another property which defines the schema for a class of item (e.g author or politician)

This property requires that the inverse property Model item also be accepted to be most useful.

Thanks

John Cummings (talk) 20:15, 11 September 2018 (UTC)

Discussion[edit]

  • Symbol support vote.svg Support - NavinoEvans (talk) 21:04, 11 September 2018 (UTC)
  • Symbol support vote.svg Support Jane023 (talk) 06:30, 12 September 2018 (UTC)
  • Symbol support vote.svg Support David (talk) 08:20, 12 September 2018 (UTC)
  • Symbol support vote.svg Support very good idea, but Pictogram voting comment.svg Comment what is the intended extent? should all classes have a model or just the upper classes? I see animated film (Q202866) in the example but wouldn't film (Q11424) be better? (both way are fine, but too many model would probably end up as confusing as no model at all) Cdlt, VIGNERON (talk) 08:33, 12 September 2018 (UTC)
Thanks very much @VIGNERON:, I don't think these items will define the schema for that class, just act as good practice examples for people to copy. I'm currently working on an idea for schema modelling using a new property. My guess is having model items for more granular items like 'author' or 'animated film' will be helpful and that you'd want for people to be specific, modelling authors from the model item for 'human' would probably mean people miss out a lot of the author specific details. Same for animated film, e.g animators, software used, rendering engine, voice actors (by language version) etc are all specific to animated films (and some specific to computer modelled animated films even). I don't know how granular you would want to go though, do we want a model item for '16th Century Welsh poets'? I think that's a community decision. --John Cummings (talk) 09:34, 12 September 2018 (UTC)
@Jura1:, I suggest that both are needed to help people navigate, they're not exactly inverse properties of each other as a model item could be the model for several subjects e.g Douglas Adams could be the model for 20th Century British authors and 20th Century British Playwrights. Having both will be more valuable than only having one of them. --John Cummings (talk) 12:19, 12 September 2018 (UTC)
I rather debate on the talk page of "20th Century British authors" about the model status of Q42 than the inverse. --- Jura 12:37, 12 September 2018 (UTC)
I think there is some confusion, do you mean you want to have a discussion on the schema for '20th Century British authors' on the item for '20th Century British Authors'? If so then I assume there is some way of setting up a bot that adds a note to the talk page for model items (e.g Douglas Adams) that directs you to the correct location (e.g item for 20th century British authors). I also think this this unlikely to be an issue once we've implemented some way of describing schemas within the items. --John Cummings (talk) 12:51, 12 September 2018 (UTC)
We already have. So even more so. You can always query it. --- Jura 12:57, 12 September 2018 (UTC)
Hi @Pasleim:, when you say enough, for which use cases do you mean? --John Cummings (talk) 22:08, 12 September 2018 (UTC)
It is enough because all the statements can be inferred from Wikidata:Property proposal/Model item. For new users, for whom this property is mainly, it will make most sense to create a list of all model items. To create such a list you only need one of the two properties. If you have both properties you don't gain anything but your maintenance work will be doubled. --Pasleim (talk) 10:08, 17 September 2018 (UTC)
  • Symbol oppose vote.svg Oppose. Better to point in the other direction. --Yair rand (talk) 22:33, 12 September 2018 (UTC)
@Yair rand:, can you explain why only one direction is better? Surely having two directions will help people to find useful items? These properties are not exactly inverse of each other because an item can be a model item for more than one class. --John Cummings (talk) 22:54, 12 September 2018 (UTC)
  • This is actually not relevant information about Douglas Adam. --- Jura 08:54, 13 September 2018 (UTC)
  • @John Cummings: I don't see how being a model item for more than one class would make it not an exact inverse. If there's a statement going one way, there would be a statement going the other way. (That is, if X is a model item for both Y and Z, this property would point from X to both, and the inverse would point both to X from both Y and Z.) With both directions, we have two versions of the data, which are not automatically in sync. If someone changes one statement but does not change the other statement, one version will be incomplete. Requiring two actions for each change will cause the data to be less reliable. --Yair rand (talk) 19:36, 16 September 2018 (UTC)
@Yair rand:, thanks. I think this is an issue that needs resolving, that inverse properties are very useful for querying and finding items but are problematic for staying in sync, do you know if anyone has proposed a bot or any other solution to keep them in sync? Not having inverse properties feels like throwing the baby out with the bath water... I will do some looking around at possible solutions John Cummings (talk) 09:31, 17 September 2018 (UTC)
@Germartin1:, could you explain why you think we shouldn't have this property? Thanks, --John Cummings (talk) 09:27, 13 September 2018 (UTC)
First of all, it's an inverse of your other proposal, hence redundant according to Wikidata principles. Personally, I don't see how it adds any kind of value to an item. Germartin1 (talk) 09:37, 13 September 2018 (UTC)
@Germartin1: I don't fully understand why this is against Wikidata principles? Is there a guideline or info page you can point? We have around 100 inverse property pairs at the moment. For example, template's main topic (P1423) and topic's main template (P1424) ... or ... is a list of (P360) and has list (P2354). NavinoEvans (talk) 10:43, 13 September 2018 (UTC)
  • Symbol support vote.svg Support Useful, particularly with inverse property. See no harm in using both in supporting developing best practice and some kind of consistency. Stinglehammer (talk) 10:31, 13 September 2018 (UTC)
  • Symbol support vote.svg Support Yeah, can see this being helpful. Lirazelf (talk) 11:06, 13 September 2018 (UTC)
  • Symbol support vote.svg Support Very useful Jason.nlw (talk) 13:21, 13 September 2018 (UTC)
  • Symbol oppose vote.svg Oppose Nepalicoi (talk) 12:21, 17 September 2018 (UTC)
Hi @Nepalicoi:, can you explain why you oppose the proposal? Thanks, --John Cummings (talk) 14:37, 17 September 2018 (UTC)

model item[edit]

   Done. model item (P5869) (Talk and documentation)
DescriptionDefines which item is a best practice example of modelling a subject, which is described by the value of this property
Data typeItem
Allowed valuesItems
Example 1human (Q5)Douglas Adams (Q42)
Example 2politician (Q82955)Nelson Mandela (Q8023)
Example 3animated film (Q202866)Zootopia (Q15270647)
Planned useRecord model items for all of the most used classes on Wikidata, then gradually expand over time to include more granular concepts
Expected completenessalways incomplete (Q21873886)
See alsoWikidata:Property proposal/Model item for

Motivation[edit]

Defines which item is a best practice example of modelling a subject, which is described by the value of this property. Providing best practice examples linked from the subject will make it much easier for people to understand how to model types of items, especially new people. It will also allow a central place to decide how to model certain kinds of items.

By modelling this within the structure of Wikidata rather than in Wikiprojects the structure is multilingual. Also looking at where the model item refers to the concept we can run a standard query that will work for most cases to find all the items that the model applies to, this is not limited to ‘instance of’. This could be used to check which items do and do not have high importance statements, e.g authors without a date of birth.

This could later be complemented with another property which defines the schema for a class of item (e.g author or politician)

This property requires that the inverse property model item for also be accepted to be most useful.

Thanks

John Cummings (talk) 20:19, 11 September 2018 (UTC)

Discussion[edit]

  • Symbol support vote.svg Support - NavinoEvans (talk) 21:07, 11 September 2018 (UTC)
  • Symbol support vote.svg Support not sure about this one - maybe "badges" are better? Or is this for just "one" iconic model item (we will never agree on which one I think)  – The preceding unsigned comment was added by Jane023 (talk • contribs).
  • Symbol support vote.svg Support David (talk) 08:20, 12 September 2018 (UTC)
  • Symbol support vote.svg Support picking one model could be difficult, maybe we could have multiple values but please keep them limited to a small set (too many models could be as confusing as no model at all). VIGNERON (talk) 08:35, 12 September 2018 (UTC)
  • Pictogram voting comment.svg Comment I think there should be models for various depths in a particular field. Looking at the full one might just be overwhelming. --- Jura 11:38, 12 September 2018 (UTC)
@Jura1: Agreed, there could be a model item for 'author' and model items for '20th century French Author', 'Academic author', 'ghost writer' etc. These items are best practice examples which reflect an agreed schema, they would most probably not be the record of the schema (I'm working on that part next). --John Cummings (talk) 12:28, 12 September 2018 (UTC)
With depth I mean less than 100 statements. 10/20/50 etc. --- Jura 20:42, 12 September 2018 (UTC)
  • Symbol support vote.svg Support Strikes me as a useful pairing wihh the inverse property. Richard Nevell (talk) 12:43, 12 September 2018 (UTC)
  • Symbol support vote.svg Support John Samuel 17:35, 12 September 2018 (UTC)
  • Symbol support vote.svg Support --Sabas88 (talk) 18:24, 12 September 2018 (UTC)
  • Symbol support vote.svg Support - PKM (talk) 19:32, 12 September 2018 (UTC)
  • Symbol support vote.svg Support --Zyksnowy (talk) 20:39, 12 September 2018 (UTC)
  • Symbol support vote.svg Support Useful! Ijon (talk) 08:52, 13 September 2018 (UTC)
  • Symbol support vote.svg Support Useful, particularly with inverse property. We point people, particularly newbs, towards featured articles on Wikipedia for examples of best practice - would be extremely beneficial to have an accepted good exemplar of a featured/model item for modelling certain data models on Wikidata. e.g. RMS Titanic for ships? Stinglehammer (talk) 10:27, 13 September 2018 (UTC)
  • Symbol support vote.svg Support Yeah, can see this one being useful, esp for beginners. Lirazelf (talk) 11:07, 13 September 2018 (UTC)
  • Symbol support vote.svg Support - Llywelyn2000 (talk) 11:14, 13 September 2018 (UTC)
  • Symbol support vote.svg Support - very useful Jason.nlw (talk) 13:22, 13 September 2018 (UTC)
  • Pictogram voting comment.svg Comment Will there be a single value constraint, who decides which value to choose, why Douglas Adam and not Barack Obama? Nepalicoi (talk) 12:22, 17 September 2018 (UTC)
@Nepalicoi:, thanks very much for the questions. I think value constraints should be dependent on wether we can find a good way to model schemas within Wikidata items, or wether model items become in effect schemas for subjects (I'm currently trying to work out a good way to model schemas). I think the decision on which are model items should be a community decision, the most sensible way of doing this is probably a discussion on the talk page for the class item (e.g the item for author). The examples are just for illustration, they are not the decided. --John Cummings (talk) 14:44, 17 September 2018 (UTC)

@ديفيد عادل وهبة خليل 2, Richard Nevell, Ijon, Nepalicoi, NavinoEvans, Lirazelf: @Llywelyn2000, Zyksnowy, PKM, Jason.nlw, Stinglehammer, Sabas88: @VIGNERON, John Cummings, Jura1: ✓ Done: model item (P5869). − Pintoch (talk) 21:33, 20 September 2018 (UTC)

Logically implies (necessary condition)[edit]

   Under discussion
DescriptionNecessary condition, i.e. logical consequence of a mathematical statement
RepresentsLogical consequence (Q374182), requirement (Q774228)
Data typeMathematical expression
DomainMaxwell's equations (Q51501)
Allowed valuesMathematical theorems (or other mathematical laws e.g. from theoretical physics)
ExampleMaxwell's equations (Q51501) =>(P?) Coulomb's law (Q83152)
Sourcehttps://en.wikipedia.org/wiki/Logical_consequence
Planned useconnect physics theorems / axioms by logical relation to annotate constraints / necessary conditions
Robot and gadget jobsshould be allowed

Motivation

My vision is to enable creating a logically structured semantic network of mathematical theorems (starting with theoretical physics). This would allow researchers to quickly grasp the constraints of the formulae (Wikidata items) they are working on, the framework they are working in. A theorem / formula (Wikidata item) is falsified already if one of its necessary conditions turns out to be falsified. Thus it is vital to know them, in order to prevent mathematical researchers from wasting their time working on something that may be invalid.  – The preceding unsigned comment was added by PhilMINT (talk • contribs) at February 19, 2018‎ (UTC).

Discussion

  • Symbol support vote.svg Support @PhilMINT: This is an interesting proposal - unfortunate that it seems to have gotten lost. I believe the datatype should be item, not "formula" (your example follows that pattern). I don't particularly like the parenthetical label - you can add that as an alias. Perhaps to be clearer the main English label should be "logically implies"? ArthurPSmith (talk) 20:30, 13 September 2018 (UTC)
  • Conditional Symbol support vote.svg Support. I agree that the datatype should be item. I think this property could be useful, although I don't know how many interesting theorems imply other interesting theorems outright, rather than imply in the context of plausible background assumptions. The "source" will be different secondary and textbook sources depending on the relation claimed. "Domain" is another field that seems to be filled in incorrectly: the domain of this property should be something like mathematical object (Q246672) or proposition (Q108163): we need a clear decision on what the domain will be. MartinPoulter (talk) 10:10, 19 September 2018 (UTC)

re3data repository ID[edit]

Descriptionidentifier for a data repository in the re3data registry
RepresentsRegistry of Research Data Repositories (Q18393912)
Data typeExternal identifier
Domaindatabase (Q8513)
Allowed valuesr3d[1-9]\d{0,8}
Example 1World Atlas of Language Structures (Q1133223)r3d100010155
Example 2Xenbase (Q8043462)r3d100011331
Example 3Tierstimmenarchiv (Q2432535)r3d100011366
Example 4PANGAEA (Q947684)r3d100010134
Example 5RCSB protein data bank (Q55823721)r3d100010327
Example 6ChEBI (Q902623)r3d100012626
Example 7NMRShiftDB (Q24170714)r3d100010316
Example 8Austrian Phonogrammarchiv (Q1427365)r3d100012527
Example 9Human Protein Atlas (Q5937310)r3d100010931
Example 10ChemSpider (Q2311683)r3d100010205
Example 11Zenodo (Q22661177)r3d100010468
SourceThe ID can be found at the end of the URL for an entry in the collection. It is also exposed via their API.
Number of IDs in sourcecurrently 2190, continuously growing (full list)
Expected completenesseventually complete (Q21873974)
Formatter URLhttps://www.re3data.org/repository/$1
Robot and gadget jobsbot

Motivation[edit]

The Registry of Research Data Repositories (or re3data) is a cross-disciplinary and global registry of research-related databases, so annotating the items about such databases with their re3data identifier seems useful. --Daniel Mietchen (talk) 21:57, 12 September 2018 (UTC)

Discussion[edit]

  • Symbol support vote.svg Support Charles Matthews (talk) 03:48, 13 September 2018 (UTC)
  • Symbol support vote.svg Support David (talk) 09:17, 13 September 2018 (UTC)
  • Symbol support vote.svg Support. YULdigitalpreservation (talk) 12:59, 13 September 2018 (UTC)
  • Pictogram voting comment.svg Comment I was made aware today that re3data actually issues DOIs (for which we have DOI (P356)) for the repositories they have indexed, e.g. 10.17616/R3Q33G for Tierstimmenarchiv (Q2432535) (see the recommended citation at the bottom of a page). This reduces the need for a dedicated re3data repository ID dramatically, but probably not to 0, so I'm leaving this proposal open to get further input. --Daniel Mietchen (talk) 19:23, 13 September 2018 (UTC)
Pictogram voting comment.svg Comment A further complication with using DOIs is that our DOI-based workflows assume that items with more than one DOI are an exception but repositories often have several of them, e.g. PANGAEA (Q947684) has been assigned 10.17616/R3XS37 by re3data and 10.25504/FAIRsharing.6yw6cp by FAIRsharing. --Daniel Mietchen (talk) 04:05, 18 September 2018 (UTC)
  • Symbol support vote.svg Support I think this is a good idea, re3data is a great resource. ArthurPSmith (talk) 20:13, 13 September 2018 (UTC)
  • Symbol support vote.svg Support John Samuel (talk) 17:17, 14 September 2018 (UTC)

@ديفيد عادل وهبة خليل 2, Daniel Mietchen, YULdigitalpreservation, ArthurPSmith, Charles Matthews: ✓ Done: re3data repository ID (P5874). − Pintoch (talk) 21:38, 20 September 2018 (UTC)

restriction of[edit]

   Under discussion
Descriptionfile format A is a restriction of file format B if all instances of A are also instances of B, but instances of B are not necessarily instances of A.
Data typeItem
Template parameteren:Template:Infobox file format extended from
Domainfile format (Q235557)
Allowed valuesfile format (Q235557)
Example 1GeoTIFF (Q1502796)Tag Image File Format (Q215106)
Example 2EPUB 3 (Q27196933)ZIP (Q136218)
Example 3Portable Document Format/Archive, version 1 Basic (Q26543628)Portable Document Format, version 1.4 (Q26085326)
Sourcehttp://hul.harvard.edu/gdfr/documents/GDFR-Format-Model-and-Relationship-1_0_7.rtf
Planned usePopulate this property with information from the extended_from infobox parameter (after careful examination, because the meaning of this parameter is often misunderstood).
See alsobased on (P144)

Motivation[edit]

This proposal is derived from a rejected "extension of" property proposal.

For digital preservation, we need to know when a file of format A is also a valid instance of format B (see http://hul.harvard.edu/gdfr/documents/GDFR-Format-Model-and-Relationship-1_0_7.rtf, section 3.2). The property based on (P144) is related but broader (for example, EPUB 3 (Q27196933) is a restriction of ZIP (Q136218), but it is also based on (P144) Extensible HyperText Markup Language (Q166074) and Cascading Style Sheets (Q46441).

Discussion[edit]

Tobias1984
Emw
Zuphilip
Danrok
Bene*
콩가루
TomT0m
DrSauron
Ruud Koot
Andreasburmeister
Ilya
Toto256
MichaelSchoenitzer
Metamorforme42
Pixeldomain
User:YULdigitalpreservation
Dipsode87
Pintoch
Daniel Mietchen
Jsamwrites
Fractaler
Giovanni Alfredo Garciliano Diaz
FabC
Jasc PL
Malore
putnik
Dhx1
Pictogram voting comment.svg Notified participants of WikiProject Informatics

  • Symbol support vote.svg Support. YULdigitalpreservation (talk) 12:56, 13 September 2018 (UTC)
  • Symbol support vote.svg Support. Toto256 (talk) 13:02, 13 September 2018 (UTC)
  • Symbol support vote.svg Support Nice and clear proposal, thanks. ArthurPSmith (talk) 20:14, 13 September 2018 (UTC)
  • Symbol support vote.svg Support John Samuel (talk) 17:18, 14 September 2018 (UTC)
  • Symbol support vote.svg Support David (talk) 09:41, 15 September 2018 (UTC)
  • Pictogram voting comment.svg Comment as this seems to be meant for file formats, I added that in the description. --- Jura 10:45, 15 September 2018 (UTC)
  • I think it would be helpful if the label was more specific, to avoid misuse. --Yair rand (talk) 19:54, 17 September 2018 (UTC)

blazon[edit]

   Under discussion
Descriptiondescription of a coat of arms
Representscoat of arms (Q14659)
Data typeMultilingual text (not available yet)
Domaincoat of arms
Example 1coat of arms of Spain (Q170600) → «Escudo cuartelado: 1º de gules, un castillo de oro aclarado de azur; 2º de plata, un león de púrpura lampasado y armado de gules y coronado de oro; 3º de oro, cuatro palos de gules; 4º de gules, una cadena de oro, puesta en cruz, aspa y orla, cargada en el centro de una esmeralda de sinople. Entado bajado curvilíneo en punta: una granada de sinople, rajada de gules. Escusón de azur, con tres flores de lis de oro; bordura cosida de gules. Al timbre, corona real. Por sostenes, dos columnas de plata con base y capitel de oro, sobre ondas de azur y plata, superada de corona imperial, la diestra, y de una corona real, la siniestra, y rodeando las columnas, una cinta de gules, cargada de letras de oro, en la diestra “PLUS” y en la siniestra “ULTRA”.» (es)
Example 2Coat of arms of Colombia (Q235826) → «Escudo con boca suiza, de proporciones seis de ancho por ocho de alto. Terciado en faja: 1º de azur, una granada de oro rajada de gules acostada de un cuerno de la abundacia de oro contornado a la diestra y de otro cuerno de la abundancia con frutas de la zona intertropical; 2º de plata, un gorro frigio de gules sobre una lanza de oro moviente de la punta; 3º de azur con fajas ondadas de plata, resaltando sobre la partición, el Istmo de Panamá de sinople moviente de los flancos, acompañado de dos navíos de sable envelados de plata. Por cimera lleva un cóndor con las alas desplegadas que sujeta una corona de laurel, la cual sostiene el escudo. Por leyenda, una cinta de oro con el lema LIBERTAD Y ORDEN en letras de sable, entre el cóndor y la corona. El escudo va acompañado de cuatro banderas acoladas, de las cuales las dos inferiores formarán un ángulo de noventa grados, y las dos superiores irán separadas de las primeras en ángulos de quince grados. Estas banderas van recogidas hacia el vértice del escudo.» (es)
Example 3Coat of Arms of Barcelona (Q8777837) → «Escudo en losange de ángulos rectos cuartelado: en el 1º y en el 4º, de plata, una cruz llena de gules; y en el 2º y en el 3º, de oro, 4 palos de gules. Al timbre, una corona real.» (es)

«Escut caironat quarterat: al 1r i al 4t, d'argent, una creu plena de gules; i al 2n i al 3r, d'or, 4 pals de gules. Per timbre una corona reial.» (ca)

Reference
Planned useusing it on Wikipedia infoboxes
See alsocoat of arms (P237), coat of arms image (P94)

Motivation[edit]

Improve the information about the coats of arms, that usually it's unique for each one. --Giovanni Alfredo Garciliano Díaz diskutujo 19:06, 14 September 2018 (UTC)

Discussion[edit]

  • Symbol support vote.svg Support David (talk) 09:42, 15 September 2018 (UTC)
  • Symbol oppose vote.svg Oppose such descriptions belong to Wikipedia. It is also technically not possible to add such descriptions because there is a length limit of 400 characters. --Pasleim (talk) 16:26, 15 September 2018 (UTC)

parties (public international law subjects who consented to be bound by the treaty)[edit]

   Under discussion
DescriptionThis property is intended to list the parties (countries or international organizations) of the treaty. It should allow adding several values.
Data typeItem
Domaintreaty (Q131569)
Allowed valuescountry (Q6256), international organization (Q484652)
Example 1Vienna Convention on the Law of Treaties (Q239768)Nigeria (Q1033)
Example 2Treaty on International Civil Law of 1889 (Q40449446)Bolivia (Q750)
Example 3Convention on the Elimination of All Forms of Discrimination against Women (Q277072)Sweden (Q34)
Robot and gadget jobsno
See alsosignatory (P1891) (previous step in the process of adoption of a treaty) depositor (P2058) (after a treaty was ratified by a country, this country sends the instrument to the depositary)

Motivación[edit]

This property is needed, because currently Wikidata can show which subjects signed a treaty by property signatory (P1891), but there is no corresponding property to know if any of the signatories consented to be bound by the treaty.

The property should work as this:

 <P> parties/consented to be bound:    <Q> country/int org
                                              <qualifier> mean                              <Q> ratification, acceptance, approval, accession, ...
                                              <qualifier> date approved                     <date> YYYY-MM-DD (date when the country consented to be bound, such as when parliament voted for it)
                                              <qualifier> approved by law* (if aṕpropriate) <Q>/<text> number or name of the law
                                              <qualifier> date deposited                    <date> YYYY-MM-DD (date when instrument was deposited to the depositary)
                                            <references>

                                       <Q> country/int org 2...
                                              <qualifier> mean                              <Q> ratification, acceptance, approval, accession, ...
                                              <qualifier> date approved                     <date> YYYY-MM-DD 
                                              <qualifier> approved by law* (if aṕpropriate) <Q>/<text> number or name of the law
                                              <qualifier> date deposited                    <date> YYYY-MM-DD 
                                            <references>
* or approved by signature, etc.

Should also be taken in account to add end date, when the treaty is not binding to the country anymore due to withdrawal of the treaty. Zerabat (talk) 22:43, 14 September 2018 (UTC)

Discussion[edit]

  • Symbol support vote.svg Support David (talk) 09:42, 15 September 2018 (UTC)
  • Is this specifically for international agreements, or could it also be used for, say, agreements between organizations? --Yair rand (talk) 19:55, 17 September 2018 (UTC)
    • This could be for agreements between any subject of international law: between states, between states and other interantional law subjets, and between other international law subjects themselves. --Zerabat (talk) 00:02, 21 September 2018 (UTC)

spoken by[edit]

   Under discussion
Descriptionthe ethnic group of a language
Represents?
Data typeItem
Domainlanguage (Q34770)
Example 1Punjabi (Q58635)Punjabi people (Q854323)
Example 2Eastern Tamang (Q12953177),Western Tamang (Q12953178)Tamang people (Q1144444)
Example 3Banjar (Q33151)Banjar people (Q2350149)
Example 4German -> German people, Austrians
Example 5Spanish -> Spaniards

Motivation[edit]

This is my first proposal. Every language is home to a people, usually an ethnic group. An ethnic group can have multiple languages. A language can have one origin, but can be spoken by multiple ethnic groups. Nepalicoi (talk) 13:00, 17 September 2018 (UTC)

Discussion[edit]

Depósito Legal ID[edit]

   Under discussion
Descriptionidentifier for a publication in Spain
Representsno label (Q56650972)
Data typeExternal identifier
Domainwork (Q386724)
Example 1Diccionari biogràfic d'Olot (Q56650936) → "Gi. 1590-2015"
Example 2El Pintor Ivo Pascual → "GE-923/83"
Example 3Diccionario Català – Alemany → "B. 30.238-1997"
Example 4Gramàtica de la llengua catalana → "B 21836-2016"
Expected completenessalways incomplete (Q21873886)
See alsoOCLC control number (P243), ISBN-13 (P212), ISBN-10 (P957)

Motivation[edit]

I would create an property for the Depósito Legal No or Depósito Legal ID (DL ID) of publications in Spain. Each publication in Spain must have this ID called „Número de depósito legal“ (even if they have no ISBN). I believe it’s analog to the DPLA ID (P760) in USA. There is a big adventage working with publications which have no International Standard Book Number (Q33057) and no OCLC control number (P243) like many art catalogues. I would reference some such works with biografical informations of artists. For example: I would assign the object Diccionari biogràfic d'Olot (Q56650936) the property Depósito Legal ID "Gi. 1590-2015". Unfortunately this book has not a unique ISBN. The Editors has used the ISBN for two different books. The DL-No is unique.

Examples (also historical examples of the Depósito Legal ID)
"GE-923/83" → El Pintor Ivo Pascual (GE for Gerona, 83 for 1983)
"Gi. 1590-2015" → Diccionari biogràfic d‘Olot (Gi. for Girona)
"B. 30.238-1997" → Diccionari Català – Alemany (Batlle et al.; B. for Barcelona, 1997)
"B 21836-2016" → Gramàtica de la llengua catalana (B for Barcelona, 2016)

Only the last No. is formally total correct. But I would show, which forms are possible in reality.

Thanks to all --Nasobema lyricum (talk) 17:13, 19 September 2018 (UTC)

Property proposal assisted by MisterSynergy (talk) after request at Wikidata:Forum.

Discussion[edit]