Wikidata

Wikidata:Property proposal/Generic

< Wikidata:Property proposal
(Redirected from Wikidata:Property proposal/Property metadata)


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

See also

edit

This page is for the proposal of new properties.

Before proposing a property

  1. Search if the property already exists.
  2. Search if the property has already been proposed.
  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. Read Wikidata:Creating a property proposal for guidelines you should follow when proposing new property.
  6. Start writing the documentation based on the preload form below by editing the two templates at the top of the page to add proposal details.

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 creation of the proposal, by a property creator or an administrator.
  3. See property creation policy.

General

edit

L'Humanité topic ID

edit
   Under discussion
Descriptionidentifier for a topic on the L'Humanité website
RepresentsL'Humanité (Q1137404)
Data typeExternal identifier
Domainitem
Example 1French Communist Party (Q192821)→pcf
Example 2Dominique de Villepin (Q131660)→dominique-de-villepin
Example 32024 United States presidential election (Q101110072)→presidentielle-americaine-2024
Expected completenessalways incomplete (Q21873886)
Formatter URLhttps://www.humanite.fr/mot-cle/$1
See alsoL'Humanité journalist ID (P10569)
Wikidata projectWikiProject France (Q10816832)

Motivation

edit

Beauciup de "tag" réunissant tous les articles.  – The preceding unsigned comment was added by Legonin (talk • contribs) at 06:00, September 17, 2024‎ (UTC).

Discussion

