Property talk:P4003

Latest comment: 3 years ago by Verdy p in topic Numeric ID is only real identifier

Documentation

Facebook page ID
official Facebook page of this entity (only for use with URLs containing "/pages/")
Applicable "stated in" valueFacebook (Q355)
Data typeExternal identifier
Corresponding templateTemplate:Facebook page (Q14400757)
Template parameterid in Template:Facebook page (Q14400757)
Domainpeople organisations, venues (note: this should be moved to the property statements)
Allowed values[\p{L}\d]+(?:[-_.][\p{L}\d]+)*/[1-9][0-9]+ (keywords or decimal integers, possibly linked by a dash, underscore or dot, followed by a slash and a decimal integer identifier)
ExampleStatistical Society of Australia (Q19879481)Statistical-Society-of-Australia-Inc/186936994713723
Garden of Remembrance, Norra Begravningsplatsen (Q28006122)Norra-begravningsplatsen/102511286468672
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://www.facebook.com/pages/$1
Tracking: usageCategory:Pages using Wikidata property P4003 (Q35064182)
Related to country United States of America (Q30) (See 762 others)
See alsoFacebook username (P2013), Facebook numeric ID (P11705)
Lists
Proposal discussionProposal discussion
Current uses
Total8,274
Main statement8,09097.8% of uses
Qualifier340.4% of uses
Reference1501.8% of uses
Search for values
[create Create a translatable help page (preferably in English) for this property to be included here]
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).
List of violations of this constraint: Database reports/Constraint violations/P4003#Unique value, SPARQL (every item), SPARQL (by value)
Single value: this property generally contains a single value. (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/P4003#Single value, SPARQL
Format “[\p{L}\d]+(?:[-_.][\p{L}\d]+)*/[1-9][0-9]+: 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/P4003#Format, SPARQL
Item “Facebook username (P2013): Items with this property should also have “Facebook username (P2013)”. (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/P4003#Item P2013, search, 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/P4003#Entity types
Conflicts with “website account on (P553): Facebook (Q355): this property must not be used with the listed properties and values. (Help)
List of violations of this constraint: Database reports/Constraint violations/P4003#Conflicts with P553, hourly updated report, search, SPARQL
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/P4003#Scope, SPARQL
Pattern ^([0-9A-zÀ-ú_\.-]+/\d+)/$ will be automatically replaced to \1.
Testing: TODO list

Discussion edit

Import edit

I shall shortly begin importing values from en.Wikipedia. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 15:20, 1 June 2017 (UTC)Reply

Formatter URL edit

Maybe currently shoud be not a /pages/$1, but /pg/$1 ? --Kaganer (talk) 01:26, 6 June 2018 (UTC)Reply

And also regexp constraint may be more simple. --Kaganer (talk) 01:29, 6 June 2018 (UTC)Reply

@99of9: Sorry, may I know why you changed it again to /pages/$1? --minhhuy (talk) 04:11, 11 November 2018 (UTC)Reply
Facebook page ID (P4003) was designed for use IDs starting with facebook.com/pages/ (see the property proposal discussion) and those links do not work with facebook.com/pg/:
Links that work with /pg/ should also work without it and therefore could be added using Facebook username (P2013) instead:
-- Zyxw (talk) 22:24, 26 January 2019 (UTC)Reply

Not official edit

What exactly is the purpose of this property? I don’t know if something has changed within Facebook, but these so called ”pages” under https://www.facebook.com/pages/ are not official Facebook pages of people, organizations, venues, etc. On the contrary, they’re ”unofficial pages created by Facebook due to people expressing interest in the place or organization”, or something like that. Quite often I see this property being used when Facebook username (P2013) should be used. This is also evident by the constraint violations of this property. –Kooma (talk) 12:53, 17 July 2018 (UTC)Reply

Edits of BlueFire10 edit

@BlueFire10: This property was clearly designed for use IDs starting with facebook.com/pages (see the property proposal discussion), please stop doing that. Kirilloparma (talk) 14:29, 14 April 2020 (UTC)Reply

Why does this property exist, if the property Property:P2013 already exists? What should be the difference? Isn't it to distinguish between profiles of less known people and the official pages of prominent people etc., which you can also follow and like? BlueFire10 (talk) 14:39, 14 April 2020 (UTC)Reply
Also in the example mentioned (Q19879481) there is no /pages on the Facebook page (after redirection). Is it possible that Facebook has changed something there? BlueFire10 (talk) 14:55, 14 April 2020 (UTC)Reply

Numeric ID is only real identifier edit

The expected/required format for this property's value consists of two parts: a text string and a numeric page ID (e.g. Statistical-Society-of-Australia-Inc/186936994713723). This value is then formatted as https://facebook.com/pages/$1.

However, it turns out only the page ID (the second part) is relevant, and the first part is not checked by Facebook and can actually be anything. As an example, all three following links go to the same page:

This property therefore doesn't add much else than the page ID, and would therefore preferably either be replaced by or morph into a strictly numeric page ID property, somewhat like X user numeric ID (P6552). We should also see how this property should relate to Facebook username (P2013). The proposed numeric ID property also sounds interesting in this regard. Victor LP (talk) 18:41, 6 September 2020 (UTC)Reply

The numeric ID is no longer displayed by Facebook for many pages, that are now only known by their keyword identifier. Any extensions after the slash are now ignored. Otherwise, this is only a decimal numeric id (also without any extension (there can be only query parameters for subpages, and tools attached to that page which will use their own keywords for the Facebook API such as "/photo/").
Note that this property applies only to pages (what can follow "https://www.facebook.com/page/"), but could as well apply to groups (what can follow "https://www.facebook.com/group/"), or topics (what can follow "https://www.facebook.com/page/".
Pages may also exist with their primary keyword (the "pages/" prefix), but not all these keywords are accepted. You can eventually know the numeric ID by looking at photos or some contents attached to the main profile page: the query string will contain a parameter "?fbid=someinteger". In some cases, the keyword for the page or group profile may not exist or could have been suppressed (e.g. if the name was claimed by someone else, and the account was still not suppressed, Facebook then asking to the account owner to give a new name, even if the ID is preserved). This means that account keywords (made of letters/digits separated by dots/hyphens/underscores) may not be permanent (and a user may want to have it changed, while keeping the content and the existing numeric ID).
Many groups however don't have a keyword assigned: you locate them by the Facebook search engine, by their display label (which is not an identifier as it may have may homonymies and are much less restricted in terms of orthography): the actual keyword created by facebook for them would be a simplified form of the account name, possibly followed by a dot and some random integer.
Finally members of a group may be only referenced by their user id within that group (it is possible to join a group without linking the membership to the personal page: the numeric user id in that group is appended after "/group/(groupid)/user/"), and it is only possible to interact with that user using this id (and members may change their named identity when becoming members, or may change their photo, so that their own personal account is not publicly affected by what they do in the group: only the group owner may know the real identity if the group was a "closed group" where permission is required to join).
So how to use the Facebook URLs? Facebook does not warranty it, unless we use their documented API. I'm not even sure that we can really host such info in Wikidata, unless these are for official pages of organizations and grands, whose ID (really a keyword) is reserved (and their identity reviewed and asserted by facebook and not concerned by individual privacy issues). Verdy p (talk) 14:36, 10 November 2020 (UTC)Reply
Return to "P4003" page.