Property talk:P380

Documentation

• Start a query
• Current uses
• Statistics by class
• String length
• List of qualifiers
• Count

Mérimée ID
identifier for a monument in the Mérimée database of French cultural heritage

Description	identifier for cultural properties in France from Base Mérimée
Represents	monument historique inscrit (Q10387575), classified historical monument (Q10387684), listed in the general inventory of cultural heritage (Q16739336), Maisons des Illustres (Q3280355), Base Mérimée (Q809830)
Applicable "stated in" value	Base Mérimée (Q809830)
Has quality	identifier (Q853614)
Data type	External identifier
Corresponding template	Template:Base Mérimée (Q12646538)
Template parameter	Template:Base Mérimée, c:Template:Mérimée
Domain	According to this template: geographic feature: instance of Monument historique According to statements in the property: geographical feature (Q618123), fixed construction (Q811430) or work (Q386724) When possible, data should only be stored as statements
Allowed values	([PEI][A]\d[0-9AB]\d{6}|ACR\d{7}|MI\d{3}B{0,1}|JAR\d{7}|SPR\d{7})
Example	Basilica of Saint-Denis (Q184407) → PA00079952 Gare de Paris-Est (Q757180) → PA00086491
Source	http://www.culture.gouv.fr/culture/inventai/patrimoine
Formatter URL	https://www.pop.culture.gouv.fr/notice/merimee/$1
Tracking: usage	Category:Pages using Wikidata property P380 (Q24285478)
Related to country	France (Q142) (See 652 others)
See also	Palissy ID (P481), Auvergne-Rhône-Alpes Regional Inventory ID (P5517), Gertrude ID (P1529), Fondation du patrimoine ID (P9875), Fontaines de France ID (P9828)
Lists	Items with the most statements of this property Count of items by number of statements (chart) Items with the most statements Items with the fewest statements Count of items by number of sitelinks (chart) Items with the most sitelinks Items with the most sitelinks, but no link to one Wikipedia (sample: Welsh Wikipedia, cywiki) Items with the fewest sitelinks Most linked wikis Items with the most identifier properties Items with no other external identifier Items with no other statements Most recently created items Items with novalue claims Items with unknown value claims Usage history (total) Usage history (main statement) Chart by item creation date Mix'n'match (Report) Database reports/Complex constraint violations/P380 Database reports/Constraint violations/P380 Map Random list
Proposal discussion	Proposal discussion
Current uses	Total 72,130 Main statement 71,432 99% of uses Qualifier 2 <0.1% of uses Reference 696 1% of uses
Search for values

[create Create a translatable help page (preferably in English) for this property to be included here]

Format “[PEI][A]\d[0-9AB]\d{6}|ACR\d{7}|MI\d{3}B{0,1}|JAR\d{7}|SPR\d{7}|”: value must be formatted using this pattern (PCRE syntax). (Help)

List of violations of this constraint: Database reports/Constraint violations/P380#Format, hourly updated report, SPARQL

Item “country (P17): France (Q142), Morocco (Q1028), Guernsey (Q25230), United States of America (Q30), China (Q148)”: Items with this property should also have “country (P17): France (Q142), Morocco (Q1028), Guernsey (Q25230), United States of America (Q30), China (Q148)”. (Help)

List of violations of this constraint: Database reports/Constraint violations/P380#Item P17, hourly updated report, search

Item “heritage designation (P1435): classified historical monument (Q10387684), monument historique inscrit (Q10387575), listed in the general inventory of cultural heritage (Q16739336), Patrimoine du XXe siècle (Q3214312), Remarkable Contemporary Architecture (Q44078976), remarkable garden of France (Q498842), Maisons des Illustres (Q3280355)”: Items with this property should also have “heritage designation (P1435): classified historical monument (Q10387684), monument historique inscrit (Q10387575), listed in the general inventory of cultural heritage (Q16739336), Patrimoine du XXe siècle (Q3214312), Remarkable Contemporary Architecture (Q44078976), remarkable garden of France (Q498842), Maisons des Illustres (Q3280355)”. (Help)

Exceptions are possible as rare values may exist. Exceptions can be specified using exception to constraint (P2303).
List of violations of this constraint: Database reports/Constraint violations/P380#Item P1435, search

Item “located in the administrative territorial entity (P131)”: Items with this property should also have “located in the administrative territorial entity (P131)”. (Help)

List of violations of this constraint: Database reports/Constraint violations/P380#Item P131, hourly updated report, search, SPARQL