edit

  Notified participants of WikiProject France  – The preceding unsigned comment was added by Legonin (talk • contribs) at 08:09, 21 September 2024 (UTC).[reply]

  Notified participants of WikiProject France - re-pinging, since the previous one was unsigned (and therefore didn't work). --Lewis Hulbert (talk) 09:53, 7 October 2024 (UTC)[reply]

‎beer style

edit
   Under discussion
Descriptionclassification of a beer based on its style
Representsbeer style (Q1998962)
Data typeItem
Domainbeer (Q44)
Allowed valuessubclasses or instances of beer style (Q1998962)
Example 1Hertog Jan Grand Prestige (Q2176488) → barley wine (Q808329)
Example 2Coors Light (Q5168060) → light beer (Q1814622)
Example 3Grolsch 0.0% (Q61043304) → low-alcohol beer (Q524679)
Example 4Brand IPA (Q19884261) → India Pale Ale (Q1543214)
See alsobeer bitterness (P6088), beer color (P6089)

Motivation

edit

Beer style is a key classification for differentiating beers by their characteristics, complementing existing properties like beer color and bitterness.  – The preceding unsigned comment was added by Mitsjol (talk • contribs) at 10:43, September 30, 2024‎ (UTC).

Discussion

edit

‎Department of Defense Identification Code

edit
   Ready Create
Descriptionidentification code for ordnance of the United States military
RepresentsDepartment of Defense Identification Code (Q130394184)
Data typeExternal identifier
Domainweapon model (Q15142894)
Allowed values([A-Z]\d{3}|[A-Z]{2}\d{s})
Example 1BLU-109B/B (Q130394989)→EC72
Example 2BLU-109C/B (Q130394999)→ED49
Example 3M718A1 (Q130411460)→D515
Example 4M741A1 (Q130411473)→D514
Sourcehttps://web.archive.org/web/20240930063511/https://www.quantico.marines.mil/portals/147/docs/safety/yellow%20book%20rev%2019%20dated%20february%202021.pdf
Planned useUniquely identify variants of models of American manufactured bomb, missile, rocket, small arms munitions, etc by DODIC and associated NSN and other labels supplied in the "Yellow Book".
Expected completenesseventually complete (Q21873974)
Applicable "stated in"-valueJoint Hazard Classification System (Q130394198)
Single-value constraintyes
Distinct-values constraintyes

Motivation

edit

Wikipedia and Wikidata have only very basic information on military ordnance (missiles, bombs, rockets, small arms munitions, tank and artillery rounds, etc) even though publications such as the Yellow Book and public NSN part information provides detail on exact variants of ordnance. For example, Wikipedia may have a page on a "Mk 82 bomb" but this is a highly conflated item which may include different variants of a bomb casing (with varying amounts of explosive) and with different guidance systems attached. Applying a DODIC code allows these variants to be listed out as separate Wikidata items, avoiding conflation of topics. --Dhx1 (talk) 06:29, 2 October 2024 (UTC)[reply]

Discussion

edit
  •   Comment If this is limited to ordnance, shouldn't ordnance be in the name of the property? AdamSeattle (talk) 04:04, 26 October 2024 (UTC)[reply]
      Comment "DODIC" is the official name of the identifier that people interested in this property would search for. It is unhelpfully non-descriptive as many military acronyms are. Rather than the name being clear in purpose, the description of the property (which Wikidata controls) makes clear what this identifier achieves. Dhx1 (talk) 22:49, 28 October 2024 (UTC)[reply]
  •   Comment Is the source pdf a complete list, if not how will other values be found? How many values are expected in total?
      Comment It's an ever expanding list. There is a database YellowBook.sqlite as part of a now-defunct Android app YellowBook v2.1.0 (APK still available online on non-official app stores) which lists 5288 DODIC codes per query "SELECT COUNT(*) FROM (SELECT DODIC FROM MunitionsHazardClass GROUP BY DODIC);". Future changes would have to be obtained through means such as being mentioned in official budget papers for Army, Air Force, Navy, Marines, etc for the type of ordnance budgeted to be procured, or a new app or new PDF publication. --Dhx1 (talk) 22:46, 28 October 2024 (UTC)[reply]
      Support proposer has a good plan. Vicarage (talk) 03:45, 29 October 2024 (UTC)[reply]

identifiant Les Inrockuptibles d'un sujet

edit
   Under discussion
Descriptionidentifiant d'un sujet sur le site Les Inrockuptibles (fr) – (Please translate this into English.)
RepresentsLes Inrockuptibles (Q2758142)
Data typeExternal identifier
Domainitem
Example 1Donald Trump (Q22686)→donald-trump
Example 2Netflix (Q907311)→netflix
Example 32024 Cannes Film Festival (Q119141934)→cannes-2024
Example 4Yelle (Q18574071)→yelle
Example 5Anatomy of a Fall (Q117037697)→anatomie-dune-chute
Example 6Emily in Paris (Q64584978)→emily-in-paris
Expected completenessalways incomplete (Q21873886)
Formatter URLhttp://www.lesinrocks.com/tag/$1
Wikidata projectWikiProject France (Q10816832)

Motivation

edit

Plein d'IDs et articles très intéressant. Pas mal de sujet/tags de journaux proposé et déjà sur Wikidata.  – The preceding unsigned comment was added by Legonin (talk • contribs) at 07:15, 16 October 2024 (UTC).[reply]

Discussion

edit

  Notified participants of WikiProject France  – The preceding unsigned comment was added by Legonin (talk • contribs) at 07:15, 16 October 2024 (UTC).[reply]

‎European Legislation Identifier (EU)

edit
   Under discussion
DescriptionEU legislation identifier for documents published by the EU
Data typeExternal identifier
Example 1directive on open data and the re-use of public sector information (Q98399993)→dir/2019/1024/oj
Example 2Capital Requirements Directive (Q1034661)→dir/2013/36/oj
Example 3Solvency II Directive (Q1255619)→dir/2009/138/oj
Source
Formatter URLhttp://data.europa.eu/eli/$1
Robot and gadget jobsImport from Eur-lex by So9qBot is planned for existing items.
Single-value constraintyes
Distinct-values constraintyes

Motivation

edit

This is an important identifier for EU legislation.--So9q (talk) 10:43, 18 October 2024 (UTC)[reply]

Discussion

edit
  Notified participants of WikiProject European Union, @Ainali, Belteshassar: Redoing the ping because it requires a signature after it. Samoasambia ✎ 14:33, 22 October 2024 (UTC)[reply]
  Weak oppose I'm not really sure why would we need this property because we already have CELEX number (P476) (it's the "32013L0036" ChristianKl mentioned) and full work available at URL (P953) where we could add the ELI URL. P953 is useful because it is used e.g. by Template:Cite Q (Q22321052). Samoasambia ✎ 14:33, 22 October 2024 (UTC)[reply]
