Shortcut: WD:PP/AUTH

Wikidata:Property proposal/Authority control

From Wikidata
Jump to: navigation, search


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

Contents

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

Authority control[edit]

See also Wikidata:Property proposal/Pending for approved items awaiting the deployment of currently unavailable datatypes
Already approved properties: list

The Baseball Cube ID[edit]

   On hold
Description identifier of a baseball player at www.thebaseballcube.com
Data type External identifier
Template parameter cube at en:Template:Baseballstats
Domain people
Allowed values string
Example Chris Young (Q2964906)Chris-Young-1
Planned use Template:Sports links (Q22674492)
Formatter URL http://www.thebaseballcube.com/profile.asp?P=$1
Robot and gadget jobs From Wikipedia
Motivation

(Add your motivation for this property here.) GZWDer (talk) 04:45, 18 January 2017 (UTC)

Discussion
  • Symbol support vote.svg Support. Thierry Caro (talk) 12:04, 18 January 2017 (UTC)
  • Symbol support vote.svg Support. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 19:51, 27 January 2017 (UTC)
  • Symbol oppose vote.svg Oppose Everything will be changing and I need the time and space to do this. There is risk involved though. If I am unable to achieve my goal, I will likely shut down. [1] --Pasleim (talk) 02:58, 28 January 2017 (UTC)
  • Symbol oppose vote.svg Oppose per Pasleim. ChristianKl (talk) 10:33, 20 February 2017 (UTC)
  • Symbol oppose vote.svg Oppose agree. if the web will be change in the next 6 months, is better to wait. - yona b (talk) 06:04, 28 February 2017 (UTC)
  • @GZWDer, Thierry Caro, Pigsonthewing, Pasleim: Not done. If the website get stable and removes the notice that everything will change, we can reevaluate. ChristianKl (talk) 06:36, 8 March 2017 (UTC)
    • @ChristianKl: You shouldn't be closing this, as you opposed. Please reopen it, so that a more neutral person can evaluate it, not least in the light of the fact that the site is currently stable; and the availability of archive.org copies of its pages. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 11:46, 8 March 2017 (UTC)
    • Okay, I removed the "Not done". ChristianKl (talk) 15:39, 8 March 2017 (UTC)

Putting Time2wait.svg On hold. Matěj Suchánek (talk) 09:35, 23 April 2017 (UTC)

@Matěj Suchánek: Why is this "on hold"? Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 10:51, 28 April 2017 (UTC)
Some users mentioned an upcoming change to the web, so as an uninvolved person I put it on hold until it happens. Matěj Suchánek (talk) 11:15, 19 May 2017 (UTC)

BDFutbol manager ID[edit]

   Under discussion
Description ID of a manager at BDFutbol
Data type External identifier
Template parameter en:Template:BDFutbol manager
Domain football manager
Allowed values \d+
Example Míchel (Q558689)1543
Planned use Template:Association football links (Q25919080)
Formatter URL http://www.bdfutbol.com/en/l/l$1.html
Robot and gadget jobs from Wikipedia
Motivation

see usage GZWDer (talk) 19:39, 11 February 2017 (UTC)

Discussion

Delusion23
WFC
happy5214
Fawkesfr
Xaris333
A.Bernhard
Cekli829
Japan Football
HakanIST
Jmmuguerza
H4stings
Unnited meta
محمد آدم
Pictogram voting comment.svg Notified participants of WikiProject Association football. Thierry Caro (talk) 11:23, 16 February 2017 (UTC)

BFI Film & TV Database ID[edit]

There're two kinds of IDs, BFI is currently switching to new style of ID, but Wikipedia template still use old style.

old style ID[edit]

   Under discussion
Description identifier for a person at BFI Film & TV Database (old style)
Data type External identifier
Template parameter en:Template:BFI db name and en:Template:Bfidb individual (two templates have the same formatter URL)
Domain people
Allowed values \d+
Example
Formatter URL http://ftvdb.bfi.org.uk/sift/individual/$1
Robot and gadget jobs from Wikipedia (but not to import IDs to thematic catalog items like Peter Sellers on stage, radio, screen and record (Q7176864))
See also other IDs by British Film Institute (Q260528): BFI work ID (P2703) and Wikidata:Property proposal/Screenonline ID

new style ID[edit]

   Under discussion
Description identifier for a person or movie at BFI Film & TV Database (old style)
Data type External identifier
Domain people, movie
Allowed values [0-9a-f]{13}
Example
Formatter URL http://www.bfi.org.uk/films-tv-people/$1
Robot and gadget jobs old style URL redirects to new style automatically
See also other IDs by British Film Institute (Q260528): BFI work ID (P2703) and Wikidata:Property proposal/Screenonline ID
Motivation

See usage and usage GZWDer (talk) 19:58, 11 February 2017 (UTC)

  • @GZWDer: this is a very bad name?
Discussion
I would suggest that we standardise on the new style IDs rather than maintaining both. If the old-style ones redirect then a bot job harvesting them can always translate from the old ones to the new during import. Andrew Gray (talk) 11:37, 19 May 2017 (UTC)

Goalzz ID[edit]

   On hold
Description ID of a player at Goalzz
Data type External identifier
Template parameter en:Template:Goalzz
Domain people
Allowed values \d+
Example Ahmed Khalil (Q2160925)21069
Planned use Template:Association football links (Q25919080)
Formatter URL http://www.goalzz.com/main.aspx?player=$1
Robot and gadget jobs from Wikipedia (but few)
Motivation

see usage, and more at [3] GZWDer (talk) 12:04, 12 February 2017 (UTC)

Discussion

Delusion23
WFC
happy5214
Fawkesfr
Xaris333
A.Bernhard
Cekli829
Japan Football
HakanIST
Jmmuguerza
H4stings
Unnited meta
محمد آدم
Pictogram voting comment.svg Notified participants of WikiProject Association football. Thierry Caro (talk) 11:27, 16 February 2017 (UTC)

  • Symbol support vote.svg Support.-- Hakan·IST 11:28, 16 February 2017 (UTC)
  • Pictogram voting comment.svg Comment. So far the link does not work. Thierry Caro (talk) 12:58, 16 February 2017 (UTC)
  • Symbol oppose vote.svg Oppose. Seems out of business or something. Thierry Caro (talk) 23:35, 23 February 2017 (UTC)
  • Mrked as "on hold". A colleague reports "...the links still work (they haven't changed the website setup) and the info is there in the code of the pages, but is not appearing for whatever reason. Hopefully they will fix it soon.". Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 17:50, 18 March 2017 (UTC)

Songwriters Hall of Fame ID[edit]

   Under discussion
Description ID for a person at Songwriters Hall of Fame
Represents Songwriters Hall of Fame (Q861660)
Data type External identifier
Template parameter en:Template:Shof
Domain people
Allowed values \d+
Example Samuel A. Ward (Q2450043)202
Formatter URL http://www.songwritershalloffame.org/exhibits/C$1
Robot and gadget jobs From Wikipedia, and also probably mix'n'match as there're relative few (383 as of 2010) entries
Motivation

see usage GZWDer (talk) 17:11, 12 February 2017 (UTC)

Discussion
  • Looks to me like the ID in the example should be C202, with the formatter URL adjusted accordingly. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 17:12, 13 February 2017 (UTC)
    • @Pigsonthewing: However the Wikipedia template use the ID without prefix, with formatter url http://www.songwritershalloffame.org/exhibit_home_page.asp?exhibitId=$1 which currently automatically redirected to the URL above.--GZWDer (talk) 11:22, 14 February 2017 (UTC)
  • It's worth investigating whether the website has ID's that don't start with a C. Symbol oppose vote.svg Oppose till it's clear whether that's the case. ChristianKl (talk) 18:30, 15 February 2017 (UTC)
  • Pictogram voting comment.svg Comment http://songwritershalloffame.org/exhibits/alphabetically is the full list and I do not see an ID that doesn't start with a C. --ネイ (talk) 17:04, 17 April 2017 (UTC)
  • @Pigsonthewing: Given what ネイ wrote, are you okay with the ID not including the C? ChristianKl (talk) 08:47, 21 May 2017 (UTC)
    • No. All the URLS on that page are the same: https://www.songhall.org/exhibits/C{primary_category_id}, which is clearly invalid, and indeed returns an error message. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 19:25, 28 May 2017 (UTC)

The Numbers person ID[edit]

   Under discussion
Description ID of an actor at The Numbers
Represents The Numbers (Q17072251)
Data type External identifier
Domain people
Allowed values \d+-[a-z\-]+
Example Simone Signoret (Q106126)132190401-Simone-Signoret
Formatter URL http://www.the-numbers.com/person/$1
Motivation

see usage GZWDer (talk) 18:08, 12 February 2017 (UTC)

Discussion
  • Pictogram voting comment.svg Comment The ID works with the numeric part only as well. – Máté (talk) 12:33, 21 February 2017 (UTC)
  • Symbol support vote.svg Support. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 22:14, 24 February 2017 (UTC)
  • @GZWDer, Pigsonthewing: Is there a reason not to switch to storing pure numbers if they also work as Máté implies? ChristianKl (talk) 07:15, 26 February 2017 (UTC)
  • It would make sense to me for the property to be number only. At the moment I don't think the question is resolved so I mark as not ready. ChristianKl (talk) 09:47, 23 March 2017 (UTC)
  • Symbol oppose vote.svg Oppose As long as the question of whether the property should contain number or number+name is unresolved. ChristianKl (talk) 19:59, 29 April 2017 (UTC)

magazines.russ.ru ID[edit]

   Under discussion
Description сайт с текстами русскоязычных литературных журналов (ru) – (Please translate this into English.)
Represents magazines.russ.ru (Q4181965)
Data type External identifier
Template parameter ru:Шаблон:ЖЗ
Domain people and magazines
Example
Source
Formatter URL * http://magazines.russ.ru/authors/$1/$1/ * http://magazines.russ.ru/$1/ – WRONG FORMAT
Robot and gadget jobs from Wikipedia
Motivation

Useful source for literature (Q8242) related articles. Krokusse (talk) 11:55, 9 April 2017 (UTC)

Discussion
  • Pictogram voting comment.svg Comment We should create two different properties, one for authors and one for magazines. Jonathan Groß (talk) 09:01, 10 April 2017 (UTC)
  • Symbol oppose vote.svg Oppose as proposed. The URL given as an example, for an ID of "Oleg Khafizov" is http://magazines.russ.ru/authors/h/hafizov/ Furthermore, two formatter URLs are give, one with two "$1" components. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 16:24, 10 April 2017 (UTC)
  • Pictogram voting comment.svg Comment About 20,000 authors. And only 40 magazines. Krokusse (talk) 22:57, 10 April 2017 (UTC)
  • Symbol oppose vote.svg Oppose as proposed, because we would need indeed two properties.
@Krokusse: would it be ok for you turning this proposal into a "magazines.russ.ru author ID" for example?
Feel free, of course, to propose an extra one for the magazines. Strakhov (talk) 13:13, 21 June 2017 (UTC)

DACS identification code[edit]

   Under discussion
Description Code to identify 50,000 artists as members of the British collective rights management organisation DACS and sister organisations worldwide
Represents Design and Artists Copyright Society (Q3705963)
Data type External identifier
Domain artists
Allowed values \d{1,7}
Example
Planned use adding DACS code of artists in museums, it makes the copyright status accessible, and compare those information with sister organisations, this database keeps also track of artists not fully represented
Formatter URL https://www.dacs.org.uk/licensing-works/artist-search/artist-details?ArtistId=$1
See also PictoRight ID code (P3361)
Motivation

With this museums and the general public can check of a wikidata-item if the copyright of an artist is handled by a collective rights management organisation in the UK. As DACS is also tracking artists worldwide we can verify the values with other national collective rights management organisations Hannolans (talk) 06:41, 12 April 2017 (UTC)

Discussion
  • Is the DACS number stable? There was a DACS catalogue on Mix'n'Match that had a lot of matches that became useless because the numbers all changed. Jheald (talk) 12:58, 17 April 2017 (UTC)
    • Good question and was not aware of the mix n match issue. They call it 'ArtistId' in the URL so I assume this is a stable id. If it is not stable, at least we have the members mapped, and can remap them if they change the ids or link to the Internat Archive--Hannolans (talk) 19:07, 17 April 2017 (UTC)
      • @Jheald: which set? Any links? Maybe someone can contact them to check this? Multichill (talk) 19:01, 20 April 2017 (UTC)
        • @Multichill, Hannolans: It was the "Picto-DACS" catalogue on Mix'n'match. Here's the thread where I notified the issue to Magnus, which will give the rough date that the previously matched values ceased to work. Jheald (talk) 19:32, 20 April 2017 (UTC)
        • * Those ids were not the DACS-ids but data with DACS and PictoRight names in it from Sweden if I'm right. We now have better sources and a tool to match those names to the ids. --Hannolans (talk) 15:35, 21 April 2017 (UTC)
          • Well Mix'n'match resolved the numerical ID all right to a page with the artist's name on the DACS website... the trouble was that after a few months the same number resolved to a different artist's name there. Jheald (talk) 19:25, 25 April 2017 (UTC)
            • Good catch. All pages were indexed by Internet Archive. Compare artistid 71710:
  • https://web.archive.org/web/20151231211607/http://www.dacs.org.uk/licensing-works/artist-search/artist-details.aspx?ArtistId=71710
  • http://www.dacs.org.uk/licensing-works/artist-search/artist-details.aspx?ArtistId=71710

while the website look similar, the artists are different. --Hannolans (talk) 21:37, 25 April 2017 (UTC)

    • I'm very curious about this, did they upgrade the database system, or is this system altering the ids once in a while?--Hannolans (talk) 13:37, 26 April 2017 (UTC)

Schema.org ID[edit]

   Under discussion
Description identifier for a concept, at Schema.org
Data type External identifier
Domain all!
Allowed values [A-Za-z\d]+
Example
Source http://schema.org/
Formatter URL http://schema.org/$1
Motivation

