Re:Dublin Core's dirty little secret (2010)
by blipmusic on Saturday October 02, 2021 @10:57AM
(#28729053)
Depends on what device generates the image perhaps? DJI Drones have a lot of info as EXIF XMP. I just parse that as XML.
EDIT: It's not 80k, but good enough as a GPS log.
Re:Dublin Core's dirty little secret (2010)
by PaulHoule on Saturday October 02, 2021 @11:51AM
(#28729566)
The gif in the story was generated by adobe tools in the bad old days, circa 2005. I noticed the nerfing happened in the last 5 years when I looked closely at what Lightroom does.
Re:Dublin Core's dirty little secret (2010)
by blipmusic on Saturday October 02, 2021 @12:50PM
(#28730073)
In terms of wasted space, only 1/8th is actual xmp for that DJI exif chunk, the rest is padding for (13mb jpg:s in our case). 8k, so 1k actual xmp data of which a lot is structural. I've only tried with scripts, verifying with exiftool and a hex editor every now and then.
I was amused at how Adobe’s XMP format amended DC used features of RDF that most people were scared to use (ordered collections) to solve the simple problem of keeping track of the order of author’s names on a paper.
The big trouble I see with semweb standards is that they stop long before getting to the goal. RDFS and OWL for instance solve some problems of mashing up data from different vocabs but can’t do the math to convert inches to meters which is absolutely essential.
I was not so amused to see Adobe thoroughly nerfed XMP and it no longer sucks in EXIF metadata from images. I was hoping I could find the XMP packet and put it through an RDF/XML parsers and get all the metadata from my images but even in Lightroom images the XMP packet is a nothingburger these days. I guess people complained about the GIF files that had 2k of pixel data an 80k of XMP and that Adobe was co-opting other standards. Heck they even deleted most of the content from the standard including how to express EXIF in RDF so you can’t stick XMP in your database and SPARQL it.