European Legislation Identifier is basically a common URL and metadata format for laws in EU member states and the EU itself. Here's a few examples: http://data.finlex.fi/eli/sd/1734/4, http://data.europa.eu/eli/dir/2013/36/oj, https://www.legifrance.gouv.fr/eli/loi/2023/4/14/2023-270/jo/texte, https://www.retsinformation.dk/eli/lta/2014/1603. Some of the URLs are actual pages and some of them just redirects. Unfortunately there does not seem to be any central domain from which you could be redirected to the right national database, so ELI properties would have to be done separately for each country (and the EU itself). Samoasambia ✎ 15:09, 22 October 2024 (UTC)[reply]

French environmental protection classification

edit
   Under discussion
DescriptionIndustrial or agricultural operations generating risks to health and the environment are regulated in France. The various risks are organized into headings in the nomenclature of installations classified for environmental protection. The dangers, pollution and nuisances of each operation are listed by public authorities.
Data typeItem
DomainQ3151661
Allowed valuesQ125631811
Example 1Raffinerie de Feyzin (Q3417389) → Q125635166
Example 2Chemical factory, Balan (Q16511667) → Q125639692
Example 3ArcelorMittal Dunkerque (Q21164927) → Q125636796
Example 4Q130526075 → Q125635500
Example 5Q123267504 → Q125635414

Motivation

edit

Cette propriété est importante pour recenser les dangers pour la santé et l'environnement associés aux activités économiques. Une propriété dédiée permettra d'ajouter les qualificatifs pertinents (dates, références, etc.) pour chaque risque. Arpyia (talk) 08:53, 19 October 2024 (UTC)[reply]

  Notified participants of WikiProject France

Discussion

edit

  Notified participants of WikiProject France. Ping needs a signature to work. Samoasambia ✎ 14:07, 22 October 2024 (UTC)*[reply]

‎operating cost

edit
   Under discussion
Descriptionongoing recurring cost for operating or using an object
Representsoperating cost (Q831940)
Data typeQuantity
Domainactivity (Q1914636), architectural structure (Q811979), facility (Q13226383), artificial object (Q16686448)
Allowed values0-10000000000000
Allowed unitscurrency (Q8142) per unit of time (USD/year, EUR/month, etc)
Example 1F-35A Lightning II (Q17519093)→USD$6.6m/year
Example 2swimming pool (Q1501)→USD$1450/year
Example 3Tesla Model 3 (Q7705507)→USD$623/year
Expected completenessalways incomplete (Q21873886)
See alsocapital cost (P2130)

Motivation

edit

capital cost (P2130) already captures the initial capital cost of an object (building, vehicle, etc) but there is no equivalent property for capturing the recurring ongoing costs of maintaining and operating an object.

Qualifiers such as determination method or standard (P459) and valid in period (P1264) would be very important to use with this property as there are many ways to calculate an operating cost for equipment or a building. In the Tesla Model 3 example provided (USD$623/year) this was only an estimate valid at a point in time, for the first five years of ownership of a car, and excluding a number of other operating costs such as electricity and insurance.

--Dhx1 (talk) 03:22, 25 October 2024 (UTC)[reply]

Discussion

edit
  •   Weak support A week support from me, because I think it needs a qualifier of sort. I think the cost of annual ownership can benefit from qualifier of a country, region, city, where it's owned. For example, cost of ownership of Tesla car in Norway and US differ tremendously. Also, I think it would benefit from more time periods like 5 year and so on, but I'm not certain about it. --David Osipov (talk) 12:11, 26 October 2024 (UTC)[reply]
  •   Comment The time span should be specified using duration (P2047) qualifier; otherwise you need to create items for every combination of currencies with day/week/month/year, which would be a nightmare for editors and data consumers. Dexxor (talk) 17:57, 27 October 2024 (UTC)[reply]

‎effective life of asset

edit
   Under discussion
Descriptionduration of time which an object/asset is expected to be used before needing to be disposed of or replaced
Data typeQuantity
Domainartificial object (Q16686448)
Allowed unitsunit of time (Q1790144) or any other useful unit of measurement for lifespan of an object (kilometres traveled, engine hours, flight hours, etc)
Example 1CT scanner (Q128486784)→10 years
Example 2combine harvester (Q26886)→12 years
Example 3laptop (Q3962)→2 years
SourceExample: https://www.ato.gov.au/law/view/document?DocID=ITD/EF20151C8/00001&PiT=99991231235958
Expected completenessalways incomplete (Q21873886)
See alsodiscontinued date (P2669), service retirement (P730), life expectancy (P2250)

