Wikidata:Property proposal/Zoning symbol - Wikidata


Article Images

Zoning classification

edit

zoning classification (item)

edit

Originally proposed at Wikidata:Property proposal/Place

Descriptionplaning zone of the municipality/region/state that applies to the subject
Representszoning (Q702232)
Data typeItem
Domainbuildings, areas, etc.
Allowed valuesitem for a specific zone where the subject is located
Example 1MISSING
Example 2MISSING
Example 3MISSING
Planned useeventually add to item that have the string version
Expected completenessalways incomplete (Q21873886)

zoning classification (abbreviation)

edit

Originally proposed at Wikidata:Property proposal/Authority control

To be able to identify the reason for the protection of buildings and areas.

The proposal includes an item-based and a string-based property for the classification.

  1. String – The definitions for a given symbol vary between municipalities (in Finland), and the only way to record this information is via a string property rather than designated items, as they are in flux. The recorded zoning symbol will later assist in recording the classification item. The symbol can be used as a qualifier, a direct property on the item, or a property on the classification item, or a qualifier for the statement using the item property.
  2. Item – ready for use in many jurisdictions. Susanna Ånäs (Susannaanas) (talk) 10:35, 2 July 2020 (UTC)[reply]
  Weak support Personally I like the idea with the "item" better because there is meaning to the symbol but I am fine with the abbreviation as well. Since I am not an expert on Finnland, I assume the use case is there even though I think it will lead to issues to use strings and abbreviations instead of logical items that correspond to different levels of protection. I think we can store these abbreviations but they will not be very meaningful for most users of the database. On the other hand, for example in Germany/Switzerland there would only be a few zones (agriculture/business/residential/mixed) which can be represented by a Q-item for each country and then connected logically, which also make sense to store in the database and I think the second proposal makes a lot of sense there. --Hannes Röst (talk) 14:03, 12 August 2020 (UTC)[reply]
  • I had to proceed with the import, here's how I modeled it in the absence of the property. The property will remain useful, and now we have more time to think it through thoroughly.

Susanna Ånäs (Susannaanas) (talk) 17:53, 16 August 2020 (UTC)[reply]

I actually like this solution better than introducing a property temporarily for something that we know we want to delete again in the future. --Hannes Röst (talk) 20:39, 16 August 2020 (UTC)[reply]