Talk:Q131734

From Wikidata
Jump to navigation Jump to search

Autodescription — brewery (Q131734)

description: business that makes and sells beer
Useful links:
Classification of the class brewery (Q131734)  View with Reasonator View with SQID
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)
brewery⟩ on wikidata tree visualisation (external tool)(depth=1)
Generic queries for classes
See also


Business enterprise and architectural structure[edit]

The combination of both is troublesome, they both use a different set of properties on items causing weird situations for constraints. I think we need to split up the two concepts. Sjoerd de Bruin (talk) 20:45, 7 October 2017 (UTC)[reply]

I agree. Often a brewing company owns more than one brewery. We see the same issue in other cases, too (museum/building; library/bulinding, etc). Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 21:29, 7 October 2017 (UTC)[reply]
Agreed, but do we need a specific "brewery item" for the enterprise? Aren't they almost always a instance of a legal body of some general sort like joint-stock company (Q134161)? Ainali (talk) 16:28, 8 October 2017 (UTC)[reply]
We could also model the companies with instance of (P31)business (Q4830453) and industry (P452)brewing (Q869095), indeed. Sjoerd de Bruin (talk) 17:14, 8 October 2017 (UTC)[reply]
That works for me. How do we then associate the company with the building (as it may not be the company's "headquarters")? Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 19:27, 8 October 2017 (UTC)[reply]
I can find occupant (P466) to use on the building itself, but not really a clear inverse. Sjoerd de Bruin (talk) 19:31, 8 October 2017 (UTC)[reply]
Hi @Sjoerddebruin, Pigsonthewing:, did you already split the two meanings? I think we really need that --Vojtěch Dostál (talk) 09:11, 3 January 2018 (UTC)[reply]
Done --Vojtěch Dostál (talk) 08:13, 28 October 2018 (UTC)[reply]