Motivation

edit

There is no property existing for the expected useful lifespan of an artificial object (such as a machine, tool, vehicle or building) after which it is expected the object needs replacing due to wear and tear, obsolescence, lack of support and lack of maintainability.

This concept is useful in finance for determining the current value of a purchased asset for taxation and financial reporting reasons. It is also useful for consumer items such as toothbrushes, phones, computers which are replaced regularly for reasons of wear and tear and obsolescence of technology.

--Dhx1 (talk) 03:23, 25 October 2024 (UTC)[reply]

Discussion

edit
  •   Oppose This varies per product and also the lifespan of a laptop obviously is not just 2 years. --Prototyperspective (talk) 09:46, 25 October 2024 (UTC)[reply]
    My thought with this property proposal is that qualifiers such as determination method or standard (P459) and the references are critical. This property could be used 10 times on laptop (Q3962) all with different sources such as standards for asset management and taxation depreciation schedules of different governments. Thus the users of this property have to pick and choose whichever of these 10 statements is most useful to them. For example, the life of a laptop (Q3962) could be 5 years after first product release until it is typically expected to be obsolete and would be scrapped, could by 3 years as determined by continuous use causing battery degradation and wear and tear typically requiring replacement, could differ in expectations between a government in country X versus country Y depending on affluence of the country and wiliness to adopt newer technologies and scrap older ones seen as obsolete, etc. Dhx1 (talk) 12:42, 25 October 2024 (UTC)[reply]
    I don't know of anybody who would replace a laptop after just 5 years. Moreover, the planned obsolescence of laptops, smartphones, several plastic products, and so on are a major problem and WD should not normalize or reinforce that by suggesting this is how long these products inherently last. They can last much longer, for example via standardized replacement parts + requirement to be somewhat modular and having parts (such as battery) offered individually. Prototyperspective (talk) 12:13, 26 October 2024 (UTC)[reply]
  •   Weak support It's connected to depreciation of an item, which is a correct accounting notion. But weak support from me, because it needs to have qualifiers like Determination method, Usage frequency of some sort. I would suggest looking up various calculation methods of the effective life of a depreciating asset, writing them out and starting to propose these qualifiers along with this property. Without these qualifiers, the property alone is deceiving. --David Osipov (talk) 12:18, 26 October 2024 (UTC)[reply]
  •   Oppose something like "depreciation period" would be a better way to store information on the legal depreciation period than a more generally named property. ChristianKl ❪✉❫ 09:01, 31 October 2024 (UTC)[reply]

‎ITV News topic ID

edit
   Under discussion
Descriptionidentifier for a topic on the ITV News website
RepresentsITV News (Q4189762)
Data typeExternal identifier
Example 1Europe (Q46)→europe
Example 2Boris Johnson (Q180589)→boris-johnson
Example 3M5 motorway (Q1824663)→m5-motorway
Example 4Wales (Q25)→wales
Example 5science (Q336)→science
Expected completenessalways incomplete (Q21873886)
Formatter URLhttps://www.itv.com/news/topic/$1
URL match pattern^https?:\/\/(?:www\.)?itv\.com\/news\/topic\/([a-z0-9]+)
web page title extract pattern (P10999) ^ITV\ News\ :\ The\ Latest\ (.+)\ News$
See alsoGuardian topic ID (P3106), BBC News topic ID (P6200), Sky News topic ID (P11632)
Single-value constraintyes
Distinct-values constraintyes

Motivation

edit

A Wikidata property to identify news website topics (Q105946994) for ITV News (Q4189762), one of the most significant news sources in the United Kingdom.

The IDs seem stable, going back to at least 2012. --Lewis Hulbert (talk) 12:44, 25 October 2024 (UTC)[reply]

Discussion

edit

‎Toki Pona headnoun

edit
   Under discussion
DescriptionToki Pona common noun for which the name serves as a proper modifier
Data typeLexeme
Allowed valueslanguage=tok
Example 1Sonja Lang (Q12854)Toki Pona headnounjan (L220656)
Example 2Tamzin Hadasa Kelly (Q127401579)Toki Pona headnounwan (L220805)
Example 3United States of America (Q30)Toki Pona headnounma (L220703)

Motivation

edit

