Documentation

equivalent property
equivalent property in other ontologies (use in statements on properties, use property URI)
DescriptionEquivalent property in other ontologies.
Data typeURL
Domain
According to statements in the property:
Wikidata property (Q18616576)
When possible, data should only be stored as statements
Allowed values
According to this template: URIs with semantics matching that of owl:equivalentProperty .
According to statements in the property:
https?://\S+
When possible, data should only be stored as statements
Example
According to statements in the property:
country (P17) → http://www.w3.org/2006/vcard/ns#country-name
http://schema.org/addressCountry
instance of (P31) → http://www.w3.org/1999/02/22-rdf-syntax-ns#type
place of birth (P19) → https://schema.org/birthPlace
When possible, data should only be stored as statements
See alsoexternal subproperty (P2236), equivalent class (P1709), external superproperty (P2235)
Lists
Proposal discussionProposal discussion
Current uses
Total745
Main statement73999.2% of uses
Qualifier40.5% of uses
Reference20.3% of uses
Search for values
[create Create a translatable help page (preferably in English) for this property to be included here]
Type “Wikidata property (Q18616576): item must contain property “instance of (P31)” with classes “Wikidata property (Q18616576)” 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/P1628#Type Q18616576, SPARQL
Item “Wikidata item of this property (P1629): Items with this property should also have “Wikidata item of this property (P1629)”. (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/P1628#Item P1629, SPARQL
Format “https?://\S{3,10000}: value must be formatted using this pattern (PCRE syntax). (Help)
List of violations of this constraint: Database reports/Constraint violations/P1628#Format, hourly updated report, SPARQL
Scope is as main value (Q54828448): the property must be used by specified way only (Help)
List of violations of this constraint: Database reports/Constraint violations/P1628#Scope, 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).
List of violations of this constraint: Database reports/Constraint violations/P1628#Unique value, SPARQL (every item), SPARQL (by value)
Allowed entity types are Wikibase property (Q29934218): 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/P1628#Entity types

Link to properties URIs edit

I believe that we should, as in the property proposal, set as value the URI of the equivalent property and not an URI of its description. I've already updated the few occurrences of this property like in this diff. Tpt (talk) 07:08, 4 December 2014 (UTC)Reply

Absolutelyǃ The "namespace" URLs (also called semantic URLs, Class/Property URLs) have very special status since RDF statements are made against them. You're not just pointing to a description, but saying "this thing (URL1) has equivalent semantics to that other thing (URL2)", and therefore must be precise about URL2. Use the true namespace of the target ontology.

@Jura1:: Please fix https://www.wikidata.org/wiki/Property:P21#P1628 to http://xmlns.com/foaf/0.1/gender (for some reason I don't have edit rights)

--Vladimir Alexiev (talk) 07:19, 12 February 2015 (UTC)Reply

I don't quite understand the edit on P21. Now it points nowhere. ----- Jura 09:35, 21 February 2015 (UTC)Reply
These URIs are done to return machine readable descriptions of the properties (usually in RDF) often, with a more or less good fallback to HTML description for humans. If you want to know more about it (and the linked data world), there is a very nice book that introduces it). Tpt (talk) 10:25, 24 February 2015 (UTC)Reply
Actually, there's no requirement that RDF property URIs (or [XML] namespace URIs) point to anything; they're nothing but names for concepts, and any description you may find by dereferencing such URIs are just a bonus, spec-wise. —SamB (talk) 04:41, 10 April 2015 (UTC)Reply

Properties with an URL edit

I suspect that most of the properties with P1630 should also have P1628 set, but most don't. --Nemo 09:19, 4 April 2015 (UTC)Reply

Mapping with OpenStreetMap edit

Hi @Thadguidry, Federico Leva (BEIC), Pigsonthewing, Gstupp, Tpt: (5 top users of this property),

Is this Special:Diff/564465420 the correct to use this property? (on the formatting and the URL to use on the OSM side ; for the background, I know it's the same concept and values).

Cdlt, VIGNERON (talk) 18:00, 23 September 2017 (UTC)Reply

No, that's what OpenStreetMap tag or key (P1282) is for. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 20:23, 24 September 2017 (UTC)Reply

Semantics - when should this be used? edit

I don't understand the semantics of this property. It uses itself to define itself as being an equivalentProperty to owl:equivalentProperty (ie "P1628 P1628 owl:equivalentProperty ."), but this is circular. If it is truly equivalent (i.e. "P1628 owl:equivalentProperty owl:equivalentProperty .") then the current triple "P1628 P1628 skos:exactMatch ." is wrong (since this would entail that skos:exactMatch has domain/range being property). There was some discussion of this in https://www.wikidata.org/wiki/Wikidata:Property_proposal/Archive/27#P1628 but I don't see the resolution being documented as triples about P1628. Based on current usage I am assuming that the intended semantics are actually more like "matches" than logical equivalence. Cmungall (talk) 19:22, 31 March 2018 (UTC)Reply

Question: Why is this not also an instance of "Wikidata property for ontology mapping" ? edit

Why the "meta" in "Wikidata metaproperty for ontology mapping"? Any reason why it could not also be an instance of Wikidata property for ontology mapping (Q30249126) ? Thadguidry (talk) 14:19, 6 April 2018 (UTC)Reply

BUMP: I have not received a response to this question and thus looking forward to one. --Thadguidry (talk) 14:40, 21 May 2022 (UTC)Reply

query for http or https edit

this is really annoying. Rotten Tomatoes (Q105584) consistently uses http over https. is there a way not to query properties without having to query for both protocols?

{
  ?item wdt:P1628 <${ namespace.replace(/^https\:/, 'http:') }/${ prop }>.
} UNION {
  ?item wdt:P1628 <${ namespace.replace(/^http\:/, 'https:') }/${ prop }>.
}

--Shisma (talk) 07:07, 4 July 2021 (UTC)Reply

Opengraph edit

I noticed the schema URL for P1476 for opengraph maybe wrong as it currently goes to http://ogp.me/ns#title which gives a error rather than XML

What should the URL's for opengraph namespaces be (such as title in this example) Back ache (talk) 08:32, 22 September 2021 (UTC)Reply

Return to "P1628" page.