Wikidata:Property proposal/foundry
type foundry edit
Originally proposed at Wikidata:Property proposal/Creative work
| Description | type foundry releasing or distributing a font or typeface |
|---|---|
| Represents | type foundry (Q377688) |
| Data type | Item |
| Template parameter | "foundry" in en:template:Infobox font |
| Domain | typeface (Q17451) |
| Example | Mistral (Q1939311) → Fonderie Olive (Q3075745) |
| Planned use | Link typefaces to their foundries |
- Motivation
Each typeface (Q17451) is created by a type designer (Q354034) and usually released and distributed by a type foundry (Q377688). This property will map to the "foundry" parameter in en:template:Infobox font used by hundreds of articles on fonts. DarTar (talk) 03:58, 19 November 2017 (UTC)
- Discussion
Support John Samuel 22:34, 19 November 2017 (UTC)
Comment This seems a rather specialized piece of terminology, do we really need it? There are less than 100 type foundries in wikidata (how many are there in the real world?) Would owned by (P127), creator (P170) or publisher (P123) or something related not cover this use case? ArthurPSmith (talk) 01:14, 20 November 2017 (UTC)- @DarTar: Can you explain how a type foundary differs from a publisher? ChristianKl (✉) 13:36, 24 November 2017 (UTC)
- @ChristianKl, ArthurPSmith: Excellent questions. You're 100% right that we could use publisher (P123) for digital foundries, i.e. organizations that release fonts in a digital form. Applying publisher (P123) to traditional foundries (e.g. producing metal typefaces) is a bit of a stretch, because they are more manufacturers than publishers. Using separate properties for distinct types of foundries, depending on whether they produce digital or physical typefaces, would make it hard to have a consistent data model for typefaces, but I am open to any suggestion if you feel there's a way of doing this consistently with an existing property.--DarTar (talk) 00:03, 25 November 2017 (UTC)