First of all, no, I don't know why there's an item about me, but I might as well use it as an example! So, in Toki Pona, names only ever serve as adjectives. So even though my name is Tansin, one can't refer to me as just that. Instead, a name must modify a common noun, which essentially serves as Toki Pona's own "instance of" statement. So it's not Mewika, but rather ma Mewika 'country called Mewika'. The ma there, is not however semantically part of the name of the country, and contextually could be replaced with some other word (for instance, a critic of the U.S. could say ike Mewika, 'bad thing called Mewika').

This common noun is called a headnoun. Some people refer to themselves with a headnoun other than jan 'person', which thereby functions as something between a courtesy title and preferred pronoun. For instance, I usually use wan 'union' to refer to myself, and that's the name I'm credited under in the acknowledgments to Toki Pona Dictionary (Q108617357). My item thus gives a name (P2561) of wan Tansin, but that's akin to saying my name in English is "person named Tamzin". One solution would be to simply remove wan, but that word is required information to understand how to refer to me in Toki Pona.

My understanding is that language-specific properties have been approved in the past, e.g. Vietnamese middle name (P8500) and second family name in Spanish name (P1950). -- Tamzin[cetacean needed] (they|xe) 23:18, 27 October 2024 (UTC)[reply]

Discussion

edit
  •   Comment Hmm, this seems like it should be attached to the "class", not the instances. Especially if several different ones could be used (as in your "ma"/"ike" example). ArthurPSmith (talk) 21:18, 29 October 2024 (UTC)[reply]
    That would work for something like a country, but wouldn't work for entities that state a preferred headnoun. Both Sonja Lang and I are instance of (P31)human (Q5), and there's no other statements in our respective items from which one could infer that I primarily use the headnoun wan (L220805) while she uses the more standard (but by no means universal) jan (L220656). This is true of organizations too. I co-own an LLC that uses the word kulupu (L220679) 'community', but another might use esun (L220644) 'business' or something else entirely. And for creative works: Common headnouns for typefaces include sitelen (L220771) 'writing', nasin (L220725) 'way', and linja (L220690) 'lines'. Again, all not inferable from any other statement. -- Tamzin[cetacean needed] (they|xe) 20:23, 1 November 2024 (UTC)[reply]
  • Vietnamese middle name (P8500) and second family name in Spanish name (P1950) exist because there's semantic content that's expressed. second family name in Spanish name (P1950) is about expressing that a name is inherited from the mother. Can you explain why you think name (P2561) doesn't work here and what you think the property would add? ChristianKl ❪✉❫ 08:41, 31 October 2024 (UTC)[reply]
    @ChristianKl: Including the headnoun in the name would be incorrect because a headnoun is not part of someone's name. A headnoun just establishes some common noun that applies to the entity, before stating what that name is. If it were standard in English to always call you "the Wikidatan Christian"—and indeed, this is roughly how some newspapers write—that wouldn't make "the Wikidatan" part of your name. So, that leaves two options: omit headnouns entirely from Wikidata, or create a property. If we did the former, it would not be possible to use Wikidata to figure out how to refer to or address someone in Toki Pona. You could guess with decent reliability based on P31 and some map of values to lexemes, but for the reasons explained above to ArthurPSmith, that will carry a significant error rate. In short: a headnoun is a required aspect of how people are addressed and referred to in Toki Pona, but is not semantically part of the name and cannot be fully predicted from other data. -- Tamzin[cetacean needed] (they|xe) 20:32, 1 November 2024 (UTC)[reply]

‎Provides data for property

edit
   Under discussion
Descriptionthe dataset associated with this external id usually contains data applicable to this other wikidata property
Data typeProperty
Domainexternal id properties
Example 1Deku Deals ID (P8364)→price (P2284)
Example 2MyWaifuList character ID (P13031)→height (P2048)
Example 3IMDb ID (P345)→title (P1476)
Example 4Fandom article ID (P6262)→unknown
See alsostated in (P248)

Motivation

edit

I was asked by @Kirilloparma: to save certain references not with reference URL (P854) but instead (for instance) ‎Playdate Catalog ID (P12125) in Wikidata:Tools/Wikidata for Web.

My concerns regarding this was that, I cannot automatically distinguish between data provided by the database item behind ‎Playdate Catalog ID (P12125) and information that just happens to be found under the same url.

