Property talk:P8253

From Wikidata
Jump to navigation Jump to search

Documentation

OSM Name Suggestion Index ID
identifier for a brand in OpenStreetMap’s Name Suggestion Index
Applicable "stated in" valueName Suggestion Index (Q62108705)
Data typeExternal identifier
Domaintrademark (Q167270), organization (Q43229), public transport (Q178512), flag (Q14660) or brand (Q431289)
Allowed values^\w+-[0-9a-f]{6}$
ExampleMcDonald’s (Q38076)mcdonalds-658eea
Shell (Q154950)shell-b3d110
shell-4d6b4b
shell-56d9b3
United States Postal Service (Q668687)unitedstatespostoffice-b9aa24
ABQ RIDE (Q580832)abqride-a45453
Sourcehttps://nsi.guide/index.html
Formatter URLhttps://nsi.guide/?id=$1
See alsoOpenStreetMap tag or key (P1282), OpenStreetMap relation ID (P402), ‎location information URL (P12454), number of branches (P8368), location URL match pattern (P11707)
Lists
Proposal discussionProposal discussion
Current uses
Total27,105
Main statement27,098 out of 36,576 (74% complete)>99.9% of uses
Qualifier6<0.1% of uses
Reference1<0.1% of uses
Search for values
[create Create a translatable help page (preferably in English) for this property to be included here]
Format “^\w+-[0-9a-f]{6}$: value must be formatted using this pattern (PCRE syntax). (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/P8253#Format, SPARQL
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/P8253#Entity types
Scope is as main value (Q54828448): 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/P8253#Scope, SPARQL
Item “‎location information URL (P12454): Items with this property should also have “‎location information URL (P12454)”. (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/P8253#Item P12454, SPARQL
Item “official website (P856): Items with this property should also have “official website (P856)”. (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/P8253#Item P856, SPARQL
Item “operating area (P2541): Items with this property should also have “operating area (P2541)”. (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/P8253#Item P2541, search, SPARQL

Discussion[edit]

Why does this property imply notability?[edit]

Tinker Bell added Wikidata property for an identifier that suggests notability (Q62589316) to this property. Accordingly Bovlb undeleted several items per this request. As this seems to be user-generated content by another project, I don’t really see why this property should confer notability within Wikidata. --Emu (talk) 09:01, 15 August 2022 (UTC)[reply]

It's a special case. The presence of this property on an item page signals structural need in the OpenStreetMap project. We thus usually keep these items, although quite some of them would otherwise be deleted here. —MisterSynergy (talk) 10:23, 15 August 2022 (UTC)[reply]
Okay, but how do OSM structural needs factor into Wikidata notability? Isn’t that essentially a loophole to create notability? --Emu (talk) 10:39, 15 August 2022 (UTC)[reply]
There are already so many loopholes… OSM has pretty much the same ethos as Wikidata/Wikimedia does, so I think it is fine. There are people that look after these items, and they are usually independent of the described entities. The property was created after OSM users repeatedly found their used items deleted (usage was difficult to track before this property existed). You can read in the proposal that there was quite some support for this property. —MisterSynergy (talk) 11:09, 15 August 2022 (UTC)[reply]
I see your point that OSM is a friendly, mostly high-quality project.
However, the property proposal explicitly states: “I don't think the presence of this property on an item would establish notability by itself, given that OSM isn't considered an authority on store locations. But it could give administrators a little more clarity when assessing whether a business-related item is merely undeveloped or whether it's spam.” And there were four deleting admins, so it’s not even that clear that this is an established practice. --Emu (talk) 17:35, 15 August 2022 (UTC)[reply]
@Emu: I probably could've phrased that better. I do think inclusion in name-suggestion-index establishes notability – the index's purpose is to standardize tagging of individual branch locations for chains of a certain size or larger. What I meant is that NSI isn't an authority on the subject. NSI uses (user-contributed) OSM data to discover missing chains to add, but there is editorial control in the sense that contributors debate whether a chain is of sufficient notability. Something like [1] probably wouldn't be added even if it satisfies Wikidata's structural need criterion for notability. Minh Nguyễn 💬 23:20, 9 November 2022 (UTC)[reply]

number of identifiers[edit]

Since NSI.guide doesn't show how many items are in brands category, this JS snippet can return quickly the number:

Array.from(document.getElementsByClassName("category")).map(v => parseInt(v.children[1].textContent.split("/")[2].slice(0,-1))).reduce((a,p) => a+p, 0);

--Tinker Bell 16:13, 15 August 2022 (UTC)[reply]