Property talk:P8402

From Wikidata
Jump to navigation Jump to search

Documentation

open data portal
the item for the open data portal belonging to this entity
[create Create a translatable help page (preferably in English) for this property to be included here]
Value type “database (Q8513), open data portal (Q27031827): This property should use items as value that contain property “instance of (P31)”. On these, the value for instance of (P31) should be an item that uses subclass of (P279) with value database (Q8513), open data portal (Q27031827) (or a subclass thereof). (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/P8402#Value type Q8513, Q27031827, SPARQL
Type “organization (Q43229), voluntary association (Q48204): item must contain property “instance of (P31)” with classes “organization (Q43229), voluntary association (Q48204)” 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). Known exceptions: Sustainable Development Goals (Q7649586)
List of violations of this constraint: Database reports/Constraint violations/P8402#Type Q43229, Q48204, SPARQL
Distinct values: this property likely contains a value that is different from all other items. (Help)
List of violations of this constraint: Database reports/Constraint violations/P8402#Unique value, hourly updated report, SPARQL (every item), SPARQL (by value)
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/P8402#Scope, 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/P8402#Entity types

Why this property?[edit]

My intention when requesting this property is to make the **process faster** when trying to find an Open Data portal for data about an object e.g

- Salgo60 (talk) 05:45, 6 July 2020 (UTC)[reply]

What properties should an open data portal (Q27031827) have ?[edit]

We will learn and hopefully create a ShEx saying what properties we expect or recommends ...

My vision is that we get all providers of Open Data awar of Wikidata and the power of a Knowledge Graph -->

  • they start to describe what metadata they have using "same as" Wikidata objects
  • they start to describe in the data saying this school is "same as" a Wikidata objects and its located in "same as" Wikidata object

Doing that I guess is the only way to scale

-Salgo60 (talk) 05:45, 6 July 2020 (UTC)[reply]

What is the difference between this property and external data available at URL (P1325)[edit]

I don't understand why there is a need for a new property when external data available at URL (P1325) was doing the same stuff. I've been doing lots of work on French public agencies and I've always used P1325. See French Environment and Energy Management Agency (Q2826599) for an example. - - PAC2 (talk) 04:22, 7 July 2020 (UTC)[reply]

@PAC2: I didnt know about external data available at URL (P1325) when we requested open data portal (P8402) but I have seen the work you have done afterwards... should we merge? If yes what name is the best? "Open Data" is a buzzword used a lot - Salgo60 (talk) 11:10, 7 July 2020 (UTC)[reply]
I asked in the Telegram group Wikidata this question and got aware of that we have a big difference that external data available at URL (P1325) is an external url and open data portal (P8402) is to another object... so I think we need both and I also guess open data portal (P8402) is the preferred way to describe external open data in a better way... See how we describe our own Wikidata Graph - Salgo60 (talk) 11:38, 7 July 2020 (UTC)[reply]
Thanks @Salgo60:. Both are useful --PAC2 (talk) 21:29, 9 July 2020 (UTC)[reply]

Official and non official[edit]

A pattern I have seen is that we add if an Open data portal is official i.e. supported by the local government or done by a third party... any suggestions how we do that in the best way? cc: @So9q, Ainali, Abbe98: - Salgo60 (talk) 07:25, 4 August 2021 (UTC)[reply]

Isn't it enough to describe owned by (P127) or operator (P137) for each portal item? The distinction between official and non-official is sometimes difficult, and to compare the subject of this property and operator of the portal helps to understand the situation. There are various properties to describe institutes related to open data portals, and in this context, owned by (P127) or operator (P137) seems good to use. See property frequency ranking of open data portals. If there are examples of non-official portals, we can discuss more based on them. --KAMEDA, Akihiro (talk) 03:11, 4 January 2022 (UTC)[reply]
According to properties for this type (P1963) of open data portal (Q27031827), operator (P137) is preferred. --KAMEDA, Akihiro (talk) 09:18, 4 January 2022 (UTC)[reply]
KAMEDA, Akihiro as Wikidata is world wide I feel its better to be more precise if you have the knowledge and say if its the official or not... e.g. my knowledge of the organisations in Africa is very limited - 79.136.51.53 08:57, 10 June 2022 (UTC)[reply]
I said "The distinction between official and non-official is sometimes difficult" not because I supposed lack of knowledge of editors but because it is difficult to assign values consistently. If we can assign values consistently, I agree with assigning the qualifier has characteristic (P1552) official (Q29509043) or unofficial (Q29509080) (see official website (P856)) to the statement of this property open data portal (P8402). If the subject and operator of the portal are the same administrative entity, that is apparently "official". Even if those are different, the administrative entity may have outsourced the operation of the portal; In that case, the portal tends to be regarded as "official". When someone creates the portal privately and then they invites the mayor of the city to the International Open Data Day and the mayor praises and promised to support the project, the portal can be still "unofficial" but it may depend on the speech content of the mayor. I don't know if this ambiguous distinction (official/unofficial) contributes to improving statements in terms of data quality. If you have appropriate references that can prove the portal is official (or unofficial), assigning has characteristic (P1552) official (Q29509043) or unofficial (Q29509080) with them can be the best way. --KAMEDA, Akihiro (talk) 07:58, 13 June 2022 (UTC)[reply]
KAMEDA, Akihiro I agree but that is life in the semantic world ;-) listen to a key note from Google KG people were he tells the same problem what is a firestation and what is a cinema.... - Salgo60 (talk) 18:42, 21 June 2022 (UTC)[reply]
@Salgo60 Thank you for reminding me of that presentation. I was there in Vienna ;-) (for those interested, there is a related discussion from 18:53 Questions of Identity: Class Membership). Yes, I should be more optimistic about knowledge accumulation as Jamie does. I just thought that properties like owned by (P127) or operator (P137) could directly enrich the related information more objectively, but Official / Non-official distinction (using has characteristic (P1552) or so) can be informative also. --KAMEDA, Akihiro (talk) 18:13, 22 June 2022 (UTC)[reply]