Property talk:P5817

From Wikidata
Jump to navigation Jump to search

Documentation

state of use
to indicate state of use of a building, monument, etc. It is not related with its heritage protection (P1435), but to its present state of use. Ex.: abandoned, in use, temporarily closed, etc.
Representsuse status (Q56557118)
Data typeItem
Domaingeographical feature (Q618123), product model (Q10929058), vehicle (Q42889), structure (Q6671777), transport network (Q924286), public service (Q161837), service (Q7406919) or facility (Q13226383)
Allowed values
Usage notesNe pas confondre avec P5816 (conservation)
ExampleParthenon (Q10288)open to the public (Q55570821)
London Eye (Q160659)in use (Q55654238)
El Hierro Launch Centre (Q67130279)proposed building or structure (Q811683)
Museu Paulista (Q371803)temporarily closed (Q55653430)
Polissya hotel (Q4549571)abandoned (Q63065035)
Down Street tube station (Q450893)out of service (Q56651571)
Tracking: usageCategory:Pages using P5817 (Q108853222)
See alsostate of conservation (P5816)
Lists
Proposal discussionProposal discussion
Current uses
Total133,463
Main statement131,63398.6% of uses
Qualifier1,8281.4% of uses
Reference2<0.1% of uses
Search for values
[create Create a translatable help page (preferably in English) for this property to be included here]
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/P5817#Type Q618123, Q10929058, Q42889, Q6671777, Q924286, Q161837, Q7406919, Q13226383, SPARQL
Value type “use status (Q56557118): This property should use items as value that contain property “instance of (P31), subclass of (P279)”. On these, the value for instance of (P31), subclass of (P279) should be an item that uses subclass of (P279) with value use status (Q56557118) (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/P5817#Value type Q56557118, SPARQL
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/P5817#Single value, SPARQL
Scope is as main value (Q54828448), as qualifier (Q54828449): 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/P5817#Scope, SPARQL
Allowed entity types are Wikibase item (Q29934200), 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/P5817#Entity types
Single best value: this property generally contains a single value. If there are several, one would have preferred rank (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/P5817#single best value, SPARQL

Please notify projects that use this property before big changes (renaming, deletion, merge with another property, etc.)

Specify range of use of the property[edit]

@ديفيد عادل وهبة خليل 2, FranSisPac, ChristianSW, Jklamo, Medol, Barcelona: @Thierry Caro, Amadalvarez, Germartin1, Tinker Bell, Voll, Strakhov: @PKM, JerryL2017, Pere prlpz, Pintoch, Pigsonthewing, Yeza: @Anvilaquarius, AndreasPraefcke, Ayack: Dear participants in the discussion about the creation of the property and @Vojtěch Dostál: (who mostly used this property at the moment), I'm here with @Alexmar983: and we are trying to assess its possible use in some additional cases. This is very important on the long term if more specific properties need to be created. So far this property has been used with institutions that are intrinsically related to physical buildings (e.g. churches or museums), but which is the correct use of this property if we need to apply to specific portions or sectors or properties of instutions? E.g. you can use this property to specify if a library is open to the public, but what about a specific archive or collection of the same library? The core aspect is not the use, but the access: shouldn't we have a specific property related to access or is this property good with additional qualifiers as well? Should we maybe suggest more values for this property (e.g. "accessible on request" or "accessible on specific time slots")? What do you think? Thank you very much, --Epìdosis 14:30, 6 December 2019 (UTC)[reply]

I would add qualifiers if needed or combined with other items or properties. For example, related to archive, we may think in the building of the archive, the different sections of documents and so on, all of them with differences in access, as you say. Barcelona (talk) 14:40, 6 December 2019 (UTC)[reply]
@Epìdosis: If I understand what you are saying, they are two different topics: a) the range of values ​​we can have; b) the object to which it applies.
Regarding topic a): When we created this property, we predicted the expansion of newly-adjusted values ​​that were a subclass of use status (Q56557118) instead of creating a closed list, to be able to expand its scope, in a simple way. That is, add your examples: "accessible on request" or "accessible on specific time slots", it does not seem a problem if these items are declared as a subclass of use status (Q56557118).
Regarding topic b): the values ​​of the properties refer always to the item where properties are. To assign properties (this or any other), to a archive or collection of a library (following your example), I think it would be necessary to define it as an item. These items of the collections, if you like, can be defined as part of the library. In the WD ontology the qualifiers are "properties that characterize or describe the relation between a value with the item", but they should not be characteristic of the value itself, when it is an item. I hope to be answered to your questions. Amadalvarez (talk) 16:33, 6 December 2019 (UTC)[reply]

Accessible only to[edit]

See Property talk:P1535#Eventual new property. --Epìdosis 15:20, 6 December 2019 (UTC)[reply]

All possible values[edit]

While the property page gives a few examples ("reformed, in use, temporarily closed, etc"), I wanted a more complete list of values, so I wrote this query:

SELECT ?item ?itemLabel WHERE {
  ?item wdt:P279 wd:Q56557118.
  SERVICE wikibase:label { bd:serviceParam wikibase:language "[AUTO_LANGUAGE],en". }
}
Try it!

It currently returns 12 results: proposed building or structure, building under construction, cancelled, closed to the public, open to the public, temporarily closed, in use, out of service, decommissioned, structure under construction, abandoned, structure under reconstruction

Any feedback is welcome! Thanks :-) Syced (talk) 12:17, 16 February 2020 (UTC)[reply]

Parthenon example wrong[edit]

The docs for "open to the public" say that it should only be used when the subject is not already owned by the public, but is e.g. a private residence. I would imagine that the Parthenon isn't privately owned. So the example is wrong? --Ysangkok (talk) 16:03, 14 October 2020 (UTC)[reply]

Wikidata usage instructions (P2559) "Ne pas confondre avec …"[edit]

@Bouzinac: Shouldn't the value of Wikidata usage instructions (P2559) at Property:P5817#P2559: "Ne pas confondre avec P5818 (conservation)" refer to state of conservation (P5816) instead of BGCI garden ID (P5818)? Best, --Marsupium (talk) 10:46, 14 April 2023 (UTC)[reply]

Typo corrected, thx Bouzinac💬✒️💛 11:07, 14 April 2023 (UTC)[reply]