Talk:Q96196009
Jump to navigation
Jump to search
Autodescription — former or current state (Q96196009)
description: political state, whether former or current
- Useful links:
- View it! – Images depicting the item on Commons
- Report on constraint conformation of “former or current state” claims and statements. Constraints report for items data
For help about classification, see Wikidata:Classification.
- Parent classes (classes of items which contain this one item)
- Subclasses (classes which contain special kinds of items of this class)
- ⟨
former or current state
⟩ on wikidata tree visualisation (external tool)(depth=1) - Generic queries for classes
Union and disjoint queries
- Instances of former or current state (Q96196009) that are instances of none of the classes historical country (Q3024240) and state (Q7275) [1]
- See also
- This documentation is generated using
{{Item documentation}}
.
Purpose or duplicate?[edit]
@TomT0m: what's the purpose of creating this? Actually state (Q7275) already comprises modern and historical states (just use appropriate qualifiers and ranks). Moreover historical country (Q3024240) can actually be avoided with the same technics. --Infovarius (talk) 20:26, 11 June 2020 (UTC)
- @Infovarius: I’d try to avoid putting "without an end date" / "item without a destruction date" / whatever the right exclusion way is … to avoid getting historical items in regular queries. Because this is actually a very very common usecase in query to want only the current items and not historical one. Plus this can be a performance issue to exclude stuffs. My opinion is that query should by default get current items and that former one should be by design excluded for common queries, and that query for historical one should be specifically designed to get them. Not the other way around (simple query get history and we have to design the query to exclude them) author TomT0m / talk page 20:38, 11 June 2020 (UTC)
- I believe that a query give by default current items even for state (Q7275) because for historical states there should be a class "historical state" with preferred rank and it should filter out such results. Hence - no need in a new item. --Infovarius (talk) 23:10, 13 June 2020 (UTC)
- @Infovarius: There is already such an item. This one is not indeed needed to filter out historical states, it however is useful to query both historical and current with its subclass ( P31/P279* Q96196009
- Currently we have something like « historical state » subclass of « state » which is a pattern that cannot work if you want only current items while you also have to query for subclasses for an item. Say you want to query the administrative divisions of the country, whatever their types, if you have something like « former administrative division » subclass of « administrative division » you’ll have to filter out all instances of « former administrative division ». For not to have this, you have to get a parent item for both former and actual. author TomT0m / talk page 18:25, 14 June 2020 (UTC)
- I believe that a query give by default current items even for state (Q7275) because for historical states there should be a class "historical state" with preferred rank and it should filter out such results. Hence - no need in a new item. --Infovarius (talk) 23:10, 13 June 2020 (UTC)