Wikidata:Property proposal/image or photo-making technique

From Wikidata
Jump to navigation Jump to search

file-making technique[edit]

Originally proposed at Wikidata:Property proposal/Commons

   Withdrawn
Descriptionthe specific technique that was used to create or generate the file
Data typeItem
DomainFiles that have been created with a specific technique such as long-exposure photography (Q1082855), microscopy (Q1074953) or many others. Note it should be reasonable to set a type constraint "instance or subclass of" technique (Q2695280)
Example 1File:Bombus lapidarius queen - Echium vulgare - Keila.jpgmacro photography (Q272444)
Example 2File:Golden Gate Park San Francisco December 2016 006.jpglong-exposure photography (Q1082855)
Example 3File:Heterocentrotus mamillatus MHNT.jpgfocus stacking (Q1435078)
Example 4File:Müürlooga (Arabidopsis thaliana) lehekarv (trihhoom) 311 0804.JPGmicroscopy (Q1074953)

Motivation[edit]

With the gradual establishment of the Structured Data in Commons, it would be good to have such a property that will allow to make an infinity of interesting queries. Christian Ferrer (talk) 18:10, 11 August 2019 (UTC)[reply]

Discussion[edit]

OK for the label "image-making technique", I did not think about fabrication method (P2079), though maybe a bit too generic. See what others think. Christian Ferrer (talk) 05:05, 12 August 2019 (UTC)[reply]
But why to limit it just for images. The other files may also have techniques. E.g. audio file might be a recording, computer created sound, etc. Juandev (talk) 20:13, 29 September 2019 (UTC)[reply]
  •  Weak support, this would also be useful in the GLAM context, specifying which digitization method was used. I would also think, SDOC aside, we could use this in Wikidata as a qualifier on properties such as image (P18). But, while I agree fabrication method (P2079) is too generic, this is a bit too specific, since Commons files can be many multimedia types (video, audio, etc.), not just "image". I think we should broaden this scope to be applicable to any file appropriate to Commons, since it wouldn't make sense to create additional properties for them. Dominic (talk) 15:07, 4 September 2019 (UTC)[reply]
Thanks you, it makes sense, I changed the name to "file-making technique". Christian Ferrer (talk) 17:07, 4 September 2019 (UTC)[reply]
So this property would apply to the digital file, not to the original physical object (if any)? Ghouston (talk) 03:46, 5 September 2019 (UTC)[reply]
I was thinking of proposing an "equipment" property at some point, which would potentially overlap with this usage. The equipment value would be an item like Canon EOS 300D (Q64039) or a scanner model. Ghouston (talk) 03:49, 5 September 2019 (UTC)[reply]
I think this property can be used to describe both the digital file and the physical object, with sevaral values possible. Technique and equipment are not the same, e.g. with Canon EOS 300D (Q64039) you can do 3 of the 4 examples I gave at top. Christian Ferrer (talk) 04:34, 5 September 2019 (UTC)[reply]
"File-making technique" seems like a strange way to describe e.g., an image capture on photographic film, since no file was involved until a separate digitization process. The techniques and equipment are linked, but whether one should be a qualifier of the other I'm not sure. Ghouston (talk) 04:54, 5 September 2019 (UTC)[reply]
So maybe it should be "file and image-making technique"? or more simply "media-making technique"? Christian Ferrer (talk) 11:02, 5 September 2019 (UTC)[reply]
Or fabrication method (P2079), which can apply to anything. Would we lose anything by using that? Ghouston (talk) 23:01, 5 September 2019 (UTC)[reply]
No, indeed. I guess we can use fabrication method (P2079). Christian Ferrer (talk) 11:14, 6 September 2019 (UTC)[reply]
We seem to be running into the same problem at multiple place, please have a look at Commons:Commons_talk:Structured_data/Modeling#Original_work_and_digital_representation. I think if we solve that, we can just use fabrication method (P2079) (with sometimes the appropriate qualifier). Probably best to keep this one open until the other discussion is finished. So this  Oppose is just to prevent that from happening. Multichill (talk) 10:04, 5 October 2019 (UTC)[reply]