Let's say the footer of a page might contain an email address, that is not related to the person reviewed in the page.

Or isbnsearch.org would tell me the title of a book but I wouldn't use ISBN-13 (P212) as the reference.

Now if I had an indication that a url that resolves to (for instance) an IMDb ID (P345) usually holds the information that applies to title (P1476), then I could make the assumption that it would make for a fitting reference statement when extracting this property from the url.

This information could be useful for other tools like:

  • A tool that tells you that an item should have a title and that you could find it on the IMDB
  • A tool that highlights a reference that might be faulty because it occours in an unusual context. Let's say Deku Deals ID (P8364) is used on a date of birth (P569) statement.

If an ID points to a wiki, that could hold all kinds of statements, it should be set to unknown.

Discussion

edit

@Addshore: –Shisma (talk) 10:00, 28 October 2024 (UTC)[reply]

  Support I quite like the idea, and it falls in line with what I am trying to do with more visual cues on items for the viability of references / sources and notability ·addshore· talk to me! 10:23, 28 October 2024 (UTC)[reply]

  Question Same as supported metadata (P8203)? Midleading (talk) 15:06, 28 October 2024 (UTC)[reply]

I'm not sure what this is meant for but the datatype is different. So it's definitely not the same. – Shisma (talk) 15:14, 28 October 2024 (UTC)[reply]
supported metadata (P8203) can be used to tell what kind of data a database stores, and not being limited to data that Wikidata has a property for. The example PubMed ID (Q2082879)supported metadata (P8203)digital object identifier (Q25670) is no different from the examples given here except that it accepts items which can be created by anyone. Midleading (talk) 04:03, 29 October 2024 (UTC)[reply]

  Support -wd-Ryan (Talk/Edits) 16:56, 28 October 2024 (UTC)[reply]

  Support Knowing the data a property may hold would be helpful for sourcing statements on items. --Lewis Hulbert (talk) 01:03, 29 October 2024 (UTC)[reply]

  Support Useful. --Prototyperspective (talk) 12:14, 29 October 2024 (UTC)[reply]

  •   Wait this property mixes three things together (1) Some entries in the database have data on this property. (2) All entries in the database have data on this property. (3) All entries have reliable data that's worthy of being imported on this property.
If we aren't clear about the meaning, different people are likely going to use it differently leading to bad conclusions. ChristianKl ❪✉❫ 19:09, 1 November 2024 (UTC)[reply]
I read the proposal and all comments again and I'm left with the impression the only assumed meaning of this property is (1). (2) can be expressed with a qualifier nature of statement (P5102) → sometimes (Q110143752). (3) if there is a property for it, I'd assume that the is a consensus that it is worthy of importing 🤷
I have an instance were data is there, but it it's format is always faulty. I would just   deprecate the statement in such cases. We could do the same for when the source is known to be factually faulty reason for deprecated rank (P2241) → source known to be unreliable (Q22979588) –Shisma (talk) 08:34, 2 November 2024 (UTC)[reply]
"A tool that tells you that an item should have a title and that you could find it on the IMDB" is only true for (3). ChristianKl ❪✉❫ 09:38, 2 November 2024 (UTC)[reply]

Resistance in Belgium ID

edit
   Under discussion
Descriptionidentifier of persons, administrative areas, resistance organizations of world war 2,... on https://data.arch.be/
Representsno label (Q130564724)
Data typeExternal identifier
Domainhuman (Q5), organization (Q43229), country (Q6256)
Example 1Groupe G (Q1767773)→Q3790
Example 2Walthère Dewé (Q631073)→Q7400
Example 3Ixelles - Elsene (Q208713)→Q104
Example 4Belgium (Q31)→Q5
Sourcehttps://data.arch.be/, https://query.data.arch.be/,
Planned useAdd the identifier to already created Wikidata Qid's.
Expected completenessalways incomplete (Q21873886)
Formatter URLhttps://data.arch.be/wiki/Item:$1
CountryBelgium (Q31)
Applicable "stated in"-valueQ130564724
Single-value constraintyes
Wikidata projectWikiProject World War II (Q10653810)

Motivation

edit