First mooted by User:The Anome in April 2014(!), and increasingly relevant in the light of Schema.org's proposal to encourage the use of Wikidata as a common entity base for the target of the sameAs relation. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 12:10, 5 May 2017 (UTC)

  • @Pigsonthewing: that proposal is for using WD entities in RDF **instances** (individuals) that conform to schema classes and properties. Fictitious example: <my hammer> rdf:type schema:Offering; schema:additionalType wd:hammer (Q25294). But it has nothing to do with correspondence of schema classes and properties to WD. --Vladimir Alexiev (talk) 02:44, 6 July 2017 (UTC)

Note: some items, e.g. actor (Q33999), are using exact match (P2888) to achieve this. I think a more specific property would be better. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 13:03, 5 May 2017 (UTC)

P.S. Some commenters have asked what advantages a unique property offers. They include:

-- Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 17:34, 16 May 2017 (UTC)

Note: Comments and examples which are not mine have been added to the proposal. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 13:53, 28 May 2017 (UTC)

Moved to a section below, for clarity. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 14:27, 6 July 2017 (UTC)
Discussion
I actually don't see why a specific property would be an improvement on exact match (P2888) here - it seems to me this is precisely what "exact match" is intended for. I also looked into the wikidata/schema.org relationship some time ago wondering essentially the same thing, why we didn't have a specific property for it, but it seemed like effort was being put into matching in the other direction which is great. ArthurPSmith (talk) 13:09, 5 May 2017 (UTC)
We can have this identifier property via authority control in Wikidata, but Schema.org isn't in a sense an authority control figurehead. "exact match" allows concepts to interchange fluidly, much more than an auth identifier. It also allows easier processing by external machine learning programs that already use "exact match" for following equivalence concept checking. DBPedia does some of this as well. So in the end, we will certainly not move from emptying values on "exact match" but would rather them heavily populated with other Linked Data sets. I myself have committed already to maintaining the mapping within Wikidata. There are parsers already that strip the base "http://schema.org/" from the concept, in the wild, so there's not much extra value with this proposed property. But I'm not against the effort to add it. I and others see more value with "exact match" since it brings alignment with other Linked Data sets. Thadguidry (talk) 13:40, 5 May 2017 (UTC)
I’ve seen equivalent class (P1709) used for this purpose (e.g. TV series season (Q3464665) equivalent class (P1709) http://schema.org/TVSeries. However I’d support a more specific property, if nothing else for the fact that we could not include the http://schema.org/ prefix (instead adding that in the formatter), which would allow us to link to https://schema.org/ (https version of webpage), or some other future reference should some other website supersede schema.org in future. Frankieroberto (talk) 19:37, 5 May 2017 (UTC)
I support the creation of a new property if and only if it makes a mapping between Wikidata and schema.org easier to complete/make comprehensive. Nemo 15:12, 6 May 2017 (UTC)
Restriction: SchemaOrg use many compositions, as Personal name (Q1071027) that must be mapped to sh:Person+sh:name, not only sh:name, neither sh:Organization+sh:name... The SchemaOrg's Class+property semantics have no ID (!), it is a free combination (pair of IDs). Only very specific (SchemaOrg's subset of) classes and properties have some exact equivalence, so this new proposed SchemaOrg_ID is only for this restricted cases. --h[User:Krauss|Krauss]] (talk) 04:47, 15 May 2017 (UTC)
Conditional support: first create explicit rules or recommendations, to avoid duplications and misunderstandings... I invite all you to review Help:Statements/Guidelines for external relationships, that is waiting rules for the use of five properties (P1628, P1709, P2235, P2236, P2888). --Krauss (talk) 04:47, 15 May 2017 (UTC)
PS: at this time, without rules, there are a lot of doubts and duplications showed by this report of ~500 entries of Wikidata-SchemaOrg mapping.
  • Symbol oppose vote.svg Oppose @Pigsonthewing: you need to justify very well why we need such special prop for Schema but not for the 1000 ontologies out there, eg DC, DCT... Schema is important, but the value of LOD comes exactly from using URLs, so what's the benefit of having this special case for Schema? In fact it will smush the distinction between the specific links (equivalentClass, equivalentProperty etc), so I think it's worse
    • @Frankieroberto: you don't need to worry that http://schema.org/ might some day change: it's used in 10B websites, so you can be certain it will live as long as the web itself. --Vladimir Alexiev (talk) 16:23, 16 May 2017 (UTC)
      • @Vladimir Alexiev: @ Pigsonthewing: http://schema.org/ may very well remain the prefix for the use in identifiers, but the actual webpage about the property/class can be viewed via https at https://schema.org. Right now, both https and non-http versions server the webpages, but in future the non-https version might redirect to the https version, and so it would be preferable to send users to the https version to avoid the extra http request (and to preserve their privacy), but we can only do this via having a specific formatterURL for that property. Frankieroberto (talk) 09:16, 24 May 2017 (UTC)
        • @Frankieroberto: you're missing an important fact: Schema says that its semantic URLs start with http, so in actual RDF data one must use http not https for Schema classes and properties. In the semantic web URLs are not simply for getting info about things, they **represent** things in certain precise ways. That's what I mean when I say that LOD (linked open data) is based on URLs not mere IDs --Vladimir Alexiev (talk) 02:44, 6 July 2017 (UTC)
          • @Vladimir Alexiev: I do understand how the Semantic Web works, and that URIs and URLs are different things (and the various debates about ways to distinguish the URI for the ID from the URI for the page about the ID, e.g. using a #resource suffice). However one reason for having a specific property for a schema.org ID is that it makes it easier to separate the two, e.g. an API user or RDF export can expand the ID to a URI by adding the http://schema.org/ prefix, whereas in constructing a link to the page about the ID (e.g. in the Wikidata editing interface using the formatter URL pattern) we can add the https prefix http://schema.org/ to preserve user privacy. Without the specific property, we can't easily do this. Frankieroberto (talk) 07:58, 6 July 2017 (UTC)
    • @Vladimir Alexiev: Where do I say that we don't need properties for other ontologies? All our external-ID properties with a formatterURL can be expressed as URLs; we've already decided not to go down the URL-only road. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 17:31, 16 May 2017 (UTC)
      • LOD is based on URLs. Established ontologies like DC, DCT, Schema and many others have stable URLs. I don't see the value of creating specific props for each of these ontologies, which props further destroy the distinction between equivalentClass, equivalentProperty, subProperty, superProperty. --Vladimir Alexiev (talk) 10:49, 17 May 2017 (UTC)
        • This is a proposal to create a property for Schema.org, not the others you list. equivalentClass, equivalentProperty, subProperty, superProperty can be applied to such a property. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 12:08, 17 May 2017 (UTC)
          • @Pigsonthewing: didn't you imply above that we'd need properties for other ontologies as well? Or is this argument intended to sneak Schema ID in, and then proceed by sneaking other ontologies, perhaps using Schema as a precedent? --Vladimir Alexiev (talk) 02:44, 6 July 2017 (UTC)
        • @Pigsonthewing: Can you give an example how this would work? Eg "airport (Q1248784) - schema.org id - Airport", and then what? --Vladimir Alexiev (talk) 08:43, 25 May 2017 (UTC)
      • @Pigsonthewing: the bullets you give above for "what advantages a unique property offers" are applicable to large datasets. They are not such important benefits for a few thousand items, which is the number of Schema classes and properties. Furthermore, ontology matching is rarely one-to-one. I may think that schema's Airport matches both airport (Q1248784) and aerodrome (Q62447), and you may disagree: deciding that "intellectual question" is a lot more important than knowing Airport is matched to 1 or 2, and knowing how many Schema terms are matched --Vladimir Alexiev (talk) 08:43, 25 May 2017 (UTC)
        • This issue exists whether or not we have a property, or whether we use a full URL as at present. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 13:50, 28 May 2017 (UTC)
  • Symbol support vote.svg Support ChristianKl (talk) 23:21, 26 June 2017 (UTC)
  • Symbol support vote.svg Support Frankieroberto (talk) 07:59, 6 July 2017 (UTC)

Commentary mistakenly added to the proposal[edit]

CAUTION:

... How to avoid mistakes? Replace properties by ID or add ID?
... We need for rules (!), before to create Schema.org_ID.
... Please edit/review Guidelines for external relationships.

--  – The preceding unsigned comment was added by Krauss (talk • contribs) at 22:38, 16 May 2017‎ (UTC).

e-museum id[edit]

   Under discussion
Description id of a work in e-museum, a website devoted to national treasures important national properties of National Museums of Japan
Data type External identifier
Domain Tangible Cultural Properties of Japan (Q2901860)
Allowed values d+
Example no label (Q28418167) -> 101224
Formatter URL http://www.emuseum.jp/detail/$1
Motivation

Multilingual, often-interesting work descriptions on this website. Zolo (talk) 09:22, 8 May 2017 (UTC)

Discussion
  • Symbol support vote.svg Support. This looks like a useful property for authority control for cultural heritage. I think the English label for this property would be more helpful to the user if the fact that this is for National Museums of Japan is made explicit, I suspect that we have/ will have additional e-musum ids in Wikidata. YULdigitalpreservation (talk) 14:15, 11 May 2017 (UTC)
  • Symbol support vote.svg Support; maybe needs a more specific name?. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 21:31, 19 May 2017 (UTC)
  • Symbol oppose vote.svg Oppose with current name. I'm open to supporting it when it has a name that's more informative for the average user. ChristianKl (talk) 16:20, 22 May 2017 (UTC)
  • @Pigsonthewing, ChristianKl: actually, even though the URL and the title shown on each page is "e-museum", the official name of the database seems to be e-Kokuho. So maybe we should use that in the property name ? I don't mind having a more transparent name, but I can't think of any that is both short and accurate. Anyhow, I don't think that should be a blocker for an "authority control" property, as there is no serious risk that it leads to a misundertanding of the property usage. --Zolo (talk) 13:06, 2 July 2017 (UTC)
  • Symbol support vote.svg Support; if we can agree on a suitable property name. I think a property named e-museum id has potential to be misused as a general property for digitised museum objects rather than for this particular collection as intended. e-kokuho id would be much more specific or perhaps something like National Museums of Japan e-museum id could be a viable alternative. Any thoughts? Sic19 (talk) 19:44, 22 August 2017 (UTC)

UK Parliament thesaurus ID[edit]

   Under discussion
Data type External identifier
Allowed values \d+
Example
Source http://www.data.parliament.uk/dataset/thesauri
Formatter URL http://explore.data.parliament.uk/?endpoint=terms/$1
Motivation

The thesaurus is used internally by the libraries of the House of Commons and House of Lords to index the work of parliament. Items in the thesaurus include names, organisations, legislation (bills and acts), concepts, content types, and a high-level Taxonomy used on the Parliamentary website for public access to material. Jheald (talk) 16:54, 9 May 2017 (UTC)

Discussion
  • Normally I'd support this without hesitation, but parliament are about to change their IDs (see this comment). I wonder whether this ID will be affected? I'll ask my contact there. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 17:44, 9 May 2017 (UTC)
@Pigsonthewing: Thanks Andy, useful info. User:Andrew Gray and I were talking to some of the Parliamentary Data people at the Newspeak House thing tonight, and you're right, they are developing a completely new data model to drive a completely rebuilt data service. As per what they told you, the beta website is primarily a tech demo, so not to expect any of those identifier values to necessarily carry over to the final release. They're still finding their way, with probably subject tagging for the petitions service to be the first thing out of the gate into the wild, in maybe the next six to nine months, then widening and deepening to more and more parliamentary services from there. The new system will include a number of API and webpage access-ways, including a public SPARQL endpoint, with more and more in place over maybe the next 18 months to two years.
Andrew and I talked a bit about whether this property still makes sense; but we reckoned it probably does, for at least a couple of reasons.
(i) it's a useful list of concepts in its own right to benchmark against, see what we have and what we don't, and how much of the existing Parliament model's 'broader'/'narrower' groupings are reflected (and how much are missing) by the relationships we currently have in Wikidata.
(ii) there's likely to be a period of parallel running when both sets of subject tags are being used by Parliament, with each different one perhaps primary in different parts of parliamentary work, as the new system is slowly extended through the different workflows. It's quite likely that there will be at least some matching done by the Parliament side between the new identifiers and the old, which they will presumably expose; so it would be a mistake to think that work done matching the old legacy identifiers will necessarily be wasted.
(iii) like any IT project, the new system may encounter all sorts of "unknown unknowns" that may take time to resolve. So the old identifiers may still have a fair amount of use left in them yet. Jheald (talk) 22:55, 9 May 2017 (UTC)
@Pigsonthewing: I think the short answer is that current Parliament IDs should be considered unstable and probably shouldn't be added to Wikidata. Parliament's IDs and URIs are all a little scruffy. Many of the identifiers we publish are just primary keys in a relational database so whilst they're unique to a given table in a given database, they're not unique across Parliament. The longer version is as per the comment on Andy's post.
We're starting to build out a new website which is currently at: https://beta.parliament.uk
The plan is to give everything in Parliament (members, committees, bills, questions, answers, subject headings etc) an 8 character opaque (obfuscated?) ID with URI patterns like: *.parliament.uk/:type_of_thing/:thing.id
The 8 character IDs will be unique across UK Parliament. Old URLs will be respected as redirects and we've built lookups into the new URI structure to allow for resources to be found by people who've stored other IDs (including the IDs currently in use (and one day wikidata)).
The URI structure for that is included here as the /lookup pattern:
https://github.com/ukparliament/ontologies/blob/master/urls.csv
In a linked data sense we'll also be published non-information resource URIs at something like:
https://id.parliament.uk/:thing.id
which will probably 303 to the website information resource URI.
On the specific subject of the Commons Library subject headings published as the taxonomy on data.parliament.uk, we're planning to bring these into the new website (as topic pages) fairly soon. It's maybe worth noting that for the example of David Cameron we'd have 2 identifiers.
One comes from a system called Members Names Information (MNIS) and identifies David Cameron the person in a FOAF style sense. This is already covered by property: P1996.
The other comes from the commons library taxonomy and identifies David Cameron as a library subject heading (a bag of things "about" David Cameron) in a SKOS type sense.
The beta website already publishes person information from MNIS (with the new 8 character identifiers) but doesn't yet publish subject headings.
When it does they'll be given the same style of 8 character ID as the people pages.
Given all IDs will be unique across UK Parliament it probably mades more sense to treat them all as one property. If you're planning to publish linked data style it's probably best to construct links to the non-information resource URI which is easily constructible from the identifier without needing to know its type
Also worth saying that User:Andrew Gray has already looked into mapping library subject headings to wikidata items so that should come in handy for mapping from our old identifiers to our new identifiers to wikidata. We also plan to publish sameAs style links from our things to Wikidata things.
Hope this makes sense
fantastic-life (talk) 18:56, 10 May 2017 (UTC)
Any update on this? Did the IDs get changed? --Yair rand (talk) 22:31, 4 September 2017 (UTC)

Istituto regionale ville venete ID (it) – (Please translate this into English.)[edit]

   Under discussion
Description Identification code attributed to the villas registered in the regional register of the Veneto villas Codice identificativo attribuito alle ville registrate nel registro regionale delle ville venete (it) – (Please translate this into English.)
Data type String
Domain villa veneta (Q3558938)
Example Villa Almerico Capra (Q505574) → A0500002654
Source Regional institute veneto villas on line register
Planned use Enter the villa's code as many items as possible
Motivation

It is important to identify the veneto villas Adert (talk) 12:22, 10 June 2017 (UTC)

Discussion
sorry, I just added it: villa veneta (Q3558938) --Adert (talk) 18:02, 10 June 2017 (UTC)

EUC code[edit]

   Under discussion
Description CJK character code in the Extended Unix Coding system
Represents Extended Unix Code (Q1140550)
Data type String
Template parameter | CodeEUC = in fr:template:Infobox Idéogramme
Domain CJK characters
Example (Q3595028) → B1AB
Motivation

There's is already a need for this, which will be more evident with the upcoming Wiktionary integration. ~nmaia d 02:41, 11 June 2017 (UTC)

Discussion
Pictogram voting comment.svg Comment I think in general perhaps this and the others you've proposed along these lines would be adequately handled by catalog code (P528) with a qualifier pointing to the character system? ArthurPSmith (talk) 15:00, 12 June 2017 (UTC)

Shift-JIS code[edit]

   Under discussion
Description kanji in the Shift-JIS coding system
Represents Shift_JIS (Q286345)
Data type String
Template parameter | CodeShiftJIS = in fr:template:Infobox Idéogramme
Domain kanji
Example (Q3595028) → 894A
Motivation

There's is already a need for this, which will be more evident with the upcoming Wiktionary integration. ~nmaia d 02:48, 11 June 2017 (UTC)

Discussion

Big5 code[edit]

   Under discussion
Description CJK character code in the Big5 encoding system
Represents Big5 (Q858372)
Data type String
Template parameter | CodeBIG5 = in fr:template:Infobox Idéogramme
Domain CJK characters
Example (Q3595028) → AB42
Motivation

There's is already a need for this, which will be more evident with the upcoming Wiktionary integration. ~nmaia d 02:53, 11 June 2017 (UTC)

Discussion
  • Why is the name EUC code and not Big5 code? What do CJK and EUC stand for? (It would be nice to have that information in the description) ChristianKl (talk) 09:44, 12 June 2017 (UTC)
    • I assume that was an error in creating the property proposal as a copy from another one. I've fixed the proposed label. ArthurPSmith (talk) 14:56, 12 June 2017 (UTC)

PatientsLikeMe[edit]

PatientsLikeMe condition ID[edit]

Description identifier for a condition on PatientsLikeMe, a website where patients can share health information
Represents PatientsLikeMe (Q3368754)
Data type External identifier
Domain medical condition
Allowed values [1-9]\d*
Example restrictive lung disease (Q7316336)610
Source https://www.patientslikeme.com/
External links Use in sister projects: [de][en][es][fr][it][ja][ko][nl][pl][pt][ru][sv][vi][zh][Wd][Ws].
Formatter URL https://www.patientslikeme.com/conditions/$1

PatientsLikeMe treatment ID[edit]

Description identifier for a treatment on PatientsLikeMe, a website where patients can share health information
Represents PatientsLikeMe (Q3368754)
Data type External identifier
Domain medical treatments, drugs as well as other interventions
Allowed values [1-9]\d*
Example salbutamol (Q410358)153
Source https://www.patientslikeme.com/
External links Use in sister projects: [de][en][es][fr][it][ja][ko][nl][pl][pt][ru][sv][vi][zh][Wd][Ws].
Formatter URL https://www.patientslikeme.com/treatments/show/$1

PatientsLikeMe sympton ID[edit]

Description identifier for a symptom on PatientsLikeMe, a website where patients can share health information
Represents PatientsLikeMe (Q3368754)
Data type External identifier
Domain medical symptom
Allowed values [1-9]\d*
Example insomnia (Q1869874)1
Source https://www.patientslikeme.com/
External links Use in sister projects: [de][en][es][fr][it][ja][ko][nl][pl][pt][ru][sv][vi][zh][Wd][Ws].
Formatter URL https://www.patientslikeme.com/symptoms/show/$1


Motivation

PatientsLikeMe is a website with over 500,000 users, where patients can share their experiences with different treatments for their conditions. ChristianKl (talk) 22:16, 23 June 2017 (UTC)

Discussion

✓ Done @ChristianKl, Pigsonthewing, LydiaPintscher: created all 3. --99of9 (talk) 12:17, 20 September 2017 (UTC)

Familypedia person ID[edit]

   Done
Description identifier for a person on Familypedia, the genealogical database by Wikia
Represents Familypedia (Q5433416)
Data type External identifier
Example Eddie August Schneider (Q5335826)Eddie_August_Schneider_(1911-1940)
Formatter URL http://familypedia.wikia.com/wiki/$1
Motivation

Adding another identifier for a genealogical database. ChristianKl (talk) 23:10, 24 June 2017 (UTC)

Discussion

ChristianKl (talk) 15:11, 24 June 2017 (UTC) Melderick (talk) 12:22, 25 July 2017 (UTC)


Pictogram voting comment.svg Notified participants of WikiProject GenealogyChristianKl (talk) 23:11, 24 June 2017 (UTC)

  • Symbol support vote.svg Support Its sematic, so maybe we can do something with bots. --Walter Klosse (talk) 15:17, 13 August 2017 (UTC)

@ChristianKl, Walter Klosse: created as Familypedia person ID (P4193). --99of9 (talk) 12:36, 5 September 2017 (UTC)

CNPS taxon ID[edit]

   Done
Description taxon ID in California Native Plant Society's taxon database
Data type External identifier
Domain taxon (Q16521)
Allowed values string pattern
Allowed units [1-9]\d*
Example Astragalus lentiginosus var. antonius (Q32340643)1578
Format and edit filter validation 1-4 digit number, currently 4053 possible IDs.
External links Use in sister projects: [de][en][es][fr][it][ja][ko][nl][pl][pt][ru][sv][vi][zh][Wd][Ws].
Formatter URL http://www.rareplants.cnps.org/detail/$1.html
Robot and gadget jobs Could be added to Mix'n'match
See also Calflora ID (P3420)
Motivation

Taxon ID from California Native Plant Society (Q5020710) which includes info such as taxon common names and UDSA taxon IDs, and a bunch more location/observation details. (tJosve05a (c) 15:02, 7 July 2017 (UTC)

Discussion

@Josve05a, Pigsonthewing, YULdigitalpreservation: created as CNPS taxon ID (P4194). --99of9 (talk) 13:06, 5 September 2017 (UTC)

REGINE water system number[edit]

   Under discussion
Description identifier for water system areas in Norway
Represents REGINE water system number (Q1520865)
Data type External identifier
Domain body of water (Q15324)
Allowed values [0-9]{3}\.[0-9A-Z]+
Example Glomma (Q214535) → 002.Z
Source https://www.nve.no/karttjenester/kartdata/vassdragsdata/nedborfelt-regine/
https://gis3.nve.no/link/?link=nedborfelt
See also Gewässerkennzahl (P1183), SANDRE ID (P1717)
Motivation

This proposal is a step towards splitting up Gewässerkennzahl (P1183) which does not represent a single identification system. 1-Byte (talk) 18:49, 19 July 2017 (UTC)

Discussion

hydrological order number[edit]

   Under discussion
Description identifier for water bodies in the Czech Republic
Represents hydrological order number (Q12021099)
Data type External identifier
Domain body of water (Q15324)
Allowed values [124]-[0-9]{2}-[0-9]{2}-[0-9]{3}
Example Svatopetrský potok (Q12057349)1-01-01-004
Source http://voda.chmi.cz/opv/doc/hydrologicky_seznam_povodi.pdf
Formatter URL http://heis.vuv.cz/data/webmap/isapi.dll?MAP=mp_heis_voda&MU=CS&GEN=LSTD&TS=14&QY={14}T[]$1
See also Gewässerkennzahl (P1183), SANDRE ID (P1717)
Motivation

This proposal is a step towards splitting up Gewässerkennzahl (P1183) which does not represent a single identification system. --1-Byte (talk) 19:08, 19 July 2017 (UTC)

Discussion
  • Pictogram voting comment.svg Comment how many of these are expected? Also I'm guessing there's no website we could point to to resolve these (formatter URL)? ArthurPSmith (talk) 17:26, 27 July 2017 (UTC)
    • @ArthurPSmith: There are 620 entries which are already indexed and can be copied from Gewässerkennzahl (P1183). In total there are several thousand numbers assigned (most of which are probably not relevant though). I added a formatter URL to display some basic information about a number. 1-Byte (talk) 20:06, 27 July 2017 (UTC)
  • Symbol support vote.svg Support ok, looks good to me! ArthurPSmith (talk) 20:47, 27 July 2017 (UTC)

MusicBrainz recording ID[edit]

   Under discussion
Description identifier for a recording in the MusicBrainz open music encyclopedia. Use as qualifier for statements with "tracklist" (P658) only.
Data type External identifier
Domain albums, extended plays, and the like (only as qualifier to tracklist (P658))
Allowed values [A-Za-z0-9]{8}-[A-Za-z0-9]{4}-[A-Za-z0-9]{4}-[A-Za-z0-9]{4}-[A-Za-z0-9]{12}
Example
Source https://musicbrainz.org/
External links Use in sister projects: [de][en][es][fr][it][ja][ko][nl][pl][pt][ru][sv][vi][zh][Wd][Ws].
Formatter URL https://musicbrainz.org/recording/$1
See also
Motivation

The same song (of the same duration, with the same performers…basically the exact same audio) may appear on different albums—take, for example, any song that also appears on an album in the Now That's What I Call Music! (Q3270600) series. Alternatively, the same song may be covered by different artists, which isn't necessarily implied at the moment when tracklist (P658) is used on different albums by those artists. Adding a property such as this as a qualifier would be another way to disambiguate these. Mahir256 (talk) 04:26, 2 August 2017 (UTC)

Sweet kate
Galaktos
Sjoerddebruin
AmaryllisGardener
Kosboot
Shingyang-i
Daniele.Brundu
Airon90
Atallcostsky
Cvbncv
LinardsLinardsLinards
Infovarius
Hannolans
Ptolusque
Pictogram voting comment.svg Notified participants of WikiProject Music

(@Pigsonthewing: A release group refers to a album, an EP, or a single released independently of other songs (or with remixes and edits, as is the case for many such releases). A recording refers to a representation in audio of a specific performance of a song, which may be included on different albums (see the new example I provided above). This means that cover versions of a song on different albums would have different values for this property. Apologies if I'm repeating myself. Mahir256 (talk) 16:00, 14 August 2017 (UTC))

Discussion
@Jura1: See the bolding to the 'domain' added above. Mahir256 (talk) 16:06, 16 August 2017 (UTC)

IDESCAT territorial code in Catalonia[edit]

   Under discussion
Description official identifier for a Catalonian territorial unit, from Institut Estadístic de Catalunya (IDESCAT)
Represents Municipality and regional codes for all the administrative entities of Catalonia territories: comarca of Catalonia (Q937876), municipality of Catalonia (Q33146843), decentralized municipal entity (Q6554043), minor local entity of Spain (Q3333989). Exemple: Alt Empordà (Q6904), Barcelona (Q1492), no label (Q9059342), etc.
Data type External identifier
Template parameter ca:Plantilla:Infotaula geografia política, now just for municipalities.
Domain subclass of (P279) of administrative territorial entity of Catalonia (Q11917457) and its dependents
Allowed values Numeric. 2 digits for comarca of Catalonia (Q937876), 6 digits for municipality of Catalonia (Q33146843), 10 digits for the rest of entities
Example
Source https://www.idescat.cat/codis/?lang=en
Planned use Upload values and incorporate them to cawiki infoboxes
Formatter URL https://www.idescat.cat/emex/?id=$1
Robot and gadget jobs Control domain constrains. Possible access to get public information to upload several properties (population (P1082), nominal GDP (P2131), et al.
Motivation

It's an official code for all catalan territory levels. Now, it's showed in infobox as a calculated code from INE municipality code (P772) just for municipalities, but not for the rest of the entities. It allows to access directly to whole statistical information (Demographic, housing, economy, etc.)

Formatter URL - Information is only for comarca of Catalonia (Q937876) and municipality of Catalonia (Q33146843)

Amadalvarez (talk) 11:39, 31 July 2017 (UTC)


Discussion

Chilean National Monuments ID[edit]

   Under discussion
Description The id number is from an older (and offline) website from the Consejo Nacional de Monumentos.
Data type External identifier
Template parameter |id= in w:es:Plantilla:MonumentoChile
Domain Items where heritage designation (P1435) is a subclass of national monument of Chile (Q6974386)
Allowed values integer
Example Castillo de la Pura y Limpia Concepción de Monfort de Lemus (Q18809829) → 170
Planned use Migrating Wiki Loves Monuments to Wikidata
Motivation

There is not external links for this because the source website is now offline, but is still useful because this information is used in old documentation. NomadDiego (talk) 19:05, 10 August 2017 (UTC)


Discussion

@Superzerocool: saw that you made the original mapping so you might be interested in this. /207.134.107.253 02:39, 11 August 2017 (UTC)

Ok, I see the new changes in the mapping and I like it (I must admit that I worked a few hours with the mapping in Esino Lario due jetlag). The old number isn't a legal number, so it can't be used in Wikidata because there is a lack of support of the original source, and the older website of monumentos.cl was deleted, so there is no formal usage outside Wikipedia/Wikimedia projects. A workaround could be the link with leychile.cl website with the decree internal number (ie). Just an idea. Superzerocool (talk) 13:50, 11 August 2017 (UTC)
@Superzerocool:Did the number use to be an official number but it has now been abandoned or was it never official to start with? /André Costa (WMSE) (talk) 18:04, 11 August 2017 (UTC)
(As an aside) for no label (Q16489745) there is 2077 (id used on Wikipedia), 27184 (id on monumentos.cl), 288451 (id norma) and "D. 36" the official decision (could there be more than one monument per decision?) /André Costa (WMSE) (talk) 18:56, 11 August 2017 (UTC)
@André Costa (WMSE): as far I can remember, the old number was an autoincrementable number from some database that the National Monuments Council (CMN in Spanish) gave us (to WMCL) to make our first Wiki Loves Monuments (2012). The number was the key field to make the link between Wikipedia and their page, but the old CMS has been replaced in 2015 and the URL has been modified. So, we don't have the official number: the CMN doesn't show -or use- a unique identifier (internal or external) to make the replace in Wikipedia. I suggest the number in leychile, because the law/decree ar in the National Congress Library and they use a lot of semantic and these stuff -I remember that they have an endpoint-. Superzerocool (talk) 21:39, 11 August 2017 (UTC)
@Superzerocool, NomadDiego: Ok. Then I suggest we abandon this proposal and use the old number with Wiki Loves Monuments ID (P2186) (maybe with a CL prefix). That way identifiers used today on Commons and in the lists still work.
For the law/decree we should probably use legal citation of this text (P1031) (as a qualifier on heritage designation (P1435)) and we can then figure out if we want to also add the url or create a property for the leyChile/NormaId. /André Costa (WMSE) (talk) 22:56, 13 August 2017 (UTC)

Videolectures ID[edit]

   Ready Create
Description identifier for person, meeting or presentation/talk (video) on the Videolectures website
Represents VideoLectures.net (Q7927787)
Data type External identifier
Domain Q5
Allowed values [a-z_0-9]+
Example
Source http://videolectures.net
External links Use in sister projects: [de][en][es][fr][it][ja][ko][nl][pl][pt][ru][sv][vi][zh][Wd][Ws].
Formatter URL http://videolectures.net/$1/
See also TED speaker ID (P2611)
Motivation

http://videolectures.net is a company and website that records and streams academic videos. There are webpages for each individual recorded video as well as list webpages for scientific meetings and for researchers. Initially the most interesting is perhaps the link to researchers. Finn Årup Nielsen (fnielsen) (talk) 16:59, 17 August 2017 (UTC)

Discussion
  • Symbol support vote.svg Support. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 14:38, 26 August 2017 (UTC)
  • The use of name strings as identifiers seems a bit brittle (re. name changes, or even correction of spelling/transliteration errors). Is there a statement somewhere on the site that the person identifiers are persistent (don't change, or stay reserved and have redirects in case of changes? Jneubert (talk) 10:31, 29 August 2017 (UTC)

Nominis saint ID[edit]

   Under discussion
Description saint ID in Nominis database
Represents saint (Q43115)
Data type External identifier
Domain saint (Q43115)
Example Peter (Q33923)899/Saint-Pierre
Source http://nominis.cef.fr/contenus/saint/alphabetique.html
Formatter URL http://nominis.cef.fr/contenus/saint/$1.html
Robot and gadget jobs Mix'n'Match
See also Nominis given name ID
Motivation

Useful database with more than 8000 saints which connect given names to saints, feast dates and similar given names — Ayack (talk) 19:16, 20 August 2017 (UTC)

VIGNERON (talk)
Mathieudu68 (talk)
Tpt (talk) (si besoin d'aide technique)
Ayack (talk) (surtout pour les MH)
Aga
Ash Crow (talk)
Tubezlob (talk)
PAC2 (talk)
Thierry Caro (talk)
Pymouss (talk)
Pintoch (talk)
Alphos (talk)
Nomen ad hoc (talk)
Framawiki (talk)
GAllegre (talk)
Pictogram voting comment.svg Notified participants of WikiProject France

Discussion

Nominis given name ID[edit]

   Under discussion
Description given name ID in Nominis database
Represents given name (Q202444)
Data type External identifier
Domain given name (Q202444)
Example Pierre (Q2093070)239/Pierre
Source http://nominis.cef.fr/contenus/prenom/alphabetique.html
Formatter URL http://nominis.cef.fr/contenus/prenom/$1.html
Robot and gadget jobs Mix'n'Match
See also Nominis saint ID
Motivation

Useful database with more than 6000 given names which connect given names to saints, feast dates and similar given names — Ayack (talk) 19:14, 20 August 2017 (UTC)

VIGNERON (talk)
Mathieudu68 (talk)
Tpt (talk) (si besoin d'aide technique)
Ayack (talk) (surtout pour les MH)
Aga
Ash Crow (talk)
Tubezlob (talk)
PAC2 (talk)
Thierry Caro (talk)
Pymouss (talk)
Pintoch (talk)
Alphos (talk)
Nomen ad hoc (talk)
Framawiki (talk)
GAllegre (talk)
Pictogram voting comment.svg Notified participants of WikiProject France

Discussion

Application number[edit]

   Under discussion
Data type External identifier
Domain goods (Q28877)
Allowed values \d{9}
Example Tentation (Q3518178) → 000885038
Source https://www.tmdn.org/tmview/welcome
Motivation

(Add your motivation for this property here.) d1g (talk) 17:05, 23 August 2017 (UTC)

Discussion

Brueckenweb ID[edit]

   Under discussion
Description identifier of a bridge, in the Bruckenweb database
Data type External identifier
Domain bridge (Q12280)
Allowed values [1-9]\d*
Example Brooklyn Bridge (Q125006) -> 192
External links Use in sister projects: [de][en][es][fr][it][ja][ko][nl][pl][pt][ru][sv][vi][zh][Wd][Ws].
Formatter URL http://www.brueckenweb.de/2content/datenbank/bruecken/3brueckenblatt.php?bas=$1
Motivation

Database used in the external link sectuib various Wikipedia, though admittedly not very extensively (en:Template:Brueckenweb + use without template). The data themselves do not look outstanding, but there are also external links and a bibilography of sorts that may be interesting. Zolo (talk) 11:03, 24 August 2017 (UTC)

Discussion

mapping relation[edit]

   Under discussion
Description qualifier, which definies the relation of the item to the external identifier more precisely in terms of the SKOS mapping relations
Data type Item
Domain statements of properties of type external identifier (Q21754218)
Allowed values One of exact match (Q39893449), close match (Q39893184), broad match (Q39894595), narrow match (Q39893967) or related match (Q39894604)
Example Overseas countries and territories (Q1451600)STW Thesaurus for Economics ID (P3911) → 29738-2 (Overseas territories)
"mapping relation" → close match (Q39893184)
Lake Constance (Q4127)STW Thesaurus for Economics ID (P3911) → 30083-1 (Lake Constance region)
"mapping relation" → broad match (Q39894595)
Source Simple Knowledge Organization System (Q2288360) (see formal and extended definition of mapping relations)
Planned use more complete mapping of STW Thesaurus for Economics (Q26903352) to Wikidata (for now), and of other knowledge organization systems already linked by external identifiers
See also exact match (P2888), narrower external class (P3950) (for values of type URL)
Motivation

Originally proposed in the Wikidata:Project chat under the title Making Wikidata fit as a linking hub for knowledege organization systems and copied over here, as suggested by ChristianKl. Jneubert (talk) 11:00, 25 August 2017 (UTC)

Wikidata covers more and more aspects of human knowledge. In certain domains or subject fields, well established knowledge organization system (Q6423319) (such as thesauri, classification schemes, taxonomies, or subject heading systems) exist, and organize knowledge by defining concepts and optionally their mutual hierarchical or associative relationships. Connecting these systems, originating mostly from the library and information science world, to Wikidata - via either external identifier (Q21754218) properties or via exact match (P2888) - is a widely used and encouraged practice.

For these knowledge organization systems (KOS), Wikidata already works as a linking hub, because it connects concepts defined in one KOS via the according Wikidata property to all other concepts connected to the same Wikidata item via other external id properties. However: While mapping external entities is straightforward for people, it gets increasingly difficult for organizations, locations, or abstract concepts. Sometimes the concepts only partly overlap, sometimes there are slight differences in meaning, sometimes there is only an associative relation (e.g. between an activity and the tool used in that activity). Currently, such kinds of matches cannot be coverd cleanly. This suggestion aims at changing this, making Wikidata fit as an universal linking hub for KOS.

W3C's Simple Knowledge Organization System (Q2288360) (SKOS) standard defines and explains five mapping relations for linking to external concepts:

  • exactMatch indicates that two concepts have equivalent meaning, and the link can be exploited across a wide range of applications and schemes. The link is meant to be transitive (A = B and B = C means A = C).
  • closeMatch indicates that two concepts are sufficiently similar that they can be used interchangeably in many applications. This link is not meant to be transitive.
  • narrowMatch indicates that one concept is narrower than the other (for the representation of hierarchical links). The link is not meant to be transitive.
  • broadMatch indicates that one concept is broader than the other (inverse of narrower). The link is not meant to be transitive.
  • relatedMatch indicates a non-hierarchical assoziative relationship between two concepts. The link is not meant to be transitive.

I here suggest to implement these relations in Wikidata as follows:

  1. Create four items "close match", "broad match", "narrow match", "related match", with definitions according to SKOS.
  2. Create a new property "mapping relation type" (instance-of Wikidata qualifier (Q15720608)) for use as an optional qualifier for properties of type external identifier, with values constrained to "close match", "broad match", "narrow match" or "related match". An exact match would be implied by a missing "mapping relation type" qualifier.
  3. Create according constraints, in particular constraints to be used instead of "single value" and "unique value", taking into account that 1:1 relationships between an item and a concept identified by an external identifier may be complemented or replaced by multiple qualified mappings (n:m). The use of such constraints in the definition of the external id properties could indicate if they are intended to be used with different mapping relation types.

That implementation could work as an extension of the already well established mechanisms. By "exact match implied in absence of a 'mapping relation type' qualifier", it would leave all existing external identifier relations undisturbed, yet would allow adding more precise mappings where appropriate.

As an important point in practice, Mix'n'match or equivalent tools can be applied for creating links to external vocabularies and catalogs without change. Once the external id property value has been added to the matching Wikidata item, it can immediately be qualified more precisely with a mapping relation type.

As a point of caution, queries would have to be aware of qualifiers to external id properties, actually meaning "this is not an exact match". However, that would not apply to the large group of existing properties for persons or other entities where only exact 1:1 relationships exist.

What do you think of this proposal? - Jneubert (talk) 11:59, 24 August 2017 (UTC)

Definitions of External identifier

These are the definitions of external identifier (Q21754218) I was able to find (if you know other, deviating or more expressive, sources, please add them here). Jneubert (talk) 16:42, 6 September 2017 (UTC)

"String that represents an identifier used in an external system. Will display as external link if a formatter URL is defined." (Help:Data_type)
"Some properties have values that are strings used in the databases of external organisations. They uniquely identify an item. For example, an ISBN for a book or the unique part of the URL of a movie or an actor in the Internet Movie Database." (Wikidata:Glossary)
Discussion

(First three comments copied from Wikidata:Project chat - I hope that's ok. Jneubert (talk) 10:59, 25 August 2017 (UTC))

This sounds reasonable to me. How about creating a property proposal? I think that's a better place to have this discussion. ChristianKl (talk) 13:52, 24 August 2017 (UTC)
I mostly support this. However, the SKOS relations (other than "exact") are somewhat vaguely defined: it's not clear what are the boundaries of "close", and "broad" (and conversely "narrow") can refer to a subclass relation, an instance-class relation, or a part-whole relation (or possibly other types of "broadening"). "related" could refer to any sort of relationship. Therefore I think in general it is preferable that, if no wikidata item already exists which is an "exact match" to an external URI, a new item should be created that is an "exact match", and the more precise wikidata properties used to relate that new item to existing items. Using these SKOS non-exact relations should, in my view, be only a fallback when creation of new wikidata items is not practical for some reason. ArthurPSmith (talk) 14:05, 24 August 2017 (UTC)
Well, KOS are not ontologies, and almost always have messy corners from an ontological point of view. However elaborated, they have been created to index or classify publications, and their concepts were tailored for that purpose. E.g., the STW Thesaurus for Economics (Q26903352) has a concept "Content management", and uses that for "Content management system", too. (Probably because among the threehundred-somthing publications, which have been found relevant for economics, and indexed with this concept, only very few focus on the system aspect.) To the more precisely defined Wikidata items content management (Q173373) and content management system (Q131093), any mapping will be necessarily inexact.
In the first example above (overseas territories), concepts on both sides are defined not very well (brittle re. Brexit on the WD side, and defined only by the indexed publications on STW side). I would very much hesitate to declare an exact match in that situation. Jneubert (talk) 11:17, 25 August 2017 (UTC)
@Jneubert: a qualifier seems useful because this applies to every property, Symbol support vote.svg Support d1g (talk) 15:36, 24 August 2017 (UTC)
  • Symbol support vote.svg Support. Thank you for proposing these ideas. I support the creation of these properties/qualifers and their application as described. This seems like a reasonable first-step toward being able to map external systems to Wikidata. YULdigitalpreservation (talk) 13:47, 25 August 2017 (UTC)
  • Currently, I'm doubtful that the name/description is clear enough to tell a new user what this property is about. Is there prior art that we can use to orient ourselves when it comes to name/description? ChristianKl (talk) 08:12, 27 August 2017 (UTC)
Unfortunatly, I'm not aware of something from the KOS domain which could apply here. Perhaps somebody else? Particularly if similar mechanisms have been used elsewhere in Wikidata?
If we have to make it up ourselves: What would you think of "mapping relation modifier" as name and "Qualifier for the in-exact mapping of an item to an external identifier (derived from SKOS relations)"? That would stress the point that the user modifies a (by default exact) relation. Jneubert (talk) 07:18, 28 August 2017 (UTC)
  • In general I support this, but I'm not sure it is a good idea to indicate exact matches by the absence of a qualifier. In my mind, the mapping relationships should default to something like closeMatch, if they should have a default type at all. exactMatch implies transitivity and that is always a bit dangerous, when you have to link between KOS (including Wikidata) that have different points of view. But safest would be to also declare exactMatch as one possible qualifier. Absence of qualifier would simply mean that we don't know the precise type of relationship - somewhat like skos:mappingRelation (the superproperty of all SKOS mapping relationships), in effect. Osma Suominen (talk) 14:24, 29 August 2017 (UTC)
Thanks for your thoughtful comment. The rationale behind proposing exact match as default was, that - as far as I can oversee - external id properties were up to now used to express identity (without ontolgical baggage). This is true for people, and probably also for some or most of the widely used identifiers for genes/proteins/rna and the like. I didn't want to devalue the millions of existing external id links where an exact match is the most appropriate interpretation. However, you are right re. the possibly unconsidered and undisrable consequences of the the transitivity of "exact match". That may already be an issue with the third-most used external id, Geonames. So I can agree on your suggested solution to additionally introduce an explicit "exact match" relationship, and considering the unqualified properties as "matching" the external entity in an extent which can sometimes be derived the domain of the items (e.g., for people), and sometimes users and applications have to take an (hopefully informed) guess. I wonder what others think of that proposed modification of the proposal. Jneubert (talk) 10:05, 30 August 2017 (UTC)
@jura1: You've made a comment re. exact matches in the project chat. I'm not sure if it hits the same spot, and if the proposed solution would solve your concerns. Jneubert (talk) 10:09, 30 August 2017 (UTC)
An additional advantage of an explicit "exact match" value may be, that it would allow to define a "mandatory qualifier" constraint on the external id property, which would play nice with a "one of" constraint on the qualifier. That would allow to impose a fairly strong regime on external ids, for which a community consensus can be reached that they should be "properly" mapped. Jneubert (talk) 07:44, 31 August 2017 (UTC)
A point of caution, however: We should carefully consider how a mandatory qualifier plays with Mix-n-match and mapping workflows. It will enhance the workload, because each statement has to be qualified. Doing this manually for every statement is a serious additional burden. On the other hand, for each larger vocabulary mapping approach, any relation can be considered as a default and, after working through Mix-n-match lists and adding qualifiers for the deviating relations, the qualifier for the "default" can be added automatically (e.g., via Quickstatements). Jneubert (talk) 09:17, 31 August 2017 (UTC)
Hi @Magnus_Manske: Does Mix-n-match support the insertion of external id properties, when these properties have mandatory qualifier constraints? (What would allow to qualify the properties in a second step, independent from M-n-m). Jneubert (talk) 09:17, 31 August 2017 (UTC)
Mix'n'match is intended for "equivalent" matches. It does not support adding qualifiers when adding statements to Wikidata. There is no storage, no interface code for this. Adding such qualifiers when matching would likely slow down and/or clutter the interface. I suggest that adding such qualifiers would be a separate task. It should be simple to generate a list of items with statements lacking such qualifiers via SPARQL. Qualifiers would then have to be added manually, as the decision about a "matching type" is likely one that cannot be done automatically. --Magnus Manske (talk) 15:32, 8 September 2017 (UTC)
Thanks! completely agree. Jneubert (talk) 15:44, 8 September 2017 (UTC)
Agree as well. Applications similar to the above wouldn't be possibly any more or be slowed down. Accordingly, the domain of such a qualifier needs to be limited.
--- Jura 09:19, 9 September 2017 (UTC)
✓ Done Added "exact match" as explicit value (instead of default), as proposed by Osma Suominen. Jneubert (talk) 11:02, 13 September 2017 (UTC)
  • Symbol oppose vote.svg Oppose domain. if this is added to any property, effectively the current approach for external ids is invalidated.
    --- Jura 06:31, 2 September 2017 (UTC)
    • What is the “current approach for external ids”? I don't get your point. Sorry. :-/ --Michael Büchner (talk) 14:13, 5 September 2017 (UTC)
      • Currently people know they can do a 1-1 matching with external ids. If this is applied to random properties, one would need to check for the absence of qualifiers every time.
        --- Jura 07:00, 6 September 2017 (UTC)
        • I agree that external ids "normally" are used to express 1-1 relationships. Their definition however actually only says that an external id "uniquely identifies an item" in an external system (see definitions above). That means, the identifier is unique in that system, but in my eyes says nothing about the Wikidata side or the relationship. So I cannot see that "the current approach for external ids is invalidated".
The 1-1 relationship is normally expressed by a combination of single value and unique value / distinct values constraints - which is used by many properties of type external id, and which can be taken as a strong indication against the use of relation type qualifiers. The absence of qualifiers can be further and formally enforced with an allowed qualifiers constraint with "no value" (as explained on the help page). On the other hand, qualifiers can be made mandatory for selected properties. So it can be actively precluded that qualifiers are "applied to random properties". Additionally, as stated above, qualifiers obviously do not make sense in large domains (e.g., persons). And finally, it takes effort to attach qualifiers, so it is not very likely that it happens randomly. Jneubert (talk) 17:05, 6 September 2017 (UTC)
Constraint or not, can you explain how the applicability of this qualifier would be limited beforehand?, e.g. it wont apply to any properties with single & unique value constraints?
--- Jura 09:19, 9 September 2017 (UTC)
As mentioned above, I doubt that could evolve to a widespread problem (due to the nature of most external id properties, and the effort and level of expertise required to apply qualifiers at all. I've checked for VIAF ID (P214) - for more than a million IDs, only a handful of qualifiers show up, some probably assigned in a wrong position). I'd suggest to handle that on a per-property basis. Trying to create some sophisticated custom constraint would add load to the machines involved, and more so, to users trying to understand what's going on. Jneubert (talk) 07:56, 11 September 2017 (UTC)
It's probably even worse if it's handled separately. People could match the identifier for Berlin to the item for Germany and might think that the exact qualifier would be added later. Users exporting to a list of identifiers and items are mislead because qualifiers haven't been included.
--- Jura 14:36, 11 September 2017 (UTC)
Perhaps this is a misunderstanding: With "handle on a per-property basis" I meant the definitions of the external id properties (which may require or preclude the qualifier), not the individual property values. Jneubert (talk) 17:30, 11 September 2017 (UTC)
  • Symbol support vote.svg Support. Thank you very much for this proposal. I totally support this idea! (Nothing more to say.) --Michael Büchner (talk) 14:13, 5 September 2017 (UTC)
  • Pictogram voting question.svg Question Would you consider broadening this to something like "type or quality of relation", with other allowed values including those not defined by SKOS? For example, I previously asked for advice on how to denote a "confidence value" published by the Australian Bureau of Statistics about how well their statistical regions match the gazetted regions. I would like to apply this as a qualifier for Australian Statistical Geography 2011 ID (P4014). Or should I apply for a whole new property just for ABS confidence? --99of9 (talk) 03:57, 11 September 2017 (UTC)
No, sorry. The idea is to restrict this property to well-known SKOS relations, in order to make Wikidata fit as a linking hub for knowledge organization systems, which can be queried in a predictable and reliable way. If I understand your use case correctly, confidence values by ABS are quite well definied, but only for their domain. Confidence values applied in other domains, e.g., to the mapping of GND and DDC, may be definied with a quite different mindset. Jneubert (talk) 07:56, 11 September 2017 (UTC)

@ChristianKl, ArthurPSmith, D1gggg, YULdigitalpreservation, Osmasuominen, Jura1:, @Hanshandlampe, 99of9: I've modified the proposal by adding "exact match" as explicit value (instead of default), as suggested by Osma. Additionally, I've slightly modified the description (in an attempt to be more clear to users, as pointed out by ChKlein). Since the values would be restricted to five explicit options, the property name could perhaps simply be "mapping relation" - what do you mean? -- Jneubert (talk) 11:02, 13 September 2017 (UTC)

  • GA candidate.svg Weak support I don't feel this is essential, but given the discussion above I do feel it could be helpful. I've shortened the English label as suggested by Jneubert just now, that seems fine. I do have a concern about what Jura mentioned just above - we perhaps should add usage instructions that these relations should only be used where there is a very close relationship. That is to make sure not to, as Jura suggests, link everything in Germany to "Germany". Again that may be more appropriate to specify on identifiers property-by-property. ArthurPSmith (talk) 13:32, 13 September 2017 (UTC)
  • I've added a draft explanation When to use "mapping relation" qualifiers?. When anchored at the start of the property talk page, I'd expect that it could additionally clarify the intended use and help to avoid the insertion of random nonsense relations, as described by Jura above. (If there is a better place to add such explanations, please let me know.) Jneubert (talk) 09:20, 15 September 2017 (UTC)

MAVISE[edit]

MAVISE TV channel ID[edit]

   Under discussion
Description ID of a TV channel in the MAVISE database of the European Audiovisual Observatory (Q1377229)
Represents MAVISE (Q28405583)
Data type External identifier
Domain television network (Q1254874)
Allowed values [1-9]\d*
Example RTL Klub (Q1094569)337
Source http://mavise.obs.coe.int/
Formatter URL http://mavise.obs.coe.int/channel?id=$1

MAVISE on-demand audiovisual service ID[edit]

   Under discussion
Description ID of an on-demand audiovisual service in the MAVISE database of the European Audiovisual Observatory (Q1377229)
Represents MAVISE (Q28405583)
Data type External identifier
Domain video on demand (Q723685)
Allowed values [1-9]\d*
Example RTL XL (Q18089153)265
Source http://mavise.obs.coe.int/
Formatter URL http://mavise.obs.coe.int/odas?id=$1

MAVISE country ID[edit]

   Under discussion
Description ID of a country in the MAVISE database of the European Audiovisual Observatory (Q1377229)
Represents MAVISE (Q28405583)
Data type External identifier
Domain country (Q6256)
Allowed values [1-9]\d*
Example Hungary (Q28)16
Source http://mavise.obs.coe.int/
Formatter URL http://mavise.obs.coe.int/country?id=$1

MAVISE competent authority ID[edit]

   Under discussion
Description ID of a licensing authority / register in the MAVISE database of the European Audiovisual Observatory (Q1377229)
Represents MAVISE (Q28405583)
Data type External identifier
Domain government agency (Q327333)
Allowed values [1-9]\d*
Example National Media and Infocommunications Authority (Q541497)239
Source http://mavise.obs.coe.int/
Formatter URL http://mavise.obs.coe.int/competent_authority?id=$1

MAVISE company ID[edit]

   Under discussion
Description ID of a company in the MAVISE database of the European Audiovisual Observatory (Q1377229)
Represents MAVISE (Q28405583)
Data type External identifier
Domain company (Q783794)
Allowed values [1-9]\d*
Example Magyar Telekom (Q458944)3432
Source http://mavise.obs.coe.int/
Formatter URL http://mavise.obs.coe.int/company?id=$1
Motivation

MAVISE is an extensive database curated by the OBS. Storing their IDs means considerable added value for our items. Máté (talk) 05:39, 27 August 2017 (UTC)

Discussion

LUMIERE[edit]

LUMIERE film ID[edit]

   Under discussion
Description ID of a film in the LUMIERE database of the European Audiovisual Observatory (Q1377229)
Data type External identifier
Domain film (Q11424)
Allowed values [1-9]\d*
Example Son of Saul (Q19816400)64000
Source http://lumiere.obs.coe.int/
Formatter URL http://lumiere.obs.coe.int/web/film_info/?id=$1

LUMIERE director ID[edit]

   Under discussion
Description ID of a film director in the LUMIERE database of the European Audiovisual Observatory (Q1377229)
Data type External identifier
Domain human (Q5)
Allowed values [1-9]\d*
Example Pedro Almodóvar (Q55171)1580
Source http://lumiere.obs.coe.int/
Formatter URL http://lumiere.obs.coe.int/web/director_info/?lum_id=$1
Motivation

LUMIERE is a unique database of cinema admissions in Europe curated by the OBS. Máté (talk) 05:39, 27 August 2017 (UTC)

Discussion


  • Symbol strong support vote.svg Strong support (WikiDataMovieDB)

Pressemappe 20. Jahrhundert IFIS[edit]

   On hold
Description identifier ("IFIS-Identnummer") for the subject in the Pressemappe 20. Jahrhundert of the German Pressearchiv 20. Jahrhundert
Represents 20th century press archives (Q36948990)
Data type External identifier
Domain topics, events, persons, companies and goods
Allowed values \d+
Example Werner Heisenberg (Q40904) → 007478
Source http://webopac0.hwwa.de/PresseMappe20/
External links Use in sister projects: [de][en][es][fr][it][ja][ko][nl][pl][pt][ru][sv][vi][zh][Wd][Ws].
Formatter URL http://webopac.hwwa.de/Digiview/DigiView_PND.cfm?IFIS=$1
Robot and gadget jobs Mapping from GND ID (P227) would be possible at least for company entries via http://webopac0.hwwa.de/PresseMappe20/tabelle/HTM_FIRMSIGNA.cfm or http://webopac.hwwa.de/digiview/DigiView_GKD.cfm?GKD=$1 or http://webopac.hwwa.de/digiview/DigiView_PND.cfm?PND=$1 or are already known as to be seen in this example page: http://zbw.eu/beta/p20/person/7478/about.de.html (found here: http://zbw.eu/labs/de/taxonomy/term/51)
Motivation

Extensive archive of (German-language) press articles mostly from the 20th century (the offline version of the archive contains 20 millions of them, though most are not yet digitized). In dewiki, only a few entries are linked via de:Vorlage:Pressemappe, but the general usefulness of the archive has been discussed, so it sure would be a nice addition to Wikidata, too. Having the specific IDs (IFIS-Identnummern) is not strictly required, as a mapping for most (if not all?) entries to the GND exists (see above, robots jobs section; this is also the way they are linked in the said template), but obviouly the curators of the archive don't want to rely solely on that themselves. --YMS (talk) 11:33, 29 August 2017 (UTC)

@YMS: Are these IDs always six digits long? Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 06:38, 5 September 2017 (UTC)
[4] only explains that they are unique and persistent. Actually, the example given on this page has only two digits (10), but if you click that link, it will be displayed on the page as 000010 nonetheless. That was true for all examples that I checked, but I can't guarantee that it's always true. And when checking this, I saw that th entries in the "Sacharchiv" do have two different IFIS umbers (e.g. "IFIS-Geo: 141595; IFIS-Sach: 145941"), and for none of them there's a link offered. --YMS (talk) 07:00, 5 September 2017 (UTC)
Discussion
  • Symbol strong support vote.svg Strong support The clippings and other material in the tens of thousands of folders of the 20th century press archives are a comprensive subject-specific collection of the international press throughout the 20th century. The Pressemappe20 application is mostly in German, with a few hints in English. The folders themselves however contain material not only in German language, but from more than 1000 different newspapers from all over the world. (For example, take a look into the dossier about Gandhi, or search for companies located in London (search box "Name/Ort").)
    Disclaimer: I am the developer of the above mentioned linked open data (Q18692990) showcase application http://zbw.eu/beta/p20 (which is, btw, now outdated re. the completeness of the published material). That was part of my work for the ZBW German National Library of Economics (Q28737664). Jneubert (talk) 10:59, 31 August 2017 (UTC)
    • I have pinged my colleague, who is in charge of the PresseMappe20 application. In regard to URLs, the current situation will probably be improved in the next future. So the technical implementation of the proposal should wait for that. Jneubert (talk) 11:07, 31 August 2017 (UTC)
  • Symbol support vote.svg Support ArthurPSmith (talk) 15:01, 4 September 2017 (UTC)
  • Symbol support vote.svg Support. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 06:38, 5 September 2017 (UTC)

Just a quick heads-up: I've put the proposal on hold, since my colleague is currently re-working the URLs. They will be based on Persistent Uniform Resource Locator (Q195305) and are intended to address a single folder of the person, corporation, wares or topic archives. (Later on, persistent URLs for single documents within the folders or for lists of folders may follow, which would probably require separate properties.) The implementation will take several more weeks. Jneubert (talk) 15:04, 13 September 2017 (UTC)

sports.ru ID[edit]

   Under discussion
Description Player code on the site sports.ru
Data type External identifier
Example Ruslan Abazov (Q4054222)69957905
Source https://www.sports.ru/
Formatter URL https://www.sports.ru/tags/$1
Motivation

(Добавьте свою мотивацию по этому свойству сюда) AleUst (talk) 09:18, 13 August 2017 (UTC)

Discussion

Sportbox.ru ID[edit]

   Under discussion
Description Player code on the site sportbox.ru
Data type External identifier
Example Ruslan Abazov (Q4054222)Ruslan-Aslanovich-Abazov-Futbol-25051993
Source http://news.sportbox.ru/
Formatter URL http://news.sportbox.ru/Vidy_sporta/Futbol/$1
Motivation

(Добавьте свою мотивацию по этому свойству сюда) AleUst (talk) 09:11, 13 August 2017 (UTC)

Discussion

rfpl.org ID[edit]

   Under discussion
Description Player code on the site rfpl.org
Data type External identifier
Example Ruslan Abazov (Q4054222)Abazov-Ruslan
Source http://rfpl.org
Formatter URL http://rfpl.org/players/$1
Motivation

(Добавьте свою мотивацию по этому свойству сюда) AleUst (talk) 08:44, 13 August 2017 (UTC)

Discussion

Kaitai Struct format gallery ID[edit]

   Under discussion
Description identifier in the global Kaitai Struct formats repository
Represents file format (Q235557)
Data type External identifier
Domain file formats
Allowed values ^[a-z][a-z0-9_]*$
Example Portable Network Graphics (Q178051)png
TrueType Font (Q751800)ttf
RAR (Q243303)rar
Source http://formats.kaitai.io/
https://github.com/kaitai-io/kaitai_struct_formats
Formatter URL http://formats.kaitai.io/$1/
See also File Format Wiki page ID (P3381)
PRONOM file format identifier (P2748)
Uniform Type Identifier (P3641)
LocFDD ID (P3266)
Motivation

Kaitai Struct format gallery is an effort to build a machine-readable repository of binary file format / network protocol specifications using .ksy specification files. Being fully machine-readable, these files can be used to:

  • generate human-readable documentation
  • visualize any given binary file in a certain format, showing which bytes store which values
  • generate libraries in multitude of target languages

In this regard, this resource is both useful as a human-readable reference for those who want to learn about particular implementation details of a certain file formats, or as a source of parsing libraries (licensed under free / open source licenses), ready to be incorporated into software that requires such parsing. There are ~90 file formats available already and it's growing with people contributing more and more formal file format specs.

KS repository uses simple identifiers for all format names that are compatible with majority of programming languages as class names — first character is always a lowercase Latin letter, then a mixture of lowercase Latin letters, ASCII numbers and underscores are allowed.

(Disclosure: I'm one of Kaitai Struct developers). --GreyCat (talk) 18:32, 5 September 2017 (UTC)

Discussion
  • Pictogram voting comment.svg Comment described at URL (P973) is already being used to link from instance of (P31) file format (Q235557) to Kaitai Struct YAML files in the Git master repository. The Formats Gallery also adds a block diagram of the structure of the file format, as well as parser source code in various languages. Instead of creating a new property just for the KS gallery, perhaps image (P18) could be used to link to the block diagram image directly? For the parser source code, the existing described at URL (P973) to the Kaitai Struct YAML files arguably describe the file format more succinctly than derived parser source code. Dhx1 (talk) 12:54, 7 September 2017 (UTC)
    • Pictogram voting comment.svg Comment I won't actually recommend linking to raw GitHub exports URLs at all, there is no guarantee that GitHub would:
  1. continue to provide them with exactly the same functionality and URL scheme,
  2. still host Kaitai project in some time in future
On the other hand, a distinct domain link (i.e. formats.kaitai.io) seems to be much more stable.
However, what's even more important, is that this set of format specs is frequently supposed to be working together (i.e. one format could require other(s)); if you just link to that single format *and* it will require some other format to compile, then this whole linking is pointless — you can't compile it, you can't find relevant dependencies (you'll have to resort to Googling them manually), you basically can't use it. My main point of separate property proposal is that this is not just a way to link to some code, but it *is an identifier*. Besides that "one format uses other" scenario, this identifier might be useful per se — for example, this repository of FLOSS-licensed format specs is used (and distributed along) with several other projects, and all of them would accept "png" as an identifier of a PNG. It is not that much important to have a link to formats.kaitai.io (although, in my opinion, it would certainly help), than to just store the identifier. --GreyCat (talk) 14:39, 9 September 2017 (UTC)

LfD-HB object ID[edit]

   Ready Create
Description identifier for cultural heritage monuments in Bremen (state) (Q1209), issued by the Bremen State Office for the Preservation of Monuments
Data type External identifier
Domain Protected cultural heritage monument in Bremen (state) (Q31948690)
Allowed values ^\d{4}$|^\d{4},T$|^\d{4},T\d{3}$
Example Town Hall of Bremen (Q19479) → 0066,T001
Source de:Liste der Kulturdenkmäler in der Freien Hansestadt Bremen, LfD Bremen, Denkmal digital
External links Use in sister projects: [de][en][es][fr][it][ja][ko][nl][pl][pt][ru][sv][vi][zh][Wd][Ws].
Planned use First add the ID to the existing items with Protected cultural heritage monument in Bremen (state) (Q31948690), later register the rest (~1500 objects).
Formatter URL http://denkmalpflege.bremen.de/sixcms/detail.php?template=20_denkmal_wrapper_d&obj=0000$1
See also LfDS object ID (P1708), DSH object ID (P1822), Berlin cultural heritage ID (P2424) ...
Motivation

Bremen (state) (Q1209) is one of the 16 German states and needs it's own property like LfDS object ID (P1708), DSH object ID (P1822), Berlin cultural heritage ID (P2424) ... Quarz (talk) 11:55, 6 September 2017 (UTC)

Discussion
  • Symbol support vote.svg Support. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 13:35, 13 September 2017 (UTC)
  • Pictogram voting comment.svg Comment @Quarz: it looks like the id for the example should be 00000066,T001 (that's what's displayed on the page when applying the above formatter URL - so the formatter URL also should be shortened to remove the 0000 before the $1). ArthurPSmith (talk) 13:38, 13 September 2017 (UTC)
Sorry, I don't think so. We handle this id for Bremen (state) in exact the proposed way in the German Wikipedia and on Commons - please see this template and that too. No benefit to handle it different on Wikidata, I think. --Quarz (talk) 14:23, 13 September 2017 (UTC) Better add a ping: @ArthurPSmith:--Quarz (talk) 14:28, 13 September 2017 (UTC)

Heritage Building in Finland ID[edit]

Description identifier of a Finnish heritage building in the National register for protected buildings
Data type External identifier
Domain Q41176
Allowed values \d{6}
Example Guard Manege (Q11868816)200047
External links Use in sister projects: [de][en][es][fr][it][ja][ko][nl][pl][pt][ru][sv][vi][zh][Wd][Ws].
Planned use WLM and further import of building data
Formatter URL https://www.kyppi.fi/to.aspx?id=130.$1
Motivation

To use for denoting Finnish heritage buildings in the National register for protected buildings. Susanna Ånäs (Susannaanas) (talk) 11:14, 7 September 2017 (UTC)

Discussion

✓ Done @Susannaanas, Pigsonthewing, YULdigitalpreservation: enjoy! --99of9 (talk) 12:57, 20 September 2017 (UTC)

Figshare author ID[edit]

Description identifier for an author, on Figshare
Data type External identifier
Domain humans (possibly organisations)
Example Kevin Dolby (Q38915079)100383
Source https://figshare.com/
External links Use in sister projects: [de][en][es][fr][it][ja][ko][nl][pl][pt][ru][sv][vi][zh][Wd][Ws].
Formatter URL https://figshare.com/authors/_/$1
Motivation

User name for accounts on the data sharing platform Figshare (Q17013516). Figshare allows users to verify their ORCID iD (P496), and to enter their Twitter and Facebook user names, so will be useful for verifying such identities. It also lists co-authors. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 19:46, 7 September 2017 (UTC)

Discussion

✓ Done @Pigsonthewing, ArthurPSmith, Pintoch, LydiaPintscher: created as Figshare author ID (P4232) --99of9 (talk) 11:36, 20 September 2017 (UTC)

Bavarian monument authority ID[edit]

   Ready Create
Description identifier for cultural heritage monuments (ensembles, buildings and grounds) in Bavaria, issued by the Bavarian State Office for the Preservation of Monuments
Data type External identifier
Template parameter BLfD-ID
Domain Bau- und Bodendenkmale in Bayern
Allowed values D-7-78-173-1, D-7-78-173-2 etc
Example no label (Q19631467) → D-7-78-173-2
Source de:Kategorie:Liste_(Baudenkmäler_in_Bayern), Bayerisches Landesamt für Denkmalpflege
Planned use Ergänzung der Artikel zu Baudenkmälern, mittelfristig Anlage aller >110.000 bayerischen Denkmal-IDs, ggf. im ersten Schritt nur die, für die bereits Bilder in Commons hochgeladen und kategorisiert sind
Robot and gadget jobs Ein Listenabgleich mit dem Bestand des BLfD und den Denkmallisten in Wikipedia soll per Bot durchgeführt werden, Deltas müssen aufgrund der unzreichenden Datenqualität von Hand abgeglichen werden.
Motivation

Aktuell gibt es Denkmalartikel, Denkmallisten und Denkmalbilder, die alle voneinander getrennt gepflegt werden. Ordercrazy (talk) 16:36, 9 September 2017 (UTC)

(from translation of de description): currently referenced on Wikipedia in all Bavarian architectural monuments. Analogous to the Hessian denkXweb denkXweb (Q19411765). The BLFD is here: Bavarian monuments list (Q812203) and so should also have an ID property. ArthurPSmith (talk) 15:08, 11 September 2017 (UTC)

Discussion

Sinnvolle Idee um alle bayerischen Denkmäler strukturiert und eindeutig zu erfassen. -Mogadir (talk) 13:36, 10 September 2017 (UTC)

+1 Es würde auch die Listenerstellung und Pflege erleichtern. --Derzno (talk) 09:59, 11 September 2017 (UTC)
Es gibt allerdings auch das Problem das auf deWiki von einer Denkmalnummer Einzelbauteile bei uns in den Listen getrennt geführt werden. (Ist aus irgentwelchen Gründen so gewünscht) Dann wäre eine direkte Zuordnung Liste(Teilbereich) auf Bild(Teilbereich) über Wikidata genauso wichtig wie die Zuordung über die DenkmalID. Agathoclea (talk) 10:57, 11 September 2017 (UTC)
Eine 1:1-Beziehung wird sich nicht Herstellen lassen, speziell bei Grossdenkmälern oder Ensembles. Es wird auf eine N:N:N-Beziehung hinauslaufen (müssen). Beispiel: Stadtmauer Kempten: 1x Wikipedia-Artikel: de:Stadtbefestigung in Kempten (Allgäu), 4xBLfD-Id, siehe de:Liste der Baudenkmäler in Kempten (Allgäu). 1x commons-kategorie commons:Category:Stadtmauer_(Kempten) mit vielen Bildern, wie wiederrum einzelnen BLfD-IDs zugeordnet sind. Wichtig ist aus meiner Sicht, dass wir die BLfD-IDs überhaupt als Gründgerüst in Wikidata haben, weil nur so ein halbwegs geordneter Abgleich von Änderungen im Bestand des BLfD möglich ist. Wie die Zuordnung zu WP, Listen, Bildern und Commonscategorien konkret aussehen kann, weiss ich derzeit nicht, ich bin auch sehr dagegen, dem Property ein Sub-Property zuzuordnen. Aus meiner Sicht sollte einzig die bestehende BLfD-ID ausschlaggebend für den Wikidata-Eintrag sein - alles andere kann aus meiner Sicht über einen eigenen Artikel oder Wikidata-Eintrag, dem das entsprechende BLfD-ID-Property anhängt abgefangen werden. --Ordercrazy (talk) 12:47, 11 September 2017 (UTC)

Frage: Es gibt in fast allen bayerischen Denkmallisten "ehemalige Baudenkmäler" mit IDs, die nicht mehr in der Denkmaliste verzeichnet sind. Ich habe keine Ahnung, wie wir mit diesen Objekten, die auch beim BLfD nicht mehr abrufbar sind, umgehen sollen. Der allgemeine Konsens bei de-wiki ist, dass wir diese "ehemaligen" Baudenkmäler mit BLfD-ID (die soweit ich weiss vom BLfD nicht neu vergeben wird, also uniq bleibt!) in den Listen erhalten wollen. Gibt es eine Möglichkeit, das in Wikidata abzubilden? Brauchen wir dafür ein zweites, oder ein Sub-Property oder ignorieren wir das einfach und pflegen diese Information nur in den Listen der Baudenkmäler bei Wikipedia und lösen die Propertyzuordnung in Wikidata, wenn die Denkmaleigenschaft eines Objekts entfällt bzw. das Objekt angeht? - Kurz: Müssen wir das bei der Property-Erstellung berücksichten oder gehen wir wie eben vorgeschlagen vor? --Ordercrazy (talk) 06:41, 12 September 2017 (UTC)

  • @Ordercrazy: (responding in English) I think we can proceed as proposed here, there is no need for an additional property. It is not unusual to have an ID for an entity that no longer exists in one way or another; it is useful to preserve that identifier if we have evidence it did represent that former entity, even if it's no longer resolvable. The wikidata item for such an entity probably should indicate via a separate statement (for example dissolved, abolished or demolished (P576)) that it no longer exists. ArthurPSmith (talk) 17:50, 12 September 2017 (UTC)

Symbol support vote.svg Support. Makes sence. Conny (talk) 15:08, 21 September 2017 (UTC).

The Black Book ID[edit]

   Ready Create
Description ID for a person wanted by the Nazi administration, in the case of an invasion of the United Kingdom, as listed in the "Black Book" ("Sonderfahndungsliste GB")
Data type External identifier
Domain humans alive during (or immediately before) World War II
Example Alfred Scharf (Q23301730)141
Source https://www.forces-war-records.co.uk/hitlers-black-book/
External links Use in sister projects: [de][en][es][fr][it][ja][ko][nl][pl][pt][ru][sv][vi][zh][Wd][Ws].
Formatter URL https://www.forces-war-records.co.uk/hitlers-black-book/person/$1
Motivation

People listed in The Black Book (Q2224789), as held at Imperial War Museum London (Q749808). The book includes "2820 names of Politicians, writers, emigrees, known intelligence agents, scientists and artists was drawn up by SS General Walter Schellenbergs office". Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 19:36, 10 September 2017 (UTC)

Discussion
  • Symbol support vote.svg Support Jneubert (talk) 16:16, 13 September 2017 (UTC)
  • Symbol support vote.svg Support. YULdigitalpreservation (talk) 12:47, 20 September 2017 (UTC)
  • I've modified the example and the formatter URL because the name part is unnecessary, the id numbers resolve to the right page. --99of9 (talk) 11:35, 21 September 2017 (UTC)

PubsHistory pub ID[edit]

   Ready Create
Description identifier for a public house in the United Kingdom, as used by the 'I Am Pub History' website
Data type External identifier
Domain public houses in the United Kingdom
Example Red Lion (Q17533815)Warwickshire/BirminghamR/RedLionSoho
Source https://pubshistory.com/
External links Use in sister projects: [de][en][es][fr][it][ja][ko][nl][pl][pt][ru][sv][vi][zh][Wd][Ws].
Formatter URL https://pubshistory.com/$1.shtml
Motivation

Database of pubs, many listed buildings (and hence already in Wikidata), with useful information on past licensees - often seemingly the only online source of such information. Given the long IDs, I would not be averse to storing these as URLs. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 10:47, 11 September 2017 (UTC)

Discussion

YouTube Playlist ID[edit]

   Ready Create
Description identifier for a playlist (official) on YouTube containing videos for this item
Represents playlist (Q1569406)
Data type External identifier
Domain creative work (Q17537576)
Example
Source YouTube (Q866)
Formatter URL https://www.youtube.com/playlist?list=$1
See also YouTube video ID (P1651) & YouTube channel ID (P2397)
Motivation

Useful for all movies and series and others ديفيد عادل وهبة خليل 2 (talk) 16:25, 12 September 2017 (UTC)

Discussion

Vincoli in Rete ID[edit]

   Ready Create
Description identifier of a building or site in the database of the MIBACT (Ministero per i Beni, le Attività Culturali e il Turismo) concerning regulatory constraints on cultural heritage in Italy
Data type External identifier
Domain cultural heritage items in Italy
Allowed values [1-9][\d]{0,5}
Example Basilica di San Giovanni Battista (Q2887005)318021
Source http://vincoliinrete.beniculturali.it
External links Use in sister projects: [de][en][es][fr][it][ja][ko][nl][pl][pt][ru][sv][vi][zh][Wd][Ws].
Formatter URL http://vincoliinrete.beniculturali.it/VincoliInRete/vir/bene/dettagliobene$1
Motivation

"allowed units" parameter in the proposal is blank: it should be a number of 1 to 6 digits. Can someone complete it? The MIBACT database is useful: there are informations about buildings and other monuments in Italy (such as dimensions, owner, kind of building, period of construction, etc.) --Yiyi .... (talk!) 13:21, 13 September 2017 (UTC)

That should be |allowed values=, which I have fixed. |allowed units= is optional, and is for things like "metres" in measurements. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 13:32, 13 September 2017 (UTC)
Thank you! --Yiyi .... (talk!) 13:34, 13 September 2017 (UTC)
Discussion

Digitised page from Lloyd's Register of Ships from 1930 to 1945[edit]

   Under discussion
Description Digitised page from Lloyd's Register of Ships from 1930 to 1945
Data type External identifier
Domain Wikidata property related to maritime and inland waterway transport (Q23779665)
Allowed values \d{2}\w\d{4}
Example SS Chelyuskin (Q572950)33b0998
Source http://www.plimsollshipdata.org/
External links Use in sister projects: [de][en][es][fr][it][ja][ko][nl][pl][pt][ru][sv][vi][zh][Wd][Ws].
Planned use Link to the digitised page (!) on plimsollshipdata.org for items which are instance of (P31) ship (Q11446)
Formatter URL http://www.plimsollshipdata.org/pdffile.php?name=$1.pdf

Pictogram voting info.svg Info: Wikidata:Property proposal/Lloyd's Register of Ships

Motivation

Separate proposal for the digitised pages of Lloyd's Register of Ships from 1930 to 1945 in order to link items to this database of digitised pages, which are not parseable for the bijective ship ID. --Ptolusque (talk) 20:26, 13 September 2017 (UTC)

Discussion
  • Symbol support vote.svg Support. I suggest this property be used in references only, for example instance of (P31) or other properties of a ship. Dhx1 (talk) 23:06, 13 September 2017 (UTC)

Lloyd's Register Ship ID[edit]

   Ready Create
Description Ship ID in Lloyd's Register of Ships
Data type External identifier
Domain Wikidata property related to maritime and inland waterway transport (Q23779665)
Allowed values [1-9]\d*
Example SS Chelyuskin (Q572950) → 39034
Source http://www.lrfoundation.org.uk/public_education/reference-library/register-of-ships-online/
Planned use ship ID for items which are instance of (P31) ship (Q11446)
See also Wikidata:Property proposal/Plimsoll ShipData Lloyd's Register of Ships Scanned Page ID for a separate linkable property proposal (due to the fact that the digitised pages aren't parseable, nor subject to a meta database assigning the ship ID to the digitised page ID)

Pictogram voting info.svg Info: Wikidata:Property proposal/Lloyd's Register of Ships

Motivation

Separate proposal for the the actual ship ID, which can not be linked using formatter URL (P1630) due to the reason stated above. Ptolusque (talk) 20:48, 13 September 2017 (UTC)

Discussion
  • Symbol support vote.svg Support. I changed the source and description to consider the register for years outside the period of 1930-1945. Dhx1 (talk) 23:04, 13 September 2017 (UTC)
    • You are right. In this case it's not limited to a specific timeframe anymore. --Ptolusque (.-- .. -.- ..) 01:04, 14 September 2017 (UTC)
  • Symbol support vote.svg Support ArthurPSmith (talk) 19:44, 14 September 2017 (UTC)

musée de Bretagne identifiant collections ID[edit]

   Under discussion
Description identifier for an object in the collection of the Brittany Museum, France
Data type External identifier
Domain work (Q386724)
Allowed values letters and numbers (regex to be refined)
Example
External links Use in sister projects: [de][en][es][fr][it][ja][ko][nl][pl][pt][ru][sv][vi][zh][Wd][Ws].
Formatter URL http://www.collections.musee-bretagne.fr/ark:/83011/$1
Robot and gadget jobs there is contact with the museum for harvesting this website
Motivation

VIGNERON (talk)
Mathieudu68 (talk)
Tpt (talk) (si besoin d'aide technique)
Ayack (talk) (surtout pour les MH)
Aga
Ash Crow (talk)
Tubezlob (talk)
PAC2 (talk)
Thierry Caro (talk)
Pymouss (talk)
Pintoch (talk)
Alphos (talk)
Nomen ad hoc (talk)
Framawiki (talk)
GAllegre (talk)
Pictogram voting comment.svg Notified participants of WikiProject France

Propriété pour lier vers le site des collections du musée de Bretagne. L'identifiant fonctionne suivant le principe du Archival Resource Key (Q2860403). VIGNERON (talk) 12:50, 16 September 2017 (UTC)

Discussion
  • Symbol support vote.svg SupportAyack (talk) 12:56, 16 September 2017 (UTC)
  • Symbol support vote.svg Support --Pymouss (talk) 12:59, 16 September 2017 (UTC)
  • Symbol support vote.svg SupportEnvlh (talk) 13:01, 16 September 2017 (UTC)
  • Symbol support vote.svg Support --Framawiki (please notify !) (talk) Sorry for my bad English :) 17:15, 16 September 2017 (UTC)
  • Comment: Why not catalog code (P528) / catalog (P972)? Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 18:58, 16 September 2017 (UTC)
  • Symbol oppose vote.svg Oppose I prefer to have all museum/collection identifiers modelled with inventory number (P217) and collection (P195). Using for some museums a specific property and for other museums a generic property makes querying extremly hard. --Pasleim (talk) 19:37, 28 July 2017 (UTC)
    • Pasleim globally I agree but did you see what I just wrote above? We already use inventory number (P217) and collection (P195) for these objects, this identifier is not the same thing and is in addition to the inventory number. I don't really see how we can use a general property here. Cdlt, VIGNERON (talk) 07:11, 17 September 2017 (UTC)
  • Symbol support vote.svg Support - I came here from a facebook discussion - this museum shares their metadata CC-0 and it looks like it has pretty good long catalog entries from what I can tell, with several detail images clickable from the entry. These are good enough for a separate property because many of these important historical items are not described anywhere else than in Rennes. See e.g. a painting Le Maire de Rennes (Q17393199) and a coin coin of Anne of Brittany (Q17280208) where I put the url in described at URL (P973) for now. Jane023 (talk) 12:15, 17 September 2017 (UTC)
  • Symbol support vote.svg Support. I support the creation of this property. YULdigitalpreservation (talk) 16:43, 18 September 2017 (UTC)
  • Symbol support vote.svg Support arguments below/ci-après ~ Seb35 [^_^] 13:19, 19 September 2017 (UTC)
    English: Additionally I see some short-term arguments to create a property in the section "Identifiers" (versus using a generic property using a qualifier): 1. as of now it’s easier to link to the external website with the current Wikibase software, and 2. easier to use in SPARQL requests; and some long-term arguments: 3. ARKs are just identifiers for the URL, with a common naming schema but it’s not really different compared to other external identifiers, 4. ARKs are stable identifiers managed by some preservation institutions, hence I find it more logical to place them in the section "Identifiers" in order to link to the external website instead of the section "Statements" which can be better used to describe the concept itself.
    français : De plus je vois quelques arguments à court terme pour créer une propriété dans la section "Identifiants" (versus utiliser une propriété générique en utilisant un qualifieur) : 1. pour l’instant c’est plus facile pour faire un lien vers un site web externe avec le logiciel Wikibase actuel, et 2. c’est plus facile à utiliser dans les requêtes SPARQL ; et quelques arguments à long terme : 3. les ARKs sont juste des identifiants pour une URL, avec un schéma de nommage commun mais ça n’est pas réllement différent des autres identifiants externes, 4. les ARKs sont des identifiants stables gérés par quelque institution de conservation, je trouve donc plus logique de les placer dans la section "Identifiants" pour faire un lien vers le site externe plutôt que dans la section "Déclarations" qui serait mieux utilisée pour décrire le concept lui-même.

Store norske leksikon ID[edit]

   Under discussion
Description identifier of an article in the online encyclopedia snl.no
Represents no label (Q30172599)
Data type External identifier
Template parameter Template:Store norske leksikon (Q13515287)
Domain any?
Allowed values string
Example
External links Use in sister projects: [de][en][es][fr][it][ja][ko][nl][pl][pt][ru][sv][vi][zh][Wd][Ws].
Formatter URL https://snl.no/$1
See also Great Russian Encyclopedia Online ID (P2924)
Motivation

Store norske leksikon (Q746368) is a Norvegian encyclopedia. Visite fortuitement prolongée (talk) 20:18, 16 September 2017 (UTC)

Discussion

Tagesschau election ID[edit]

   Under discussion
Description identifier of a parliamentary election in the elections archive on tagesschau.de
Data type External identifier
Domain legislative election (Q1076105)
Allowed values (19|20)(\d{2}-){3}(EP|BT|LT)-DE(-[B-Y]{2})?
Example
Source wahl.tagesschau.de
External links Use in sister projects: [de][en][es][fr][it][ja][ko][nl][pl][pt][ru][sv][vi][zh][Wd][Ws].
Formatter URL http://wahl.tagesschau.de/wahlen/$1/
Motivation

Election results and other data about all elections on EU, federal and state level in Germany since 1946 on the website of Germany's main public service news programme Tagesschau (Q703907). --Entbert (talk) 22:06, 16 September 2017 (UTC)

Discussion

Bavarian geotope ID[edit]

   Under discussion
Description identifier for geotopes in Bavaria (Germany), issued by the Bayerisches Landesamt für Umwelt
Represents Bavarian State Office for the Environment (Q812422)
Data type External identifier
Template parameter Geotop-BY-ID (which template?)
Domain geotope (Q372363) in Bavaria (Q980)
Allowed values \d{3}[A-Z]\d{3}
Example Alfelder Windloch (Q14544537)574H005
Source https://www.lfu.bayern.de/geologie/geotope_daten/geotoprecherche/index.htm
External links Use in sister projects: [de][en][es][fr][it][ja][ko][nl][pl][pt][ru][sv][vi][zh][Wd][Ws].
Planned use The usage of this ID is already implemented to all Bavarian Geotopes-lists (nearly 2.500 records) and reference in articles of the German Wikipedia. An import is planned.
Formatter URL https://www.lfu.bayern.de/gdi/dokumente/geologie/geologieerleben/geotop_pdf/$1.pdf
See also WDPA id (P809)
Motivation

Eindeutige Zuordnung eines geologischen Objektes in umfangreichen Listen, Artikeln und Commons Kategorien.

Unique assignment of geological objects in huge lists, articles and commons categories.

Derzno (talk) 11:17, 18 September 2017 (UTC)

Discussion
  • Pictogram voting comment.svg Comment is 2500 the number of id's, or are there more? ArthurPSmith (talk) 17:49, 18 September 2017 (UTC)
    • @ArthurPSmith:, currently I’d applied approximately 2.500 Bavarian Geotopes in many lists. According official point of view it’ll be more as 3.600. As written above, my long term plan would be to import all of these objects into WD to make the maintenance simple as possible and for avoiding redundant with misleading information. --Derzno (talk) 03:55, 19 September 2017 (UTC)
  • Symbol support vote.svg Support --Ptolusque (.-- .. -.- ..) 22:32, 18 September 2017 (UTC)
  • Symbol support vote.svg Support --Cavaliere grande (talk) 06:18, 19 September 2017 (UTC)
  • Symbol support vote.svg Support I'd prefer a separate property each of the german countries (as advertised above by Derzno) since every country has its own ID-Format and it's own website for geotop-descriptions. --Ordercrazy (talk) 10:09, 19 September 2017 (UTC)
  • Symbol support vote.svg Support --Foreign Species (talk) 12:57, 19 September 2017 (UTC)
  • Symbol support vote.svg SupportMisterSynergy (talk) 13:06, 19 September 2017 (UTC)
  • Symbol support vote.svg Support Jneubert (talk) 14:05, 19 September 2017 (UTC)
  • Symbol support vote.svg Support@Derzno: don't forget that there are a lot of geotopes (Bavaria...) within one nummer, but on a lot of sites? Before working, this problem must be cleared? --Rikiwiki2 (talk) 15:58, 19 September 2017 (UTC)
  • Symbol support vote.svg Support. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 19:18, 19 September 2017 (UTC)
  • Symbol support vote.svg Support. --Blech (talk) 21:45, 20 September 2017 (UTC)

Riigikogu ID[edit]

   Under discussion
Description identifier for a member of the Estonian Parliament
Represents member of the Estonian Riigikogu (Q21100241)
Data type External identifier
Domain human
Allowed values [0-9a-f]{8}-([0-9a-f]{4}-){3}[0-9a-f]{12}
Example Taavi Rõivas (Q3785077)47201a8e-4ae7-45fa-8659-b47930d6f99c
Source https://www.riigikogu.ee
External links Use in sister projects: [de][en][es][fr][it][ja][ko][nl][pl][pt][ru][sv][vi][zh][Wd][Ws].
Planned use Linking all members of the Riigikogu
Formatter URL https://www.riigikogu.ee/riigikogu/koosseis/riigikogu-liikmed/saadik/$1
Motivation

Authority control for Estonian parliamentarians, in the same manner as with other countries. All current members are pre-matched and can be added using QuickStatements. --Oravrattas (talk) 16:54, 18 September 2017 (UTC)

Discussion
  • @Oravrattas: I suppose the identifier in your example is "47201a8e-4ae7-45fa-8659-b47930d6f99c" - right? Could you perhaps edit the proposal to make that more clear? Jneubert (talk) 14:10, 19 September 2017 (UTC)
    • @Jneubert: oops, yes, sorry — I used the full URL rather than the ID by mistake. Corrected now. --Oravrattas (talk) 14:59, 19 September 2017 (UTC)
  • Symbol support vote.svg Support. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 19:22, 19 September 2017 (UTC)
  • Symbol support vote.svg Support Jneubert (talk) 06:38, 20 September 2017 (UTC)
  • Symbol support vote.svg Support --Entbert (talk) 22:44, 20 September 2017 (UTC)

DPLA subject ID[edit]

   Under discussion
Description identifier for a subject area in the Digital Public Library of America
Data type External identifier
Domain Digital Public Library of America (Q2944483)
Allowed values [^\s\/]+
Example
Source https://dp.la/subjects
External links Use in sister projects: [de][en][es][fr][it][ja][ko][nl][pl][pt][ru][sv][vi][zh][Wd][Ws].
Formatter URL https://dp.la/search?subject%5B%5D=$1
Motivation

This would be used for subject areas, as a complement to DPLA ID (P760), which is used for individual items in the collections. Pharos (talk) 21:00, 19 September 2017 (UTC)

Discussion

YouTube playlist ID[edit]

   Under discussion
Description identifier of a notable video playlist on YouTube
Data type External identifier
Allowed values [A-Za-z0-9_\-]+
Example Fantastic Beasts and Where to Find Them (soundtrack) (Q27888384)PLBKadB95sF46S0OjNmQr0GeXMXZ-Byso3
Source www.youtube.com
External links Use in sister projects: [de][en][es][fr][it][ja][ko][nl][pl][pt][ru][sv][vi][zh][Wd][Ws].
Planned use Add Playlist to items which are instance of (P31) album (Q482994)
Formatter URL https://www.youtube.com/playlist?list=$1
Motivation

I found several articles on de and en Wikipedia referring to playlists on YouTube, e.g. using en:Template:YouTube#Playlist and de:Template:YouTube#YouTube-Playlists. By now, using YouTube channel ID (P2397) and YouTube video ID (P1651), it's only possible to refer to either single videos or channels with the respective id but not to playlists. Ptolusque (.-- .. -.- ..) 02:00, 20 September 2017 (UTC)

Discussion
Pictogram voting comment.svg Comment seems to be a similar proposal of Wikidata:Property proposal/Youtube Playlist ID --Pasleim (talk) 16:32, 20 September 2017 (UTC)
@Pasleim: You're right. Never thought there'd be another proposal. That's due to the huge backlog on property proposals. Otherwise I UTFSE. Shall we delete this one? --Ptolusque (.-- .. -.- ..) 19:21, 20 September 2017 (UTC)
you can mark this proposal as "withdrawn" (enter that in the status field). On the "backlog" - the full list of property proposals still under consideration together with their length of time in process is available here - most of them are waiting on sufficient supporting votes or other discussion to be "ready" for creation. To see those which have been established as ready, see this list. I see 21 at the moment. These are usually dealt with by one of the property creators (created) within a week, unless there is some concern arising from the discussion or something missed. Before proposing properties you should really do a full search of "everything", as all previous property proposals, whether approved or not, are retained. ArthurPSmith (talk) 16:51, 21 September 2017 (UTC)

Japanese Database of National important cultural properties ID[edit]

   Under discussion
Description identifier of a site in the Japanese Database of National important cultural properties
Data type External identifier
Domain Buildings in Japan
Allowed values [1-9]\d*
Example ?? → 95
Source http://kunishitei.bunka.go.jp/bsys/index_pc.html
External links Use in sister projects: [de][en][es][fr][it][ja][ko][nl][pl][pt][ru][sv][vi][zh][Wd][Ws].
Planned use Import all items from the database into Wikidata and the ID numbers
Formatter URL http://kunishitei.bunka.go.jp/bsys/maindetails.asp?register_id=401&item_id=$1

Note: The English name of the register is taken from here

Motivation

To index build Japanese cultural heritage on Wikidata, we are importing the data as part of the Connected Open Heritage project. John Cummings (talk) 08:12, 21 September 2017 (UTC)

Discussion

Reddit user name[edit]

   Under discussion
Description user name on the social news website Reddit
Data type External identifier
Domain people
Example
Source https://www.reddit.com/
External links Use in sister projects: [de][en][es][fr][it][ja][ko][nl][pl][pt][ru][sv][vi][zh][Wd][Ws].
Formatter URL https://www.reddit.com/user/$1
See also
Motivation

Although they are currently under-represented in Wikidata, many notable people have accounts on Reddit (Q1136), and a good number of them have undertaken Reddit's "IAmA" process. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 13:51, 21 September 2017 (UTC)

Discussion

WBPLN author ID[edit]

   Under discussion
Description This is an identifier for the authors listed in the West Bengal Public Library Network, which is a central digital repository of books in the Indian state of West Bengal. The books are mostly in Bengali and English, published in India and abroad, scanned and uploaded by libraries from West Bengal. This repository is initiated with the assistance of Mass Education Extension and Library Services Department, Government of West Bengal and Center for Development of Advanced Computing, under the Ministry of Information & Technology , Government of India. I
Represents West Bengal Public Library Network (Q40567016)
Data type External identifier
Domain authority control
Allowed values name of the author in the form of text
Example Satyendranath Tagore (Q7426958)Tagore%2C+Satyendranath
Source http://dspace.wbpublibnet.gov.in:8080/jspui/browse?type=author
Formatter URL http://dspace.wbpublibnet.gov.in:8080/jspui/browse?type=author&order=ASC&rpp=20&value=$1
Motivation

This can be an external identifier for different Indian and non-Indian authors, especially the Bengali language authors. It will be helpful for Bengali and English Wikisource projects. Bodhisattwa (talk) 16:37, 21 September 2017 (UTC)

Discussion

How will you reconcile the above-said author id with http://dspace.wbpublibnet.gov.in:8080/jspui/handle/10689/183/browse?type=author&order=ASC&rpp=20&value=Thakur%2C+Satyendranath ? In that site, there is no standard system for spelling author names; so an author name can be spelled in multiple ways, each spelling listing different books. If the author edited some books, then the term ed. will be added to author name, thereby making a different spelling. For example, 1, 2, 3, 4, these four different IDs, as per your formula, denote the same author, but the books are different. Therefore, please suggest a standard way of formatting the id here for that site, instead of the sample given above. Hrishikes (talk) 17:32, 21 September 2017 (UTC)

IMHO, there is no other possible standard formatter url for this website. Of course, any spelling changes will create different urls, but that doesn't change the formatter url. Also, if there are multiple identifiers for the same author, we can use multiple values for the same identifier property, but not all authors have multiple identifiers here. Bodhisattwa (talk) 18:02, 21 September 2017 (UTC)
In that site, multiple spellings of author names is the norm rather than exception. It occurs when (1) the author has multiple books (first & middle names combined and separate; surnames in Bengali-style and Western style, like Thakur vs. Tagore, Chattopadhyay vs. Chatterjee etc.); (2) When the author has edited some books (author name + ed = new name); (3) When a book has multiple authors (name 1 + name 2 + name 3 ... = new name); (4) Plain spelling mistakes, which is also frequent. So most major authors would have multiple identifiers. I have never seen the display of multiple values for a given identifier in authority control (e.g. multiple values for VIAF or LCCN being displayed). This will be regularly required in this case. How do you propose to accomplish it? And will not such a display of variant author name spellings make the authority control look quite ugly? Hrishikes (talk) 01:12, 22 September 2017 (UTC)
@Hrishikes:da, multiple values for a given identifier is not at all uncommon in Wikidata. You can find multiple values for Open Library ID (P648), see Truby King (Q7847131) for example. It is beyond our reach to fix the multiple IDs for same author in WBPLN or Open Library or any other site, its the job of the website maintainers. IMHO, it is not about looking ugly or pretty, its about data linkage only. If it is required, then it has to be done. -- Bodhisattwa (talk) 06:57, 22 September 2017 (UTC)
@Bodhisattwa: But where is the display? The Open Library identifier is not at all displayed in the destination site (Wikipedia). As I said, I have never seen such a double display. Have you seen it? Moreover, reader comfort is essential. That's why so much time and energy is being spent for mobile phone display. If the display looks ugly, it won't lend itself to reader comfort. However, the display can be formatted like this: if the author has, say, 3 IDs, it may show up as WBPLN: 1, 2, 3; the numbers hyperlinked to specific urls. Hrishikes (talk) 07:43, 22 September 2017 (UTC)

Banglapedia ID[edit]

   Under discussion
Description Banglapedia is the online national encyclopedia of Bangladesh created by over 1450 scholars. The encyclopedia is the most comprehensive reference work on Bangladesh from high ancient period to date.
Represents Banglapedia (Q2642057)
Data type External identifier
Domain authority control
Allowed values name of the topic in the form of text
Example Rabindranath Tagore (Q7241)Tagore,_Rabindranath
Source http://en.banglapedia.org
Formatter URL http://en.banglapedia.org/index.php?title=$1
Motivation

This can be an external identifier for different topics related to Bangladesh and Bengal region in large. The encyclopedia serves as a good reference in Bengali Wikipedia already. The proposal if accepted, will make this ID the first external identifier Bangladesh specific topics. Also, the site is powered by Mediawiki, so, I assume, it would be easy to fetch the data and make it ready for Mix n Match. The list of all articles in this website is here -- Bodhisattwa (talk) 07:13, 22 September 2017 (UTC)

Discussion