Type “geographical feature (Q618123), fixed construction (Q811430), work (Q386724)”: item must contain property “instance of (P31)” with classes “geographical feature (Q618123), fixed construction (Q811430), work (Q386724)” or their subclasses (defined using subclass of (P279)). (Help)

Exceptions are possible as rare values may exist. Exceptions can be specified using exception to constraint (P2303).
List of violations of this constraint: Database reports/Constraint violations/P380#Type Q618123, Q811430, Q386724, SPARQL

Qualifiers “applies to part, aspect, or form (P518), start time (P580), end time (P582), reason for deprecated rank (P2241), reason for preferred rank (P7452), latest start date (P8555), earliest date (P1319), earliest end date (P8554), latest date (P1326), subject named as (P1810), archive URL (P1065)”: this property should be used only with the listed qualifiers. (Help)

List of violations of this constraint: Database reports/Constraint violations/P380#allowed qualifiers, hourly updated report, SPARQL

Distinct values: this property likely contains a value that is different from all other items. (Help)

Exceptions are possible as rare values may exist. Exceptions can be specified using exception to constraint (P2303). Known exceptions: Q311, Q3583854, Q663673, Q377882, Q19754562, Q15950605, Q3398972, Q18342694, Q19690465, Q19754556, Q19754549, Q19754589, Q15945210, Q19754605, Q3061807, Q19754833, Q19754849, Q19754895, Q19754919, Q2956968, Q2974390, Q842932, Q15940257, Q2859246, Q19760046, Q15948789, Q14627669, Q15950557, Q1075988, Q3368000, Q20968690, Q917337, Q747541, Q1141316, Q2010697, Q1569396, Q2946, Q3363782, Q19802141, Q2669368, Q730948, Q214654, Q19297902, Q3279847, Q3153054, Q3053805, Q3424634, Q3305924, Q2911199, Q3268959, Q3584999, Q3402925, Q2985915, Q2968742, Q2970369, Q1630460, Q12185655, Q16008530, Q1061061, Q19817291, Q18011136, Q3034002, Q3054862, Q3145400, Q3268638, Q2820425, Q2866135, Q1329976, Q2970739, Q1232116, Q3117134, Q3424607, Q2064073, Q2315733, Q2084520, Q1709158, Q1770845, Q2942776, Q3078504, Q3424643, Q2914150, Q3001762, Q3145566, Q271, Q2820433, Q333851, Q376932, Q922303, Q15950349, Q15950850, Q2111621, Q19825954, Q952229, Q2248639, Q1283154, Q3320413, Q3424623, Q3361199, Q1516, Q8625, Q19826159, Q19826167, Q2400326, Q2971299, Q3146135, Q2940300, Q3396357, Q19826313, Q3286279, Q2982097, Q13518233, Q2972548, Q577871, Q3279851, Q3000980, Q2971723, Q3145389, Q3410669, Q17984083, Q20080833, Q14627548, Q13402647, Q3145704, Q334077, Q766938, Q20888947, Q20888642, Q1510, Q143463, Q18621190, Q18012881, Q18004204, Q21252932, Q22674805, Q2948025, Q917914, Q21584222, Q138101, Q1048391, Q1385053, Q135225, Q2971879, Q22117156, Q284444, Q22910830, Q273482, Q201428, Q220301, Q18636936, Q639319, Q1520841, Q2970548, Q3364200, Q2820441, Q3320391, Q22671047, Q22671049, Q1739261, Q1739286, Q11682090, Q426064, Q3046756, Q648534, Q2030715, Q3397113, Q2971727, Q2974823, Q23304128, Q23304114, Q22941793, Q32989, Q15943957, Q2974391, Q22965185, Q3057828, Q2820462, Q2845777, Q1775545, Q3390189, Q1131080, Q22927482, Q22939731, Q18342194, Q1231132, Q12252858, Q28442965, Q22926014, Q189764, Q22996818, Q705054, Q56718530
List of violations of this constraint: Database reports/Constraint violations/P380#Unique value, SPARQL (every item), SPARQL (by value)

Allowed entity types are Wikibase item (Q29934200): the property may only be used on a certain entity type (Help)

Exceptions are possible as rare values may exist. Exceptions can be specified using exception to constraint (P2303).
List of violations of this constraint: Database reports/Constraint violations/P380#Entity types

Scope is as main value (Q54828448), as reference (Q54828450): the property must be used by specified way only (Help)