Resistance in Belgium is a platform that makes it possible to do research on the resistance in Belgium during the Second World War.
  Comment: This database contains mostly persons, but most of them are only known in this database (Wikidata:Notability). That's why I said in the 'planned use' section that I will only use the ID for already created Wikidata QIDs.  – The preceding unsigned comment was added by RVA2869 (talk • contribs) at 10:51, 28 October 2024 (UTC).[reply]

Discussion

edit

Identifiant Mediapart d'un blogueur

edit
   Under discussion
Descriptionidentifiant d'un blogueur sur Le Club Medipart (fr) – (Please translate this into English.)
RepresentsLe Club Mediapart (Q116280260)
Data typeExternal identifier
Domainitem
Example 1Pierre Joxe (Q977974)→pierre-joxe
Example 2Bernard Lamizet (Q2898165)→bernard-lamizet
Example 3Allan Barte (Q2837667)→allan-barte
Example 4Association France Palestine solidarité (Q2867251)→afps-association-france-palestine-solidarite
Example 5Roxana Eminescu (Q18539984)→roxana-eminescu
External linksUse in sister projects: [ar] • [de] • [en] • [es] • [fr] • [he] • [it] • [ja] • [ko] • [nl] • [pl] • [pt] • [ru] • [sv] • [vi] • [zh] • [commons] • [species] • [wd] • [en.wikt] • [fr.wikt].
Formatter URLhttps://blogs.mediapart.fr/$1
Wikidata projectWikiProject France (Q10816832)

Motivation

edit

Pas mal de personnalités écrivent dans Mediapart (ça permetrrait d'enlever de official website (P856) et de official blog URL (P1581) les blogs Mediapart, voir ici)Legonin (talk) 16:25, 31 October 2024 (UTC)[reply]

Discussion

edit

‎ISCC

edit
   Under discussion
DescriptionInternational Standard Content Code. Hash code that identifies a media object based on fuzzy hashing.
RepresentsInternational Standard Content Code (Q129857134)
Data typeString
Allowed valuesISCC:[A-Z2-7]{10,73}
Example 1
 
Zaadpeulen van goudenregen (Laburnum anagyroides), 31-08-2024. (d.j.b)
→ ISCC:KECV7KS6BOJ35WEUX7SMMG3BY4LGBACQ2PJPVVGGHVEZ4DZISC7CXLI
Example 2
Rooster crowing small
→ ISCC:KMCU72IF2EHZH5PKFS2UODT2EGOTGY5CIBRMRYSQR6HGLFBHAAUANVY
Example 3
 
Aristotle latin manuscript
→ ISCC:KECV7NLW5ME7CEN2XZHDHAODEGDT66ZOQVNDPKM4AKWU6L32BHKVXMQ

Motivation

edit

As of May 2024, the International Standard Content Code (Q129857134) has been an ISO standard (ISO 24138:2024) to identify digital assets in a robust way by applying fuzzy hashing technology to objects. Awinkler3 (talk) 14:50, 1 November 2024 (UTC)[reply]

Discussion

edit
Jheald (talk) 06:27, 17 August 2014 (UTC) Micru (talk) 07:20, 17 August 2014 (UTC) Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 15:41, 17 August 2014 (UTC) Sannita - not just another it.wiki sysop 12:50, 18 August 2014 (UTC) Susannaanas (talk) 08:05, 19 August 2014 (UTC) Mushroom (talk) 12:02, 21 August 2014 (UTC) I do think Commons is the better place to talk about this. Multichill (talk) 18:50, 21 August 2014 (UTC) Jarekt (talk) 04:38, 3 September 2017 (UTC)  徵國單  (討論 🀄) (方孔錢 💴) 11:23, 14 November 2017 (UTC) Mike Peel (talk) 22:50, 12 May 2018 (UTC) Yann (talk) 23:27, 7 July 2018 (UTC) John Samuel (talk) 10:10, 22 September 2018 (UTC) 99of9 (talk) 06:27, 12 July 2019 (UTC) Christian Ferrer (talk) 18:05, 19 July 2019 (UTC) Jura GPSLeo (talk) 13:30, 29 July 2019 (UTC) Tris T7 TT me[reply]
Juandev (talk) 17:35, 7 September 2019 (UTC) Jean-Fred (talk) 15:21, 26 September 2019 (UTC) Premeditated Vahurzpu Dr Isaac Andy (talk) 05:21, 29 January 2020 (UTC)[reply]

  Notified participants of WikiProject Commons

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