Talk:Q2195
Jump to navigation
Jump to search
Autodescription — JPEG (Q2195)
description: conflation of multiple topics including compression algorithms, various file formats, standards/technical specifications and a non-profit organisation
- Useful links:
- View it! – Images depicting the item on Commons
- Report on constraint conformation of “JPEG” claims and statements. Constraints report for items data
- See also
- This documentation is generated using
{{Item documentation}}.
 | Please consider using the actual item (likely one of which the intended subject of deprecated statement (P8327) is pointed to) instead of this item, in statements you're adding to reflect the correct concept, also please do not insert {{Item documentation}} on this talk page as this template isn't really suitable, and designed for this purpose, we do apologizes if resulted matters to your works. |
Change of meaning[edit]
@Dhx1: looks like you radically changed the meaning of this item. This does cause more than ten thousand constraint violations so I added the file format (Q235557) back for the moment. What item should I use now with file format (P2701) to indicate JPG files? Multichill (talk) 20:43, 5 April 2019 (UTC)
- @Multichill: I've added back the various instance of (P31) items and marked them as deprecated with some usage instructions on what items to use instead. Most links to JPEG (Q2195) are via file format (P2701) where the person using JPEG (Q2195) has intended to refer to the item described at JPEG (Q27996264) (generic item for any JPEG-like format typically having file extension .jpg or .jpeg). I suggest that a bot could update file format (P2701) links to JPEG (Q2195) fairly easily. A better approach in the future would be for a bot to download the image, check the file format and provide a more specific answer such as Exif image file, version 2.31 (Q26383046) or JPEG File Interchange Format, version 1.02 (Q1676669). Dhx1 (talk) 18:48, 10 April 2019 (UTC)
- @Multichill: Also see Help:Conflation of two persons for related guidance I have followed for setting JPEG (Q2195) instance of (P31) conflation (Q14946528). Dhx1 (talk) 19:01, 10 April 2019 (UTC)
- @Dhx1: I assume you meant JPEG (Q27996264) for the change of file format (P2701). That will throw a constraint violation because JPEG (Q27996264) is not a file format (Q235557). See for example River Landscape (Q11866824). Multichill (talk) 09:00, 11 April 2019 (UTC)
- @Multichill: relation (P2309) on the value-type constraint (Q21510865) of file format (P2701) could be relaxed to instance or subclass of (Q30208840) but I would argue that if one doesn't know the file format accurately, perhaps file format (P2701) is not the most appropriate qualifier to use. If someone is only guessing file format (P2701) based on file extension, then wouldn't it better to use file extension (P1195) instead of broadly guessing file format (P2701)? Dhx1 (talk) 12:55, 11 April 2019 (UTC)
- I updated the constraint. Let's see if anyone complains. Multichill (talk) 15:42, 11 April 2019 (UTC)
- @Multichill: relation (P2309) on the value-type constraint (Q21510865) of file format (P2701) could be relaxed to instance or subclass of (Q30208840) but I would argue that if one doesn't know the file format accurately, perhaps file format (P2701) is not the most appropriate qualifier to use. If someone is only guessing file format (P2701) based on file extension, then wouldn't it better to use file extension (P1195) instead of broadly guessing file format (P2701)? Dhx1 (talk) 12:55, 11 April 2019 (UTC)
- @Dhx1: I assume you meant JPEG (Q27996264) for the change of file format (P2701). That will throw a constraint violation because JPEG (Q27996264) is not a file format (Q235557). See for example River Landscape (Q11866824). Multichill (talk) 09:00, 11 April 2019 (UTC)