Exceptions are possible as rare values may exist. Exceptions can be specified using exception to constraint (P2303).
List of violations of this constraint: Database reports/Constraint violations/P380#Scope, SPARQL

Label required in languages: fr: Entities using this property should have labels in one of the following languages: fr (Help)

Exceptions are possible as rare values may exist. Exceptions can be specified using exception to constraint (P2303).
List of violations of this constraint: Database reports/Constraint violations/P380#Label in 'fr' language, search, SPARQL

This property is being used by: ca:Plantilla:Infotaula patrimoni cultural/designació id wd, ca:Plantilla:Protecció patrimonial wd/dades cs:Šablona:Rejstříky památek eu:Txantiloi:Eraikin infotaula automatikoa/Ondarea, eu:Txantiloi:Eraikin infotaula automatikoa, eu:Txantiloi:Eraikin infotaula, eu:Txantiloi:Eraikin infotaula/Ondarea ast:Plantía:Edificiu/Patrimoniu de:Vorlage:Ligne de tableau MH ha:Template:Infobox building/legend, ha:Samfuri:Infobox building/legend incubator:Template:Wp/shi/Infobox building/legend, incubator:Template:Wp/jje/위키데이터 속성 추적 kab:Talɣa:Infobox building/legend shi:Talɣa:Infobox building/legend ko:틀:위키데이터 속성 추적 wikt:ko:틀:위키데이터 속성 추적 Please notify projects that use this property before big changes (renaming, deletion, merge with another property, etc.)

Inconsistency between the identifier and the location
Place with identifier prefix indicating a departement but located in another departement. (Help)
Violations query: SELECT DISTINCT ?item WHERE { ?item wdt:P380 ?merimee; wdt:P131/wdt:P374 ?insee . FILTER( substr(?merimee, 3, 2) != '00' && substr(?merimee, 3, 2) != substr(?insee, 1, 2) ). FILTER( ?item NOT IN ( wd:Q38383288, wd:Q41772591, wd:Q38503834, wd:Q3582098 ) ) . }
List of this constraint violations: Database reports/Complex constraint violations/P380#Inconsistency between the identifier and the location

Custom single value constraint
Monument with two completed inventory records (Help)
Violations query: SELECT DISTINCT ?item ?id1 ?id2 WHERE { ?item wdt:P380 ?id1 ; wdt:P380 ?id2 . FILTER (?id1 > ?id2). FILTER regex (?id1, "^IA"). FILTER regex (?id2, "^IA"). FILTER( ?item NOT IN ( wd:Q38503834, wd:Q41784520, wd:Q3582098, wd:Q3582307, wd:Q3582676, wd:Q3583199, wd:Q3583641, wd:Q3583633 ) ) . }
List of this constraint violations: Database reports/Complex constraint violations/P380#Custom single value constraint

Constraints

Hi,

I'm not very good with technic, regexp and so on… So I come here to know how to it correctly. Since there is already reports on Wikidata:Database reports/Constraint violations/P380.

The Merimée identifier in itself is a unique and single value for a specific monument but sometimes an indentifier will be use in serveral articles. Eg. PA00086780 is for the tombs in the Père Lachaise Cemetery. The tombs are several monuments with several articles on wikipédia but counted as only a monument in Mérimée. So it's will be difficult to keep a unique value.

Then, a monument have a primary identifier but it's not unusual to have 3 to 6 identifiers for a single monument (typically, one beginnig with PA and one other with IA). Should we only keep the primary identifier (single value) or not ?

Finally, the regexp \w\w\d\d\d\d\d\d\d\d is not good, why is Oscar Wilde's tomb (Q12432989): PA00086780 in "Format" violations ? At least, it should be \w\w\d\w\d\d\d\d\d\d because the 4th character could be A or B. I think the regexp could be more efficient, something like [PEI][A]\d[0-9AB]\d\d\d\d\d\d (and there is probably more efficient regexp). I've tried to do an analysis of this value on User:VIGNERON/MH.

Cdlt, VIGNERON (talk) 17:32, 6 May 2013 (UTC)

Hi,

The feature is still experimental, feel free to change the settings and try others.

Q12432989 was listed as the identifier had a leading whitespace.

I think it's a bad idea to use PA00086780 on items for individual tombs (one could use it on photographs, of course).

Even if there are constraints, there may be a few false positives that should remain. We haven't found an efficient way to save them however. For now, they just appear on the lists.

--  Docu  at 18:41, 6 May 2013 (UTC)

I don't really know how WikiData or Regexp exactly works, so I prefer not to try anything.

Ah leading whitespace… It happens a lot with the copy-paste… (I have to clean a lot of them during WLM…).

Why is it a bad idea ? In some way, the tombs are the monument and each tomb is a monument ; plus, they are explicitely protected (see the Merimée base : http://www.culture.gouv.fr/public/mistral/merimee_fr?ACTION=CHERCHER&FIELD_1=REF&VALUE_1=PA00086780 ). One other tricky example : two « stones » cordon des Druides (Q1132337) and Pierre courcoulée (Q2093334) are approximatevely 1 kilometer away from each other but they are protect together and there is a single entry in Mérimée for both : PA00090609 (+ two separated entries without protection IA00007259 and IA00007257).

We can found a “single” value (since there is a primary : PA over IA and EA and one PA over the other if there is more than one ; even if it's not really natural to me) but “unique” will be a lot more difficult.

Cdlt, VIGNERON (talk) 12:33, 7 May 2013 (UTC)

At some point the leading whitespaces needs to be fixed. I doubt hiding it from the report is they way to achieve that.

In any case, the result of the checks don't need to be free of false positives. They should improve overall quality however. --  Docu  at 23:15, 15 May 2013 (UTC)

P131

Hi,

What should be put for P131 ? Allways the commune, more or less precise ? PS: I just discover that for 8 MH in Q25362 Saint-Barthélemy and Q126125 Saint-Martin there is no commune…

Cdlt, VIGNERON (talk) 10:09, 10 July 2013 (UTC)

It should be always the smaller administrative area possible, even if Eeyou Istchee James Bay Regional Government (Q1820447) or Baffin, Unorganized (Q2878890) are bigger that some country of Europe. For a historic monuments in Saint Barthélemy (Q25362) and Saint-Martin (Q126125), P131 should be at this administrave level. For communes divided in borough, it should be at the borough level. --Fralambert (talk) 02:31, 29 July 2013 (UTC)

Nouvelle contrainte

J'ai rajouter une contrainte « type ». Elle devrait permettre d'afficher une erreur si monument historique inscrit (Q10387575) ou classified historical monument (Q10387684) ne sont pas présente. La seule conséquence de cette contrainte serait d'effacer Historical Monument (Q916475) dans les éléments, car en présence de cet élément, il ne présentera pas d'erreur. Je l'ai testé sur Quebec cultural heritage directory ID (P633) et tout semble fonctionner correctement. --Fralambert (talk) 02:47, 29 July 2013 (UTC)

Je viens de la retirer. Beaucoup de monuments non classé ou inscrit figurent en effet dans la base Mérimée (ex. Torra di San Pellegrinu (Q7826897)). Je ne sais pas comment gérer ce cas. Des idées ? — Ayack (talk) 09:54, 14 March 2014 (UTC)

@Fralambert et Ayack : cela me semble symptomatique d’un problème récurrent (qui existait déjà sur Wikipédia) : la base Mérimée contient bien plus que juste des MHs. Par contre, sauf erreur, tout ce qui est dans la base Mérimée doit avoir pour instance of (P31) : classified historical monument (Q10387684), monument historique inscrit (Q10387575) ou listed in the general inventory of cultural heritage (Q16739336).

Sinon comme je le disais ci-dessus en 2013, la contrainte « une seule valeur par propriété » ne semble pas pertinente non plus, à retirer ? On a déjà 532 violations et pour la Bretagne, il me semble pertinent de mettre au moins deux valeurs pour la quasi-totalité des 3000 MHs de la Région.

Sinon, grâce à mon analyse de cet identifiant : User:VIGNERON/MH, serait-il possible de faire une vérification plus poussée que {{Constraint:Format|pattern=<nowiki>[PEI][A]\d[0-9AB]\d\d\d\d\d\d}}</nowiki> ? Si je comprends bien cette contrainte, actuellement PA0A000000 est accepté alors qu'il ne le devrait pas (le A ou le B en 4e position est forcément précédé d'un 2 et l'identifiant ne finit jamais par 5 zéros).

Cdlt, VIGNERON (talk) 08:15, 4 September 2014 (UTC)

J'ai fait sauté la contrainte «seule valeur». Le simple fait qu'un bien peu avoir un code pour l'inventaire et un pour le classement rend le nombre d'exception trop grand pour qu'il soit utile. --Fralambert (talk) 02:26, 5 September 2014 (UTC)

Merci Fralambert ! Et pour la contrainte de format, cela vaut-il la peine d'aller plus loin ou bien est-ce inutile ? VIGNERON (talk) 16:09, 5 September 2014 (UTC)

@Fralambert, VIGNERON: On a un autre problème relatif à la controverse sur l'utilisation ou non de heritage designation (P1435) : une partie des éléments a instance of (P31) = MH, une autre a heritage designation (P1435) = MH et une troisième cumule les deux. Difficile dans ce cas là d'établir une contrainte quand on est pas d'accord sur la règle... — Ayack (talk) 08:51, 5 September 2014 (UTC)

@Ayack, VIGNERON: Dédoublé une information me semble redondant (Donc pour moi, pas la troisième solution). J'ai l'impression qu'on a affaire à un débat «généraliste - spécialiste» et j'en vois pas la solution à court terme, surtout que l’opposition est arrivé trop tard pour empêcher la création, mais assez trop tôt pour bloquer sa mise en application. Et finalement, personne ne semble avoir eu les couilles de proposer sa suppression. Personnellement, je suis en train de passer tout Quebec cultural heritage directory ID (P633) manuellement vers heritage designation (P1435), et j'en profite pour corriger les erreurs. --Fralambert (talk) 12:38, 5 September 2014 (UTC)

J'avoue hésiter et ne pas trop savoir quelle est la meilleure solution. La forme et l'étendue de la protection au titre MH est très variable. Sauf erreur, la protection ne concerne que rarement tout un bâtiment (en tout cas, j'ai l'impression de souvent voir « partie protégée : façade/toiture/etc. ») et cela peut aller d'une toute petite partie (une pourtre sculptée, une cheminée, un fresque - parfois enlevée du site pour être exposé dans un musée d'ailleurs) ou au contraire une très grande zone (genre le domaine de Versailles ou la commune du Chambord qui est intégralement protégée). Du coup, dire que le bâtiment est un MH (P31) ou qu'il est protégé (P1435), ça me gêne un peu dans les deux cas.

Je serais tout de même pour le passage à P1435 mais pour une autre raison assez triviale, cela obligerait/pousserait à renseigner P31 avec autre chose que MH (parce que c'est autant sinon plus intéressant de dire qu'un élément est une église, un pont, un chateau, etc.). De nombreux MH ne sont pas (encore) sur Wikidata donc il serait temps de se décider rapidement. Par contre, il doit être possible de faire ça semi-automatiquement (genre avec AutoList2), non ? (bon, des vérifications ce n'est jamais inutile mais je me vois mal faire des dizaines de milliers d'éléments à la main).

En tout cas, la solution de doublonner me semble clairement à rejeter (on doublonne bien assez d'informations comme cela sur Wikidata).

Cdlt, VIGNERON (talk) 16:09, 5 September 2014 (UTC)

J'avoue que j'avais observé, mais pas du tout pensé à l'avantage de libéré P31. Personnellement, j'aime particulièrement cette liste de suivi. Avec AutoList2, tu pourrais toujours débuté pour les biens sans date de début (P580) (Mais je ne réussi pas à programmer un code affichant les éléments sans date.) --Fralambert (talk) 19:46, 5 September 2014 (UTC)

Ah oui, j'avais oublié les qualificateurs, cela complique un peu la tâche. Cdlt, VIGNERON (talk) 07:44, 6 September 2014 (UTC)

D'accord aussi pour passer le classement en heritage designation (P1435) (je débarque ici suite à une question sur le bistro où justement je m'étonnais de l'absence de propriété du type "classement").

Pour la question du classement partiel MH, c'est plus compliqué, on pourrait éventuellement créer une qualité "partiellement classé" voire même une propriété "partie classée", mais qui ne pourra pas être facilement remplie si il faut mettre des trucs du genre "petite porte à gauche façade nord". --El Caro (talk) 08:08, 6 September 2014 (UTC)

El Caro : oui c’est compliqué (en dehors même du « partiellement classé »). On réveille l'idée de créer Wikidata:WikiProject France/Monuments historiques et on y fait un fait sur le déplacement instance of (P31) → heritage designation (P1435) ? (parce que là, on dépasse largement le cadre de la propriété P380). Cdlt, VIGNERON (talk) 08:27, 6 September 2014 (UTC)

Pour le classement partiel, on peut utiliser un qualifieur applies to part, aspect, or form (P518), non ? -Ash Crow (talk) 11:26, 6 September 2014 (UTC)

Bien vu pour le classement partiel. Pour le déplacement de la discussion, OK aussi. --El Caro (talk) 11:35, 6 September 2014 (UTC)

nom officiel

Where to put the official (french) name, which every Mérimée entry has? (f.e. "Abbaye de Sénanque (ancienne)"). Should this be a qualificator of this property or an own property entry with reference to Base Mérimée?--Sinuhe20 (talk) 15:08, 26 July 2020 (UTC)

Is it really a "nom officiel" ? It is called "titre courant" in your example. I am not sure it is really useful to have it. --Zolo (talk) 15:29, 26 July 2020 (UTC)

+1 with @Zolo:, it's not a official name. Plus, most of the time it's just the label in French, not sure this should be store in Wikidata. Cheers, VIGNERON (talk) 10:53, 27 August 2020 (UTC)

It could be added as qualifier of Mérimée ID (P380) with subject named as (P1810). Ayack (talk) 11:13, 27 August 2020 (UTC)

@Ayack: yes « it could », but should it? @Sinuhe20: what is your use and/or need here? Cheers, VIGNERON (talk) 12:23, 27 August 2020 (UTC)

@VIGNERON: I think this name should be used in french monument lists, I use the german translation of it.--Sinuhe20 (talk) 10:21, 3 September 2020 (UTC)

@Sinuhe20: why not just use the label then? and lists on Wikipedia don't use Wikidata (not yet at least), are you taling about a list somewhere else? I'm also thinking, when a monument has several Mérimée entry, then the "titre courant" can be different, how to deal with that? see Château de Caradeuc (Q2968767) z. B. Cheers, VIGNERON (talk) 11:00, 3 September 2020 (UTC)

New format

Hi,

Just a quick message to tell that I update this property format to : ([PEI][A]\d[0-9AB]\d{6}|ACR\d{7}).

It allows the new identifier like ACR0000597 on Schlossberg Stadium (Q3496093). ACR stands for « Architecture contemporaine remarquable » which replace the Patrimoine du XXe siècle (Q3214312) label.

Cheers, VIGNERON (talk) 10:53, 27 August 2020 (UTC)

Bonjour @VIGNERON, ne faut-il pas le modifier aussi pour gérer les sites patrimoniaux remarquables ? Exemple Cabourg qui entraîne une violation de format : https://www.wikidata.org/w/index.php?title=Q202445&type=revision&diff=1459926374&oldid=1438805513 Ayack (talk) 15:38, 9 February 2022 (UTC)

@Ayack: tout à fait, merci du signalement, je viens de corriger. Cdlt, VIGNERON (talk) 15:59, 9 February 2022 (UTC)

New qualifier allowed

Hi,

Since some identifiers sometimes disappears (luckily, it's rare cases), I added archive URL (P1065) as a valid qualifier allowed for this property, see Q21427861 for instance.

Cheers, VIGNERON (talk) 17:10, 12 July 2023 (UTC)

Proposal of single constraint

Hello/Bonjour,

@Ayack, GautierPoupeau, Gzen92, Nono314, Peter17, Chabe01: (top user of this property)

I'm wondering if we shouldn't re-add a single-best-value constraint (Q52060874) to this property (and yes, I'm the one who advocated to remove it 10 years ago, see above and @Fralambert:, my mistake). Of course, it would need some talk and work and at least defining the separator (P4155) but in the end, I think it would worth it. Look for instance what I tried on Q2968767#P380, adding a qualifier (not recognized yet) allowed to make each value unique and more importantly more understandable (no need anymore to click on each link to understand why there is 3 IDs).

What do you think?

Je me demande si il ne faudrait pas remettre une single-best-value constraint (Q52060874) à cette propriété (et oui, je suis celui qui a poussé pour l'enlever il y a dix ans, voir supra, c'est mon erreur). Bien sûr, cela va nécessiter des discussions et du travail, au moins définir les separator (P4155) mais au final, je pense que cela vaut la peine. Regardez par exemple ce que j'ai essayer sur Q2968767#P380, ajouter un qualificatif (pas encore reconnu) permet de rendre chaque valeur unique et surtout plus compréhensible (plus besoin de cliquer sur chaque lien pour comprendre pourquoi il y a trois identifiants).

Qu'en pensez-vous ?

Cdlt/Cheers, VIGNERON (talk) 08:03, 14 July 2024 (UTC)